i have a problem to render a comp with motion blur, dont know if it is a problem with deadline or with the shellrender.exe itself.
I animated a few layers over a background, nested my layers and added a motion blur operator on this.
When i submit the job to deadline without motion blur , it renders without problems,
with motion blur ( use all cpus) i get an error message (see attached log file),
when rendering with only one cpu it seems to render, but it takes forever ( local render about 90sec a frame, with deadline 1 hour and not finished…)
Using Combustion 2008 on Win XP 64.
Deadline is just passing command line arguments to shellrender.exe and waiting for it to complete, so a good test to see if the problem is Deadline specific or not is to run the same render from a command prompt on the render node. Here is a command that Deadline ran that produced the error:
“C:\Program Files (x86)\Autodesk\Combustion 2008\ShellRenderer.exe” -nobar -start 323 -end 323 -startnumber 323 -skip 1 -output “Polaroids/output1” -quality best -depth 16 -framesize normal -skipexisting “C:\Documents and Settings\Administrator\Local Settings\Temp\polaroid_v70.cws”
Nothing looks incorrect in the command line, so try running the same command line on a render node and see what the results are (note that you should copy the cws file locally to the machine and change the path to it in the command line as necessary).
Also, I’ve noticed that there is no explicit error message from Combustion, just a non-zero exit code (which indicates that there was an error). Just to confirm, when the render fails with “non-zero error code, 3”, are any frames produced?
i tried the script on a render node, and it produced a C++ Runtime error,
the same happens when rendering with deadline.
I also tried to render using only one cpu, but it takes forever.
So it seems to be something wrong with the shellrender, unfortunatly since autodesk stopped development of combustion…
When rendering with deadline, only 0kb files are generated…
Yeah, definitely seems like a shellrenderer issue, and the crash would explain the 0kb files that are generated. If it crashed all the time, I would have suggested trying to reinstall Combustion, but since it seems specific to this case, the only thing I can suggest is asking Autodesk’s support team (assuming they still support the software to some degree).
Hey Andre,
Can you post the actual Combustion wks file, with no footage? Sounds like something is wrong with the actual Combustion script?
Also, just to make sure this is not interferring, I would resolve the missing audio file that Combustion wants:
Audio file not found: S:\ACTIVE\byp09xxx_mccann_neu.de polaroid\mixpreview48.aif