Is it possible to send Deadline jobs to a system with only the FU Client? The documentation seems to indicate it only runs on Render Nodes.

Thanks,

-David

Hi David,



Yes, this is possible. Here are the details on how to set this up (from

our fusion FAQ):



You can use workstation licenses to render, you just need to do a little

tweaking to get this to work nicely. In the Plugin Configuration

settings, you need to specify two paths for the RenderExecutable option,

separated by a semicolon. The first path will be the render node path,

and the second will be the actual Fusion executable path. You then have

to make sure that the render node is not installed on your workstations.

Because you have specified two paths, Deadline will only use the second

path if the first one doesn’t exist, which is why the render nodes can’t

be installed on your workstations.



Cheers,

• Ryan
  
  
  
  –
  
  –
  
  Ryan Russell
  
  Frantic Films Software
  
  http://software.franticfilms.com/
  
  204-949-0070
  
  
  

Thanks Ryan,

I missed that bit in the FAQ. I have not been able to get Fusion 5 to render this way yet. Just to clairify, I have given it this secondary path C:\Program Files\Fusion 5.1\Fusion.exe and I have set the Fusion Prefs:Script = No Login required.

It sends the job, loads the Fusion interface, but does not load the scene file. It then sits for the 135s timeout and shutsdown.

I did a quick try with Digital Fusion 4 and it works a-ok. Any ideas what to check?

-David

Whoops, forgot this part.

After trying in with DF4, I gave the Fusion Quicktime Generation a whirl in DF4. That did not work. In the configuration I see that it points to a directory and not an executable. I assume it is then looking for RenderSlave.exe, which on a workstation, would not exist. Is this telling me that trying to use the QT Generation on a workstation is not possible. I really like the idea of  the template files and QT generation right out of Deadline. However, I don't have a RenderNode copy, just workstation version.

Thanks again - David

Hi David,



I’ve tested our current working version of the Fusion 5 plugin with the

full version on our farm and it works fine, so it’s possible that we’ve

fixed something since the release of Deadline 2.6. Does the slave log

for the failed render show any messages that might explain the problem?



With regards to the QT plugin, you’re correct that it currently only

works on RenderSlave installs. This will also be addressed in the

upcoming release. Instead of specifying a directory, you will be able to

specify the direct path to the executable you want to use. In the

meantime, you could probably tweak the current QT plugin on your farm to

work with the full version of F5. To do so…

1. Open the file
   
   \your\repository\plugins\FusionQuicktimeGen\FusionQuicktimeGen.dlinit
   
   
   
2. Change the line…
   
   
   
   Fusion5Exe=RenderSlave.exe
   
   
   
   …to…
   
   
   
   Fusion5Exe=Fusion.exe
   
   
   
3. Save the file
   
   
   
4. In the Fusion QT plugin configuration, specify the directory for the
   
   full version of F5.
   
   
   
   
   
   Of course, your first problem with F5 not loading the comp could
   
   probably prevent this from working, although the rendering is handled a
   
   little differently, so you could still give it a try. We hope to have
   
   the next version of Deadline out within a month.
   
   
   
   Cheers,
   

• Ryan
  
  
  
  –
  
  –
  
  Ryan Russell
  
  Frantic Films Software
  
  http://software.franticfilms.com/
  
  204-949-0070
  
  
  

Hello Ryan,

I have posted the error log from the Fusion 5 workstation job. It loads Fusion UI, but not the .comp. As mentioned, Digital Fusion 4 does work after adding the workstation directory as suggested.

Hi David,



I’ve attached both working copies of our Fusion5 and FusionQuicktimeGen

plugins respectively for you to test out. Hopefully this will resolve

the problems you’re having, because tests here seem to work fine.



For Fusion5:

1. Make backup copies of the files in \your\repository\plugins\Fusion5
   
   and \your\repository\submission\Fusion5, just to be safe
   
2. Unzip the attached Fusion5.zip, and open the extracted folder
   
3. Copy the contents of the plugins folder to
   
   \your\repository\plugins\Fusion5
   
4. Copy the contents of the submission folder to
   
   \your\repository\submission\Fusion5
   
5. Modify the Fusion5 plugin configuration (from the Tools menu in the
   
   deadline monitor while in super user mode) to point to the correct
   
   render executable
   
   
   
   For FusionQuicktimeGen:
   
6. Make backup copies of the files in
   
   \your\repository\plugins\FusionQuicktimeGen, just to be safe
   
7. Unzip the attached FusionQuicktimeGen.zip, and open the extracted folder
   
8. Copy the contents of the folder to
   
   \your\repository\plugins\FusionQuicktimeGen
   
9. Modify the FusionQuicktimeGen plugin configuration (from the Tools
   
   menu in the deadline monitor while in super user mode) to point to the
   
   correct render executable (you no longer point to the directory)
   
   
   
   Both plugins have been tested with Fusion.exe, RenderSlave.exe, and
   
   ConsoleSlave.exe as the render executables. Hopefully, you have some
   
   luck with them. If you have any questions or run into any problems, let
   
   us know!
   
   
   
   Cheers,
   

• Ryan
  
  
  
  –
  
  –
  
  Ryan Russell
  
  Frantic Films Software
  
  http://software.franticfilms.com/
  
  204-949-0070
  
  
  
  
  

Hi Ryan,



Well here is where I am at after making your changes with the new plugins.



In DF4 submitting .flw renders a-ok (it did before the changes).



In DF4 QT generation, it now loads the UI (did this before changes), loads QT generation .flw (did not before), and then crashes DF4 before rendering first frame.



In Fusion 5.1 when either submitting a .comp or submitting a Fusion QT render, it loads the Fusion 5.1 UI, does not load the .comp and then times out.



Now the interesting part.



If I rename my 5.1 and 5.02 directories so that 5.02 is where DL looks, then I get the following behavor:



In a submitted .comp, it loads and renders a-ok.



With a submitFusion QT job, it loads Fusion 5.02, creates/loads the project, renders the project and then the following two dialogs appear before Fusion shuts down:

1. Render Completed - Press OK
   
   
   
2. Save changes to qtgem.comp - y, n, cancel.
   
   
   
   After replying to two dialogs then Fusion shuts down and sends the job completed info back to Dealine.
   
   
   
   I have checked my 5.1 configuration and the prefs for allowing external script access and network rendering are both set.
   
   
   
   I also checked my firewall to see if those requests are being blocked for 5.1, and they are not being stopped there.
   
   
   
   So to wrap up, DF4 works to .flw submissions, but crashes on QT submissions. FU5.1 doesn’t work because the .comp is not loaded and the system times out. FU5.02 works for .comps a-ok, and for QT subs it renders but gets stopped by those two dialogs, which means the next job will not process without manual intervention. I saw another tread about Fusion and catching dialogs so I assume that is a known issue at this point.
   
   
   
   I still have no clue why FU5.1b100 does not work.
   
   
   
   -David

Here is a new version of the Fusion QT plugin. It should fix the popup

problem you’re having with Fusion 5, and it also fixes a bug that

prevented the use of semicolon separated paths in the plugin configuration.



Same install instructions:

1. Make backup copies of the files in
   
   \your\repository\plugins\FusionQuicktimeGen, just to be safe
   
2. Unzip the attached FusionQuicktimeGen.zip, and open the extracted folder
   
3. Copy the contents of the folder to
   
   \your\repository\plugins\FusionQuicktimeGen
   
4. Modify the FusionQuicktimeGen plugin configuration (from the Tools
   
   menu in the deadline monitor while in super user mode) to point to the
   
   correct render executable (you no longer point to the directory)
   
   
   
   I’m not sure why DF4 is crashing on QT jobs. The tests I ran here worked
   
   fine (we’re using vesion 4.05 build 89). The version of Fusion 5.1 I’m
   
   testing on is build 95 (maybe something has changed recently…).
   
   
   
   Cheers,
   

• Ryan
  
  
  
  –
  
  –
  
  Ryan Russell
  
  Frantic Films Software
  
  http://software.franticfilms.com/
  
  204-949-0070
  
  
  
  
  

Hi Ryan,

Thanks for the update, that solved the pop-boxes. I finally figured out why my 5.1 install was failing. I had a .scriptlib file in my install and it caused DL to fail. I don't really need it, so I just tossed it out.  I'm sure the script is the issue and not DL, but  here is the script for your reference:

OrphanSaverCheck.scriptlib

while composition == nil do
 
end

globals.ev = AddEventSuite("Composition")

function ev:OnStartRender(event)

        local toollist=comp:GetToolList(false, "Saver")

 for i, tool in toollist do

  if tool.Input:GetConnectedOutput() then
   self:Default(event)
  else
   -- report the problem
   msg = "The saver named ".. tool:GetAttrs().TOOLS_Name .. " is not connected to any other tools.\n\n"
   msg = msg.."Select OK to continue anyway, or Cancel to exit."
   
   ret = comp:AskUser("Warning: Orphan Savers!", {
    {"Warning", Name = "Warning", "Text", ReadOnly = true, Lines = 5, Wrap = true, Default = msg},
    })
   
   if ret then
    self:Default(event)
   end
   
  end
  
        end
 
end

_______
 
DF4 still crashes on QT jobs, but since I'm not really using it much, its not a big deal. I see your version is different than mine (4.04e) and I don't see the 4.05b89  version on the Eyeon web site.

Deadline is a very slick bit of programming. I just noticed that when you do a Render Elements pass in Max, that you even have the option to view each pass in the Task RMB menu. Very nice. And the ability to set up multiple image viewers is also very handy. Great work.

Thanks for all your help.

-David

PS. Forgot to mention that in the new Fusion QT plugin, the help window at bottom of configure plugins has the help for the older version referring to a path ending with \. That is no longer correct.