Ashley's Forum Posts

  • The Browser object is still there in r250.

  • Import the data as a project file.

  • With low quality fullscreen mode, the 'Set canvas size' action modifies the render resolution IIRC.

  • These days you should use the Clipboard API.

  • You can change the language Construct uses in Settings.

  • I can try to recover the project, but sometimes it is not at all recoverable. It is absolutely critical that you make regular backups of any important digital work with any software. Anything from hardware failure to ransomware could cause you to lose your work.

  • It looks like you have a browser extension that is breaking web pages. It looks like something to do with "adguard". Try disabling any browser extensions you have.

  • Use the 'Wait' action, like you had already but disabled.

  • We've worked hard to make Construct performance shine, and it's nice to see that reflected in a microbenchmark. Modern JavaScript JITs are also extremely sophisticated and it's cool to see that they're competitive even with compilers.

    However I'd caution against taking any performance advice from tests like these. As noted often you can get significantly different results by making obscure changes to events. However these changes usually only affect microbenchmarks that are hammering one code path super hard. Real games generally don't do that, so porting microbenchmark-level changes to real games will probably have no effect. So don't look at results like these and think "Wow, I should always use conditional expressions instead of conditions". Most likely you'll just needlessly obscure your events to no performance gain. As ever, with real games the only meaningful approach is to make measurements, and target optimisations at the things you've actually measured are slow, and only keep optimisations that measurably improve things.

  • Use the "Install as app" option in Construct and you can install it locally where it works just like a desktop app.

    I would advise against using the NW.js app - it's only really actually useful if you need to regularly test features of the NW.js plugin. If you don't need to do that, it's the same as you'd get in the browser, but browsers tend to be better tested.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • IIRc, requesting fullscreen is only supported on iPad. It is not supported on iPhone. This is a limitation of the Safari browser.

  • I don't know what you're really trying to achieve here, since the events look like you're trying to permanently move Sprite2 to the right, but for some reason it tries to ignore input while it's moving, which I don't think actually makes any difference in this case (while it's moving to a tile, input isn't used anyway, it's just waiting for the object to move in to the next tile).

    Since your events stop ignoring movement and then immediately starts moving it again the next tick, you have a one-tick duration before movement restarts, which is framerate dependent.

  • Triggered events can be sub-events. However you are not allowed to have two triggers in the same event branch (e.g. a trigger as a sub-event to another trigger), as that doesn't make sense.

    As I said in my previous post, you just need to drag an event block and move the mouse to the right a little to get it to show the insert mark as indented, which means it will drop it as a sub-event. If Construct doesn't let you do that, it's probably because it would be an invalid event, for example the restriction with triggers.

  • As I noted in that other thread about positioned sound, the audio playback engines are managed by the browser, so issues with the playback engine are out of our control. You most likely should contact the browser vendor directly for any such issues.

  • Please file issues on the bug tracker. Things only mentioned in the forum are easily lost and forgotten, which is part of the reason we have a bug tracker.