Ashley's Forum Posts

  • Construct should be logging something to the console if an error occurred. Perhaps it's a network issue, in which case you may need to look in the network tab (you'll probably need to reload to capture network requests while loading).

  • I just want to point out that Construct already has a real-time 3D view in the editor - drop in a 3D shape and scroll around, and you can see you have a 3D view there. It doesn't however have a free look camera. That's a fairly significant amount of work to implement, but it's doable.

    Once you do something like a 3D view in the editor, I assume there will naturally be a lot of follow-up feature requests that will amount to implementing a significant portion of a 3D engine. That is also possible, it's just a great deal of work.

    We've so far avoided going too far in to 3D features so we don't spread ourselves too thinly - making a quality 2D tool has for many years been more than enough work, and there's already years of further work submitted as feature requests. We wouldn't want to spend years working on advanced 3D features while the rest of the editor was lacking the basics, or was full of bugs and limitations that were neglected in favor of shiny 3D stuff - that would overall be to the detriment of the product. Despite that, we have still gradually done a bunch of 3D features already, including Z elevation, 3D mesh distortion, 3D camera, 3D shape, and even 3D audio playback. With those we took the time to ensure we did a good job, carefully considering the design, ensuring they integrate nicely with other features, dealing with bug reports, doing follow-up feature requests, optimizing performance, etc.

    However Construct is a pretty mature product now. Perhaps risk the rest of the product suffering or getting left behind is not that significant a concern any more. So perhaps we could more seriously consider doing more work on 3D features. If that's of interest to you, then I'd suggest filing feature requests the usual way, as it helps us gauge the interest relative to other features, and especially which particular things to work on next. For example which is more important: a 3D editor view, 3D physics, 3D collisions, 3D particles, 3D models, 3D lighting, or something else? There's years of work to be done there, especially if it's to be done to the same quality as the rest of the engine, so just choosing what the next single thing should be is a significant decision too. Let us know what you think!

  • The Steamworks plugin documentation has a section on using Steam Cloud.

  • The Pin behavior mostly exists for backwards compatibility, and because hierarchies don't support the 'Pin at distance' mode. However for most purposes hierarchies should be used instead. For this reason the Pin behavior is listed in the superseded features section of the manual.

  • You can file an issue if you can reproduce the issue by filling a new empty project with dummy content.

  • Getting all instances in the editor isn't currently supported. Nothing else needs it, and it's not clear for what purpose you'd need it in the editor. You can however access all instances at runtime.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The best thing to do in such cases is file an issue following all the guidelines so we can fix it, and then you don't have to work around it.

  • Chrome supports using 'Open local project folder'. It's under Menu > Project > Open local project folder. Then you need to select the folder the .c3proj file is in. The folder needs to have the complete project in it, so if you've done something like download a zip, you need to fully extract all the files first.

    Firefox does not support the 'Open local project folder' option - unfortunately they don't support the File System Access API that this feature depends on. You have to use a Chromium-based browser for that at the moment (typically Chrome or Edge).

  • If you run in to a problem with Construct please file an issue following all the guidelines. Note we need all the requested information to be able to help.

  • As noted in the Local Storage manual entry:

    The Local Storage plugin stores all saved data in an internal browser database. This does not produce any easily discoverable files on disk. If you want to save data to easily identifiable files on disk, such as storing save data in a file in the user's Documents folder, consider using the File System plugin instead.

    The Steamworks plugin documentation has some advice on using Steam Cloud.

  • Looking good!

  • If you think it's a Construct bug it's best to file an issue following all the guidelines.

  • We believe this issue is caused by the system graphics driver rather than Construct or the browser. We are trying to track down cases where this happens, so it would be useful if you could share your system's graphics information with us. To do that, with the Chrome or Edge browsers, visit chrome://gpu in the address bar, and then click the 'Download Report to File' button at the top. Then attach that file to an email and send it to us at supportfzj@construct.net with a link to this thread for context, and we should be able to identify things like your specific graphics card model.

    To fix the problem, try installing any available system software updates, or check for an updated graphics driver from the device's graphics vendor. Alternatively to work around the problem, try opening Construct's settings and change the 'Enable WebGPU in editor' setting to 'No'.

  • The build server had a technical issue that meant builds were not working. We've now corrected this and it should be working normally again. Apologies for the inconvenience.

  • The build server had a technical issue that meant builds were not working. We've now corrected this and it should be working normally again. Apologies for the inconvenience.