Q100112: Launching Nuke in verbose mode and isolating potential customisations causing issues



If you are experiencing issues with Nuke/NukeX/NukeStudio but find that launching in safe mode resolves your issue, then it is likely that the issues you are seeing may be due to a plug-in or customisation installed on your system. You can use verbose mode to determine what plug-ins/custom scripts you have installed and then begin to troubleshoot which one(s) might be the possible cause.


Launching Nuke in verbose mode

To launch Nuke/NukeX/NukeStudio in verbose mode you need to use the -V flag when launching from a terminal or Command Prompt. Exact steps are below.

Please note that you will need to add --nukex, --hiero or --studio to the command below in order to launch NukeX, Hiero or NukeStudio as appropriate.

NOTE: The commands below are to launch Nuke 14.0v5 in verbose mode. If you are running a different version, then please change the command to your version of Nuke.

Open Command Prompt and run the following command:

"C:\Program Files\Nuke13.2v4\Nuke13.2.exe" -V

To avoid missing part of the verbose mode output in Command Prompt, you may want to change the screen buffer setting to ensure the entire output can be displayed. This can be done by doing the following:
1) Right click the top window bar of Command Prompt and select Properties from the drop down menu. Edit these 
2) In the Layout tab, under the Screen Buffer Size, increase the Height value. The maximum is 9999.

Open a terminal from Finder > Applications > Utilities > Terminal and run the following command:

/Applications/Nuke14.0v5/Nuke14.0v5.app/Contents/MacOS/Nuke14.0 -V

Run the following command in a terminal:

/usr/local/Nuke14.0v5/Nuke14.0 -V

This will print out in the terminal/command prompt a list of active plug-ins or custom scripts being loaded in Nuke.

TIP: If you wish to see all of the command line options available in Nuke then you can replace -V with --help to get the complete list of options.


Troubleshooting potentially problematic plugins/scripts

Within the printout you should see a lot of Nuke specific plugins which will have a file path similar to the following (this example is from Windows):

Loading C:/Program Files/Nuke14.0v5/plugins/icons/Read.png
However you may also see additional plugins which have file paths pointing to alternate directories outside of the Nuke install directory. These are the files that we are interested in troubleshooting and the ones that we would recommend that you temporarily remove (by cut and pasting them to an alternate location, or by renaming the file or its folder) and then launching Nuke again to see if that plugin was a potential cause for the issue you are experiencing.

If a plugin is not the cause, then it is possible any customizations you have made to your preferences or ~/.nuke folder may be the root of the problem. We would recommend that you temporarily move or rename your ~/.nuke folder from its current directory and launch Nuke to see if the issue still persists. If removing the ~/.nuke folder helps resolve your issue, you then need to go in and remove/rename files contained within the ~/.nuke folder to try and isolate which files are the possible cause (commonly the menu.py or init.py files).

Once you have isolated a particular file in the ~/.nuke folder, you can further troubleshoot the file if it contains code, by commenting out sections or lines, and launching Nuke to see if the problem still occurs. Once you know which section of code is causing the issue, you can either remove it, or modify it. You can also find more information on troubleshooting the .nuke directory here.

    We're sorry to hear that

    Please tell us why