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 <mar...@gmail.com>
>To: Nuke Python discussion <nuke-python@support.thefoundry.co.uk>
>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:
>
> -h
>
>
>
>
>On 27 November 2012 11:46, Nico Dufort <nduf...@gmail.com> 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 <fr...@beingfrank.info> 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
>>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
>
>
>
_______________________________________________
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
