Is there anything specific you need added to WebView2 to move over to it from NW.js?
Construct Classic first came out in 2007 if I remember right... so about 18 years so far!
We'd be happy to investigate any reported issues with this release, but unfortunately comments like this give us virtually nothing to go on - would you be able to file an issue following all the guidelines? That would give us enough information to investigate.
This should be fixable, but the GPU vendors need to do it. File an issue with GPU vendors - we're currently pursuing that ourselves but the more people do it, the more they'll see demand for it.
See the section on the overlay in the documentation. The in-game overlay is not currently supported (Valve need to add support for that), but when the in-game overlay is not supported Steam uses a fallback approach, and that definitely worked for me last I tried.
It's not impossible to use - you only have access to the message data in a trigger; if you need it later, you can save it in a global variable.
It should work - it just compares the ControllerValue expression, which is set in a 'Control change' message, so it doesn't need the controller number to be passed.
The next LTS release (in ~6 months) will continue to support both NW.js and legacy SDK v1 addons, and that will be supported until the end of 2026, so you should aim to use that if you need extended support.
Steam has fallbacks that show the actual Steam UI instead of an in-game overlay, so Valve have an alternative implementation there that WebView2 uses. As NW.js is essentially unmaintained, may well be retired at some point, and integrating custom native code in NW.js for things like Steam integration is extremely difficult and requires constant maintenance (and has finnicky version matching requirements), I don't think it makes sense to continue to support NW.js just to get the in-game overlay instead of the fallback.
It's not like we've ignored the community over this - we have in fact gone to great lengths to try to support the in-game overlay, but various problems and limitations with Valve's implementation make it infeasible. So while it is unfortunate we can't support that, if you want it supported the best thing to do is contact Valve, as it seems only they can solve the problem.
There is a Steam plugin for WebView2: construct.net/en/make-games/addons/1105/steamworks
.capx files are for Construct 2 which was retired in 2021. For Construct 3, it's built in to the Example Browser, and you can open it here.
It does trigger for single instances - an instance without any children still counts as the root of a hierarchy, as it has no parent, and so 'On hierarchy ready' still triggers for it after 'On created'. It doesn't trigger for children, as then we have to decide what sequence to trigger in: top-to-bottom, bottom-to-top, or some other sequence, and whatever we choose, someone will need some other sequence. Therefore it only triggers for the root of the hierarchy, and you can then initialize children in whatever sequence is best for your project.
It looks like you emailed us on Friday December 6th, and we already sent a response on Monday December 9th.
You have to use an action to go to the next layout. Construct won't change the layout automatically.
Yeah, notarization only applies to the end app, not individual libraries.
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.