Page 1 of 1

Render Settings Corrupted

Posted: Thu Apr 04, 2019 12:06 am
by blastframe
A. Windows 10
B. GeForce GTX TITAN Black (compute model 3.5)
C. 64GB
D. 24.21.13.9882
E. OctaneRender 4.02.1
F. OctanePlugin 4.00 - 13.19
G. Maya 2018.5, Cut ID: 201811122215-49253d42f6

Hello,
I am not able to edit the Octane Settings from Maya's Render Settings window. Instead, I see this:
octane_renderSettings.PNG
Some history:
I copy and pasted an object with Octane nodes into my scene. I was getting an error about a duplicate Sky node, so I turned off DAG Objects Only in the Outliner and found the duplicate octaneSettings node, which I deleted. My Render Settings, however, are still broken. In new scenes, the Render Settings are correct, but when I import my character, they break again.

Can I restore any broken Settings node links with Octane plugin? Or was this caused by something else perhaps?

Any help towards a fix would be tremendous, thank you.

Re: Render Settings Corrupted

Posted: Thu Apr 04, 2019 1:58 am
by JimStar
Most likely this happened because you had deleted the active render settings node (which must never be done), instead of the duplicate one... The plugin will not function correctly without its settings node, so the broken UI is just one of all the possible problems you get if you delete the active settings node.
Could you give me the scene you have trouble with, and the exact step-by-step description of what you do when this happens?..

Re: Render Settings Corrupted

Posted: Thu Apr 04, 2019 3:35 pm
by blastframe
Hi Jim,
Thank you for the quick response. I hadn't (intentionally) deleted any Settings nodes prior to seeing the Render Settings error.

I have attached the scene file with the broken Render Settings. I had to delete the character rig from it, but left the nodes.
BrokenSettings.zip
(392.7 KiB) Downloaded 213 times
I tried replicating the error by importing one Maya scene to another, but the Octane Render Settings still work. I'm not sure how the Settings node was corrupted.

Thanks for your help.

Re: Render Settings Corrupted

Posted: Thu Apr 04, 2019 6:00 pm
by JimStar
JimStar wrote:... and the exact step-by-step description of what you do when this happens?..

Re: Render Settings Corrupted

Posted: Thu Apr 04, 2019 7:12 pm
by blastframe
JimStar wrote:
JimStar wrote:... and the exact step-by-step description of what you do when this happens?..
blastframe wrote:I tried replicating the error by importing one Maya scene to another, but the Octane Render Settings still work. I'm not sure how the Settings node was corrupted.

Re: Render Settings Corrupted

Posted: Thu Apr 04, 2019 7:22 pm
by JimStar
This is not the reproduce-sequence description, sorry.
The scene itself is almost useless for understanding what is happening on your side without the description of what you did exactly step-by-step and what output you got at each step... Scenes you opened/referenced, menu items you selected, buttons you pressed, etc...

Re: Render Settings Corrupted

Posted: Thu Apr 04, 2019 7:46 pm
by blastframe
JimStar wrote:This is not the reproduce-sequence description, sorry.
The scene itself is almost useless for understanding what is happening on your side without the description of what you did exactly step-by-step and what output you got at each step... Scenes you opened/referenced, menu items you selected, buttons you pressed, etc...
Wow, you could be a little more polite. I'm barely hanging on to Octane for Maya as it is.

I don't have a step-by-step. I found the Settings corrupted in my file when I checked it. I don't know what got me there. If the scene is useless, thank you for your time.

Re: Render Settings Corrupted

Posted: Thu Apr 04, 2019 9:19 pm
by JimStar
Octane automatically fixes an accidentally removed settings node and re-creates a new default one after re-opening the scene. So if you got into the situation where you had accidentally deleted this node ("octaneSettings node, which I deleted" is the only info I got from you for guessing why), and saved the changed scene - don't worry please, your scene will not be lost. Re-opening the scene must fix this by creating a new default settings node.