How do I determine what GPU is being used for NW.js?

I have a dual gpu in my laptop that's supposed to switch to a dedicated Geforce chip for gpu-hungry apps, but I suspect NW.js is always using the integrated chip. There's an easy way to tell in Chrome with "chrome://gpu" so is there anything like that for NW.js too?

https://github.com/nwjs/nw.js/wiki/Extr ... -about-gpu

Did not understand but seems to be exactly what you actually want

Thanks! I found out I can just open nw.exe from the install folder and type in chrome://gpu there. And I see it sticks to using intel integrated no matter what I try to override it. Balls.

There's no doubt quite a few people with this dual-gpu thing in their laptops out there, and if those computers refuse to switch to the dedicated GPU for NW.js apps then that's a performance problem. I guess there's not much we or Scirra can do about that?

http://steamcommunity.com/app/242920/di ... english#p1 may or may not be related, I wonder if the user can choose himself which gpu to use, I did remember in the past that some computer prevented being able to choose it for chrome for reasons unknown to me.

I have a dual-GPU laptop and it appears to be able to switch GPU OK, it depends on the vendor's own control panel settings though, which can be a bit fiddly or confusing.

I found this:

http://superuser.com/questions/645918/h ... rd-optimus

[quote:3b9l7d3x]According to NVIDIA, chrome and firefox both have been disabled from using the Nvidia GPU by design.

[quote:3b9l7d3x]new nvidia drivers allow running with nvidia gpus, but you still have to run chrome with

--disable-gpu-driver-bug-workarounds

parameters. otherwise backend always uses intel gpu. you can check this on

chrome://gpu

page and see for yourself.

Changing the flag worked great, hopefully I'm not disabling some important bug-workarounds in the process <img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz">

My advice: have some shortcuts of your game inside a subdirectory to deal with those situations on a case by case basis.

I think that post is out of date and nVidia allowed support for high-performance GPU in browsers eventually. Still, the next version of C2 has a new "rendererDetail" expression which in Chrome and IE can return the renderer hardware info e.g. "NVIDIA GeForce GTX 660", which should make testing this easier.

( Beginner Question) Does that also work with NW.JS ?

NW.js basically is Google Chrome, so yes.

that's what I thought. thanks Ashley

I think that post is out of date and nVidia allowed support for high-performance GPU in browsers eventually.

Yep, still it's good to have a solution for people with old-ish dual gpu's.

Still, the next version of C2 has a new "rendererDetail" expression which in Chrome and IE can return the renderer hardware info e.g. "NVIDIA GeForce GTX 660", which should make testing this easier.

That'll come in handy, thanks!