Render Settings
Priority
Jobs with higher priority are usually send first.
There are some exceptions (see rrConfig, tab Jobs):
- You can setup RR to average clients between projects, so each project gets the same amount of render power,
no matter if one project uses priority 60 and the other project uses priority 50 for all its jobs.
By default the averaging is enabled if your job has a priority of 20-80.
Which means if you use helper button "ultimate" or "low", your job is rendered before or after all other jobs no matter the project.
Note that you can disable "ultimate" priority via the rrSubmitter Default files for non-rrAdmins. - By default the preview rendering stage of a job has a +20 higher priority.
- You can tell a client to prefer e.g. Nuke jobs, no matter if Maya jobs have a higher priority.
Abort Jobs with lower priority
After the rrServer receives the new job, it will abort all jobs that are rendering on the assigned clients and that have a lower priority than the new job.
Render Preview First
Before RR renders all frames, it will render a few frames of each job first.
See Preview Render
Do Not Check For Frames
Usually the rrServer checks each job and counts the frames done.
If there is a frame missing, the server tries to render it.
There are some jobs that do not produce output images or it is not possible to tell RR the right image name.
Then you can enable this setting.
Each frame of the job is send once. The server does not check if there is a frame missing.
Little Job
Little jobs are send to clients even if the client is disabled.
They will use less CPUs if the client is disabled.
GPU required
Not all machines are able to process GPU rendering.
Even if you can login on the machine and use the GPU, it might not work with RR.
Please see rrHelp section Infos/GPU rendering.
The sole task of this checkbox is to tell the rrServer NOT to send this job to machines that have no GPU.
Note that each Client has a config setting "GPU requires user X to be logged in" and there is another rrJob option "GPU in Appmode required" for OpenGL renderer.
Preview- Contiguous Frames
Instead of using a wide spread of frames from your sequence, this option uses the first, last and a middle segment of the sequence.
This is useful if you want to check for example the noise of contiguous frames
No Frame by Frame Loop
Royal Render controls many render applications via a script.
It calls the render function in a loop for each frames.
For some renderer like OpenGL it might be faster to tell the renderer to render many frames at once.
(Note that RR enables this settings while renderering automatically if the frame time is very low, but enabling it right away still improves speed)
Number of Preview Frames
Sets the number of preview frames shown on the job information page at rrControl/rrWebsite.
GPU in Appmode required
The NVidia driver does not allow OpenGL rendering within a Windows background service.
Therefore you have to enable this setting for these jobs.
AMD driver do not have this restriction.
Please see rrHelp section Infos/GPU rendering for more information.
Start Multiple Instances
A client can start multiple instances of the same render.
E.g. if it receives the frame frame 1-8, then the rrClient can up to start 4 render instances, each render instance will render 2 frames (1-2, 3-4, 5-6, 7-8 ).
You should consider using multiple render threads on a client instead for most render jobs.
A seperated render thread can take its own job with a different frame range.
Sequence Divide