The scene should only rendered when one or more of the following happens:
User interaction.
When the camera appears to be moving (since it glides to a stop).
The animation updates.
The window needs to be redrawn because it was opened, moved, resized, etc.
The user should be able to control the frequency of animation, from unlimited to just snapping to the snapshots. Patriot and Alexander_Yalt both suggested that it'd be all right for the rendering step to consume non-trivial CPU resources during the render step when one of these things happens.
FPS should be unlimited during user interaction or when the camera is moving, but should be tied to the speed up the update during the animation.
The scene should only rendered when one or more of the following happens:
The user should be able to control the frequency of animation, from unlimited to just snapping to the snapshots. Patriot and Alexander_Yalt both suggested that it'd be all right for the rendering step to consume non-trivial CPU resources during the render step when one of these things happens.
FPS should be unlimited during user interaction or when the camera is moving, but should be tied to the speed up the update during the animation.