Hello I am using the threejs r131.It gives the error message mapTexelToLinear: no matching overloaded function found But I change threejs r131 to threejs r111. The demo normal I haven’t found the reason The code is a little messy because it is temporary demo ShaderDemo ThreejsR111 ShaderDemo …

Threejs r111 it normal but threejs r131 it error Using shaderMaterial.error:'mapTexelToLinear' : no matching

Mugen87 September 6, 2021, 8:44am 10

Try adding the new normal_pars_vertex, normal_pars_fragment and normal_vertex shader chunks to your custom shader. These chunks were introduced with r132. Update your code similar to the respective PR:

2 Likes

Upgrading three.js from 131 to 132 causes error in fragment shader for ShaderMaterial

Topic		Replies	Views
Upgrading three.js from 131 to 132 causes error in fragment shader for ShaderMaterial Questions shaders	6	4460	September 11, 2021
Need help with color space using a custom fragment shader Questions shaders , fragment-shader , color , color-space	1	997	May 5, 2023
Shader Error 0 - VALIDATE_STATUS false Questions materials	3	876	June 25, 2023
Making mapTexelToLinear work with rendertarget texture Questions post-processing , shaders	4	1171	June 12, 2021
Issue with splatmap shader? Questions shaders , shader-material , fragment-shader	5	1139	May 28, 2020

Threejs r111 it normal but threejs r131 it error Using shaderMaterial.error:'mapTexelToLinear' : no matching

Related Topics