Some of 3Delight's behaviour can be configured through options that can be specified in the 3delight.config
configuration file. The renderer looks for it in four different locations in the following order:
- In 3Delight's installation directory, as specified by the
$DELIGHT
environment variable. - In the directories specified by the
$DELIGHT_CONF
environment variable (a colon separated list). - In user's home directory, as specified by the
$HOME
environment variable. It also looks for an.3delight.config
file in the same directory. - Finally, the
3delight.config
in the current directory. ← Do we need to keep this ???
If 3Delight encounters the file in more than one location, it uses the latest keys and values it finds (so that latter options settings override former ones). This enables to have a site specific configuration file in the $DELIGHT
or $DELIGHT_CONF
directories and user specific settings in their home directory. The former often is best left to the system administrator responsible for the software installation.
Each line in the configuration file is of the form "key value1 [value2 ... value_n]
". The recognised keys are:
Key | Description |
---|---|
networkcache.directory | Specifies the directory for 3Delight's network caching. Should point to directory located on a local drive (disk or, better yet, SSD) on each render nodes. |
networkcache.size | Specifies the maximum size (in GB) of 3Delight's network cache. The recommended minimum size is 30GB. Large projects (with lots of texture maps) could easily benefit from 100GB or more. |
license.server | Specifies the name or address of the license server to be used. |
license.hold | By default, the renderer will request new licenses for every render and release them once it’s done. Multiple request/release can be undesirable if several frames are rendered in sequence from the same process. If this option is set to 1, the licenses obtained for the first frame are held until the last frame is finished. |
license.wait | If this attribute is set to 1, 3Delight will wait for a license when no license are available for rendering. Otherwise (If it is set to 0), 3Delight will stop/exit if no licenses are available. The latter setting is useful when managing a render farm and other work could be scheduled instead of leaving a machine waiting for a license for rendering. |
The following is the default 3delight.config
file content (included in the 3Delight's installation directory):
|