- Wed Jul 28, 2010 6:24 am
#327634
Hi All,
First off I should say I'm very new to Maxwell, as I just bought it during the recent promo. I'm also fairly new to C4D and Realflow too.
I was rendering a 300 frame animation created using C4D and Realflow. It rendered the first 86 frames without a problem but then my computer crashed (my fault) and I had to do a hard reboot. I tried to resume my render by specifying frames 87 to 300, first in the C4D render settings and then in the Maxwell plugin for C4D. No matter what I do it renders from the beginning of the animation instead of starting at frame 87. I'm wondering if I missed a step or if it's a bug.
I'm running the newest version of Maxwell and C4D 11.5 on a Mac OSX 10.6.4, 8 core, 12 GB RAM. Not rendering over the network.
So now I'm rendering again from scratch, but I'm hoping someone might have a suggestion on how to resume rendering an animation in case this happens again.
Thanks,
Walter
First off I should say I'm very new to Maxwell, as I just bought it during the recent promo. I'm also fairly new to C4D and Realflow too.
I was rendering a 300 frame animation created using C4D and Realflow. It rendered the first 86 frames without a problem but then my computer crashed (my fault) and I had to do a hard reboot. I tried to resume my render by specifying frames 87 to 300, first in the C4D render settings and then in the Maxwell plugin for C4D. No matter what I do it renders from the beginning of the animation instead of starting at frame 87. I'm wondering if I missed a step or if it's a bug.
I'm running the newest version of Maxwell and C4D 11.5 on a Mac OSX 10.6.4, 8 core, 12 GB RAM. Not rendering over the network.
So now I'm rendering again from scratch, but I'm hoping someone might have a suggestion on how to resume rendering an animation in case this happens again.
Thanks,
Walter
Cinema 4D 13, Maxwell 2.7, Vue xStream 10.5, Realflow 5