renderdl
reads a file containing scene description commands and “executes” them. Such files are commonly called NSI files (NSI stands for Nodal Scene Interface). There are two kinds of NSI files: ASCII encoded and binary encoded. A binary NSI file is smaller than its ASCII encoded equivalent, but an ASCII NSI file has the advantage of being human readable and editable in a text editor.
To render a file named file.nsi
, just type:
renderdl file.nsi
Command Line Options
Option | Description | ||||||
---|---|---|---|---|---|---|---|
-t n | Specifies the number of threads to use for the rendering. "n" can take any of the following values:
| ||||||
-stats | Embed statistics in rendered images. This is supported for EXR and TIFF files only. Statistics are explained in more detail in Understanding 3Delight Statistics. | ||||||
-progress | Prints a progress status after each rendered bucket. | ||||||
-cat | Print NSI commands instead of sending them into the renderer. An example usage is converting a binary (or compressed) NSI into an human readable ASCII version: renderdl -cat binary.nsi.gz > ascii.nsi | ||||||
-cat -binary | Outputs the NSI commands in binary format. For example: renderdl -cat -binary ascii.nsi > binary.nsi | ||||||
-cat -gzip | Outputs the NSI file in compressed form. For example: renderdl -cat -gzip ascii.nsi > ascii.nsi.gz | ||||||
-v | Prints the current version of the renderer. | ||||||
-h | Prints the following 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:
renderdl Reading (stdin) <enter commands here>
If you wish to pipe the content of file.nsi
in renderdl
, type:
cat file.nsi | renderdl
Shell Return values
The renderdl
executable will return one of the following values:
Return Value | Description |
---|---|
0 | No error. |
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. |