Thanks for your answer! I wonder why this problem hasn’t been adressed before. I understand the connection with the design concept of component definitions. But even in the non-api world, this concept has significant drawbacks for very simple use cases: If you have e.g. a simple wall component, add a brick texture to it and want to reuse it, scale it to a different length for example, it won’t work nicely. I think it is a design flaw, that there isn’t an api/nonapi way to prevent textures which are applied to a group/definition/instance from getting transformed/scaled with the component instance.