Hi everyone,
I run ZennoPoster 7.9.1 on Windows 11 with an Intel Iris Xe GPU.
Some context on what I built: I got tired of guessing whether my profiles were clean, so I wrote a local HTML audit page that runs inside the profile itself, right after the instance starts. It reads about 120 fingerprint values — WebGL, WebGPU, canvas, audio, fonts, Client Hints, Worker parity, shader precision — and runs 49 hard-fail checks and 71 weighted warnings against them. It hands the result to a C# cube that keeps a blacklist of used fingerprints so no two profiles ever share one. That's how I caught this.
The problem:
In Run Instance I have both boxes ticked:
Despite that, WebGL alternates between two renderers on the same machine:
ANGLE (Intel, Intel(R) Iris(R) Xe Graphics (0x00009A49) Direct3D11 vs_5_0 ps_5_0, D3D11)<br>ANGLE (Microsoft, Microsoft Basic Render Driver (0x0000008C) Direct3D11 vs_5_0 ps_5_0, D3D11)
I restarted three times in a row and got Basic Render Driver all three times.
Here's the part that rules out a driver problem: at the exact same moment, navigator.gpu.requestAdapter() still returns intel. So the GPU is available to the system — only WebGL fails to initialize on it and Windows hands back WARP (software rendering).
Basic Render Driver is one of the loudest bot signals there is. Any profile that gets it is burned before it does anything.
Questions:
I run ZennoPoster 7.9.1 on Windows 11 with an Intel Iris Xe GPU.
Some context on what I built: I got tired of guessing whether my profiles were clean, so I wrote a local HTML audit page that runs inside the profile itself, right after the instance starts. It reads about 120 fingerprint values — WebGL, WebGPU, canvas, audio, fonts, Client Hints, Worker parity, shader precision — and runs 49 hard-fail checks and 71 weighted warnings against them. It hands the result to a C# cube that keeps a blacklist of used fingerprints so no two profiles ever share one. That's how I caught this.
The problem:
In Run Instance I have both boxes ticked:
- Enable GPU hardware acceleration for processing animations
- Use GPU. Required for using WebGL
Despite that, WebGL alternates between two renderers on the same machine:
ANGLE (Intel, Intel(R) Iris(R) Xe Graphics (0x00009A49) Direct3D11 vs_5_0 ps_5_0, D3D11)<br>ANGLE (Microsoft, Microsoft Basic Render Driver (0x0000008C) Direct3D11 vs_5_0 ps_5_0, D3D11)
I restarted three times in a row and got Basic Render Driver all three times.
Here's the part that rules out a driver problem: at the exact same moment, navigator.gpu.requestAdapter() still returns intel. So the GPU is available to the system — only WebGL fails to initialize on it and Windows hands back WARP (software rendering).
Basic Render Driver is one of the loudest bot signals there is. Any profile that gets it is burned before it does anything.
Questions:
- Is there a limit on how many simultaneous instances can use GPU acceleration? What is it?
- What makes ANGLE fail to create the D3D11 device and fall back to WARP?
- Is there a command-line argument to force D3D11 and fail instead of silently falling back to software?
- Has anyone solved this by lowering thread count, changing drivers, or not running through RDP?