It seems to be trying to load the wrong scene ( ‘C:/Users/ScanlineVfx_user/Documents/maya/projects/default/untitled’ ) instead of the one in the jobs/ folder
cheers,
laszlo
Do you have beta 10 installed on both the machine you’re submitting from and the machine(s) you’re rendering on? There were breaking changes in the last 2 beta releases that directly affect the job’s plugin info settings, which could definitely explain what you’re seeing here. Any jobs submitted from beta 9 or earlier will not render on beta 10, and vice versa.
Cheers,
- Ryan
Yeah its rendering on the machine its submitting from (mine)
Tested on other machines as well, and i get the same:
0: INFO: Render Executable: “C:\Program Files\Autodesk\Maya2012\bin\MayaBatch.exe”
0: INFO: Render Argument: -prompt -file “”
0: INFO: Startup Directory: “C:\Program Files\Autodesk\Maya2012\bin”
Then later:
0: INFO: Deadline is ignoring error: “Error: File not found.: C:/Documents and Settings/ScanlineVFX/My Documents/maya/projects/default/untitled” because plugin setting Strict Error Checking is enabled and this error is not usually fatal.
0: STDOUT: Error: File not found.: C:/Documents and Settings/ScanlineVFX/My Documents/maya/projects/default/untitled
Both submission & render slave version:
Deadline Slave 6.0
Deadline Version: 6.0.0.49986
FranticX Version: 2.0.0.49984
C:\Program Files\Thinkbox\Deadline6\bin>deadlinecommand.exe Version
Deadline Version 6.0.0.49986
Hmm, I can’t seem to reproduce this here. I tested both a script and regular render job, and I also tested submitting the scene file with the job and not submitting it with the job.
Is it possible that when you submit the job, your plugin info file (the second file you submit with the job) is missing some entries? Can you post your job info and plugin info files for us to have a look at?
Thanks!
- Ryan
Let me confirm quickly that its not something i just noticed (illegal characters are returned from maya when querying the environment variables… which, since they are added to the job files might be upsetting deadline’s parser). Ill remove those and test if it makes things work.
Nope, not the reason.
The job file:
UsingRenderLayers=0
Camera=
ScriptJob=True
RenderLayer=0
Build=64bit
SceneFile=
StrictErrorChecking=1
ImageHeight=480
RenderHalfFrames=0
OutputFilePath=
Animation=0
MaxProcessors=0
AntiAliasing=low
ProjectPath=
Version=2012 x64
Renderer=mayaSoftware
IgnoreError211=0
ImageWidth=640
ScriptFilename=\inferno2\projects\common\pipeline\submission_queue\2013_01_29\TST_003_0002_maya_animation_layout.ma_11_43_12_241\farmCommand.mel
LocalRendering=0
OutputFilePrefix=
The info file:
OutputDirectory0=
LimitGroups=
Group=maya
Name=[TBOA] Animation Publish: TST_003_0002_maya_animation_layout.ma version: v0094
Plugin=MayaBatch
EnableAutoTimeout=0
Priority=40
LimitConcurrentTasksToNumberOfCpus=0
Department=
ConcurrentTasks=1
ChunkSize=15
Comment=
TaskTimeoutMinutes=60
JobDependencies=
InitialStatus=Active
MachineLimit=15
Frames=1
Pool=3d
Please note that with beta10, i removed the following info settings:
OnJobComplete = this errored on submission if not set to anything (deadline said it could not parse the string)
Whitelist, Blacklist = both were defined by default, and deadline complained that it will only use the whitelist. So i removed both from the default settings (they were empty strings anyway).
cheers,
laszlo
Thanks for posting those files. The problem is actually the empty “SceneFile=” entry in the “job” file (we refer to this as the plugin info file). In beta 8, these empty values were thrown away, which was actually a bug. We fixed this in beta 9. This explains why this worked before you upgraded to beta 10, because the plugin wouldn’t have seen this entry, and instead would have used the scene file submitted with the job.
If you remove the empty SceneFile entry, it should start working again.
Cheers,
- Ryan
Awesome, thanks Ryan!
yep, works great!