I've noticed an extremely problematic behavior with the VFB that I'm certain was not previously there. When rendering out an animation into the VFB -- which is often my preferred batch method so I can monitor progress visually -- previously I'm pretty sure hitting Esc would simply kill the current frame and nothing would be written to disk. However, I've now noticed that this is no longer the case, and unfinished frames are fully written out. This results in what appears to be a finished frame being written into the sequence, with full file size and date stamp, but in fact what is written out is a frame containing the previous frame's pixels in the unrendered areas of the current frame, with only those buckets that have completed from the current frame. Effectively, these are broken frames containing pixels from two adjacent frame numbers. Often this is not obvious to the naked eye, depending on the animation, and I've already had to circle back a couple of times to fix renders that I thought were finished only to find such frames later. Is this by design or this is a bug? It seems to me that if a user hits "Esc" while a render into the VFB is in progress, it means they do not want anything from the current render written out in this way.
Announcement
Collapse
No announcement yet.
VFB saving full but unfinished frames out
Collapse
X
Comment