OTOY Forums

Hello to all octane enthusiasts, possibly makers

I was really looking forward to render my diploma animation with octane for Rhino. I got convinced by the superb rendering times and bought me two hydrocooled 980Ti.

Unfortunately there are two reasons why I am absolutely down after one day of using Octane demo.

1. Disappointment:
Bongo Animation with some few objects and camera moving:

I discovered that unless you make "camera-only" animation octane has to load the scene each time again. Even though live mesh is turned on only for objects that move each frame needs almost a minute to load. (1982 elements, 3 000 000 triangles). With some of the scenes even more heavier.

2. Disappointment:
Scene loading generally takes simply too long. It is insane waste of worktime. Also is it normal that if all meshes are turned on to be live you can load only few objects? already with 300 elements - all live meshes - I get out of Memory RAM ( which is 32GB!!)

My last hope would be that this has been taken care of in some of the updates, as I only use demo for it. Also could this be Rhino specific or is it the issue with other 3d programs too?

Hi Daniel

The OctaneRender for Rhino plugin does a complete reload of the entire scene each frame when rendering from Bongo. This is because the plugin cannot access the individual geometry object transforms from within the RhinoCommon API (in fact, RhinoCommon provides all geometry in world coordinates, not local coordinates with an object transform). It may be possible in the future to incorporate Bongo API access to obtain the geometry transforms each frame, however I believe (and I might be wrong) that there is a Bongo API, and it is C++, which is going to be a problem with the Octane plugin being done in the C# RhinoCommon API.

So in summary, if there was a way to access the actual Bongo geometry positions each frame from the RhinoCommon API, a scene reload would not be needed, and animation would be very fast. This is the way it works on most of the other Octane plugins.

Regarding running out of memory with all meshes being live - I'm not aware of any issue with this, and it has possibly been corrected in the latest version (there have been over 20 releases since the demo version that you are using). If you send me a scene which gives you this problem, I can check for you.

Paul