More of the log would be helpful here. Can you send along a job report?
This part of the log says “a problem happened” without actually telling us what fusion said the problem actually was. The job report should have all that info.
Well, it definitely looks like this is the core problem:
2016-09-15 11:42:07: 0: STDOUT: Rendering from 10 to 14, high quality is true, proxy is 1
2016-09-15 11:42:07: 0: STDOUT: Rendering with Fusion version: 8.2
2016-09-15 11:42:07: 0: STDOUT: ...plugins\57da7a977fdbfe36f032baa0\RenderTasks.eyeonscript:290: attempt to index global 'comp' (a nil value)
Then the Slave couldn’t close FuScript, which is a bit weird since it thought FuScript died…
Are you able to reproduce this reliably? Could you send me a sample project that reproduces and I’ll pass it to the integration team?
Update here: Jessy just fixed this by porting an old workaround we used to have. It should land in Service Pack 10, which is going to be a few weeks, but it is coming. Let me know if you’d like to beta test the plugin and submitter from SP10 a bit early.
Here’s the contents of the patch (pretty much just replaces the few lines for “Composition Loaded Successfully”).
if(comp) then
print("Composition Loaded Successfully")
else
-- GetCurrentComp() fails sometimes. This is a workaround for that issue.
-- This code is a workaround pulled from version 7.2. It loads the comp while avoiding an error from eyeonscript when setting comp = fl[1].
comp = nil;
for i=1, table.getn(fl), 1 do
name =fl[i]:GetAttrs().COMPS_FileName
if( name ~= "")then
if( name ~= nil) then
comp = df:LoadComp( name, true )
end
end
end
if(comp) then
print( "Composition Loaded Successfully" )
else
print( "ERROR: Composition failed to load, rendering will now end." )
io.flush()
wait(5)
os.exit(0)
end
end