at the moment I’m testing Octane for animation use, because the render times in ambient occlusion mode are short and the image quality is very nice. But there is a limit: the time to reload the geometry from frame to frame. I think and hope, that there can be something done. It looks like the first steps need to be done from the McNeel team. Finally all render engines could profit by a quicker information transport.
Could it be possible to send the object transformation info only? So, the object could keeped in RAM/VRAM and needs to be moved there only. Only a few infos would be needed - where is a object placed and how is it turned/scaled. Maybe Andy can help here.
Here a quote from the Octane forum.
[quote=“face_off”][quote]No, not rendering 30 fps, but moving geometry without to wait for a reload of the parts of the scene, that’s my dream. Like I wrote my current animation test scene needs approx. 10 s to reload the geometry for the next frame. If I would buy some graphic cards than the render time per frame could be faster the loading time. So, bring the loading time down to real time interaction should be a big goal of Octane.[/quote]I don’t think Rhino is designed for this type of thing. It’s a modelling app, not an animation app. Something like modo, LW, C4D, Maya, 3ds max will be more capable of this sort of animation control.