I am trying to generate simple animation/simulation of 3D objects that are rendered using a display conduit. I am using the old .NET SDK (not RhinoCommon).
The problem is that when I call doc.regen in a loop, it doesn’t behave synchronously. The loop finishes before the animation has finished, and then the display jumps to the final state/transformation.
I have see the sample plugin in the wiki (TestAnimator); our code is structured similarly. However in that example the animation is GUI driven. We also often use the MouseMove of the GetPoint to animate interactions and that works. The problem exists when we have a fast loop.
Is there any built-in way to wait for one rendering to finish before sending the next doc.regen?
It would also help if you could give me an idea of how the doc.regen works internally.