Global
Sort Client List
You can sort and remove clients from the list via this table.
Sorting Clients
The sort command is available after you select some clients and right-click on the selection
Removing clients
Important:
If a client starts, then it adds itself to the list.
So if you want to delete a client, then you have to be sure the client is not running any more.
Deinstall the service/deamon on the machine and shut the rrClient down if it is running.
Local scene and texture cache
With these settings you can control how many days the textures are cached and how many free drive space should be kept (for rendering, the artist logged in and for new software installations).
RR has 2 different features that are affected by these settings:
1) Local Scene Copy
This is a rrJob option and is enabled by default for many render apps.
The scene is copied to the local drive first before it is loaded.
2) Local Texture Copy
This is a special feature that requires special submission tools.
See rrTerms/Local_Data_Folder for a description of Local Textures.
Wake on Lan
Wait x seconds between WOL |
The Server has a delay between auto-WOL of Clients. Waking up all clients at the same time can be a problem with the power supply architecture. |
WOL if more than x clients needed |
The server will wake up new clients if the current jobs require more than x clients to finish. See current WOL client need on the rrWebsite (client table) or in rrControl (global info tab) |
WOL port |
You sometimes require to change the WOL port that your switches send them to all other machines. If WOL is not working, try port 80. |
Subnet mask |
The subnet mask of your network. It has to be the same as in your machines TCP/IP config |
Send WOL Modes |
For most networks "General Broadcast" is sufficient. |
Network
Connect to rrServer via |
You can decide how the rr Applications try to connect to the rrServer. This can be either via
|
A client connects every x sec. to Server |
Each client connects to the server in invervals. You can set the delay time via this setting. A client can get commands/jobs only at the time it connects to the server. |
Server TCP/IP Port |
Port used for all RR communication. If you use a firewall inside your network, please open this port. (of course this port should be closed at your firewall to the internet) |
Network adapter to listen for connections |
By default the rrServer asks the system to get all TCP connections with the RR port on any network adapter it has installed. You can restrict the network adapter in case you want to restrict the rrServer to one network. |
Defer Mode
If you have a lot of free clients assigned to a job, then the rrServer sets the slower clients into "Idle - Defer Mode".
This mode is similar to "disabled", the clients do not get a job.
Just temporaly.
As soon as the faster machines get rendering, the less faster machines switch from "Idle- defer mode" into "Idle" and are able to get jobs.
There are two reasons why a client is in defer mode:
- You have a lot of idle clients assigned to the job. The faster machines are not rendering yet.
The slower ones are in "defer mode" until the faster ones render. - The clients are not assigned to the job or cannot render the job.
Therefore they have no job to render and are in "defer mode".
To check if a client can get a job, please select the client and the job in rrControl and execute menu Debug/Show Servers send decision. It will show a reason why the client does not get the job.
Config presets for new clients
You can setup the configuration of a client in two different ways:
Config Preset |
There are two ways to set the config of a client:
Config presets are set in menu Clients / Per Client |
Render License Group |
You can set a different number of licenses for different parts of your render farm |
Drive Mapping |
You can set different drive mappings for different regions. |