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 cause of the issues you are seeing is 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 troubleshoot which one 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 the terminal. Exact steps are below.

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

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

Open a Command Prompt and run the following command:

"C:\Program Files\Nuke13.2v4\Nuke13.2.exe" -V
NOTE: By default the Command Prompt screen buffer can hold a maximum of 300 lines so you may miss part of the Nuke verbose output. You can change the default setting to view the entire output by: 
1) Right click the top window bar of the Command Prompt and select Properties from the drop down menu. Edit these 
2) In the layout tab, under the Screen Buffer Size, the Height will be set to 300. Set this to something higher, the max is 9999. This only sets it for this instance of having the command prompt open.

Open a Terminal from Applications > Utilities and run the following command (note this should all be on one line)

/Applications/Nuke13.2v4/Nuke13.2v4.app/Contents/MacOS/Nuke13.2 -V

Run the following in a terminal

/usr/local/Nuke13.2v4/Nuke13.2 -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 OS X):


However you may also see additional plugins which have file paths pointing to alternate directories outside of the Nuke app. These are the plugins that we are interested in troubleshooting and the ones that we would recommend that you temporarily remove (by copying and pasting to an alternate location or renaming the file) 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 file is 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 coding language 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 find more information on troubleshooting the .nuke directory here.

    We're sorry to hear that

    Please tell us why