When the task bar icon 'Open' is selected, the window shown on the right is opened. The options of the window correspond the startup switches of the RendD rendering daemon.
Starts / stops the rendering daemon (RendD) with the specified options. This option can also be controlled via the On-line and Off-line pop-up menus associated with the task bar icon.
When enabled, network users can use the workstation for rendering.
Specifies the maximal amount of clients, which will be served simultaneously. Under normal circumstances (i.e. when the daemon is configured to use all available processors and sub servers), this control should have value 1. Then only one client will be served at a time. Providing rendering services to several clients simultaneously can cause virtual memory swapping, which slows down rendering. Powerful multi processor systems with a large memory capacity can naturally serve several clients. For example: a quad processor system with 8 gigabytes of RAM in a network of multiple users, who constantly need rendering power, could be configured as follows:
With these settings, the daemon will give each client only one rendering thread. One client cannot use all resources of the workstation and therefore several clients can be served efficiently.
Enables automatic image sub division. If checked, the program attempts to find an optimal box count based on the image resolution and the number of threads and sub daemons in external workstations.
BoxCountX / BoxCountY
If automatic subdivision is disabled, these fields determine the number of sub images generated to distribute rendering.
Enables automatic thread detection to take advantage of multiple processors available in the workstation (SMP). If checked, the number of rendering threads, which are started to serve each client corresponds to the number of processors. In other words, a client gets the total rendering power of the server computer.
The number of threads spawned for rendering. This option can be controlled only when Automatic multi threading option is not set.
Automatic Sub Servers
This option is needed only when setting up hierarchical rendering farms. If checked, the rendering daemon searches the network and joins the other servers it finds to the rendering farm. For example: a client connects to only one rendering daemon via internet. The daemon the redistributes rendering to it own sub servers using this option. The actual client will not know how many servers eventually render the image.
|You should never set the Automatic Sub Servers option for multiple rendering daemons in a same local network. Similarly, the rendering client and the rendering daemon running on a same LAN should not use the automatic configuration feature simultaneously.|
Specifies the maximal amount of memory (in megabytes), which the computer system is allowed to use for rendering. This option is used only when the client uses the Automatic Network Rendering option. Clients won't send projects to servers, which don't have enough memory to render the scene or whose owner does not want to use more memory than a certain limit. By default, the value is set to the amount of physical memory.
Add / Remove
Add and Remove buttons below the host list allows you to add and remove host names manually. These fields are disabled if the Automatic Sub Servers option is active.
If the host list is configured manually (Automatic Sub Servers off), you can select a host from the list and disable it temporarily using this checkbox.
Host / Port
These fields specify the host name and port number through which clients can contact the daemon.
Turns on image map caching to the local system. The proxy option is active by default and should be used by default.
This option controls the proxy cleanup system. Textures older than the given amount of days are removed. Cached textures are placed into temp folder.
|Do not place important files into temp folder! Cleanup will remove them.|
This field specifies search paths for textures. This field is only needed when texture proxy is not used. More than one search paths can be defined by separating them using a semicolon.
Enables printing of additional diagnostic information into the server log tab.