LocalDB : Materials/nodes imported form LocalDB lose names.

Forums: LocalDB : Materials/nodes imported form LocalDB lose names.
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/nodes imported form LocalDB lose names.

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

itsallgoode9 Mon Nov 25, 2019 3:08 am
When I import materials from LocalDB, none of the node names are intact. Not even the top material itself has kept its name. If it was intended to work this way (which I do see reasoning for), can we have an option to keep node naming intact?

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/nodes imported form LocalDB lose names.

Postby JimStar » Mon Nov 25, 2019 7:01 pm

JimStar Mon Nov 25, 2019 7:01 pm
That feature has already been implemented some time ago, I'm just still testing it... Will be available in newer releases.
Just be aware, that if you already have same name for other DG nodes in Maya, then it will conflict with the nodes being imported. So you will anyway not get exactly the same name - it will be auto-incremented by Maya. Plus - Maya doesn't allow spaces in names (which Octane allows), so they will always be replaced by underscores.
User avatar
JimStar
OctaneRender Team
OctaneRender Team
 
Posts: 3782
Joined: Thu Jul 28, 2011 8:19 pm
Location: Auckland, New Zealand

Re: LocalDB : Materials/nodes imported form LocalDB lose names.

Postby itsallgoode9 » Mon Dec 02, 2019 4:12 pm

itsallgoode9 Mon Dec 02, 2019 4:12 pm
gotcha. Yeah that's expected for the names to change slightly, if there's already that name existing. Before it would just completely lose the name--I'd have a texture node named "Diffuse" and when I brought in my material it would switch to "octaneImageTexture4" instead of "Diffuse" or "Diffuse1" etc. Great to hear this will be fixed soon.
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

Mon May 13, 2024 10:27 am [ UTC ]