The "cam update" option of 1.17 works with Octane 1.5
S basically, to prevent corruption you use "export obj only", if you changed the geometry and "update camera only" if you changed the camera. Tho this works only for stills.
It would be helpful to know what was changed in 2.02, before going on a blind search
What do you mean by Blender exporter ? The CVS instances exporter or the OBJ exporter ?
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.
The reason 2.02 exports everything not just visible layers, is that line 50 in export.py has been commented out.
It works the first time you export the scene, because Octane 1.5 can read the old .ocs structure. But when you save the .ocs project it gets saved in the new structure. And that file will get corrupted if the exporter changes *anything* in it. SO you are basically limited to "export only the obj" or "export only the camera" (since this mode doenst write in the .ocs, but passes cam data to the cmd line)
@tomas_p : try to install from a zip file containing a folder with the py file. If it doesn't work, put a folder containing the py file in scripts\addon folder. if it still doesn't appear, add a copy of the py file in scripts\addons, at same level as the folder ...
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.
