Ashley's Forum Posts

  • There's always QueryPerformanceCounter, which is accurate to microseconds, and available to any C++ program. Construct uses it.

  • Construct already uses 64-bit floats in the event engine. Positions, angles etc. are stored as 32 bit floats since that's generally all that's necessary for sufficient precision, and I think the Physics engine uses 32 bit floats as well, for efficiency.

    • Post link icon

    Bug reports from anonymous users are now no longer allowed. You must register a SourceForge account and submit your bug report from there.

    We receive a lot of anonymous submissions and sadly, a lot of them cannot be reproduced by a developer, or contain incomplete or ambiguous descriptions. In these cases, we need to contact the submitter in order to solve the problem. When the submitter is anonymous, it's impossible to contact them unless they come back and check the report, and in nearly all the cases I have seen, the anonymous submitter never returned to the bug report.

    We'd rather these problems were fixed than left closed due to being incomplete, therefore, you must now submit from a registered SourceForge account.

  • Put it on a layer with "Force own texture" enabled and it will cut a hole in the layer.

  • I'm sorry this happened, but Construct is beta software, and so long as it is, we can't really guarantee it's not going to explode. This can even happen in other mature software releases as well, so I guess you learnt the hard way, to make backups, and not to assume that any backups are done for you. Sorry.

    Still, all such cases should be reported on the tracker - if you find something you undo and redo and it screws up the cap, obviously that's something we desparately want to fix so it doesn't affect anyone else - a good bug report with reproduction steps will help there.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You do not have permission to view this post

  • Crashes are always bugs. Better put it on the tracker.

  • Oh, btw, is there a way to check how much fps we get for the runtime? That'd be helpful for debugging and making sure that the thing runs even on older hardware.

    Enable 'FPS in caption' in Application Properties. However, exported EXEs won't put the FPS in the caption, only the preview. You'll need to show FPS in-game for other people to know their FPS, or use a program like FRAPS to tell you.

  • For now you can try simulating a layer effect with a window-sized canvas object and 'grab layout before drawing' enabled.

  • Then I propose

    random(N) returns 1 to N

    and random(A, B) would return any number from A to B inclusive (so random(1, N) is the same as random(N)).

    This means any cases of random(N) that currently exist must be changed to random(0, N-1). This will break a lot of things, but (hopefully) Construct will only grow more in future, so the least damaging time to do this is definitely now.

  • I think everything in Construct should be 1-based index. 0-based makes sense in low-level programming, but for Construct, it's just more intuitive to have everything 1-based.

    I think it's worth seriously considering making Random() return 1-N instead of 0-(N-1) for the same reasons. However I can imagine that breaking a lot of stuff. What do you think?

    Also, I thought LoopIndex was 1-based already - if you find anything like that which is 0-based, report it as a bug and I'll correct it back to 1-based.

  • Your expression would look more like this in Construct:

    Shooter('Cannon Power') * Sin(Shooter.Angle)

  • I'd like to see a object that allows you recolor a sprite's pallette. Like in the Megaman games.

    How would that differ from the existing colour filter?

  • The way I see it, people want a 2D perspective transform, so they can make 3D things. Construct is not a 3D tool and if you want to make something 3D, an object like 3D box is way more intuitive than stitching together perspective-transformed sprites. Therefore, I do not see a reason this should be implemented.

  • I think arrays are 1-indexed, so you'd want (random(3) + 1)...