While making an omf with fusion5, a framerate error triggered a popup cascade. Deadline doesn't seem to catch this lockup so it hangs indefinately and takes up a fusion render lic.
I'm also not confident that DL always kills the fusion render slave.exe when finished rendering without any errors.
Hi Ben,
We haven’t added popup handling to the Fusion 5 plugin yet (although we
really should). To enable it on your end, open up the *.mpr files in
\your\repository\plugins\Fusion5 and add this line to each file after
the UseJobObject=true line:
UsePopupHandling=1
Now whenever fusion pops up a dialog, Deadline shoud catch it and report
an error. After enabling this feature, see if you can reproduce the
framerate error and let us know if Deadline catches the popups.
Also, can you confirm whether or not the fusion render slave fails to
exit? What signs are you noticing that would make you think that it’s
not exiting?
Thanks!
The fusion renderslave is still running after the job fails. I remote in and see the process is still there. Plus we run out of licenses on the other machines.
That reminds me. It would be nice if the plugin would query the flexlm service rather than relying just on limit groups.
Should I be using ConsoleSlave.exe or RenderSlave.exe? The eyeon docs say that ConsoleSlave is designed for deadline.
The Deadline plugin for Fusion 5 has only been tested with the RenderSlave.exe application (this was how the Digital Fusion 4 plugin worked). But after reading the eyeon docs, I think we should to investigate the possibility of switching the plugin to use the ConsoleSlave.exe application.
Cheers,
That would be great.
Also, it's still not catching all the popups. Crashdumps still elude DL. I think the omf errors are caught now. Need to double check...
But I'd rather just wait for a console slave plugin. Since that would help us distribute our licenses more efficiently.
Thanks,
Ben.
We’ve modified our Fusion 5 plugin to support both 5.0 and 5.1. For 5.1,
you will have to specify the console slave application instead of the
render slave application. We’re currently testing this here, and it
seems to be working well so far, so we expect to include this in the
next release.
Cheers,
Hey guys, so yeah, we are looking at switching over to ConsoleSlave.exe on our render nodes, we are currently using FU5.2 and upgrading beta builds on a regular (at least weekly) basis, along with adding plug-ins rather frequently. So when RenderSlave.exe does its usual thing where it will just randomly leave EyeonScript.exe and EyeonServer.exe running on a render node it tends to bug stuff out when we update a plug-in or update to a newer build...
Apparently ConsoleSlave.exe is going to fix all this for us, so naturally we would like to switch over to it. I have not yet had the time (delivery on a show or two) to update to Deadline 2.7 (from 2.6) but if indeed this fix is implemented in this newest version I have a window of time that I can in fact update Deadline today...
So, is there any confirmation that I can now use ConsoleSlave.exe with Deadline? I am assuming there is also a new submission script for artists?
Thanks for any input,
Joe
>We've modified our Fusion 5 plugin to support both 5.0 and
>5.1. For 5.1,
>you will have to specify the console slave application
>instead of the
>render slave application. We're currently testing this here,
>and it
>seems to be working well so far, so we expect to include
>this in the
>next release.
>
>Cheers,
> - Ryan
Hey Joe,
Deadline 2.7 supports the use of the ConsoleSlave.exe application in the
current Fusion5 plugin (it’s not a new plugin with a new submission
script). In the Fusion5 plugin configuration, you would specify the
ConsoleSlave.exe as the application, and then you have the choice to use
command line rendering.
If command line rendering is off, then the plugin will essentially
function the same as before, except that ConsoleSlave.exe is used in
place of RenderSlave.exe (they both can function in a server mode where
you tell them to execute scripts). From a user standpoint, there isn’t a
noticable difference between the two.
If command line rendering is enabled, then Deadline will just execute
ConsoleSlave.exe as a command line application, instead of telling it to
run scripts. Because of this, some submission options will be ignored,
such as the Proxy, High Quality, and Check Saver Option options.
Cheers,
Ah, werd, I will be installing 2.7 today then! Thanks Ryan!
J