If you have already tried launching Nuke/NukeX/NukeStudio in safe mode, and this resolved your issue, the next step to troubleshoot the problem would be to launch Nuke in verbose mode.
Verbose mode outputs, to the Athera session log, which plugins are being loaded as well as Python, TCL and Nuke scripts. This information may help you to locate potentially problematic files.
Launching Nuke in verbose mode on Athera
To launch Nuke/NukeX/NukeStudio in verbose mode you need to add the
-V flag to your Nuke Run Parameters dialog. This can be done by using the 'Edit Run Parameters' option under your Nuke session launcher.
1) Click the Apps tab or the Athera logo in the dashboard.
2) Click the settings menu next to 'Launch' under your Nuke entitlement
3) In the Nuke Run Parameters dialog under 'Arguments', type
4) Click Continue to save the argument as a run parameter Nuke can use for new sessions.
5) Launch Nuke from your Apps section as usual. The Run Parameters will remain applied and allow you to run in verbose mode.
6) Close the Nuke session so that the verbose log can be saved to your session log.
7) To find your verbose log, navigate to the Reports page in the Athera dashboard. From this page you can see your recently closed sessions. You can find your session by looking for its unique name under the 'Session' column.
8) To open the session log and inspect the verbose output, click the icon under the 'Logs' column.
NOTE: It is important to note that any future sessions of Nuke will launch with this parameter applied, until it is removed from the Nuke Run Parameters dialog above.
Applying this parameter to Nuke does not apply it to NukeX and Nuke Studio, the flag needs to be added individually for each application you're trying to launch in verbose mode.
Troubleshooting potentially problematic plugins/scripts
Within the session log containing the verbose output, you can see a list of all the Nuke specific plugins loaded, which will have a file path similar to the following:
However, you may also see additional plugins which have file paths pointing to alternate directories outside of the Nuke applications area. These are the plugins that you should review when troubleshooting and temporarily remove.
You can start by removing all of them either by copying and pasting to an alternate location, or renaming the files. Then, reintroduce one plugin at a time and launch Nuke again to see if that plugin was the potential cause for the issue you were experiencing.
If a plugin is not the cause, then it is possible that customisations you have made to your preferences or .nuke folder may be the root of the problem. In this case, we recommend that you temporarily move or rename your .nuke folder from its current directory, and launch Nuke again 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 to resolve the problem.
The Foundry Support Portal contains a wealth of knowledge that can help you with any Nuke issues. If you are having problems that seem specific to Athera then please create a ticket with our support team by following the steps here: FAQ102: Using the Athera Portal