hi, I have been using the octane betas for a little bit and love the ease, speed and definetely quality it has offered me.
Recently with v5 beta I am having a problem where i load a obj mesh, assign materials, save the file and let it render. All is fine.
Client says they want to change some tone or color or strentgh of lights, so I go and open the same file I saved and where there used to be lets say 20 material nodes nor there is only 10. Just an example, not actual figure, but this is what has happened to me over the last week or so. I had not really noticed because I did not need to go back into my saved ocs files to make any lighting changes or such until today. Then i noticed it.
By the way I am not using any octane live nodes or saved nodes. All materials are built in the ocs file itself and ar every basic.
This kills any workflow gains of loading a mesh setting materials, lights, saving and thinking your good to go. Where I know have to either keep the said ocs scene file open until I know that all and any changes are truly done or just re open it and have to apply all materials again.. This really sucks.
Again I love the product, and do not recall having this issue with the previous betas, and no I am not changing my obj. mesh in the host 3d app, so that cant be the cause of it.
Just would like to know if anyone else has ran across this and knows of a fix.
Thanks all.
re opening scene ocs file and materials indexs changing
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.
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.
I encountered this trouble with the early demos of Octane, before 2.2, but the bug has been fixed for a while... very weird.
French Blender user - CPU : intel Quad QX9650 at 3GHz - 8GB of RAM - Windows 7 Pro 64 bits. Display GPU : GeForce GTX 480 (2 Samsung 2443BW-1920x1600 monitors). External GPUs : two EVGA GTX 580 3GB in a Cubix GPU-Xpander Pro 2. NVidia Driver : 368.22.
Same problem here! I saved the scene in v5 and reopened the .OCS file and the materials and light settings have gone!
I send also a notification about that problem but didnt get a relable answer...
I think is a major bug for now at this version.
Hope to see a fix in next release.
I send also a notification about that problem but didnt get a relable answer...
I think is a major bug for now at this version.
Hope to see a fix in next release.
Dual Xeon E5540 CPU 2.53 - 1x GTX470 - win7 64 -12GB ram
Got the same problem here 

Intel i7 5960X | 32Gb DDR4 | GTX 980 Ti 6Gb | Windows 10 64bit
Guys do you just tweak the material settings in Node inspector, or do you create material nodes (or macros) and tweak those? Cause I always do the latest, and I haven't had this problems. Of course this problem had to be looked into, but as a temporary workaround you could try to create material nodes.
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
cgmo.net
I always create the material nodes/macros, but sometimes when for example I hide one element in the scene and rewrite the .obj I find the materials shifted in position when I open the .ocs file. This will not occur if I have the .ocs file already open in Octane and I just reload the .obj
Intel i7 5960X | 32Gb DDR4 | GTX 980 Ti 6Gb | Windows 10 64bit