Ashley's Forum Posts

  • Maybe it's somehow a mistake in your project, or maybe it's a bug, or maybe it's a graphics driver bug on your system, or maybe something else is going on. It's hard to say unless you share a project.

  • Use the File System plugin. The Steamworks plugin documentation has some advice about using it with Steam Cloud.

  • You should only need to extract the zip and run the main executable. See the guide Exporting to Linux and the Steam Deck for more information.

  • It's probably a graphics driver bug. Check for any available system software updates or driver updates.

  • I'd guess it's a graphics driver bug on your system. Try checking for driver updates, or use a different device if available.

  • That's supported too using the File System plugin.

  • The FolderPath expression just repeats the Folder path parameter of file operations like Write text file in triggers like On file operation complete. You can get the name of the chosen folder after a folder picker completes using the FolderNameAt(0) expression. (I realized this purpose was not documented, so I updated the manual entry to cover that.)

    You cannot get the full file path to the folder (C:\Users\username\Documents\somefolder). For privacy reasons browsers do not expose such paths, as it can leak personal details like your username. Besides even if you could get that full path, you can't do anything with it in the File System plugin, as it never uses full paths. You can only work starting from picked folders, or known folders or desktop, only ever knowing the relative path from that folder.

  • Probably the easiest way to see the URL for your project in mobile exports is to add a Text object and the Browser object and set the text to the Browser.URL expression. IIRC in modern Construct versions the Android URL is https://localhost/, and the iOS one is on the app: protocol and I think included some kind of app ID in place of the domain.

  • If you want to continue using NW.js, stick to the r449.x LTS releases. However even those will eventually be unsupported, so my advice is to switch to the Windows, macOS and Linux export options instead.

    I don't think export with windows webview2 will work for me because in the exported folder json files are directly available for the user to edit and the kind of game I'm building is not meant for this to be easily accessible.

    Enable the 'Bundle assets' option for the Windows WebView2 export and it will hide your files much like the NW.js 'Package assets' option did.

  • I'd guess that means it's a graphics driver bug, since if changing the graphics performance preference fixes it, it probably means it is using a different GPU with a different driver that does not have a bug.

  • This may be what was noted in the r458.2 release notes:

    There have been some reports of Layout View glitches that we could not reproduce in r458. The main change to rendering in that release is that WebGPU (a more modern graphics technology) is now enabled by default for both the editor and runtime, whereas previously it used the older WebGL. It is possible some systems have graphics driver bugs that cause problems with WebGPU only. If you are having trouble with rendering glitches in the Layout View, try checking for any available system software updates or for a graphics driver update. Otherwise, you can disable WebGPU for the editor in Settings, and for your project in Project Properties. If you consistently see the same rendering issue with WebGPU across different devices, please do still file an issue with us, as it may then be an issue with Construct itself.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Support for 32-bit Windows systems is now so rare it's been retired in the latest releases. 64-bit systems appeared around 20 years ago, and even Windows 11 doesn't support 32-bit systems any more. If you still need x86 Windows support, it's still available in the r449.x LTS releases.

  • In short, you can load a URL in to a Binary Data object with the AJAX object by using 'Set response binary' just before making the request. Then you can write that Binary Data to storage using the Local Storage 'Set binary item' action. You can load it again with 'Get binary item' and if you need a URL again, use the GetURL expression of the Binary Data object.

  • Use the Windows WebView2 or macOS WKWebView export options instead of NW.js - they're much smaller, and in fact NW.js has been retired in the latest releases. There's also a guide in the manual on optimizing download size.

    • Post link icon

    For privacy and security reasons we cannot deal with subscription support questions in a public forum - please contact supportnpi@construct.net for such queries.