If it will open via the terminal, often it is helpful to open it up, disable
all the nodes and save to a new name. Then you can open it up in the UI and
enable nodes until it breaks.
nuke -t
nuke.scriptOpen('broken.nk')
[x['disable'].setValue(True) for x in nuke.allNodes() if x.knob('disable')]
nuke.scriptSave('debug.nk')
m
----- Original Message -----
From: "Andreas Frickinger" <andreasfrickin...@me.com>
To: "Nuke Python discussion" <nuke-python@support.thefoundry.co.uk>
Sent: Monday, November 26, 2012 1:38:03 PM
Subject: [Nuke-python] Nuke Script debug
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
