From what I can see, none of the image optimisations apply to images stored in the project files folder, is this correct? I have to use the project file folder in the absence of a 3D object "set face to use image of (by name)" action
To think of an example, we're yet to find a way to prevent browser prompts (e.g. "Press ESC to show mouse cursor" on cursor lock) showing, which aren't shown on NW.js.
Another example, in WebView, pressing ESC while your pointer is locked does not register as a key press (one press unlocks, second press registers). This makes opening a pause menu seem broken. This isn't an issue for NW.js.
We've also had videos not work as expected on Windows 10 with WebView that work fine with NW.js.
I think these issues and others I've forgotten to mention are why Construct devs making large/paid games still tend to go with NW.js over the other options. You get the security of knowing a game will behave consistently cross-platform, which you seem to loose when choosing platform specific wrappers. If you could shed some light on all this we would massively appreciate!
Nice to see better support for Steam deck, this is great! Although have to admit, a little worried to see the stuff about NW.js support, hopefully the alternative export options will have all their issues resolved before NW.js support is dropped
Looks great and barely impacts performance
The ignore transparency depth buffer is gonna save me so much headache. Awesome!
Crashes whenever I open a new layout :(
Member since 9 Jan, 2022