No one is saying that it's bad, I haven't said a word about that. I am truly grateful to Construct for growing from a lab project into a commercial product and giving me experience in game development back in the day. It's just that without proper support for integrations, it's becoming obsolete.

So many positioned themselves as 2D engines, and Construct has some really cool solutions. But the problem is limited integration and support for integration solutions.

Well, yes, there won't be normal integration with normal Steam overlays, there won't be normal animation with Spine, and there won't be adequate 3D.

What about Godot or Unity? These are currently being actively tested for future projects.

Let's put it this way, Construct 3 has always been very beginner-friendly, but without these features, it becomes just something very old and outdated.

Yes, perhaps WEBGPU will be some kind of breakthrough in performance. But if everything continues the same way, it's just a playground for beginners. Don't expect any breakthroughs. It's a shame, I've been with them since Construct 1. But everyone either stays in their beloved summer of the mid-2000s or moves on.

When will NW.js be shut down?

The “new” exporter, as I understand it, is WebView2, for which there is no working plugin for Steam, and judging by the comments will not be (since the problem with the plugin not working is addressed to Valve...).

I'm not talking about Spine, which for 2D has long been a standard, but it also will not work, because there webgl is used, and is unlikely to be used gpu. but yes, esotericsoftware has a problem there too, not in the construct...

If you set the startup parameters in the project parameters on the startup tab

Loader style Progress bar & logo (the default)

Then the project ends with an error. This works even out of the box, any empty project with one sprite.

Normal test, create a new project - run

Error:

Uncaught (in promise) Error: released image asset which still has texture references

at ImageAsset.Release (imageAsset.js:2:276)

at C3Runtime.ReleaseLoadingLogoAsset (runtime.js:54:591)

at CanvasManager.EndLoadingScreen (canvasManager.js:65:222)

at C3Runtime.Init (runtime.js:27:522)

at async InitRuntime (workermain.js:8:1)

Same error.

Thank you Mikal! :)

Version 1.4.0

It looks like there is some kind of conflict in the latest version of the plugin.

When launched normally in the editor window (Preview button), it gives an error.

Exception in 'greenworks' handler 'load': TypeError: Cannot read properties of null (reading 'isSteamRunningOnSteamDeck')

at GreenworksDOMHandler._Load (a14447cc-e0cf-40ff-9f2b-aa57bc8182b3:137:49)

at a14447cc-e0cf-40ff-9f2b-aa57bc8182b3:25:30

at RuntimeInterface._OnEventFromRuntime (domSide.js:32:114)

at RuntimeInterface._OnMessageFromRuntime (domSide.js:30:377)

at _messageChannelPort.onmessage (domSide.js:13:68)

_OnEventFromRuntime domSide.js:32

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'isSteamRunningOnSteamDeck')

Hello! which flag is currently relevant for version NW.JS?

--ignore-gpu-blocklist or -ignore-gpu-blacklist

the chromium help says blocklist but does not specify which version the changes were made from. Has this flag changed for Nwjs?

How do I roll back the version to 225?

Script type - classic

Use worker - no

Not run just "Please wait, loading ..."

Script type - module

Use worker - no

The whole constructor breaks

I am not using scripting only events. Perhaps some plugins are the reason, but I don't have time to figure it out right now. At least it should be able to run only the 225 version on which everything worked

same. The game started once, and after that it didn't start again