Electron uses the same browser engine as NW.js. I don't know why it would work differently with screen recorders - perhaps they disable the GPU process, which might degrade performance. You can do that with NW.js anyway if you pass the --in-process-gpu flag. Still, as I said before, it's a bug in the screen recording software if it can't record your screen.
BTW the latest C3 releases include the Game Recorder object which has a built-in screen recording feature... which always works!
I don't understand how you still can't understand the issue... I'll try to make myself even more clear (let's hope)
- NW.js had several issues for capture the window with STREAMING softwares, such as OBS, XSplit etc..
- So now maybe you may get why, I don't care about this "built it Recording" whatever that is. Why the hell should I force Streamers and youtubers to record with that thing, when they're used to do the same with their tools, do you really think they would even bother trying to find a solution as it's not on their end? I don't think so.
- I've contacted support, here, for OBS, XSplit, and even forwarded that to the NW.js team, no one seems to care at all.
- Issue is, that window can't be capture, doesn't matter what you try to do, yes, "--disable-gpu-compositing" was working but it's also heavyly reducing performance of the game itself (the arg you mentioned didn't work on my end) to a point that's, it's absolutely unplayable for the type of game I'm making (which is a rhythm game, and every frame is god damn important)
- I see you coming, no, there's no optimization problem, since I made a test batch on my game with more than 25+ different PC configurations, from very low end hardware / refresh rate to the highest ones, absolutely 0 problems noticed so far.
- I'm sorry but Electron seems to be different somehow as, without doing anything, I've got better performances according to my tests and this issue is gone, alongside the other one linked to your official Greenworks plugin, working yes, to unlock achievements, but also absolutely incomplete in term of features (you just have to look at the documentation to see how much features it's missing). But my main problem with Greenworks wasn't the lack of features and such, as I could have workaround, what I couldn't workaround was the Overlay absolutely not working at all, switched to Electron, stopped using your plugin and magic, it's all working again.
So yes, as I'm saying, I'm pretty sure having a secondary option to build on Windows won't be luxury.
The more choice you'll give to people, happier they'll be (and I know how much work it does represent, but why don't you come over the Community Discord and ask "Armaldio" which is the guy working on that Electron builder for Construct 2/3? I'm pretty sure he'd be happy to help)
Sorry if my message sounds harsh, but I'm tired of explaining the same thing over and over, when it's absolutely clear that there's an issue, somewhere in NW.js, and it's not recording software's fault as it's working god damn fine with Electron, which according to you "is the same".