Firefox - Wind Particles, Console errors
-
Windows 10 64bit
Firefox 117.0.1 (64-bit)
Wind particles not displayingErrors in console after hard refresh (ctl-F5):
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. -Rain-thunder-rain
Failed to create WebGL context: WebGL creation failed:- tryANGLE (FEATURE_FAILURE_EGL_NO_CONFIG)
- Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS) index.js:1:220152
Failed to create WebGL context: WebGL creation failed: - tryANGLE (FEATURE_FAILURE_EGL_NO_CONFIG)
- Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS) index.js:1:220177
Failed to create WebGL context: WebGL creation failed: - tryANGLE (FEATURE_FAILURE_EGL_NO_CONFIG)
- Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS) index.js:1:220152
Failed to create WebGL context: WebGL creation failed: - tryANGLE (FEATURE_FAILURE_EGL_NO_CONFIG)
- Exhausted GL driver options. (FEATURE_FAILURE_WEBGL_EXHAUSTED_DRIVERS) index.js:1:220177
Uncaught (in promise) TypeError: d(...).onopen is not a function
Y https://www.windy.com/v/39.3.3.ind.5235/plugins/gl-particles.js:1
promise callbackW/Y< https://www.windy.com/v/39.3.3.ind.5235/plugins/gl-particles.js:1
W https://www.windy.com/v/39.3.3.ind.5235/plugins/gl-particles.js:1
W https://www.windy.com/v/39.3.3.ind.5235/plugins/gl-particles.js:1
value https://www.windy.com/v/39.3.3.ind.5235/index.js:1
n https://www.windy.com/v/39.3.3.ind.5235/index.js:1
value https://www.windy.com/v/39.3.3.ind.5235/index.js:1
promise callbackvalue https://www.windy.com/v/39.3.3.ind.5235/index.js:1
a https://www.windy.com/v/39.3.3.ind.5235/index.js:1
promise callbackb/ https://www.windy.com/v/39.3.3.ind.5235/index.js:1
gl-particles.js:1:20320
Uncaught (in promise) TypeError: w is undefined
M https://www.windy.com/v/39.3.3.ind.5235/plugins/particles.js:1
value https://www.windy.com/v/39.3.3.ind.5235/plugins/particles.js:1
value https://www.windy.com/v/39.3.3.ind.5235/plugins/particles.js:1
value https://www.windy.com/v/39.3.3.ind.5235/index.js:1
promise callbackvalue https://www.windy.com/v/39.3.3.ind.5235/index.js:1
value https://www.windy.com/v/39.3.3.ind.5235/plugins/particles.js:1
paramsChanged https://www.windy.com/v/39.3.3.ind.5235/plugins/gl-particles.js:1
value https://www.windy.com/v/39.3.3.ind.5235/index.js:1
a https://www.windy.com/v/39.3.3.ind.5235/index.js:1
promise callback*b/ https://www.windy.com/v/39.3.3.ind.5235/index.js:1
particles.js:1:2016 -
Further troubleshooting...I was seeing the errors below in about:support. I temporarily changed the refresh rates of my dual monitor system to match each other (60hz) and restarted Firefox and now the WebGL stuff was working again. I changed the refresh back to default (75hz, 60hz) and tried to see if it would fail again. Of course it did not, and continued working no matter what combo was used. Go figure.
WEBRENDER_COMPOSITOR
default available
runtime unavailable No DirectComposition usage Blocklisted; failure code NVIDIA_REFRESH_RATE_MIXED
WEBRENDER_PARTIAL
default available
WEBRENDER_SHADER_CACHE
default available
WEBRENDER_OPTIMIZED_SHADERS
default available
WEBRENDER_ANGLE
default available
WEBRENDER_DCOMP_PRESENT
default available
env blocked Monitor refresh rate too high/mixed Blocklisted; failure code NVIDIA_REFRESH_RATE_MIXED
WEBRENDER_SCISSORED_CACHE_CLEARS
default available
WEBGPU
default available
runtime blocked WebGPU cannot be enabled in release or beta Blocklisted; failure code WEBGPU_DISABLE_RELEASE_OR_BETA
WINDOW_OCCLUSION
default available
HW_DECODED_VIDEO_ZERO_COPY
default blocked Blocklisted by gfxInfo
VP8_HW_DECODE
default available
VP9_HW_DECODE
default available
REUSE_DECODER_DEVICE
default available
BACKDROP_FILTER
default available
CANVAS_RENDERER_THREAD
default available
ACCELERATED_CANVAS2D
default disabled Disabled by default Blocklisted; failure code FEATURE_FAILURE_DISABLED -
@airboss001 Hi there, unfortunately we know about certain issues with WebGL, especially in Firefox browsers. They occur sometimes, but we cannot do much about them at this moment. I can only recommend using different browser to avoid this.
