Ashley's Forum Posts

  • If an incognito window, or clearing all cache locally, doesn't update it, then it sounds like it's being cached on the server side. You probably want to check your server caching configuration (and CDN caching configuration if you use one). For example if your server is behind a CDN that does server-side caching of certain types of resources, like images, for 24 hours, then nothing you do on the client will be able to update that cache.

    If all else fails, publishing your project to a different URL as you have been doing is the ultimate cache-busting approach.

  • We're not aware of any such issues with the new Windows WebView2 exporter. If you run in to a problem, please file an issue.

    False positives are common with antivirus tools and have historically affected any kind of executable. We've had false positives with NW.js before too. It's not really related to the kind of export.

    NW.js had a range of bugs and issues that proved difficult to deal with - including many complaints about the file size of exports - and having two export options complicates supports and doubles the amount of maintenance work involved. As our newer export options now cover all the features previously supported by NW.js, the time has come to retire NW.js support and focus our efforts on the new ones.

  • Use the lineThickness BBcode tag, e.g. [lineThickness=0.5][outline=blue]Text[/outline][/lineThickness] will adjust the outline thickness to half its usual size. All the supported BBcode tags are in the manual.

  • Those must be very old systems - as I mentioned 64-bit hardware has been standard for many years now, to the extent even the latest version of Windows doesn't support 32-bit hardware any more. Such old systems are not going to be supported forever. And if you still need 32-bit exports, it's still supported in the r449.x LTS release, so you can just keep using that.

  • rgbEx works in the range 0-100. If you want an expression that works in the range 0-255, use rgbEx255. See the documentation in system expressions.

  • You should also be able to open the project in an older version of Construct (which the error message links to, IIRC), rename any instance variable named ParentUID, save the project, and then open it again in the latest release.

  • Lately most of these issues have been graphics driver bugs (part of the system software, not part of Construct, browsers or WebGPU). So you could try updating your graphics drivers, or installing any available system software updates.

  • Does the Video Recorder plugin only record based on the actual canvas size, not the fullscreen resolution?

    It only records the actual canvas size, because that's the size that is actually rendered. The viewport size is more or less just how much of the layout you get to see, and that is stretched to the window size in the default letterbox scale mode. If the window is smaller than the viewport size, then it will have been resized smaller.

    If you want a full resolution recording, make the window fullscreen before starting recording (press F11 or use the Browser 'Request fullscreen' action). If necessary, you can change your display resolution to the intended video resolution.

    I'd also note that Construct Animate's 'Export to video' option does record the video at the resolution given by the viewport size - as Construct 3 is a game engine it will just render the canvas fit to the window size.

  • It's impossible to help from just that information. If you think it's a problem with Construct, please file an issue following all the guidelines.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • That's when we enabled WebGPU by default, which my previous post referred to.

  • Perhaps your network is blocking the login request to the Construct server. Press F12 and look in the browser console for more details - there should be an error message there which may shed more light on what happened.

  • You do not have permission to view this post

  • I'm afraid it's a bug in WebView2. We can work around it, but the workaround would break the Steam in-game overlay, which is important to commercial titles on Steam. So for now we're hoping that Microsoft fix it soon.

    You can work around it for an individual export if you don't care about the Steam in-game overlay: open package.json and under the "settings" key, add "allow-host-input-processing": false. That puts it in the mode where gamepad input works but the Steam in-game overlay doesn't.

  • Performance should not be significantly different between NW.js and WebView2 - both use the same Chromium browser engine after all. I've never heard anyone else reporting such an issue. If you think there is a problem to be investigated, please file an issue.

  • I'd guess this is a graphics driver bug on your system. Checking for a driver update may fix it. You could also disable WebGPU in your project - that's enabled by default and seems to have cropped up a bunch of graphics driver bugs on some people's systems.