r115 -> r118 breaks extensions derivatives

Description of the problem

Just upgraded my project from r115 to r118 (mainly to exploit the VAO support). My shaders fails compiling due the use of dFdx|dFdy.

The GL_OES_standard_derivatives doesn’t seems to be loaded, even though I have:

  extensions: {
    derivatives: true,
  },

Is the syntax changed or something?

Three.js version

• Dev
• r118
• …

Browser

• All of them
• Chrome
• Firefox
• Internet Explorer

OS

• All of them
• Windows
• macOS
• Linux
• Android
• iOS

Hardware Requirements (graphics card, VR Device, …)

[Mugen87]

Since GitHub was down for some time, we discussed this issue via Twitter PMs.

Fiddle demonstrating the issue: https://jsfiddle.net/yph50ntu/ Fixed fiddle: https://jsfiddle.net/s8um05ev/2/

Since r118, three.js uses a WebGL2 rendering context by default. The engine tries to convert existing GLSL 1.0 code to GLSL 3.0 as good as possible but only for built-in materials or custom shader code base on ShaderMaterial. There is no such conversion for RawShaderMaterial.

So the solution was to just convert your shader code to GLSL 3.0. Another possibility is the usage of WebGL1Renderer which would solve your issue without refactoring of shader code.

Keep in mind that extensions like GL_OES_standard_derivatives are enabled in WebGL 2/GLSL 3.0 by default so it’s not necessary anymore to enable it manually.

[luruke]

@Mugen87 , thanks makes sense. In my case I will just force WebGL1.