Legacy Documentation: Version 5.0
Setting Up A Clustered Scene
High Dynamic Range Rendering

Operating The Cluster

Suggest a change

Success!

Thank you for helping us improve the quality of Unity Documentation. Although we cannot accept all submissions, we do read each suggested change from our users and will make updates where applicable.

Close

Sumbission failed

For some reason your suggested change could not be submitted. Please try again in a few minutes. And thank you for taking the time to help us improve the quality of Unity Documentation.

Close

Cancel

Skip to the “Start the Nodes Manually” section below if you have your own deployment system.

Setting Up the Nodes

  1. With the master node deployment tools running, browse to <ip>:<port>/cluster of the node.

  2. Click on “Admin” tab and enter username password from Master Node: Step 5"

  3. Click “Add” on “Cluster Nodes”

  4. Fill up the form, the uri must be in this format: socket=<ip>:<port>

  5. Click “Save”

  6. Repeat to add all the nodes

Upload A Build

  1. Click on the Upload tab

  2. Compress the build into a zip file. Ensure xxx.exe and xxx_data is at the root of the zip.

  3. Click on the “Upload” button, select the zip file and click OK. The index value refers to which index this node assumes in the rig. It MUST be unique and should be used to determine the camera setup.

  4. Note that a unique id is generated for your build. This id is generated based on the zip file’s name. To update your build simply upload a zip file with the same name.

Starting the Cluster

  1. Ensure all slave nodes are turned on. See Slave Node.

  2. On the deploy page, select from the drop down the build you want to push out

  3. The selected build should be synced to all enabled slaves and will be executed together with the master node.

  4. Click StopAll

Starting the Nodes Manually

  • Master Node - This has to be started first <exe> -server <num slaves> tcp://:<pubport> tcp://:<ackport>

    • The master will not proceed if number of slaves connected is less than specified in the command line
    • ENSURE pubport and ackport is not the same
  • Slave Node - These must come after Master Node and the order doesn’t matter <exe> -client <index> tcp://<masterip>:<pubport> tcp://<masterip>:<ackport>

    • DO NOT USE “localhost” as master ip. It won’t resolve properly.
    • DO NOT use duplicate index.
  • For testing, all master and slave instances could be started on the same machine using the command line above.

Setting Up A Clustered Scene
High Dynamic Range Rendering