Formats default to anamorphic.

Limit the cache memory usage, where size equals a number in bytes. You can specify a different unit by appending k (kilobytes), M (megabytes), or G (gigabytes) after size.

Nuke attempts to render subsequent frames in the specified range after an error. When --cont is not specified, rendering stops when an error is encountered.

Breakpad crash reporting allows you to submit crash dumps to Foundry in the unlikely event of a crash. By default, crash reporting is enabled in GUI mode and disabled in terminal mode.

Use --crashhandling 1 to enable crash reporting in both GUI and terminal mode.

Use --crashhandling 0 to disable crash reporting in both GUI and terminal mode.

Tip:  You can also use the NUKE_CRASH_HANDLING environment variable to control crash handling. See Environment Variables for more information.

This allows Nuke to be viewed on one machine while run on another. (Linux only and requires some setting up to allow remote access to the X Server on the target machine).

Open Nuke script at full resolution. Scripts that have been saved displaying proxy images can be opened to show the full resolution image using this flag. See also -p.

Frame numbers to execute the script for. All -F arguments must precede the script name argument. Here are some examples:

• -F 3 indicates frame 3.

• -F 1-10 indicates frames 1, 2, 3, 4, 5, 6, 7, 8, 9, and 10.

• -F 1-10x2 indicates frames 1, 3, 5, 7, and 9.

You can also use multiple frame ranges:

nuke -F 1-5 -F 10 -F 30-50x2 -x myscript.nk

When set, enables GPU usage in terminal mode with an optional GPU index argument, which defaults to 0. Use --gpulist to display the selectable GPUs.

Note:   Overrides the GPU set in Preferences > Performance > Hardware when run in interactive mode.

Prints the selectable GPUs and their corresponding index for use with the --gpu ARG option.

Display command line help.

Display command line help.

Use an interactive (nuke_i) RLM license key. This flag is used in conjunction with background rendering scripts using -x. By default -x uses a nuke_r license key, but -xi background renders using a nuke_i license key.

Note:  If you still use FLEXlm licenses and you're interested in making a move to RLM licensing, please contact sales@foundry.com to obtain a replacement license.

New read or write nodes have the colorspace set to linear rather than default.

Set the number of threads to the value specified by #.

If have multiple GPUs of the same type installed, you can enable this preference to share work between the available GPUs for extra processing speed. This is a global preference and is applied to all GPU enabled nodes.

Note:  For more information on GPU support, see the Release Notes for your version of Nuke.

Open script without postage stamps on nodes.

When crash handling is enabled in GUI mode, submit crash reports automatically without displaying a crash reporter dialog.

Tip:  You can also use the NUKE_NO_CRASH_PROMPT environment variable to control the crash prompt. See Environment Variables for more information.

Launch Nuke Assist, which is licensed as part of a NukeX Maintenance package and is intended for use as a workstation for artists performing painting, rotoscoping, and tracking. Two complimentary licenses are included with every NukeX license.

Open Nuke script at proxy resolution. Scripts that have been saved displaying full resolution images can be opened to show the proxy resolution image using this flag. See also -f.

Measure your nodes’ performance metrics and show them in the Node Graph. See Using Performance Timing for more information.

Initial Viewers in the script specified on the command line should be paused.

Measure your nodes’ performance metrics and write them to an XML file at render time. See Using Performance Timing for more information.

Runs Nuke in Nuke Non-commercial mode. See About Nuke Non-commercial for more information.

Runs Nuke with a different priority, you can choose from:

• high (only available to the super user on Linux/OS X)

• medium

• low

Prevents the application of knob defaults to the root node when executing a Python script.

Quiet mode. This stops non-essential printing to the command-line and suppresses information pop-ups, such as loading autosaved scripts and local changes to LiveGroups.

Allows you to remap file paths in order to easily share Nuke projects across different operating systems. This is the command line equivalent of setting the Path Remaps control in the Preferences dialog.

The --remap flag takes a comma-separated list of paths as an argument. The paths are arranged in pairs where the first path of each pair maps to the second path of each pair. For example, if you use:

nuke -t --remap "X:/path,Y:,A:,B:/anotherpath"

• Any paths starting with X:/path are converted to start with Y:

• Any paths starting with A: are converted to start with B:/anotherpath

The --remap flag throws an error if:

• it is defined when starting GUI mode, that is, without -x or -t

• the paths do not pair up. For example, if you use:

nuke -t --remap "X:/path,Y:,A:"

A: does not map to anything, and an error is produced.

The --remap flag gives a warning (but does not error) if you give it no paths. For example:

nuke -t --remap ""

Note:  Note that the mappings are only applied to the Nuke session that is being started. They do not affect the Preferences.nk file used by the GUI.

Sets the stack size per thread, in bytes. The default value is 16777216 (16 MB). The smallest allowed value is 1048576 (1 MB).

None of Nuke's default nodes require more than the default memory stack value, but if you have written a custom node that requests a large stack from the memory buffer, increasing the stack size can prevent stack overflow errors.

Running Nuke in safe mode stops the following loading at startup:

• Any scripts or plug-ins in ~/.nuke

• Any scripts or plug-ins in $NUKE_PATH or %NUKE_PATH%

• Any OFX plug-in (including FurnaceCore)

Forces Nuke to obey the render order of Write nodes so that Read nodes can use files created by earlier Write nodes.

Terminal mode (without GUI). This allows you to enter Python commands without launching the GUI. A >>> command prompt is displayed during this mode. Enter quit() to exit this mode and return to the shell prompt. This mode uses a nuke_r license key by default, but you can get it to use a nuke_i key by using the -ti flag combo.

Terminal Mode. This also starts a QApplication so that PySide/PyQt can be used. This mode uses an interactive license, and on Linux requires an XWindows display session.

Enables the new top-down rendering project setting to render the full frame at the cost of more memory. Although top-down rendering produces the full frame faster, it disables progressive rendering and uses more memory. You may want to use the classic method if you're only interested in the first few scan lines in the Viewer.

Note:  The render mode is only saved as part of the script if you set render mode to top-down in the Project Settings. This ensures that the chosen render method is used the next time the script is opened. Using the --topdown command line argument does not save the render mode in the script.

Verbose mode. In the terminal, you’ll see explicit commands as each action is performed in Nuke. Specify the level to print more in the Terminal, select from:

• 0 (not verbose)

• 1 (outputs Nuke script load and save)

• 2 (outputs loading plug-ins, Python, Tcl, Nuke scripts, progress and buffer reports)

This command displays an image file inside a Nuke Viewer. Here’s an example:

nuke -v image.tif

Only execute the specified views. For multiple views, use a comma separated list:

left,right

Display the version information in the shell.

Launch Nuke and activate the specified workspace automatically. Any named layout specified in the Workspace dropdown is valid, including custom workspaces. For example:

--workspace Compositing

--workspace "Monitor Out"

--workspace MySetup

Tip:  If the workspace name contains a space, you may need to add quotes around the name.

eXecute mode. Takes a Nuke script and renders all active Write nodes.

Note:  Nuke Non-commercial is restricted to encrypted .nknc scripts with -x from the command line, that is, using the syntax:
nuke -x myscript.nknc

This mode uses a nuke_r license key. To use a nuke_i license key, use -xi. This is the syntax:

nuke -xi myscript.nk

On Windows, you can press Ctrl+Break to cancel a render without exiting if a render is active, or exit if not. Ctrl/Cmd+C exits immediately.

On Mac and Linux, Ctrl/Cmd+C always exits.

Note:  If you still use FLEXlm licenses and you're interested in making a move to RLM licensing, please contact sales@foundry.com to obtain a replacement license.

Render only the Write node specified by node.