[BUG] material setting order, possible Bug?

Hey bennetherwood -

It actually would be more performant to have a few additional instructions in a single material versus completely new material which has not been loaded into memory yet. In either case you are adding shader instructions.

We’ve spent time looking at your blueprints and it definitely is an issue with the order of operations of the array set and call, but we’ve not been able to determine where that order breaks.

Eric Ketchum