The mental ray service name is based on the version of mental ray that ships with Softimage. The version number specified in the documentation may differ from the actual version of mental ray that you are using.
This section contains solutions to common problems with distributed rendering.
Slaves Not Rendering
If a slave is not participating in the distributed rendering, check to see if:
• It uses a different version of mental ray from the other computers in the network. All computers in a distributed rendering network must use the same version of mental ray.
• Its shaders are located in the same path as the master. To find the specific cause of the problem, open a Softimage shell (command prompt) and enter:
ray3.exe -verbose on
This produces a detailed account of ray3’s actions.
Render Not Starting
Make sure that you have enough licenses available. From the Lictools program, check the SPM server log for license request information.
Corrupted Images
If your rendered images have corrupted tiles, a slave may be losing its connection to the license server. Ensure that the license server is not running any memory-intensive tasks.
Machine Won’t Load For a Network Render
If a machine won’t load for a network render with mental ray, try the following to see if the machine is responding:
For example, if sparky won’t load, type:
telnet sparky mi-raysat3_7_52_5
• If you see some messages (“Escape character is...”), this is good.
• If you see “Unable to connect...”, there is a problem with the slaves’ /etc/inetd.conf or /etc/services.
|
The mental ray service name is based on the version of mental ray that ships with Softimage. The version number specified in the documentation may differ from the actual version of mental ray that you are using. |
Autodesk Softimage v.7.5