This looks strongly like a color space issue, but I think the use of a custom “ShaderColor” class instead of THREE.Color is likely to make a solution rather more complex. For details (and how to opt-out of color management, if you prefer) at:
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Strange differences between different three.js versions | 6 | 2173 | December 22, 2017 | |
Shader stop working with ThreeJS update | 5 | 727 | September 29, 2020 | |
After migration from version 0.92.0 to 0.130.0 object materials looks different! | 5 | 511 | August 14, 2021 | |
I cannot show as expected color after upgrade to r118 from r110 | 6 | 1114 | July 22, 2020 | |
Threejs r111 it normal but threejs r131 it error Using shaderMaterial.error:'mapTexelToLinear' : no matching | 7 | 2809 | September 6, 2021 |