We have some trouble with frames mark as completed but not written to disk.
There is various situations when it can happen, but one easy to report is when the render is aborted because of license fail (arnold), but still marked as completed. please see below.
Hm it is odd that this was not caught as an error. The plugin has a list of regexes that will trigger an error. Look around line 2487 of MayaBatch, there are a bunch of statements like this:
Thanks mois for the tip ! I’m going to investigate the regexes trigger
We also have another recurring error. (let me know if i should make another post for it).
Some of our characters abcs “glitch”. It happen on around 10% of the frame.
The model “pop” to a specific frame then go back to it’s normal animation.
We use local caching and motion blur.
We also have a maya script node that repath the alembic path when the scene open to the correct animated abc for the shot.
When we requeue the popping frame, it’s fixe the issue.
For those that that don’t know what files and locations are being discussed above, this is what I did to solve this issue:
go to “[DeadlineRepsoitory]\plugins\MayaBatch\MayaBatch.py”
make a copy of the file as a backup.
open original file in a code editor, I used Visual Studio. Go to line 2497 and add this line:
self.AddStdoutHandlerCallback( "aborting render because this is a batch render and abort_on_license_fail option is enabled" ).HandleCallback += self.HandleFatalError
save and run a job. Tasks that do not have a license should now fail as expected.
I’m not a code-savvy person by any means, but I find it helpful when there’s explicit instructions, so thought I’d add that in