Yes. When Rhino renders a camera flythru, it call the renderer OnBeginRender (where the scene is loaded), and then for each sun position it calls ContinueModal() to render that frame.
Whereas for a Bongo render, the OnBeginRender() gets calls at the start of each frame, so the plugin needs to load the full Rhino scene into Octane. For a rendering plugin like Octane, there is no way for the plugin to tell if it’s rendering a single frame, a sun study or a bongo animation.
I tried exporting bongo to ocs format, works very nice! Bigger scene get
me into freeze again, probably same cause as loading static scene cuz
live meshes need to be used.
I just checked the code. When you export a Bongo animation to OCS, the plugin opens the Viewport, then saves that frame to the Alembic file, then progresses the Bongo timeline, then only refreshes the Rhino geometry with Live Update ENABLED, and saves that frame to the Alembic file, etc. So you can just set the geometry you need to animation with Live Update ENABLED, and then only those mesh items will be reloaded into the Octane Viewport. I take it you are getting a freeze when first opening the Viewport. Is it possible to send me that scene pls, and I can take a closer look.
Also when i render bongo fly-throughs with octane directly inside rhino, I can add sun animation to it too: Rhino - Animating the Sun
This
oddly works only when the rhino sun tab is active (means it is
separated from other tabs). This sun animation is unfortunately lost
when exporting to ocs, would be nice to have in standalone too.
Yes, the export to OCS process is simply iterating through the Bongo timeline, extracting the relevant geometry. As I understand the RhinoCommon RDK, the actual sun position from a sun study is not available to a plugin unless the sun study is actually rendering. The sun timeline is not necessarily the same as the Bongo timeline.
Paul