Hi,
in the past a whole animation can be rendered and if there was something wrong at some frames, the user was able to delete the frames from the disk, adjust the model and start the animation rendering again with the option "overwrite exist files" disabled. Only the missed frames was rendered again. This workflow was also very useful to start two or three Rhino task and start the animation rendering at all tasks. So, there was no gaps of the CPU usage for preparing the scene anymore, one task filled the gap of the other.
But now the whole animation is rendered again from the first frame to the last. This is a hugh step backward. Please try to find a way to get back the old functionality.
-Micha
in the past a whole animation can be rendered and if there was something wrong at some frames, the user was able to delete the frames from the disk, adjust the model and start the animation rendering again with the option "overwrite exist files" disabled. Only the missed frames was rendered again. This workflow was also very useful to start two or three Rhino task and start the animation rendering at all tasks. So, there was no gaps of the CPU usage for preparing the scene anymore, one task filled the gap of the other.
But now the whole animation is rendered again from the first frame to the last. This is a hugh step backward. Please try to find a way to get back the old functionality.
-Micha
Comment