Ashley's Forum Posts

  • You can't force the CPU to work any harder. It already works as fast as it can. Construct's CPU reading is only an estimate, subject to caveats noted in the manual, and so there is probably still a bottleneck somewhere else.

  • If your game isn't using all the CPU available, that's a good thing! It means it will continue to run well on lower-end devices. You shouldn't aim to consume all possible resources.

    If the game is GPU-bottlenecked, naturally the CPU usage won't be as high, which means you need to focus on optimising the rendering, not the logic.

  • I'm not aware of any issues at all using either C2 or C3 on Windows 11.

    Please note since C2 has now been retired, it won't be supported even if there were issues on Windows 11. However Microsoft generally have a very strong track record of keeping Windows backwards-compatible for years.

  • I don't believe anything has intentionally changed. From years worth of experience dealing with bug reports, things like this are also very commonly just mistakes in your project that cause confusion. If you think something has changed in Construct, you can prove it by making a test project in an older release, and testing it in newer releases to see if a specific release changed how it works. If a release did break it, then you can file the test project with a bug report and let us know the release number where it changed.

  • I deleted 3 other topics you made because they looked like advertising spam. See the Forum & Community guidelines and be warned if you make too many posts that look like spam you may be banned.

  • The message is stating both WebAssembly and WebGL (at any version) are not supported. It's because that version of KaiOS is based on Firefox 48 from 2016, which is now just too old to run modern web content. The message is correct that the device needs a software update to be able to run the content. Unfortunately whether or not you get one from the device manufacturer is another matter...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • You can't import in scripts in event sheets. (Those are really inside functions, and the JavaScript language disallows import and export inside functions.) The syntax is also wrong for the module specifier (it should be "./brain.js").

    This is what the 'Imports for events' script is for - anything you import there will be accessible by scripts in event sheets. However the script you've included does not actually export anything (it uses a different module system), so you'll need to load it differently anyway.

  • Import them as project files and then load them with AJAX.

  • If a device only supports WebGL 1, Construct will just use WebGL 1. WebGL 2 support is optional. So you shouldn't need to change anything.

  • I'm not sure I understand. Any script you import to the main script is already automatically loaded.

  • I would advise to as usual file an issue following all the guidelines, as we generally need all that information to be able to investigate or help.

  • I don't think this is anything specific to Construct - you can just use the usual browser APIs for this. The code below will create a canvas element and insert it to the document. You'll probably need to use CSS to position it. 

    const canvas = document.createElement("canvas");
canvas.width = 300;
canvas.height = 200;
document.body.appendChild(canvas);

  • Currently worker mode "auto" will only switch to DOM mode if you use any script file or script block in an event sheet anywhere in your project. You can still change worker mode to "Yes" or "No" to force it to use one or the other instead of using "auto".

  • Try uninstalling the app, rebooting the device, then re-testing it. I think iOS caches app icons a bit too keenly and it may have remembered an old icon before you changed it.

  • I appreciate it's important to have lots of good documentation on coding in JavaScript for newcomers and more would be useful. The main limiting factor is just that good quality documentation is time consuming to write. The current in-progress "Learn JavaScript in Construct" tutorial series is a months-long project, and there's probably several other similar tutorial series we could potentially write on coding various aspects of different games. We'll work on it, but it will take time. In the mean time it would be great if any other users who've learned some useful things about JavaScript coding could share what they've learned in the tutorials system - part of the reason it's there is so everyone can share their own tips, tricks and guides, both for the event sheets and coding.