Known Issues with Distribeast

This page details some known issues and limitations with the current version of Distribeast. If you encounter additional problems, or you want to request additional features, please do not hesitate to contact Autodesk Support. See Support.

More than 32 logical processors are not detected

Currently, Distribeast is distributed as a 32-bit process. So, it detects only 32 logical processors in a computer. If your computer has more than 32 logical processors, you cannot use all of them for rendering. As a workaround, you can divide the computer into multiple virtual machines.

Installation fails when Windows Firewall is disabled

To prevent connectivity issues, the Distribeast installer will fail if it is unable to add the necessary firewall exceptions to the Windows Firewall configuration. This also occurs when the Windows Firewall is disabled. For details on how to work around this limitation, see Installing Distribeast.

File access rights

Currently, Distribeast requires read access to the resources in the Beast cache. The directory you specify in your call to the ILBCreateManager() function will automatically be updated to be readable by the NetworkService account.

Sleep issues

When a computer with a Distribeast node sleeps, it becomes disconnected from other nodes. However, when Windows resumes, the Distribeast node may not immediately detect that it has been disconnected. The Distribeast node should attempt to reconnect to the controller soon after waking. If this takes too long, you can stop and restart the Distribeast service manually in order to resume normal operations.

Controller connectivity

If the controller has a shaky network connection that causes it to lose connections to other computers, this may interfere with your rendering jobs. Make sure that you choose a computer that has a stable network connection to be the controller for your Distribeast deployment.