candycoated

I have the same trouble. I am using Redshift also, and I think that my access to the network drive I'm using is too slow. There is some lack of code in the way C4D saves the files that doesn't give it a chance to buffer or something before saving the next frame. It just calls the save file code for that frame and brute forces on to the next one. Since Redshift renders so much faster than the built in renderers I believe the network drive (or the network itself) is a bottle neck and it causes some frames to not save at all, or to be in partial save right as the render goes to save the next frame, causing you to have some frames that are left corrupt. I never have the problem if I render local to the PC, but if I go to a network drive, if it's a super fast render, I usually end up with missing or corrupt frames sporadically.

Ha! This is great!