Ashley's Forum Posts

  • 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?

  • Please file a bug report following all the guidelines and we'll look in to it.

    You need to follow the bug report guidelines for us to be able to help, though.

  • Construct should be able to smoothly scale up to 120 FPS with delta-time and framerate independence. You may need to alter your events to correctly take this in to account though, in case you accidentally designed your game to work at 60 FPS.

    Other than that, the frame scheduling is controlled entirely by Safari/iOS. You could try reporting any framerate issues to them at https://bugs.webkit.org/ if you think it's a problem.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • LuisCGForte - that looks like an old bug we fixed ages ago. Try downloading the latest version of the desktop app from the first post in this thread.

  • Press F12, are any further errors in the browser console?

  • How significant is the mentioned code? Could it potentially corrupt projects or is it just minor stuff without any major impact?

    I'm not sure what scale to measure significance on, but there's lots of desktop-app specific code scattered across the editor, and most of it is now redundant as Chrome can basically do everything NW.js can now. Removing it helps simply the codebase and should reduce the number of bugs we have to deal with pertaining to that desktop-specific code too. In every case we'd just switch it over to doing what Chrome already does, so it seems unlikely any serious bugs will be introduced by doing this.

  • Yes I'm using C2 runtime for retro compatibility with IE11 and Edge + WebGL1.

    FYI the C3 runtime works with WebGL 1 too, so that is not a reason to stick to the C2 runtime.

  • I've been planning how we might approach the effective retirement of the desktop builds. With this plan, we won't actually really fully retire them: instead we will stop distributing builds ourselves (allowing direct downloads from nwjs.io instead), and gradually unify the codebase with the browser version.

    Currently the plan is:

    • Instead of providing our own desktop downloads, we will just provide the package.json file which you can add to any NW.js download.
    • Replace most NW.js code with the same code as is currently used in Chrome. For example this means deleting all the NW.js-specific saving code, and replacing it with the local file & folder saves as used in Chrome (but ideally without permission prompts).
    • The Windows Store download will be fully retired. Users will be advised to switch to either the Chrome or NW.js version.

    This means:

    • We no longer have to manage NW.js releases ourselves, freeing up our time.
    • You can download any NW.js version yourself, without having to wait for us to release it. This also includes using NW.js on other OSs that we didn't previously provide builds for (e.g. macOS, Linux).
    • We can delete the vast majority of NW.js-specific code and stop having to maintain it with bug fixes and such.
    • You can still preview and debug with NW.js features using the editor in NW.js.
    • It's largely backwards-compatible: everyone who has already downloaded the NW.js desktop download can keep using the editor with that.

    Basically this turns the NW.js version of the editor in to the same thing as you get in Chrome, but with NW.js features still enabled in preview mode. I think this covers everything we want, which is basically eliminating the NW.js maintenance overhead, while keeping all existing features that users rely on (like debugging with NW.js). We'll also provide the NW.js version of Remote Preview on a similar basis, so you can Remote Preview your project with NW.js features active somewhere else without having to send your full project.

    Let me know if you have any feedback or if there's anything I missed. I think the next step is to formally notify users of the Windows Store app that it will be retired, so I will do that in the near feature if there are no objections.

  • This should not happen with imported Web Font files in the C3 runtime, since it pre-loads the fonts before starting the game ensuring they can render correctly on the first frame. The C3 runtime does not work in IE11, so I assume you're using the C2 runtime? This should not be an issue for modern projects.