LocalDB: materials lose shared nodes

Forums: LocalDB: materials lose shared nodes
Sub forum for bug reports

Moderator: JimStar

Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)

LocalDB: materials lose shared nodes

Postby itsallgoode9 » Mon Nov 25, 2019 3:12 am

itsallgoode9 Mon Nov 25, 2019 3:12 am
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]
Intel i7-3930K, 64gb RAM, Asus X79 Deluxe mobo, 2x EVGA 780 6gb (for rendering), 1x PNY quaddro k4000 (for display)
Windows 8.1 x64, Maya 2014, Octane Render v2
itsallgoode9
Licensed Customer
Licensed Customer
 
Posts: 885
Joined: Thu Apr 03, 2014 9:04 am
Location: New York City

Re: LocalDB: materials lose shared nodes

Postby JimStar » Mon Nov 25, 2019 6:29 pm

JimStar Mon Nov 25, 2019 6:29 pm
That feature has already been implemented some time ago, I'm just still testing it... Will be available in newer releases.
User avatar
JimStar
OctaneRender Team
OctaneRender Team
 
Posts: 3784
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Re: LocalDB: materials lose shared nodes

Postby itsallgoode9 » Mon Nov 25, 2019 7:08 pm

itsallgoode9 Mon Nov 25, 2019 7:08 pm
awesome! That's great to hear, thanks for the update.
Intel i7-3930K, 64gb RAM, Asus X79 Deluxe mobo, 2x EVGA 780 6gb (for rendering), 1x PNY quaddro k4000 (for display)
Windows 8.1 x64, Maya 2014, Octane Render v2
itsallgoode9
Licensed Customer
Licensed Customer
 
Posts: 885
Joined: Thu Apr 03, 2014 9:04 am
Location: New York City

Re: LocalDB: materials lose shared nodes

Postby itsallgoode9 » Sat May 30, 2020 5:10 am

itsallgoode9 Sat May 30, 2020 5:10 am
re: the few local DB posts around this time. A couple weeks ago, it hadn't changed.
Intel i7-3930K, 64gb RAM, Asus X79 Deluxe mobo, 2x EVGA 780 6gb (for rendering), 1x PNY quaddro k4000 (for display)
Windows 8.1 x64, Maya 2014, Octane Render v2
itsallgoode9
Licensed Customer
Licensed Customer
 
Posts: 885
Joined: Thu Apr 03, 2014 9:04 am
Location: New York City

Return to Bug Reports


Who is online

Users browsing this forum: No registered users and 1 guest

Tue Jun 04, 2024 10:00 am [ UTC ]