Question by Essential · Jan 20, 2013 at 02:36 AM · texture material performance

Computing required to assign pre-existing material

I have a menu system that has a series of pushable buttons — only one can be selected at a time, so previous selections are de-selected.

I'm just wondering… if I use a for loop to go through each object and basically assign the default 'non-pushed' material to each button, only changing it to the 'pushed' material for that selected button, would it be a waste of resources to be re-assigning the material to all the other buttons even if they already have that material applied? Or would the CPU ignore it?

0 Show 2

robertbu · Jan 20, 2013 at 04:53 AM 1

You can just reassign the texture rather than reassign the whole material.

renderer.material.texture = texNew;

I doubt there are performance issues with either way of changing the look.

Essential · Jan 20, 2013 at 09:42 PM 0

Hadn't considered just changing the texture, thanks for the tip. (Although I believe it's material.mainTexture, rather than just material.texture).

It seems to be working alright, hopefully there's no noticeable slowdown.

Unity Answers is in Read-Only mode

Unity Answers content will be migrated to a new Community platform and we are aiming to launch a public beta on June 13. Please note, Unity Answers is now in read-only so we can prepare for the final data migration.

For more information and updates, please read our full announcement thread in the Unity Forum.