The following is a list of builtin Nuke variables. More...
Variables | |
| threads | |
| Number of render threads. | |
| interactive | |
| Set, if Nuke is running in interactive mode. | |
| saved_version | |
| Version number written to saved scripts. | |
| script_version | |
| Version of script being loaded. | |
The following is a list of builtin Nuke variables.
Nuke provides a number of variables that return information about the inner status of the application.
Number of render threads.
This many threads are used to calculate images. This is in addition to a "main" thread used to update the GUI.
'1' means a single parallel thread, ie it does not disable multithreading. However this may be useful for getting around bugs in plugins.
'0' disables multithreading to assist in debugging. In this case the user interface will be blocked until the viewer finishes updating. If you execute a node the "cancel" button may be a bit sluggish.
The default value is the number of processors on your machine times 2.
Set, if Nuke is running in interactive mode.
If interactive is set, Nuke runs either from a terminal or with full graphical UI support. If clear, Nuke runs as a renderer.
Version number written to saved scripts.
You can set this to change the version number written to saved scripts. This can be used to save scripts that will run under an older version of Nuke without any warning message. It is your responsibility to avoid any non-forward-compatible scripts, however.
Default value is $version.
Version of script being loaded.
When a script is being read, this is set to the version number of it. This may be useful by gizmos to provide back-compatibility emulations. When no script is loaded this is set equal to $version.