Ashley's Forum Posts

  • I'd advise contacting supportwrn@construct.net for such queries as generally they can't be dealt with in a public forum without sharing sensitive information.

  • Typically you'd do masking/clipping using blend modes like 'destination out' with a force own texture layer. That's all done using the regular engine - do you really need to use the SDK for that? If you want to set something like that up automatically in an addon, you could probably do it using the existing layer and blend mode APIs.

  • What methods were those exactly?

    If they were undocumented methods in SDK v1 please note they were never officially supported, the documentation explained such features could break or be removed at any time without warning and so addon developers should never use or rely on them, and we are not obliged to support them with SDK v2.

  • Is there any chance you could still get that information from affected users? It sounds like a graphics driver bug affecting WebGPU, and it may affect other Construct projects unless we can identify affected hardware and automatically disable WebGPU on those systems.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I'm not sure what you mean - isn't this just typing a special character? What are you doing exactly that no longer works?

    Maybe to make things easier you could put the non-breaking space in a global constant string variable, and then you can always refer to it in expressions via that variable name.

  • As I said Chrome doesn't seem to allow copy-pasting this character, but you can use the Alt+0160 sequence to type it directly in to Construct.

  • We just released r487.3 to correct a few more regressions. Hopefully that resolves any remaining compatibility issues since the previous stable release.

    No software is perfect and also no testing system is perfect either - there is always going to be the risk of a couple of issues that slip through the net and end up in a stable release. We are usually very responsive when people file issues, and if you follow all the guidelines, often an issue can be fixed within minutes. The main cause of delays in fixing issues is nobody filing an issue. I'm afraid it's usually impossible to investigate issues when people just write that something doesn't work in a forum post or comment - we're not telepathic! And if we haven't been able to identify the issue ourselves, then we have nothing to go on. So I would ask for your patience and co-operation if any issues come up - please file an issue, and with a good report, often we can have it fixed very quickly.

  • Don't use a braille blank - use the unicode character "non-breaking space", which is designed specifically for this purpose.

    Weirdly it doesn't seem possible to copy-paste a non-breaking space in Chrome - maybe it is normalizing the copied text somehow. However you can type one in on Windows with Alt+0160. Most unicode characters have a code you can type in like that, it should be straightforward to look up the codes.

  • Safari releases are often a nightmare for us too. If you think a Safari update broke your web app then probably the best thing to do is to report it to Apple directly at https://bugs.webkit.org/. If the issue is with a third-party library then you could report it to them as well so they're aware - or it may be that if you update that library to the latest version it has an update for that.

  • EpicNoobDudePro888 - please file an issue so we can look in to that - I'm afraid it's virtually impossible to help from just a forum post.

  • pumacap - we're not aware of anyone else reporting such issues, and it could also be something else on your system using up a lot of memory. If you want us to investigate further, please file an issue and be as detailed as possible, including testing every beta release since the last stable release to identify which specific release it changed in, along with a sample project file, steps to follow, and measurements of memory usage (preferably from Chrome's task manager as it is probably most accurate - press Shift + Escape to open).

  • It's still useful if you can file an issue, or at least share the platform information of the affected device here. With sufficient detail we may be able to work around the problem and prevent it affecting others. Again, please always file issues to our tracker instead of the forum - it makes the reporting process much better for both sides.

  • I just tested this and it works fine for me. I would guess there is either it's less obvious than you think, or it's a device-specific graphics driver issue (both common issues). I would really recommend you file an issue for any such problems, as we have a process designed to help us properly investigate and resolve reports like this - it is usually impossible to help from just a forum post like this.

  • That's just a standard Windows security dialog for running an executable. It's probably only appearing because we made some changes to the executable since the last stable release, so it may be the first time your system has seen that particular executable. If you tell it to run anyway it should work as normal.

  • There isn't currently a way to do that from code, but we have an internal capability to do it which is easy to expose to code. So the next beta release will have an ImageInfo method toCanvas() which will let you extract the image off its spritesheet to a canvas (either HTMLCanvasElement in DOM mode or OffscreenCanvas in worker mode).