Hi,
since we upgraded to DM 2.7, the "view rendered output" feature does not work correctly. If you right-click on a completed task of DFusion that contains more then 1 frame, the naming of the chooseable output files is wrong. The frame numbers are missing.
Is there some configuration setting, that solves this issue?
Another thing is the strange render time display that I get on auto-refreshs (7611h 58m 44s per task). How to fix this?
cheers
Marcus
Hi Marcus,
Which software are you rendering with? There is a bug in 2.7 which
removes the frame number padding, and I believe it affects only Maya. We
will be releasing a 2.7 maintenance release soon (more than likely at
SIGGRAPH) that will fix this bug, along with a few others that have
cropped up.
If you are using Maya, there is a workaround that you can implement to
get this working in the meantime:
- Open \your\repository\submission\maya\SubmitMayaToDeadline.mel in a
text editor.
- Find this line (I believe it’s around line 1105):
$FrameQuestionString = $FrameQuestionString + “?”;
- Replace the ? with a # so the line now looks like:
$FrameQuestionString = $FrameQuestionString + “#”;
- Save the file and restart maya, then try to submit the job again.
The auto-refresh bug is still on our todo list. It’s one of those little
bugs that keeps falling off the priority list.
Cheers,
Hi Ryan,
we use DFusion 4.04e. Can I modify the SubmitToDeadline.dfscript somehow to get a similar workaround as you discribed? What's the point in the job description file that makes it work or not?
Marcus
Hi Marcus,
For DFusion, you can open up
\your\repository\submission\DFusion\SubmitToDeadline.dfscript and find
this code around line 100:
if frameNumber == nil then
digits = “?”
while string.len(digits) < digitCount do
digits = “?” … digits
end
else
digits = tostring( frameNumber )
while string.len(digits) < digitCount do
digits = “0” … digits
end
end
Just replace the “?” instances with “#” and save the file. You should
then be good to go.
The problem is that Deadline is checking the path names in the job to
make sure there are no illegal path characters, which used to cause job
submissions to fail. That’s why the '?'s are stripped from the filename
and not the '#'s. We should probably just move all of our submission
scripts to use ‘#’, for the sake of conistancy if nothing else.
Cheers,
Works great, thanks for the quick reply
thumbs up, Marcus