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
[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
