![]() 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). The OctaneRender for Rhino plugin does a complete reload of the entire scene each frame when rendering from Bongo. Also could this be Rhino specific or is it the issue with other 3d programs too? 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 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!!) Scene loading generally takes simply too long. With some of the scenes even more heavier. Even though live mesh is turned on only for objects that move each frame needs almost a minute to load. I discovered that unless you make “camera-only” animation octane has to load the scene each time again. Unfortunately there are two reasons why I am absolutely down after one day of using Octane demo.īongo Animation with some few objects and camera moving: I got convinced by the superb rendering times and bought me two hydrocooled 980Ti. Hello to all octane enthusiasts, possibly makers, was really looking forward to render my diploma animation with octane.
0 Comments
Leave a Reply. |