The built-in projects seem to open just fine. As ever if you run in to any problems, please file an issue following all the guidelines.
As we've regularly noted since November, you'll need to contact addon developers for an update if a third-party addon does not work in classic mode. It should only take them 5-10 minutes - it's a really simple change.
This sounds like the same issue as discussed in this other comment thread. In short we fixed a bug that actually caused incorrect vertical alignment in some cases. If you'd repositioned text objects to compensate for the bug, you'll need to put them back.
If you run in to any problems please file an issue following all the guidelines.
Do you mean for the editor? It's not necessary - try using the 'Install as app' option in Chrome.
Fullscreen is already supported in the Windows Wrapper, currently in the same way as the browser (requiring a user input event).
To avoid the security warning you need to digitally sign the executable, as described in the tutorial on the Windows wrapper export option.
I'm not aware of any recent changes to the scaling. As ever, if you run in to any unexpected problems, please file an issue following the guidelines.
I'm afraid it's impossible to help without more information. If you run in to any problems, please file an issue following all the guidelines.
Were you using vertically centered text objects? Previously there was a bug that did not align these correctly. Another user reported it as a bug, so we fixed it, but it may change the vertical positions of text in existing projects slightly. Unfortunately cases like this are tricky since our options are to either leave it broken permanently, or fix it and have some small changes to existing projects. While such changes can be inconvenient, I think it's the best way in the long run, since ultimately things get fixed.
It is in the NW.js release of C3. The NW.js release is basically the same as you get in the browser.
Steam integration is not currently supported in WebView2, but it's possible it could be in future. For performance, as ever measurements are the way to test that, but I would not expect there to be any significant difference as both NW.js and WebView2 are based on the same Chromium browser engine.
If you run in to any problems please file an issue following all the guidelines, as we need that information to be able to help.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.