Shader.SetGlobalColor works but Material.SetColor doesn't when working with custom shaders

[janine]

Hi @abliss86, welcome back to the community!

One initial guess I have for your situation has to do with how materials are handled in a given Cesium3DTileset. Each tile mesh has its own material, and thus its own shader parameters, so changing a value on the tileset’s opaqueMaterial will not propagate the changes to any existing tiles. Here’s an older thread with a similar situation that might be helpful for your use case:

Shader for Cesium World Terrain

Hi @MutterOberin, I’m not sure what you mean exactly. Can you describe what you’re trying to accomplish? Each tile has a copy of the “Opaque Material” (made using Object.Instantiate), and the tile provides its own information using the material parameters. For example, glTFs with different textures will set those texture parameters on its copy of the material. In other words, tiles do not share the same instance, they each contain a separate copy. So at runtime, if you wanted to change the ma…

If this looks to be different from what you’re talking about, though, it would help if you provided a minimal example for us to reproduce so we could observe that behavior. I admit I’ve never tried to use the Shader.Set___ approach with the tileset material. Perhaps other community members can chime in with their experience?