Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • $\begingroup$ I like what you tried to do with the object data property, but there’s no way to use a different object data property with each object for the same material, unless you did some stuff with attribute storing in geometry nodes, perhaps. $\endgroup$
    – TheLabCat
    Commented May 23 at 13:44
  • $\begingroup$ I don’t think there’s any way around having some kind of duplication, either different materials or different mesh data blocks with different UV maps. $\endgroup$
    – TheLabCat
    Commented May 23 at 13:45
  • $\begingroup$ instead of a driver use an Attribute node set to object, and plug the output of the attribute into the mix factor of a Mix RGB node. Use 2 different image texture nodes $\endgroup$
    – Gorgious
    Commented May 23 at 13:55
  • $\begingroup$ Does this answer your question? Using independently two values of two object that share the same material. This is a very similar subject and there are different methods in the answers. One of them might be applicable for your problem. @TheLabCat Why is there no way? There are different ways. $\endgroup$ Commented May 23 at 16:21
  • $\begingroup$ @GordonBrinkmann This can be a solution only if there are 2 textures, maximum 4. But what to do if there are a lot of textures and it is unknown how many there are? It will be very inconvenient and very expensive $\endgroup$
    – notgrilbi
    Commented May 24 at 13:35