Why WebGL 1.0 in Electron for Windows

Questions
1

image
image1920×1080 159 KB

These weird texture crops happen in WebGL1, but I thought that would never be used when delivering your own Chrome package with Electron.

But I still see it in the wild, how can this be?

Windows NT 10.0; renderer: Google Inc. (Intel) ANGLE (Intel, Intel(R) HD Graphics Direct3D9Ex vs_3_0 ps_3_0, igdumd64.dll) WebGL 1.0 (OpenGL ES 2.0 Chromium)

it also happens rarely on Firefox/Windows:
renderer: Google Inc. (Intel) ANGLE (Intel, Intel(R) HD Graphics Direct3D11 vs_4_0 ps_4_0), or similar WebGL 1.0

2

what crop?

One rule of thumb is to always have power of 2 textures for webgl1

3

right, I fixed it by disabling mipmaps on webgl1, then the crops are normal.

I’m still curious how it can be that webgl2 is not supported on Windows 10 with a modern Chrome. In which layer is this not supported?

(these are the weird crops I’m talking about, on dynamic textures + mipmaps)
image

4

That is a good question :slight_smile: Are you running into a webview? because on some win10 the webview is still using IE11

5

it’s Electron, so I’m pretty sure it’s always Chrome (120 in this case).
It’s a bit of a mystery, but fortunately only a small minority.

6

this is weird then…i don’t see how Chrome will revert to webgl1