Link to .capx file (required! If link is blocked remove the http and www parts):
Steps to reproduce:
1. Run Layout 1 in Debug using Node Webkit
2. Select full screen
3. Note - Debug : Profile : Draw Calls (for me it's approx 74%)
4. Repeat steps 1 to 3 but in a browser - draw calls show normal (for me < 1%)
I had been testing in Chrome with no problems (r163) - the display scales up from 450 to 1080 with smooth 60 fps. When tested on Node Webkit significant stuttering was observed due to poor display refresh rate. A little investigation showed that Node was using up a lot of resource making the draw calls. Is this a Node Webkit bug or is it a bug in C2? I did a search of the forums and couldn't find any other reports of something like this.
Node Webkit should perform the same as the Chrome browser - smooth 60 fps when scaled up with such a simple layout.
Internet Explorer: no
Operating system & service pack:Windows 7 family edition
W7 SP1 x64