Closed dpotekhin closed 7 years ago
I also met this bug on Chrome Version 54.0.2840.71 m (64-bit) Creating new THREE.WebGLRenderer() will return an error
three.js:19184 Uncaught TypeError: Cannot read property 'getExtension' of null(…)
get @ three.js:19184
WebGLRenderer @ three.js:19609
(anonymous function) @ VM313:1
Sounds like Chrome blacklisted that GPU...
Do you see the cube in https://get.webgl.org/?
How about in Firefox?
In IE11 and FF49 WebGL works fine. Only Chrome can't detect it in most cases: http://prntscr.com/cziwmc ( include https://get.webgl.org/ ) But I noticed, that examples with disabled antialiasing are working: http://prntscr.com/cziu5m
Sounds like it's a Chrome issue then.
No, @mrdoob, it is actually ours, the poor users, issue. Chrome is doing well being #1 browser and has no issue with just giving 🖕 to all people with old GPUs.
I am now hit by this shit and can no longer use chrome for webgl related work. In case anyone knows how to lift the GPU ban short of patching and recompiling Chrome, let me know.
Ok, I am overreacting here, as always.
/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --ignore-gpu-blacklist
Annoying, but can work.
Had the same error in Chrome Version 55.0.2883.95 (64-bit) - Mac 10.9.5 and I can confirm toggling flag 'Override software rendering list' solves the issue.
(* This section is for bug reports and feature requests only. This is NOT a help site. Do not ask help questions here. If you need help, please use stackoverflow. *)
Description of the problem
With new Chrome (54.0.2840.71 m) WebGL content on my configuration (Win7 + GTS250) starts to throw exception:
THREE.WebGLRenderer: Error creating WebGL context.
And Detector.js doesn't see WebGL context on my computer.Meanwhile, there's no exception and renderer works properly if I activate it without antialias parameter.
How is it possible? WebGL doesn't detected but working?
Three.js version
Browser
OS
Hardware Requirements (graphics card, VR Device, ...)
nVidia GTS250