autodesk backburner not always maxing out cpu

Log onto the machine, launch 3ds Max and render the scene. Make sure that the scene renders locally on the Render Slave machine. You can re-run the test after checking on each item in the list of possible causes until the issue is resolved. Make a few basic primitives, add a light and try running a DR job to see if it succeeds or fails. This issue is easy to debug with a very simple scene. We recommended reading the Setup Distributed Rendering page for all necessary steps to properly configure your DR setup. More information about this can be found bellow in the Multiple V-Ray Spawners running at the same time section.

Multiple V-Ray Spawners are running at the same time.

For more information on tools that can be used to check network and port connectivity, please the Tools for Testing Network Connectivity page. You can stop the Spawner and check if another process is occupying the same port. If the ports used by V-Ray are already taken by another application, then the Spawner will not be able to receive and send information.

Another process is already using one or more of the communication ports.

More information about configuring your license setup can be found here. E ach Render Slave needs a Render Node license in order to participate in Distributed Rendering.

A Render Node license is not available.

If you observe 3dsMax to constantly appear and then disappear in the Windows Taskbar when V-Ray Spawner is launched, then most likely Backburner is not installed. To function properly, V-Ray DR requires Autodesk Backburner to be installed on each Render Slave.

Autodesk Backburner is not installed on the Render Slave.

This ensures proper communication between the Render Slaves and the License Server.

Incoming and outgoing communication should be allowed for V-Ray Spawner on TCP port 30304 on the Render Slaves. This ensures proper data exchange between the Workstation and the Render Slaves. Incoming and outgoing communication should be allowed for V-Ray Spawner on TCP ports 20204 (for CPU Rendering) and 20206 (for GPU Rendering) on the Workstation and Render Slaves machines. Check if the following permissions are set correctly: Since network configuration is a very large topic, it is recommended to involve an IT specialist to debug your network setup in more depth. This can be checked in the Windows Services app. If the spawner runs as a service - make sure that a “VRaySpawner for 3ds Max 20xx” ( “20xx” is your 3dsMax version) is started as a Windows service. Log on to the Render Slave machine and ensure that a V-Ray DR Spawner is running.

It is fairly easy to check if that's the cause and fix the problem.

Autodesk backburner not always maxing out cpu