renderdl reads a file containing scene description commands and “executes” them to produce an image.
renderdl also has some auxiliary usage as explained in the parameters description below.
In the simplest form, to render a file named
file.nsi, just type:
Command Line Options
|-cloud||Render the file using 3Delight Cloud instead of locally.|
|-collective name||Render the fils using 3Delight Collective with the specified collective|
|-lowpriority||Launch the render using a lower system priority. This is useful when using the same machine for batch renders and 3Delight Collective renders.|
|-id||Launch 3Delight Display to display the image while rendering instead of writing images to files (as specified in the NSI file).|
Specifies the number of threads to use for the rendering. "n" can take any of the following values:
n > 0 : Use "n" threads.
By default, renderdl use as many threads as there are available cores.
|Prints a progress status after each rendered bucket.|
Print the NSI commands in human readable ascii format instead of processing them for rendering. This can be used to convert a binary (or compressed) NSI file into an human readable ASCII file:
Outputs the NSI commands in binary format. For example:
Outputs the NSI file in compressed form. For example:
|expand all procedurals and archives. This is very useful when packaging an NSI file.|
|output NSI stream to filename instead of stdout.|
|Interpret input file as a LUA file.|
|Prints the current version of the renderer.|
Prints the help.
No File Name Specified
If no file name is specified,
renderdl reads scene description commands from the standard in. This feature enables piping commands directly in
renderdl. For example, to enter scene description commands interactively (which is not really practical), do the following:
If you wish to pipe the content of
Shell Return values
renderdl executable will return one of the following values:
|1||Bad combination of parameters. An error message will explain why.|
|199||Option "licensing" "waitforlicense" 0 was used and no license was available.|
|255||The NSI file specified on the command line could not be read.|