Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
muster:9.0:applications_plug-ins_connectors:houdinipdg [2019/04/24 10:29]
admin
muster:9.0:applications_plug-ins_connectors:houdinipdg [2019/04/24 10:30]
admin
Line 6: Line 6:
 THE PLUGIN SUPPORTS HOUDINI 17.5 OR GREATHER THE PLUGIN SUPPORTS HOUDINI 17.5 OR GREATHER
  
 +==== Installation ====
  
-1) Copy the Digital asset musterscheduler.hda inside your otls folder (system wide or inside your documents Houdini folder under otls), this will let you override the scheduler job paramaters on a node base. The Python script is only required if you need to modify it +  * Copy the Digital asset musterscheduler.hda inside your otls folder (system wide or inside your documents Houdini folder under otls), this will let you override the scheduler job paramaters on a node base. The Python script is only required if you need to modify it 
- +  ​* ​Copy also the vvmuster.py script into your Houdini documents folder under pdg\types (i.e. My Documents\Houdini17.5 in Windows) or into the Houdini installation folder to install system-wide 
-2) Copy also the vvmuster.py script into your Houdini documents folder under pdg\types (i.e. My Documents\Houdini17.5 in Windows) or into the Houdini installation folder to install system-wide +  ​* ​Start Houdini, and follow the PDG guidelines by setting the Muster scheduler as the TOP node scheduler  
- +  ​* ​Fill the scheduler parameters using your Dispatcher settings. Pay attention to the following things: 
-3) Start Houdini, and follow the PDG guidelines by setting the Muster scheduler as the TOP node scheduler  +  ​* ​The default Working directory value of Houdini that defaults to $HIP is not used, the working directory is a combination of the Local Shared Root Path (The shared path to your farm data, i.e. Z:​\renderfarm) and the Local Shared Folder (defaults to $HIPNAME, your scene name) 
- +  ​* ​No dependencies ​to Muster are required, all the connections are handled with the REST APIs (HTTP(s)) so be sure your Muster web server is setup and running 
-4) Fill the scheduler parameters using your Dispatcher settings. Pay attention to the following things: +  ​* ​Be sure to have to firewall running or add an exception on Houdini, the scheduler needs a local server on your GUI Houdini instance to receive callbacks and notifications of cooking status 
- +  ​* ​Be sure your Houdini PDG template is well configured on your render clients, it should point it's home variable to your Houdini root installation folder. The default template ID is 86, you may change it into the PDG scheduler 
-The default Working directory value of Houdini that defaults to $HIP is not used, the working directory is a combination of the Local Shared Root Path (The shared path to your farm data, i.e. Z:​\renderfarm) and the Local Shared Folder (defaults to $HIPNAME, your scene name) +  ​* ​The Houdini PDG template is supported on Muster 9.0.13 or greater
- +
-No dependancies ​to Muster are required, all the connections are handled with the REST APIs (HTTP(s)) so be sure your Muster web server is setup and running +
- +
-Be sure to have to firewall running or add an exception on Houdini, the scheduler needs a local server on your GUI Houdini instance to receive callbacks and notifications of cooking status +
- +
-Be sure your Houdini PDG template is well configured on your render clients, it should point it's home variable to your Houdini root installation folder. The default template ID is 86, you may change it into the PDG scheduler +
- +
-The Houdini PDG template is supported on Muster 9.0.13 or greather+
  
 Happy Cooking! Happy Cooking!