This means that if there are multiple scripts affecting the renderer through material property blocks, they will be interferingВ with each other.

If your new property block doesnвЂ™t hold a value that was present before, that value will be reset. Job done! However, it is important to note that setting a property block on a renderer overwrites any other data set by property blocks on that renderer. Using renderer.SetPropertyBlock(), we can apply our new values to the renderer. The MaterialPropertyBlock class is nothing more than a plain C# class that holds keys and values вЂ“ the keys being the shader property names, and values whatever you wish them to be. SetColor() to write a shader property to a MaterialPropertyBlock. LetвЂ™s start with the second line first: we use. it hides the property from the material inspector to signify that it will be different per renderer. If you like, you can add in front of the attribute. Just create a new вЂњStandard Surface ShaderвЂќ from the вЂњCreateвЂќ menu in the project tab. If youвЂ™re not yet familiar with writing shaders, donвЂ™t fret вЂ“ you donвЂ™t need to be. First of all, you need to create a custom shader. Now thatВ you have seen the value of this technique, itвЂ™s time to get to its implementation. YouвЂ™ll also be happy to know that the memory usage is back to what is when using a single, stationary material, since all spheres are in fact using that same material. See how that thick band of highlighted green has become naught but a sliver. If thatвЂ™s not a win, I donвЂ™t know what is. See that? 0.01 millis for the same effect.

Say hello to MaterialPropertyBlocks! This is the profiler for the exact same scene, but using the aforementioned technique instead of renderer.material. Take a look at the CPU profiler when animating the 2500 materials using renderer.material:ДЎ5.19В of your precious millis are gone! IвЂ™m sure you would like to have them back so you can put them to good use elsewhere. Time to get to the meat of the issue: there is also a significant CPU overhead to uploading material changes to the GPU. 6 MB might not seem like much in a world of many gigabytes of memory, but itвЂ™s still a very sizable increase! However, I can feel your judgmental stares вЂ“ surely you havenвЂ™t been reading this far for just a few megabytes more memory. Now, this is what the memory profiler looks like when using renderer.material:ДЄs expected, we have created 2500 materials. Of those 40 materials only one is for our spheres, the others are stuff like the default material for the plane, the skybox, etc. Notice how thereвЂ™s just 40 materials in the scene, requiring a manageable 47 kB. This is the memory profiler when all spheres are using a single, stationary material: This means that there are potentially a lot of material copies out there, all eating memory. This copy is henceforth used for that renderer 1.

Because of this, Unity creates a copy of a material when you access renderer.material for the first time (unless that renderer is already the only one using that material). The problem with this is that in order to change the color in the shader, Unity needs to tell the GPU that this object is going to be rendered differently, and the only way it can do so is by changing the material instance. Д®asy, right? Just grab that color and animate away.

Change material color ui unity