> > I think the screen recorders are fine ane Construct 2 is the problem. If the youtubers can record any game from other engines than that means Construct 2 is the problem. If Construct 2 developers don't want to fix the problem, then just say so. Stop with all the excuses already , everything can't be someone elses fault.
> It doesn't work like that. Construct 2 relies on NW.js to have your game working on PC. Try exporting as HTML5 and testing if it works in Firefox or Chrome. If it does, then the problem is NW.js.
> NW.js is not made by Scirra but everytime something breaks on it, they take it to the developers of NW.js. Still it is faster if you just go to https://github.com/nwjs/nw.js/issues and create a new issue there so the bug is looked at by people who actually work in NW.js.
But Ashley said it was the screen recorders that was the problem. The screen recorders are not the problem. I just notice lately everytime something doesn't work or breaks, its not Construct 2 problem. Whether its this, Steam or Kongagrate its always someone elses fault.
I feel the same way sometimes but it is indeed not Scirra's fault. They just rely WAY too much on third-party applications and if something breaks on their end there's nothing they can do.
NW.js is just a port of Chrome. If the game records well on Chrome and not on NW.js, it's NW.js fault.
If you want to test it you could grab the code for any HTML5 game NOT made in C2 yourself and compile with NW.js. If it does work with this game and not with a game made in C2, then it's C2's fault and you should fill a bug report.
This happens with every engine. If you buy a plugin for Unity and it doesn't work with a new Unity update, who has the fix it? The Unity team or the plugin creator? The same applies here.