Could you have multiple go.property() definitions? One per texture that can be set on the model. And at run-time you select the go.property() that matches the external info you mentioned.
1 Like
Thank you for your reply. I could do that yes, and at first it would be fine (around 20 textures). But additional texture variants (color packs) would increase this number substantially (potentially in the hundreds). Having 100+ lines repeating the same statement but with a different texture string seems very inefficient but I’m sure there is a back end reason why you cant just easily change the value just like any other property. I guess I can try it this way while the number of textures is relatively small, and deal with the increasing textures later.
1 Like