I am doing conversion from three.js r103to three.js r128. In the same chrome browser, EXT_frag_depth and ANGLE_instanced_arrays extensions are supported if I use three.js r103, but NOT supported if I use three.js r128. It must be related to WebGlRenderer. I previously thought the extensions are only related to the hardware. Now it seemed it is related to the version of three.js as well.
WebGLRenderer now defaults to WebGL2 if available. This could be the issue. Can you try using the
WebGL1Renderer and see if that fixes it?
Yes, that worked perfectly! Thanks!
I found that WenGL2 supports both EXT_frag_depth and ANGLE_instanced_arrays by default. However, the tests “renderer.extensions.get( “EXT_frag_depth” )” and “renderer.extensions.get( “ANGLE_instanced_arrays” )” all returned “null”. So we don’t need these tests or do we have new test functions?
There is no need to request WebGL extensions which are enabled by default.