2.3v5 saving bug

A forum where development builds are posted for testing by the community.
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Post Reply
User avatar (Default)
Zay
Licensed Customer
Posts: 1123
Joined: Sun Jan 17, 2010 2:53 am

I have never seen this before, but this one scene I have will not save to .OSC and reload with the changes I made.

I load the OBJ file. Do a few chages in the Node Inspector. Save to .OSC file. Open the OSC file and all the changes I did are gone and materials I didn't touch are missing.
This is a serious bug!

It saves/loads fine in 2.2.
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
Top
User avatar
Lutze
Licensed Customer
Posts: 101
Joined: Sat May 08, 2010 6:02 pm

Zay wrote:I have never seen this before, but this one scene I have will not save to .OSC and reload with the changes I made.

I load the OBJ file. Do a few chages in the Node Inspector. Save to .OSC file. Open the OSC file and all the changes I did are gone and materials I didn't touch are missing.
This is a serious bug!

It saves/loads fine in 2.2.
It is a long known bug. As far as I know the only workaround at the moment (at least until the next version is comming out) is to make changes to your materials in the node editor. All materials that are defined there through nodes will be saved correctly and reloaded when octane opens again. Hope I am right and it is a help to you.

Lutze
_________________
System: AMD X4, 2x GTX470, 8GB Ram, Win7-64Bit
Top
User avatar (Default)
Zay
Licensed Customer
Posts: 1123
Joined: Sun Jan 17, 2010 2:53 am

Aren't we talking about the same thing here ? Node inspector=Node editor?
Im not using the graph editor at all if that was what you ment.
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
Top
User avatar
matej
Licensed Customer
Posts: 2083
Joined: Fri Jun 25, 2010 7:54 pm
Location: Slovenia

If you create material nodes (or material macro nodes) in the Graph Editor and link them to your mesh object, everything will save fine. It's a known bug that will be gone in the next release.
SW: Octane 3.05 | Linux Mint 18.1 64bit | Blender 2.78 HW: EVGA GTX 1070 | i5 2500K | 16GB RAM Drivers: 375.26
cgmo.net
Top
User avatar (Default)
Zay
Licensed Customer
Posts: 1123
Joined: Sun Jan 17, 2010 2:53 am

matej wrote:If you create material nodes (or material macro nodes) in the Graph Editor and link them to your mesh object, everything will save fine. It's a known bug that will be gone in the next release.
Ah, ok. I thought it was the other way around for a moment. I guess I have been extremly lucky up until now then as I have rendered over 50 scenes with v5 :)
Win 11 Pro | i5 12600K | 32GB ram | 2x GTX 1080Ti + 3080Ti - studio driver 560.94| Modo/Blender/ZBrush/Daz/Poser
Top
Post Reply

Return to “Development Build Releases”