Strange error when submitting Fusion jobs to Deadline 5

Deadline
1

Hi everyone,

we’ve been using Deadline 5 for our Maya and Fusion renderfarm and so far it seems to work way better than 4.1, especially for Fusion.
But we encountered some strange error which happens every now and then when a machine tries to grab a Fusion task.
It is not machine or job dependent, the job gets rendered anyway, it doesn’t seem to influence the overall rendertime a lot. But every job throws about 10-15 errors; the error messages are always the same:

[code]=======================================================
Slave Log

0: Task timeout is disabled.
0: Loaded job: PRECOMP_VFX130_Motorrad_Retusche_Fleck02_v01.comp (000_090_000_40410e1d)
0: INFO: StartJob: initializing script plugin Fusion
0: INFO: About: Fusion Plugin for Deadline
0: INFO: Starting monitored managed process Fusion
0: INFO: Any popup windows with titles matching the regular expression “.Queue.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Render Manager.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Editor.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Precision.” will be ignored
0: INFO: Any popup windows with titles matching the regular expression “.Taper.” will be ignored
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: True
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
0: INFO: Render Executable: “C:\Program Files\eyeon\Fusion 6.1\Fusion.exe”
0: INFO: Render Argument: /quiet /listen /verbose
0: INFO: Startup Directory: “C:\Program Files\eyeon\Fusion 6.1”
0: INFO: Process Priority: BelowNormal
0: INFO: Process is now running
0: INFO: Starting monitored managed process StartJob
0: INFO: Any stdout that matches the regular expression “SCRIPT ERROR: (.*)” will be handled as appropriate
0: INFO: Update timeout has been set to 150 seconds
0: INFO: Stdout Handling Enabled: True
0: INFO: Popup Handling Enabled: True
0: INFO: Using Process Tree: True
0: INFO: Hiding DOS Window: True
0: INFO: Creating New Console: False
0: INFO: Render Executable: “C:\Program Files\eyeon\Fusion 6.1\eyeonScript.exe”
0: INFO: Render Argument: “C:\Users\capture\AppData\Local\Thinkbox\Deadline\slave\plugins\StartJob.eyeonscript” “P:\Stadtwerke\Stadtwerke_Duesseldorf_Elektromobilitaet\Files_Fusion\VFX130_Motorrad\PRECOMP_VFX130_Motorrad_Retusche_Fleck02_v01.comp” 30
0: INFO: Startup Directory: “C:\Program Files\eyeon\Fusion 6.1”
0: INFO: Process Priority: BelowNormal
0: INFO: Process is now running
0: STDOUT: eyeon Script Interpreter
0: STDOUT: Copyright © 2005 - 2010 eyeon Software
0: STDOUT: Connecting to Fusion…
0: STDOUT: Connection timeout in 29 seconds
0: INFO: Ignoring popup “Render Manager - [Queue1]”
0: INFO: Ignoring popup “Ellipse/Rectangle Editor”
0: INFO: Ignoring popup “Helix-Spiral Editor”
0: INFO: Ignoring popup “Freehand LUT Precision”
0: INFO: Ignoring popup “Freehand Precision”
0: STDOUT: Connection timeout in 28 seconds
0: STDOUT: Connection timeout in 27 seconds
0: INFO: Ignoring popup “Spline Taper”
0: STDOUT: Connection timeout in 26 seconds
0: STDOUT: Fusion (0x0000000005C14130) [App: ‘Fusion’ on 127.0.0.1, UUID: 4365c6d8-94df-4049-8027-e9b2324d8f37]
0: STDOUT: Connected to Fusion
0: STDOUT: Getting comp list.
0: STDOUT: STARTJOB: Closing comp 1
0: STDOUT: Loading comp P:\Stadtwerke\Stadtwerke_Duesseldorf_Elektromobilitaet\Files_Fusion\VFX130_Motorrad\PRECOMP_VFX130_Motorrad_Retusche_Fleck02_v01.comp
0: STDOUT: Locking the comp.
0: INFO: StartJob returned exit code 1[/code]

Does anybody know how to solve this? We sometimes also get the error message that we should activate “no login required” in the eyeonscript settings, although it’s already activated.

2

That’s strange. It could be one of those “Fusion being Fusion” situations, but let’s dig a bit before making that assumption.

First, do you see this in the log for tasks that render successfully?

I’m just curious if there is a previously opened comp in cases where the tasks render properly.

Also, I noticed that you are using Fusion.exe as your render executable. Do you happen to have the Fusion Render Node installed on your slaves? If so, maybe try pointing to renderSlave.exe or consoleSlave.exe as your executable to see if that makes a difference. While using Fusion.exe as the render executable is supported, renderSlave.exe and consoleSlave.exe were designed for network rendering, and maybe they’re a little more reliable.

Cheers,

  • Ryan