Submitter Defaults

Parent Previous Next


You can change the default settings for the job settings via config files.

These files can be different for each user, company project, machine or render application.

You can even define them via commandline and via the scene info xml as well.

And the settings are stackable, see


You can edit the files via the rrSubmitter menu.


Edit via text editor

A # in front of a parameter means it should be ignored.

All preset files have this # by default.

You have to remove the # first, then you can change the values.


Edit via UI

The UI editor shows you all possible files that can hold value overrides. 

Besides the render config files!


Select a file you want to change on the left side and either hit Edit or Create.

Load Order


The files are loaded in this order:

0) renderapp/_config/[renderApp].cfg

---------------------------------------

1) sub/cfg_global/submitter_first.txt

2) sub/cfg_user/submitter_prj_[ProjectName].txt

3) sub/cfg_user/submitter_usr_[UserLoggedIn].txt

4) sub/cfg_user/submitter_mac_[MachineName].txt

5) Commandline

6) ("Show All" button: Sets allowChange=1 for all options, => all options are visible)

7) sub/cfg_global/submitter_last.txt

8) sub/cfg_global/submitter_last_non_admin.txt 

---------------------------------------

9) renderapp/_config/[renderApp].cfg



The Settings are stacked:

e.g. If you set a value in 1) submitter_first and this value is not set in any other config file, it is kept.

Values set in 3) user configs overwrite values from 1) submitter_first.




The different files are used for:

1) First

Basic global settings for all users, projects on the farm

2-4) prj_[ProjectName]

usr_[UserLoggedIn]

mac_[MachineName]

Override settings for one special project only, one user only or one machine only.

5) Commandline

For a per job base. Mostly used for automated commandline submission.

6) Show All

If you need a setting for the current job and it is not shown, press the button

7) Last

This config is used to verify that some settings are set, no matter what you have set before. So no matter what you have set in the project config, these settings will apply. 

8) last_non_admin

Similar to 7), but this one is only loaded if the user logged in is not a RRender admin. So if you want that default users can never change an option, you have to set it in this file.

0) 9) renderapp/_config/[renderApp].cfg

0) 9) The render application config is applied two times

The first time 0) it is loaded as basic settings for the render application.

Then all the submitter config files are overwriting the parameters.

Then 9) the render application config is checked again if parameters are not allowed for that render application.
If a render application does not allow some parameter, it is simply not possible to use it with that application.
To ensure that those options are not set, it is checked again while a job is send to the rrServer


To choose if a settings should be used as base 0) or forced to be set 9), you have to use the AC/AllowChange part of the parameter.

E.g.

Base value: SeqDivMIN= 1~3

Forced to set: SeqDivMIN= 0~3




Note:

A # in front of a parameter means it should be ignored and is skipped!





Which presets have been used?



If there are default variables used, then the file is checked in the rrSubmitter menu. And shows the number of values loaded.


Create new preset files


Open the submitter and choose "Edit preset file" via the menu.


You have to remove the # in front of the parameter to take effect.

(But do not remove it in the line with the parameter description "= AC~..") 


Examples


Render into a separate layer subfolder



The preset <Layer> only is not available by default.

You can add it via the rrSubmitter menu "default values", "Edit preset file" "first".

Add a line PathPresets= <Layer>\

This makes the preset available.


If you want to use it for all jobs add a line

OverridePathPreset=1~1~<Layer>\


If you want to use it for Softimage jobs only, you have to add the OverridePathPreset line to the XSI render config RR\render_apps\_config\3D01__Softimage__.... 


Sequence/Shot/Version


The Sequence/Shot/Version has some additional functions.

Possible values:

<auto>

if it is set to <auto>, then the settings in rrConfig, tab jobs is used to get the values

any hardcoded value

You can just write any value and this value is used.

<s XX>

<s XX><e XX>

You can add the same logic as you have in rrConfig, tab jobs.

Set the string that is right before your value, use <s XX> (XX is the string)

Set the string that is right after your value, use <e XX> (XX is the string)

If you do not set a <e XX>, then the next underscore, point or the end of the complete name is used.


sA043_sh34_v54.scn

Sequence= A43 , Shot=34, Version=54

CustomSeQName=1~<s s>

CustomSHotName=1~<s _sh>

CustomVersionName=1~<s _v>

MAN_TR7_0270_light_CHR_np_v0011.Alpha.1001.exr

Sequence= 7 , Shot=0270, Version=0011

CustomSeQName=1~<s _TR>

CustomSHotName=1~<s _>

CustomVersionName=1~<s _v>

A043sh34_v54.scn

Sequence= A43 , Shot=34, Version=54

CustomSeQName=1~<s >

CustomSHotName=1~<s sh>

CustomVersionName=1~<s _v>