Page 1 of 1

LocalDB: materials lose shared nodes

Posted: Mon Nov 25, 2019 3:12 am
by itsallgoode9
If, for example, you've exported a material to LocalDB that uses a single transform node to control the tiling of multiple textures in a material... when I import from local DB, each material has its own transform node instead of sharing transform nodes, like it was originally exported as. Much of the time you need multiple textures to tile at the exact same rate so this is imperative to have working properly.


Working in Maya 2019.2 and Octane plugin OctaneRender for Maya 2019.1.4-15.13 [STABLE]

Re: LocalDB: materials lose shared nodes

Posted: Mon Nov 25, 2019 6:29 pm
by JimStar
That feature has already been implemented some time ago, I'm just still testing it... Will be available in newer releases.

Re: LocalDB: materials lose shared nodes

Posted: Mon Nov 25, 2019 7:08 pm
by itsallgoode9
awesome! That's great to hear, thanks for the update.

Re: LocalDB: materials lose shared nodes

Posted: Sat May 30, 2020 5:10 am
by itsallgoode9
re: the few local DB posts around this time. A couple weeks ago, it hadn't changed.