Vray Sun Maya

[Joseph]

Notall Render Elements get picked up by Deadline. In my testscene, only the Sample Rate element gets picked up by the vrayscene parser. Z-depth and Multi Matte get ignored. I did not test any other elements.

Even when animation is disabled in Maya, the filenames have a framenumber at the end. This framenumber is missing in the Draft assembly config file so the assembly job fails. When animation is enabled, even with just one frame, Deadline picks it up correctly.

Please let me know if you want the Maya file, vrscene file, Draft config or if you need any other info. If you think that any of this is a bug on Chaosgroups side, please let me know so I can bring it up with them.

If I specify the output file, Deadline parses the render elements correctly and also submits all needed assembly jobs. After the render finishes, the assembly job does not start automatically even though all dependencies are fulfilled. When I start the assembly job manually, I get the following error message in the logs.

Reason for using this setting in Maya: VRay will always save to the TMP folder in the renderings folder if not rendering an animation. If I am just rendering a still, setting frame name padding to 0 will get me a file name without a frame number.

The interactive submitter will submit a V-Ray Spawner job (V-Ray Standalone for Maya, Softimage, 3dsMaxRT, Rhino, Sketchup) to reserve render nodes, and the submitter will automatically update the V-Ray server list.

Here is a consolidated list of port requirements for the various versions of V-Ray. Ensure any applicable firewalls are opened to allow pass-through communication. Typically if in doubt, opening TCP/UDP ports in the range: 20200-20300 will cover all V-Ray implementations for DBR. During initial testing, it is recommended to open all ports in this range, verify and then consider tightening up security.

Port Number (Softimage/Maya/3dsMax/3dsMaxRT only): The port number that V-Ray will use for distributed rendering. In the case of Softimage, this is necessary because Softimage uses V-Ray Standalone for distributed rendering and the default port number for V-Ray in Softimage is different from the default port number in V-Ray Standalone. The port number needs to be identical on all machines including the workstation machine for a particular DCC application to communicate correctly. It is recommended to disable any client firewall whilst initial testing/configuration is carried out. Typically, opening TCP/UDP ports in the range: 20200-20300 will cover all V-Ray implementations for DBR.

Complete Job After Render (3dsMax only): When checked, as soon as the DR session has completed (max quick render finished), then the Deadline job will be marked as complete in the queue.

Active Servers (3dsMax only): Individual Deadline Workers can be enabled/disabled here (V-Ray Spawner as a job will still continue to run on the disabled Workers until the job is deleted/completed/suspended).

After the render is finished, you can press Release Servers or close the submitter UI (Setup V-Ray DBR With Deadline) to mark the V-Ray Spawner/V-Ray Standalone job as complete so that the render nodes can move on to another job.

You can also submit V-Ray Spawner/V-Ray Standalone jobs from the Monitor, which can be used to reserve render nodes for distributed rendering. Note, if you submit the job via the Monitor submission script, that you will need to manually configure/update your local workstation settings to point to the correct, corresponding Deadline Workers over an identical port number.

Port Number (3dsMaxRT/Cinema4D/Maya/Modo/Softimage/Standalone only): The port number that V-Ray will use for distributed rendering. In the case of Softimage, this is necessary because Softimage uses V-Ray Standalone for distributed rendering and the default port number for V-Ray in Softimage is different from the default port number in V-Ray Standalone. The port number needs to be identical on all machines including the workstation machine for a particular DCC application to communicate correctly. It is recommended to disable any client firewall whilst initial testing/configuration is carried out. Typically, opening TCP/UDP ports in the range: 20200-20300 will cover all V-Ray implementations for DBR.

You can configure the V-Ray Spawner/V-Ray Standalone plug-in settings from the Monitor. While in super user mode, select Tools -> Configure Plugins and select the V-RaySpawner plug-in from the list on the left.

Handle Existing DR/DBR Process: Only one instance of the same DR process running over the same port is possible. This option allows for Deadline to fail the task if this is the case or attempt to kill the currently running process, to allow the Deadline managed DR process to run successfully. Note, if the process is set to kill and does indeed kill a currently present process, but seems to auto-restart even after killing; then this indicates the process is already running as a service and the service will need to be stopped by your IT staff. Do NOT install as a service as Deadline can NOT support this configuration.

If enabled, these settings control what happens when a Worker that is running V-Ray Spawner has entered an IDLE state where it is not currently partaking in a V-Ray DBR render. We define a session as the time between a V-Ray DBR render completing and the next DBR based render starting. There are additional settings to control the behaviour once at least one DBR render has taken place on a Worker.

DR Session Auto Timeout Enable: If enabled, when a DR session has successfully completed on a Worker, the task on the Worker will be marked as complete after the DR session auto timeout period in seconds has been reached (Default: False).

DR Session Auto Timeout (Minutes): This is the timeout period (Default: 15 Minutes) when a DR session will timeout and be marked as complete by a Worker. This timeout is only active prior to the first render on the Worker.

DR Session Auto Timeout: After First Minute: This is the timeout period (Default: 15 Minutes) when a DR session will timeout and be marked as complete by a Worker. This timeout becomes active once the first render on the Worker is complete.

You can also submit V-Ray Spawner jobs for Rhino and Sketchup from the Monitor. In this case, the render nodes will simply be reserved for DBR, and the distributed rendering process itself will have to be initiated manually from within Rhino or Sketchup.

The following procedures describe how to install the integrated V-Ray DBR submission script for 3ds Max. The integrated submission script and the following installation procedure has been tested with Max versions 2012 and later(including Design editions).

As of Deadline 10.0.10 the manual submission documentation and submitter installers have been updated to install both the userSetup.mel file and DeadlineMayaVRayDBRClient.mel are being installed into the user directory. This change has occurred so the submitter installer will work without requiring admin access and to ensure that all versions of Maya will use the same client script file. This should not affect any installs and is not a required update.

The following procedure describes how to install the integrated V-Ray DBR submission script for Maya. The integrated submission script and the following installation procedure has been tested with Maya versions 2012 and later.

If you do not have a userSetup.mel in [My Documents]\maya\scripts, copy the file [Repository]\submission\MayaVRayDBR\Client\userSetup.mel to [My Documents]\maya\scripts. If you have a userSetup.mel file, add the following line to the end of this file:

If you do not have a userSetup.mel in /Users/[USERNAME]/Library/Preferences/Autodesk/maya/scripts, copy the file [Repository]/submission/MayaVRayDBR/Client/userSetup.mel to /Users/[USERNAME]/Library/Preferences/Autodesk/maya/scripts. If you have a userSetup.mel file, add the following line to the end of this file:

If you do not have a userSetup.mel in /home/[USERNAME]/maya/scripts, copy the file [Repository]/submission/MayaVRayDBR/Client/userSetup.mel to /home/[USERNAME]/maya/scripts. If you have a userSetup.mel file, add the following line to the end of this file:

The following procedure describes how to install the integrated V-Ray DBR submission script for Rhino. The integrated submission script and the following installation procedure has been tested with Rhino 5.

The following procedure describes how to install the integrated V-Ray DBR submission script for Softimage. The integrated submission script and the following installation procedure has been tested with Softimage versions 2012 andlater.

Launch Softimage. The submission script is automatically installed when Softimage starts up. To make sure the script was installed correctly, select the Render toolbar on the left and click the Render button. A Setup V-Ray DBR With Deadline menu item should be available.

V-Ray DBR interactive rendering is supported for 3ds Max, Maya, and Softimage 2012-2015. You can also submit V-Ray Spawner jobs for Rhino and Sketchup from the Monitor. In the latter case, the render nodes will simply be reserved for DBR, and the distributed rendering process itself will have to be initiated manually from within Rhino or Sketchup. Finally, V-Ray Standalone is supported for Cinema 4D and V-Ray Standalone itself.

During initial configuration of V-Ray DBR & any future debugging, it is recommended to disable any firewall & anti-virus software at both the DBR master host machine as well as all render Worker machines which are intended to participate in the DBR render. We suggest you manually get V-Ray DBR up and running in your studio pipeline to verify all is well before then introducing Deadline as a framework to handle the Spawner/Slave process.

Do I need to run the vrayspawner (or RT/vrayslave/vray Standalone) application or install vrayspawner (or RT/vrayslave/vray Standalone) executable as a service/daemon on each machine?

3a8082e126