Curious about this statement, could you elaborate further?
textures to be usable on all objects.
What kind of limitations are you experiencing? What would be ideal to you? I wonder if this related to a number of the issues I’ve run into:
- An attempt to abstract tiling textures as material instances doesn’t feel like the right solution. It isn’t scalable or ideal (even prompting runtime efficiency warnings when applied as overrides).
- TextureData seems more ideal, and is widely adopted and a standard workflow component for the game / platform. But is only applicable to pre-existing content since there isn’t a prop / architectural material we can instance for custom content.