Ashley's Forum Posts

  • I'm sure it would be quite a bit of work to add Electron support, it would need on-going maintenance, probably bring its own various quirks that would have to be dealt with, and architecturally it's basically the same as NW.js - it's the Chromium browser engine with node.js integrated. So I don't think it's worth it. Regardless of the outcome of my experiment with a node native addon, I'd rather focus on WebView2 which is a better technology in my view.

  • If you are merely trying to load a file in a subfolder, then the path to use depends on the Export file structure project setting. The new default is folder mode, which means you need to specify the full subfolder path, e.g. "Dialogues/Timothy/Test/Timothy-dialogue-1.json".

  • In order to try to prevent unwanted reverse engineering, we've deliberately made it as difficult as possible to reverse engineer an exported project back to a Construct project. If you use advanced minification, it's probably close to impossible since so much information is lost.

    This is why it's important to keep regular backups!

  • It might be because the version of Closure Compiler used for minifying has been updated. It's difficult to help any more without seeing the project. It's probably best to file an issue about it.

  • To be clear: providing your content is hosted on a secure server (HTTPS), all content exported by Construct automatically works offline.

  • It's a graphics driver or ANGLE bug that only affects newer Construct versions. That doesn't mean it's our fault or that we can do anything about it - as I said the best thing to do is to report it to Google via crbug.com who would be best placed to investigate and either fix or work around the problem.

    For what it's worth, we have stats on WebGL support for people using the Construct editor, and that shows 98.5% get WebGL or WebGPU support in some form. So only ~1.5% of people don't get any WebGL support, which I think is about what it's always been long-term, even before r317 came out. There have always been reasons a small number of people don't get WebGL support, such as broken drivers or unsupported hardware. This case looks like an error Google could potentially fix though, providing someone with an affected device reports the issue to them.

  • I think I've seen reports of this before - it looks like it affects a small number of older devices with some specific hardware/driver configuration.

    It looks like either a graphics driver bug or a bug in Chrome's WebGL implementation. The error refers to a D3D shader compilation error, which is probably happening inside ANGLE, Chrome's internal graphics library that converts WebGL to D3D. Like all other WebGL content Construct makes WebGL calls and uses GLSL shaders, so it does not directly use anything in D3D - that's all generated by ANGLE. And if anything Construct does was invalid, it would have failed earlier, with a WebGL or GLSL error message (and probably affect other systems too).

    I think the best thing to do would be to report this to Google at crbug.com, showing that error message, and including details about the hardware of the affected device.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It's been there since the first public release of Construct 3 in 2017! 😅

  • Sounds like what the 'Background color' project property is for!

  • Sorry, it's not something we do ourselves so I don't know how to help. It would be best to use Apple's support if available - it's all their code and services.

  • Looks like this known issue which is a bug in the Chrome browser, not Construct. It appears to be fixed in the next Chrome update.

  • It's based on an internal project unique ID. There isn't currently any option to change it, although if you were determined, you could save the project to a folder and modify the "uniqueId" property in project.c3proj.

  • It's entirely up to you which you use. If you're experienced with both, event sheets and JavaScript code still have their own strengths and weaknesses. For example in my Command & Construct game project, I mostly used JavaScript coding, but I still used event sheets for the menu systems, because it's quicker and easier than having to write code for a menu system.

  • We did some maintenance on the Remote Preview server last week and it accidentally introduced a bug where the host would be disconnected after 25 seconds. This has now been resolved so it should be working normally again (I just did a test and I could successfully host a Remote Preview for 5 minutes). Apologies for the inconvenience.