Issue metadata
Sign in to add a comment
|
Webgl 2.0 is disabled in browser settings on AMD switchable laptop
Reported by
arul.ra...@gmail.com,
Oct 17 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. enable WEBGL 2.0 in chrome://flags 2. use hardware acceleration when available in chrome ://settings 3. Override software render list in chrome://flags What is the expected behavior? Webgl 2.0 samples should be supported in the browser. What went wrong? My Chrome browser version is 61.0.3163.100 (Official Build) (64-bit) I am running Chrome browser in a Windows 10 64 bit DELL laptop. Webgl 2.0 works without any issues in Mozilla firefox browser in the same machine. I checked www.webglreport.com to check WebGL 2.0 support for my browser. The following message is displayed there. "This browser supports WebGL 2, but it is disabled or unavailable. Sometimes this is the result of older video drivers being rejected by the browser. Try updating your video drivers if possible." Webgl 1.0 works fine without any issues in the same machine. My GL_RENDERER is "ANGLE (Intel(R) HD Graphics 530 Direct3D9Ex vs_3_0 ps_3_0)" & GL_VERSION is OpenGL ES 2.0. for chrome as seen from chrome://gpu I've AMD graphics card in my machine (Amd Firepro W5130M) I am unable to make my Chrome browser use this graphics card. It always uses the inbuilt Intel card described in the above step. I made sure that, both my graphic cards are not black listed and they are upto date. Did this work before? No Does this work in other browsers? Yes Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version: Here is what I've ALREADY tried. Use hardware acceleration in chrome://settings Enabled WEBGL 2.0 in chrome://flags Enabled WebGL Draft Extensions in chrome://flags Override software render list in chrome://flags Finally tried uninstalled and reinstalled chrome browser
,
Oct 17 2017
I have already included page content from chrome://gpu/ as pdf(Chrome_GPU.pdf). Should i do it in any other way?
,
Oct 17 2017
Here's why you're falling back to D3D9: Disable Direct3D11 on systems with AMD switchable graphics: 451420
,
Oct 17 2017
arul.raj86@gmail.com, the capture you provided should be sufficient. Thanks for that.
,
Oct 17 2017
You can enable WebGL2 by running chrome with --disable_d3d11=0
,
Oct 17 2017
Note: we found in another recent investigation on such a dual-GPU Intel/AMD laptop that even after getting past the disabling of D3D11, that Chrome was still locked to the Intel GPU by the driver, and that this was by design to minimize power consumption. It may be better at this point to remove the D3D11 blacklisting for AMD switchable systems with recent drivers. I'm not sure whether the video rendering bugs seen in Issue 451420 are still present. (I think I started investigating that the last time this came up and couldn't prove whether the hardware accelerated video decoding pipeline was being taken.)
,
Oct 17 2017
Ah, found it: that blacklist entry was revised in Issue 755722 . So WebGL 2.0 should start being enabled on this machine as of Chrome 62, which is rolling out now.
,
Oct 17 2017
,
Oct 17 2017
,
Oct 20 2017
Thanks for the solution. It saved us a lot of time!!!! Disabling of Direct3D11 works on machines with AMD switchable graphics. We do have a Nvidia machine where the above solution did not work. We still face a similar problem with WebGL 2.0 context creation. I am enclosing the chrome://GPU details for the Nvidia machine.
,
Oct 20 2017
arul.raj86, does the NVIDIA machine in question happen to have NVIDIA Nsight installed? If so, try uninstalling it. If not, I'm not sure exactly what the problem is, but you could try upgrading your drivers.
,
Oct 23 2017
Wow!! It worked in Nvidia machine after uninstalling Nsight. Thanks so much for your help. On 20 Oct 2017 6:14 p.m., "jmad… via monorail" <monorail+v2.4292351161@ chromium.org> wrote:
,
Oct 23 2017
No problem. There's issue 716784 open to track the Nsight issue, although it's marked as restrict-view-google right now for some reason. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by zmo@chromium.org
, Oct 17 2017Components: Internals>GPU>ANGLE