renderdl reads a file containing scene description commands and “executes” them. Such files are commonly referred to 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:
Command Line Options
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 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:
Outputs the NSI commands in binary format. For example:
Outputs the NSI file in compressed form. For example:
|Prints the current version of the renderer.|
Prints the following help:
Expand to view
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.|