I have a sample react project using three.js. I recently upgraded three.js from v0.131.3 to v0.132.2 and received an error in my fragment shader. I suspect it is due to the recent removal of Blinn Phong support. I created a minimal reproducible repo at GitHub - kimbaudi/threejs-test . If you clone t…

Thanks for your response. I removed normal_pars_vertex and normal_vertex from the fragment shader (shader.frag) and added it to the vertex shader (shader.vert). Now I am getting a different error from shader.frag: Program Info Log: Fragment shader is not compiled. FRAGMENT ERROR: 0:459: 'getDire…

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

Questions

Mugen87 September 10, 2021, 7:49am 3

Please use the solution from: Threejs r111 it normal but threejs r131 it error Using shaderMaterial.error:'mapTexelToLinear' : no matching - #10 by Mugen87

Topic		Replies	Views
Threejs r111 it normal but threejs r131 it error Using shaderMaterial.error:'mapTexelToLinear' : no matching Questions glsl , materials , shader-material	7	2442	September 6, 2021
Need help with color space using a custom fragment shader Questions shaders , fragment-shader , color , color-space	1	981	May 5, 2023
Shader Error 0 - VALIDATE_STATUS false Questions materials	3	859	June 25, 2023
Issue with splatmap shader? Questions shaders , shader-material , fragment-shader	5	1132	May 28, 2020
Fragment shader is not compiled Questions environment-map	4	1382	October 19, 2022

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

Related Topics