Bug on Blender when rendering though command line
Posted: Thu Aug 09, 2018 2:05 pm
Hi, I'm testing the demo of Octane and I've found a bug with the Blender plugin/version.
If I start a render from the command line for a frame other than 1 Blender gets stuck on
However passing
Octane 15.2.6
Blender 2.79b
GTX 980 (4GB VRAM)
16GB RAM
Linux / Nvidia 396.51 / CUDA 9.2
If I start a render from the command line for a frame other than 1 Blender gets stuck on
"Final render - Rendering | Waiting for image..." and OctaneServer spits these errors.Code: Select all
Octane: Starting Octane engine...
Octane: ...started
Octane: unknown ERROR: 25
Octane: unknown ERROR: 26
Octane: unknown ERROR: 22
Octane: unknown ERROR: 19
Octane: unknown ERROR: 20
Octane: unknown ERROR: 10
-f 1 to Blender avoids this bug, and it also seems to "unlock" Octane since it can render other frames afterwards. Code: Select all
/usr/local/OctaneBlender/blender -b /home/januz/tmp/OctaneTest/octane_test.blend -x 1 -F 'PNG' -o /home/januz/tmp/OctaneTest/render_octane_test_Scene -f 1Blender 2.79b
GTX 980 (4GB VRAM)
16GB RAM
Linux / Nvidia 396.51 / CUDA 9.2