Has anyone here seen backburner thinking it was rendering one frame, but actually rendering another. So that when the frame it thinks it's rendering is done, it considers it done in the manager (but doesnt save it out) and the other frame it's actually rendering it saves out, then renders again on another farm machine because it doesnt know it's been done?
Leads to an animation with most of the frames missing (but BB thinking they're all done fine) and another animation with most of the frames being rendered twice.
It's doing my tits in. 80% of my frames on an animation were not rendered last night - and the few farm machines that were doing this were completley wasted because everything they did ended up being re-done by another one.
It's happened a few times in the past few weeks - not being aware it was rendering a strip then having to re-do it - but it's the first time it's got in the way of an animation.
Anyone seen this, and can offer a reason?
Ditching bb is probably out of the question here.
Leads to an animation with most of the frames missing (but BB thinking they're all done fine) and another animation with most of the frames being rendered twice.
It's doing my tits in. 80% of my frames on an animation were not rendered last night - and the few farm machines that were doing this were completley wasted because everything they did ended up being re-done by another one.
It's happened a few times in the past few weeks - not being aware it was rendering a strip then having to re-do it - but it's the first time it's got in the way of an animation.
Anyone seen this, and can offer a reason?
Ditching bb is probably out of the question here.
Comment