We are aware of these and we're working to get them all resolved before the time NW.js is retired.
Steam overlay doesn't appear. This is happening with the fallback (disabled in-game overlay) and otherwise.
The fallback (showing the actual Steam UI over the game rather than in-game overlay) should be working, and did last I tried. If it does not, please file an issue. As for supporting the in-game overlay, please see the section on the Steam overlay here.
OBS cannot display our webview exports. It appears as blank white screen instead of the game canvas. Streamers cannot live broadcast our games. This is a non-issue in NW.js
I can successfully capture a WebView2 export with OBS using either the display capture (suitable for a fullscreen game) or window capture with capture method Windows 10. So there do appear to be working fullscreen and windowed capture methods in OBS. If some other mode that you want to use doesn't work, it would be best to report it to OBS - it's their software and it's OBS's job to be able to capture things no matter what the app does.
Cannot be NV-Patched to seek out dedicated GPU's on the device
We're following up with GPU vendors about fixing this. If others contact them as well that would help. It's also possible to fix if the Chromium browser engine is updated to support multiple GPUs, which Google have said they want to do. It's probably also possible to fix via WebView2 and I will look in to following up there too. So there's a few avenues where this could be resolved.
Webview export uses a Microsoft service, and Microsoft collects telemetry data.
I realize I'm not a data/privacy lawyer, but WebView2 is now a Windows component, and so doesn't that just fall in to the general telemetry of the Windows OS itself? As in, if you use Windows, then you are subject to Microsoft's telemetry anyway, and the data Microsoft collect is dealt with via Microsoft's privacy policy and the agreement between Microsoft and the user, rather than your app and the user.
Hopefully as well, Ashley doesn't respond with "go contact OBS, Steam, Microsoft and AMD" because, like mentioned earlier, these are non-issues in tons of other games on Steam.
I'm afraid in some cases things are genuinely outside of our control and sometimes we do have to talk to other organisations to get things changed. The fact other games work does not mean it is possible for us to do the same thing - we have our own technologies which have their own tradeoffs. It is always a tricky problem for us when people either don't understand or don't believe us on this point: if people continue to insist we do something that is outside of our control, there is really nothing we can do. For example if there is a graphics driver bug affecting someone's game, usually we genuinely cannot fix it - the GPU vendor has to. Whether the bug affects other games is pretty much irrelevant - bugs can have extremely specific circumstances and so affect some games but not others, and the fact a different game is not affected does not mean it's feasible for us to just do the same thing as that game, which may be built using entirely different technologies.
If people co-operate and follow up with the organisations we advise, it is much more likely that these issues will actually be resolved. If you don't believe me and continue to insist we fix them, then it will make it less likely they are resolved, and much frustration may result. For this reason our Forum & Community guidelines includes:
Demanding impractical measures or infeasible solutions. If we say we can’t do something, it’s not because we don’t want to, or we’re being difficult, we genuinely can’t do everything!
Hopefully it won't come to that though.