Configuration

Parent Previous Next




New job data folder location

The job data are log files, preview images, rrViewer caches, html files, framebars, ...

The folder for the job data has changed from [RR]/website to [RR]/rrJobdata.

You can now decide to change this folder into [CompanyProjectRoot]/rrJobdata.

This way users who do not have access to the project cannot view any render log file.

See "Hide jobs without file access" as well.



Seperate project name settings  per OS

 As you have different mapping/mount points on each OS, you can now define how RR gets the project name from the path for each OS.



Caching fileserver

RR supports caching fileservers.

For example half of your clients render to a cache fileserver XXXX. 

And after some time, these files get transfered to your main fileserver by your caching system.

The rrServer will search your main and cache fileserver for output files and pauses the job until all files are on your main fileserver.



Convert fileserver name into IP

The rrSubmitter can convert fileserver names  \\YourFileserver into the IP of the fileserver \\192.168.0.12 at submission.



Cost per render license

Define cost per hour for each renderer. 



Multiple renderer license types

Set a different number of render licenses for a pools of clients. Each client has a config setting in which license pool it is.

Available render license pools are:  Default, Workstation, Renderfarm, Cloud. 

You can use commandline switches in your render config as well to change the license type an application is using. If your render applications offer you to switch between for example interactive UI licenses and batch licenses.



Disallow the rrServer to convert preview images

The preview images that you see in rrControl are either converted by the client at render time.

Or, if that fails or if they are busy, then the rrServer converts preview images. This slows down the rrServer execution.



New user setting to prevent sending jobs

Disallow users to submit jobs.




Config update via TCP/IP

If you change a setting that affects a client, the rrServer will send the new config to the rrClients via TCP/IP.

This way the rrClient does not have to load the config files itself.