I don't know about the evaluation of nodes and it sure would be
usefull, but the way i deal with that kind of problems is to get the
viewer from the top of the tree and gradually looking trough to find
where it is crashing.
Not having a viewer should make it load without crashing unless a
postage stamp is guilty, you can disable them too in the pref.
hope it helps in waiting of a script
Olivier
Dorian Fevrier wrote:
Hi all!
We have nuke crashing without any messages, nothing... I'm currently
trying to know where this happen and, it happen (of course...) within
the:
nuke.execute( writeNode, f, f, 1, forcedViews )
I would like to know what are nodes that could do Nuke crash. So I
would like to know what are nodes running during Nuke crash (doesn't
seems to be a memory prob).
I know this is not something easy to follow with multithreading but
something like:
node1 -> Start
node2 -> Start
node3 -> Start
node2 -> End
node4 -> Start
node1 -> End
node3 -> End
Could be really enought for me. To find the part where nuke crash.
Is there a way to script during a evaluation start and end to print
the node name?
How deal with this kind of prob?
Thank in advance.
Have a good day!
_______________________________________________
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
