Hi,
Last time I've had this problem with windows 7 but I'm experiencing the same issue on multiple PCs with windows 10, now.
A while back, I've updated the windows 7 PC that didn't support WebGL2 to windows 10 but it didn't solve the issue.
It took a clean install of windows 10 to solve this issue.
However, I've got another PC, also with a clean install of window 10, that still doesn't support WebGL 2.
Same issue as last time, ANGLE uses DirectX 9, despite up to date GPU drivers:
WebGL2 works in firefox if I disable ANGLE but I couldn't find a way to get it to work in chrome.
Using --use-gl=desktop falls back to GoogleSwift renderer, instead.
It's probably been discussed already but do we really have to use ANGLE if a system is capable of using OpenGL?
I'd love to adopt WebGL 2 but it's hard to gain confidence in it if it doesn't even work on my own machines,
let alone machines of my users.
On 06/10/2017 14:41, Jamie Madill wrote:
I don't think this has already been mentioned: a large proportion of Chrome users are stuck on D3D9 because they are missing a key Windows 7 platform update. See below links.
The platform update installs DXGI 1.2 which allows surface sharing between processes. Without this ANGLE can't render to the window handle that is owned by a different process.
See https://msdn.microsoft.com/en-us/library/windows/desktop/jj863687(v=vs.85).aspx and https://support.microsoft.com/en-ca/help/2670838/platform-update-for-windows-7-sp1-and-windows-server-2008-r2-sp1 .
I don't have numbers on-hand, but this is a pretty large number of D3D9 users, particularly if you have a good card and new drivers on Windows 7. You will see some messages about falling back to D3D9 at the bottom of about:gpu if you fall into this category. The good news is you can install the update and then D3D11 should work.
Also of particular interest to developers - installing NVIDIA Nsight will cause Chrome to fail D3D11 initialization currently due to a conflict with the sandboxing of the GPU process.
On Fri, Oct 6, 2017 at 4:57 AM, Markus Schütz <markus_schuetz@gmx.at> wrote:
I just noticed that my PC does indeed use ANGLE with D3D9. (windows 7)
That means I have a 1080 with the latest drivers but WebGL2 still doesn't work.
I could try to install a new version of DirectX myself but that doesn't fix the potentially large number
of users that also have WebGL2 compatible hardware but old D3D drivers.
On 17.06.2017 11:27, Florian Bösch wrote:
On Sat, Jun 17, 2017 at 3:30 AM, Kenneth Russell <kbr@google.com> wrote:
On Thu, Jun 15, 2017 at 10:16 PM, Florian Bösch <pyalot@gmail.com> wrote:
On Fri, Jun 16, 2017 at 1:57 AM, Kenneth Russell <kbr@google.com> wrote:
Looking at Chrome's internal statistics, about 30% of Chrome users are stuck at Shader Model 3.0, implying that they're using ANGLE's Direct3D 9 backend. WebGL 2.0 requires Direct3D 11.
Do you redistribute the DirectX runtime with Chrome? Here's what games typically do: https://www.junkship.net/News/2012/11/06/how-to-properly to get around the "old DirectX version" problem.-distribute-directx-in-an-inst aller
I'm not sure -- I think we redistribute the D3D compiler but not the runtime.
It's possible the number of people that only have the (system install) D3D9 but do have D3D11 compatible hardware is significant.