Extended meshBasicMaterial does not have access to cameraPosition uniform about three-customshadermaterial HOT 3 CLOSED

I've looked into it. Unfortunately, the fix is not as simple as just setting isShaderMaterial to true, being a ShaderMaterial means the WebGLRenderer handles the material differently in terms of creation, disposal and caching. The main issue being that the pre-build shader IDs are hardcoded into the renderer here:
https://github.com/mrdoob/three.js/blob/74939a623cf06ef68b6eb3e2c66f36d127f8bd1a/src/renderers/webgl/WebGLPrograms.js#L20

This means that setting isShaderMaterial runs some code ment for ShaderMaterial and some code meant for baseMaterial. Reuslting in things breaking.

I think the best thing for CSM is to simply pretend to be its baseMaterial all the way through. It is a shame ThreeJS doesnt have a first class system for material extentions but this is the best were going to get for now.

You can also pass in the uniforms you need manually and use them as needed

from three-customshadermaterial.

Thanks for looking into it @FarazzShaikh. The good news is that there are plenty of workarounds but I wanted to file in case it helped to improve CSM.

Appreciate it!

from three-customshadermaterial.

Appreciate you using it! Glad to look into any possible improvements 😄

from three-customshadermaterial.