How to use Distributed Rendering?
Distributed Rendering Requirements
You must have all of the following applications installed:
- On the slaves and master: Corona Renderer for 3ds Max - it is best to use the newest version available at https://corona-renderer.com/download/
- On the slaves and master: 3ds Max - any version supported by your current Corona Renderer version
- On the slaves and master: Autodesk Backburner version matching your 3ds Max version - it is included in the 3ds Max installation package, or can be downloaded and installed separately. You need to have the exact version matching your 3ds Max version (for example Backburner 2019 if you are using 3ds Max 2019).
- On the slaves: Corona DR Server - it is included in the Universal Installer, and by default it is installed into C:\Program Files\Corona\DR Server\DrServer.exe.
Note: Autodesk Backburner is not directly used in Corona Distributed Rendering process but it is required for it to work correctly.
Note: Starting with Corona V3, the DR server is installed in a separate subfolder of the the main Corona install folder (in Corona versions prior to V3, the DR server was installed into the Corona root folder, C:\Program Files\Corona)
For Backburner installation/uninstallation troubleshooting, see: Distributed Rendering does not work - "Unknown error while loading application"
- DrServer.exe must be running on all slaves
- All slaves must be on the same LAN network and sub-network
- Both 3dsmax.exe and DrServer.exe must be allowed to communicate (both incoming and outgoing connections) on these two ports: TCP 19667 and TCP 19668. Sometimes adjusting firewall settings may be necessary
- Both the workstations and the render nodes taking part in the distributed rendering must have Corona Renderer licenses active!
See: Activating Corona Renderer
- 3ds Max does not have to be activated on the slaves. You may use the demo license, or even an expired demo license and that is absolutely fine with Autodesk licensing terms as 3ds Max will be used in command line mode only, without the user interface visible.
Using Distributed Rendering
- On all slaves: run the DrServer application
Note: the DrServer must not be running with elevation (it must not be running "as administrator").
Do not run DrServer on the master pc!
- On the master PC: in 3ds Max, go to Render Setup > System > Distributed Rendering, tick the "Enable" checkbox, and press "Search LAN"
- On the master PC: wait for the addresses or names of your slave PCs to appear on the list (or enter their network names or IPs manually via the "Add" button at the bottom)
- On the master PC: start rendering
- On all slaves: a new 3ds Max instance should appear after some time (minimized, so you won't be able to see its UI or the VFB), then it should start rendering your scene, and sending rendered data to the master PC based on "Synchronization interval" time specified in the DR rollout on the master.
- On master PC: you can see Distributed Rendering information in the DR tab of the Corona VFB
Note: you can also check "Search LAN during render" option in the DR rollout on the master PC to make Corona search for any machines with the DrServer application running and automatically add them to the rendering even after it has already started. As a result, any machines where the DrServer application was launched at some point during rendering will join, and any machines where the rendering was interrupted due to an error or user intervention will be able to re-join the rendering again.
The rendering will stop after it reaches the given render limit, or after you stop it manually on the master computer. In case of render limits, each limit is considered based the master machine statistics, not for each of the slaves. For example, if you set the limit to 10 minutes, the rendering will stop after 10 minutes pass on the master machine, not on the slaves. If you set it to 100 passes, it will stop after the total number of passes (reported on the master machine) will reach 100, regardless of how many passes each slave has rendered. If you use the noise limit, it will stop once the target noise level is reported on the master machine.
Distributed Rendering Troubleshooting
For known solutions to problems with Distributed Rendering please refer to our Distributed Rendering Troubleshooting Section.
Note: the error messaging system will catch the known issues, and will warn you about any detected problems. This is often helpful for troubleshooting.
- First diagnostic step when experiencing DR issues is always disabling all installed antivirus / firewall software on both the master and render node machines.
This does not mean that AV / firewall software should be always disabled when using DR. But it can verify if the issue is related to this software at all. If so, then further steps can be made to fix the issue.
The usual solution is adding custom rules to Windows Firewall to allow DR. See: Creating custom inbound and outbound rules
- Using DR with a VPN
- "Unknown error while loading application" message
- Missing assets when DR server is running in administrator mode
- "Creating a Render Farm" forum thread - https://corona-renderer.com/forum/index.php/topic,12173.0.html
- General guide on reporting issues - How to report issues