Ashley's Forum Posts

  • Thanks for the feedback and I'm glad you're enjoying C3!

    Nevertheless, I'm very sorry that you still haven't corrected the problems due to the canvas

    I'm not sure what you're referring to here. Could you explain some more? Obviously we'd like to correct any problems where we can, but some things are fundamental limitations or otherwise out of our control.

  • The iframe is part of the parent page. If the iframe page is on the same origin (i.e. domain), it should be able to remove itself from the parent page via accessing its parent window. However if it's on a different origin it is not allowed to do that for security reasons. Instead you could use postMessage in JavaScript to get the iframe to tell the parent page to remove the iframe.

  • If your game did not pause at all, it would continue to waste battery and system resources, resulting in alienated users, poor reviews, and then eventually the browser or OS would kill it anyway to save the user. So it's a pretty good thing that it does pause automatically.

    • Post link icon

    This has been discussed to death already, and the short version is we have no plans to change this right now.

    Something I do want to point out though is I think a lot of people don't realise that I was the sole developer on Construct 2. Being the only developer working for years with a one-time payment model while people are crying out for more features, it became pretty obvious there was no way we could have done a fraction of what everyone wanted under the previous model. With Construct 3 we were able to hire more developers, making it possible to do way more, such as a completely rewritten runtime with vastly improved performance, an ongoing mobile app build service, timelines, scripting, a big batch of new plugins and behaviors, and loads more. If you're looking at those things and wishing you could upgrade, then I think you should recognize most of that would not exist at all if we had stuck to the old model.

  • The main cause of the app crashing is an incorrect configuration. (Unfortunately Google's code does not elegantly handle such misconfigured cases and tends to just crash the app.) Make sure everything is set up correctly as described in the documentation.

  • You can save your project as a folder and then use that with existing version control tools like SVN and Git.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It seems there was an oversight and the project property for "Viewport fit" was missing from the manual, so I just added it.

    In short you should only need to change the viewport fit to "cover". You may also need to adjust the game to fit different screen sizes too.

  • You probably need to adjust the Cache-Control HTTP header on the server response.

  • The settings applied by 'Optimize for pixel art' are documented in the manual here.

  • Yes, it's because you downgraded the NW.js version and it can't read the updated data format from the newer version. You can delete the app's data from your AppData folder to reset it (clearing all the app's storage too) and the message will go away.

  • That's JSON data, so you can use the JSON object.

    • Post link icon

    The Windows Store app for Construct 3 is now deprecated. It has low usage, is difficult to maintain, and no longer provides any advantage over the browser-based version. We will be removing all features specific to the Windows Store version in the near future. This means it will revert to the same features as you get in the Edge browser. It has also been de-listed from the Windows Store to prevent new customers finding it.

    We advise all existing users of the Windows Store app switch to the browser-based version of Construct 3 by visiting editor.construct.net. All your projects will continue to open and work exactly the same in the browser-based version.

    If you use local file & folder saves, note this is now available in Chrome.

    If you use Microsoft Edge as your browser, note Construct 3 works particularly well in the latest Microsoft Edge browser based on the Chromium browser engine.

    Thanks for your patience and we hope you continue to enjoy using Construct 3 in your browser!

  • An easier way to do it would be to use 'Sprite2: spawn Sprite'. That action automatically works per instance. Since 'Create object' is a system action it will only create one instance.

  • It probably has no effect at all. You can run your own performance tests and try to measure the difference if you really want to know.

  • I thought iOS already capped Safari pages to 60 FPS for compatibility reasons. If you display the game FPS does it read 120?