Thanks guys for the feedback, those are all great ideas! Fur further reference, here's a quick summary:
- launching nuke with "-safe" to avoid loading ~/.nuke and any custom stuff. (Nuke 7)
pre v7 I'd rename ~/.nuke and make sure no NUKE_PATH is set to get a vanilla nuke.
- launch with -V to see terminal output to see if you can spot the moment nuke folds. (Did you mean -V, Frank? -vv seems to be loading image files) ...Also for -V there are the levels 0,1 and 2 depending on what kind of information you want to see
- Try to import script instead of opening it
- check if there are any Viewer nodes in your comp and delete them if they exist (in a text editor), or turn off the option in the Nuke Preferences (Or launch nuke with --pause flag)
- Split the script in half and try to launch it, repeat until it doesn't open up anymore
I still think there should be something more sophisticated, for example I had a script today which didn't open up and launching it in verbose mode froze the launch process at a certain plugin that had nothing to with the eventual problem, so that didn't help at all. In this case we found the issue by guessing and digging through the nk file (it wasn't a very large script) as it could neither be imported nor opened in the terminal.
I was more thinking of a Python script that crawls through a Nuke script, evaluates it and reports any issues. It then should be able to isolate the malicious parts and save a version of the Nuke script without them.
Maybe there should be even a proper Debug included with Nuke...?
Any thoughts?
thanks again for the input!
andy
- launching nuke with "-safe" to avoid loading ~/.nuke and any custom stuff. (Nuke 7)
pre v7 I'd rename ~/.nuke and make sure no NUKE_PATH is set to get a vanilla nuke.
- launch with -V to see terminal output to see if you can spot the moment nuke folds. (Did you mean -V, Frank? -vv seems to be loading image files) ...Also for -V there are the levels 0,1 and 2 depending on what kind of information you want to see
- Try to import script instead of opening it
- check if there are any Viewer nodes in your comp and delete them if they exist (in a text editor), or turn off the option in the Nuke Preferences (Or launch nuke with --pause flag)
- Split the script in half and try to launch it, repeat until it doesn't open up anymore
I still think there should be something more sophisticated, for example I had a script today which didn't open up and launching it in verbose mode froze the launch process at a certain plugin that had nothing to with the eventual problem, so that didn't help at all. In this case we found the issue by guessing and digging through the nk file (it wasn't a very large script) as it could neither be imported nor opened in the terminal.
I was more thinking of a Python script that crawls through a Nuke script, evaluates it and reports any issues. It then should be able to isolate the malicious parts and save a version of the Nuke script without them.
Maybe there should be even a proper Debug included with Nuke...?
Any thoughts?
thanks again for the input!
andy
On 26 Nov, 2012,at 04:03 PM, Howard Jones <[email protected]> wrote:
As well as all of that the quickest way to ever find a fault (assuming one fault) is to
divide and conquer.
1) Split the script in half - see if it loads
2) No - divide it into half again, does it load?
3) Yes - try the other half
and so on.
For multiple faults you divide anything that fails until you can get down to a few lines.
Not saying it's not tedious but still a quick way to find a fault in an Avid 90 minute timeline, er I mean a script.
Howard
From: Marten Blumen <[email protected]>
To: Nuke Python discussion <[email protected]>
Sent: Monday, 26 November 2012, 22:54
Subject: Re: [Nuke-python] Nuke Script debug
launch script with no viewer is:
--pause
useful is the help file:
-hOn 27 November 2012 11:46, Nico Dufort <[email protected]> wrote:On top of what Frank already suggested, assuming the file itself is not corrupted, maybe check if there are any Viewer nodes in your comp and delete them if they exist (in a text editor), or turn off the option in the Nuke Preferences (I think there is something about it hidden in there). After that, start the detective work by plugging in a Viewer going down your tree until you connect to the offending node?--
On Mon, Nov 26, 2012 at 2:13 PM, Frank Rueter <[email protected]> wrote:if you are on v7 the first stop should probably be launching nuke with "-safe" to avoid loading ~/.nuke and any custom stuff.
pre v7 I'd rename ~/.nuke and make sure no NUKE_PATH is set to get a vanilla nuke.
launch with -vv to see terminal output to see if you can spot the moment nuke folds.
Also, see if you can import the script rather than open it.
At this point, if the script still won't open and you aren't getting any indication why, things will likely become labour intensive (i.e. copy/pasting chunks of the nk file into Nuke).
On 27/11/12 10:38 AM, Andreas Frickinger wrote:What's the least labor intense way to debug a Nuke script that won't open up anymore. There must be a clever way to find out where it breaks...? (not stepping through the nk file manually)
thanks,
andy
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
"Attention, attention. Here and now, boys," the mynah repeated. "Here and now, boys."
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python_______________________________________________
Nuke-python mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
