TheRealDannyyy, thanks for the reply,
I just released a game in alpha stage on itch.io and found jerkiness problems with the Node Webkit export.
https://nabu.itch.io/ultimate-barbarian
Heres my specs :
- NW.js 0.20.0, the last one
- I7 3630QM 2.40 GHz
- GeForce GTX 660m
- OS is Windows 7 SP1
The game has 20 to 200 sprites on screen with about 100 average, and some shaders. The stutters occurs about every second whatever happen on screen, in cpu intensive times or not. Average CPU usage is 30%, up to 50% some times, with less than 10% for the engine and the same for draw calls, the rest being logics. The preview under Chrome and HTML5 export works smooth on various browsers. Only NodeWebkit export is jerky.
I found the stutters are almost invisible running the application with my Intel integrated graphic card 4000, although a lot more visible and annoying with the GTX 660m.
I also tested the game exported with NW.js on a low end computer and it worked well and smooth.
This is a very common with NV graphics on laptops. NV's drivers detect "browser" and puts the GPU into idle mode to save power usage. It's very aggressive, resulting in very low power for browsing. But because C2/NWjs is Chromium based, it thinks our games are browsers..
This can be fixed (in the past, not sure now) by setting a power profile in windows or NV's control panel to "Maximize performance" instead of "Balanced" or the default option.
Exceptions or game-specific profiles can also be made with the NV control panel.