WebGL on Chrome not using the right 3d card, ignoring app settings
Reported by
rachid.e...@gmail.com,
Dec 7 2017
|
|||||
Issue descriptionChrome Version : 62.0.3202.94 OS Version: 10.0 URLs (if applicable) : http://webglreport.com/?v=2 Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari: NA Firefox: OK (version 57) IE/Edge: NA What steps will reproduce the problem? 1. run the webglreport and read the setting for unmasked renderer 2. on Firefox I get: ANGLE (NVIDIA GeForce GTX 1070 Direct3D11 vs_5_0 ps_5_0) 3. on Chrome: ANGLE (Intel(R) HD Graphics 630 Direct3D11 vs_5_0 ps_5_0) What is the expected result? I set the chrome app in the NVidia control panel to use the GeForce. What happens instead of that? Chrome picks the integrated graphics card Please provide any additional information below. Attach a screenshot if possible. This is causing 20x slowdown on my webgl renderer between chrome and firefox I am using and verified WebGL 2.0 context on both UserAgentString: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36
,
Dec 13 2017
,
Dec 15 2017
,
Dec 15 2017
I am not sure at App level we can select which GPU to use. If NVidia control panel fails to work, this should also be reported to NVidia. In the meantime, please provide the about:gpu page content.
,
Mar 8 2018
No feedback from original reporter. Mark as WontFix. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by sc00335...@techmahindra.com
, Dec 12 2017