(Scene has been uploaded via the Corona Private Transfer with a link to this thread)
Did some testing on this today - took the scene, limited the passes to just 2, and rendered using Backburner with three machines (one was the workstation, also set up to be a server, and two pure server nodes). I could not replicate the problem.
There is a slight "odd movement" from the camera at the end, but this is in the animated path and can be seen in the Max wireframe, and is not the same as the result seen in the problem renders, which is where the image appears to "jump backward" briefly in some frames.
Couldn't test possible solutions since I couldn't replicate the problem. Extra info from the user:
- Job is submitted via backburner to a network of 7 machines. Only one machine seems to generate "bad" frames. However, if the job is submitted again with that machine excluded, another machine gives bad frames.
- Problem occurs when submitted to Rebus
My thoughts, but have been unable to test since I can't replicate the problem
- Rebuild the animated camera?
- Try without motion blur?
- Perhaps something to do with scene scale and location vs world origin?
- Only happens above a certain number of machines in the network?
Note - my test passed the textures via the checkbox in Submit to Network Rendering; all machines rendered to a folder on their local drive, and files were copied manually once complete for assembly in Premiere; 1.5.2 was used, freshly reinstalled on all three machines.
