Ashley's Forum Posts

  • It will only be released when you close the project. It will not be released if deleted, because you can press undo and it will come back.

  • Is it possible to save the position of the game window on another screen without keeping it open in the background? I need to close the window after each test.

    Why do you need to close the window after each test? If you leave it open, you can still launch new previews from the editor, and problem solved.

  • Where did you save it? If it was to a local file, look on your file system; if you saved it to Google Drive, have a look on there; etc. Basically, look in the place you saved the project.

  • I don't think what Flutter does is that applicable to Construct - it looks like a very different thing, being primarily a native-based framework using the Dart programming language, and having the option to compile for the web. That makes it a very different situation to a web-first framework like Construct. For example perhaps Flutter fundamentally works by running their own programming language and outputting directly to a surface of pixels, and everything else (input elements, text rendering, layout, interactivity etc.) they built themselves on top of that. In that case, it may well be easier to make a web port by ditching HTML/JS/CSS and compiling Dart to WebAssembly that outputs to a canvas element as the surface of pixels. However I believe that would be a poor move for any web-first framework like Construct. HTML and CSS provide superpowers for layout, styling and interactivity. For example something as seemingly straightforward as a text input field is actually a formidable project, as described in this blog - it is far, far better and easier to just use a HTML text input field.

    Is WebAssembly faster than JavaScript? There's a great blog post on the subject: Is WebAssembly magic performance pixie dust?. tl;dr - the answer is basically "no". Carefully written high-performance JavaScript is basically just as fast, and avoids any performance overhead of having to transfer things into and out from a WebAssembly module, and we've spent years carefully tuning our codebase for maximum performance. For example despite the fact GameMaker's GML language is compiled to C++, JavaScript is way, way faster. You don't have to use WebAssembly to do that. It may well be the case that Flutter previously had a pretty inefficient Dart-to-JavaScript compiler, and found that converting Dart-to-WebAssembly produced better results - in that case it may well be good for them and something they will highlight, but it still has little relevance to a tool like Construct.

    WebAssembly excels at using smallish C++ modules on the web. We've used WebAssembly for Construct's physics engine for years, as the original Box2D engine was written in C++. We also use WebAssembly in the editor for converting and optimizing PNG, WebP and AVIF images, as well as transcoding audio. So we do make use of WebAssembly, but just in the few areas it's best suited for.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • There aren't currently any filed issues to do with the animations editor crashing in the latest update - if you find a case please file an issue following all the guidelines and we will look in to it. I'm afraid forum posts only saying "it crashes a lot" give us virtually nothing to go on and so we can't help from just that - if you can file an issue following the guidelines then that makes sure we get enough information to be able to help.

  • This appears to be exactly the same issue as this post you already made, where I already responded (my best guess is a browser extension is causing this, so try disabling any you have).

  • If it's an SDK v1 addon, it is not showing you an error, just a deprecation warning. You might be able to use the built-in CSV plugin instead. Alternatively you'll need to contact the addon developer for an update, or remove it from your project. SDK v1 addons will also still be supported in LTS releases of Construct through to the end of 2026 (about 2 years from now).

    • Post link icon

    Please see the Forum & Community guidelines, which advise against posting AI-generated content:

    Please don't use AI, such as ChatGPT, to generate content. It often produces text that sounds plausible, but is actually misleading, incorrect, or otherwise unhelpful. This causes confusion and ends up wasting people's time and making it harder for people to get help. It can also put pressure on more experienced users to have to step in and provide a correction, as it's important to ensure the forum is a useful source of information. So please only write posts that you personally know to be true and don't rely on AI to generate responses for you.

    You are welcome to use AI tools if you believe they help you, but please don't take their output and post it to the forum.

  • We had several weeks of testing beta releases with no known serious problems reported before we released a stable update. If we missed something please file an issue following all the guidelines and we will look in to it, but please note we need all the requested details to be able to help.

  • For the duration a release is supported, we will also make sure all associated services work with that release, including the mobile app build service, Remote Preview, and minifying. This means all these services will continue to work with the LTS release I previously mentioned through to the end of 2026. Beyond the end of its support period though, we cannot guarantee whether those services will continue to work - they may stop working soon afterwards, or work for a long time afterwards; it depends on what changes we need to make and when beyond the end of support.

  • We've seen a number of reports about an error involving "d.getModifierState is not a function" over the past several months, but we've never been able to reproduce it ourselves and so cannot investigate it. Our best guess is a browser extension is interfering with Construct and breaking it, so try disabling any browser extensions you have installed.

  • It sounds like the project has a corrupt image inside it. However it shouldn't crash Construct. Could you share the project file? You can send it to me at ashleyikz@scirra.com if you'd prefer not to share it publicly.

  • Let me clarify a few points:

    • Old releases are permanently available in the archive. We never go back and remove things from old releases. So any release which can use SDKv1 addons will always be able to do so.
    • Continuing to support software means fixing bugs, issuing updates, and answering support questions. In this sense, old releases are not supported, although they can still use SDKv1 addons. (Perhaps some confusion comes from terminology like "old releases support SDKv1 addons": they can still use SDKv1 addons, but we do not provide bug fixes or customer support.) So the old releases will always remain there, but if you run in to problems, they won't be changed nor can we provide assistance for them.
    • According to our current schedule, SDK v1 addons will continue to work in all releases, up until the middle of this year (June/July). At that point we will make a Long Term Support (LTS) release that still works with SDK v1 addons. That LTS release will be supported for another 18 months (to the end of 2026). Therefore there will be a version of Construct that is supported with bug fixes, updates, customer assistance etc. and can still use SDK v1 addons for around 2 years from now.
    • After that LTS release comes out, future beta and stable releases of Construct will only support SDK v2 addons. However you can continue to use the LTS release for a supported version of Construct that can use SDK v1 addons. Even after the LTS release is no longer supported (from 2027), it will still be there in the archive and can still be used and will still work with SDK v1 addons; it's just we won't be providing bug fixes, updates or customer assistance with it.

    Hope that helps clarify the situation.

  • If you run in to any problems please do file an issue following all the guidelines and we will investigate. I'm afraid with forum posts like this, there is not enough information for us to be able to investigate anything - we need more details to be able to look in to it, and the bug report process is designed to collect that information.

  • We heard someone else mention this, but so far we don't have a bug report following all the guidelines about this, so at the moment it's basically impossible for us to investigate. If you can figure out how to reproduce this and file an issue about it, we would look in to it with a high priority.