Ashley's Forum Posts

  • Actually, I guess now there are so many more suggestions, increasing the max vote count makes sense. I've been thinking about bumping it up from 10 to 25, so maybe now's a good time to do that.

  • No, it's not in permanent beta. There are periodic stable releases.

  • People can adjust their votes at any time. And if we just go back to random passer-by comments on the forum for feature suggestions, I think that would be a step back.

  • The best thing to do is post a suggestion to the features platform which is as small and concise as possible, and see if it collects votes. The point is to focus on the features that lots of people want, rather than just one or two.

  • Since this seems to have tripped up more than one person, I added a check on export for the next release that makes sure Instant Games exports have the Instant Games object added.

    • Post link icon

    This post is 3 years old - since then, Construct 3 got the Game Recorder object, which provides built-in support for screen recording with no watermark.

    Edit: thread locked as it has become a spam magnet. See the Screen recording example in Construct for a demonstration of how to use the new built-in screen recording feature.

  • Ashley I'm not asking for a personal favor here, this is something many people will benefit from...

    I know, but you could say exactly the same about the close-to-600 other suggestions filed on the suggestions platform. That represents years and years of work, and suggestions are being filed faster than we could possibly implement them, so many ideas will probably never be done. So the question every suggestion has to answer is: why is this more important than all the other possible ideas we could work on? And what is the smallest, quickest and easiest way it could be done?

    Could you tell which of these changes are possible to make, and which are not possible or too difficult?

    I can only make educated guesses, since to know for sure would mean actually doing it and seeing how long it took, but based on speculation I'd say:

    1. Allow rotation: extremely difficult

    2. Arcs/curves: extremely difficult

    3. Paste layer: moderately difficult

    4. Allow resizing/fixed resolution: probably relatively straightforward

    5. Drawing with transparency: possibly quite easy if one of the existing blend mode suffices (i.e. similar to using destination-out on an own-texture layer)

    6. Flood fill: difficult and messy, since AFAIK it can't be done on the GPU, so would require a performance-killing GPU readback, software implementation of flood fill, then uploading the GPU buffer again. This is async and so will also conflict with any other attempts to draw while it processes. It's also inconsistent with all the other drawing commands which are GPU-accelerated.

    7: Load URL: it's not clear that this is necessary if you can already do it via a Sprite?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I don't think this is technically feasible I'm afraid.

  • I don't think Safari on iOS supports this.

  • As a small team constantly pushed for time, the more you ask for, the less likely you are to get it. It's much more feasible to deal with small and highly focused suggestions. So if you had to pick just one of those, which would it be?

  • Will the collision shape with multiple points SLOW-DOWN everything EVEN if the collision itself are disabled on all objects.

    No. If you don't make collision checks, the collision mask is not used at all.

  • Will many shapes on the screen, each one with multiple polygon shapes (20-40 points) make things slower?

    Answer your own performance questions with measurements

  • It's not supported because it's an incredibly complicated feature, likely has worse performance than collision masks, and I've not seen any convincing cases where it really is necessary. In particular mouse input is not really that precise - most users move the mouse to an approximate area, not a specific pixel, because mouse control is fairly inaccurate. That's why large buttons are easier to click on. Therefore there's no point having a super-accurate collision mask for clicks, because mouse input is not that precise. In fact usually the click area is simplified and enlarged to make it easier to click on.

  • FYI Construct 3 supports solid collision filtering which should be able to do this.

  • Continuous preview was removed in C3, because it appeared nobody used it. That happened back in 2017.