I've experienced a similar issue with a 3D-heavy Nuke script on 64-bit Windows. Launching Nuke with the -n flag (don't run postagestamps) got me going again enough to restructure the script. It might work for you, too.
-t On Jun 2, 2011, at 2:02 AM, Jordan Olson wrote: > hey fellow Nuke power-users and TDs! > > I've got an odd issue at our CG animation studio- sometimes (maybe one > out of every 20 shots) a shot will crash while nuke is reading in > image data. So you can open the .nk file, nuke itself will load fine, > and then while the viewer starts rendering and it starts querying the > tree itself, and then nuke will completely crash a few seconds into > it. I've narrowed it down to the odd postage-stamped read node, so by > setting "postage_stamp false" in the .nk file, then we can load the > shot. > > (windows 7, nuke 6.2 64 bit) > > A current workaround was to use Nuke 6.1, which could load the shot > fine. Soon we won't have 6.1 though. (due to backwards compatibility) > > Anyone else have this issue of postage_stamp enabled nodes crashing > the scene upon loading? > > Cheers, > Jordan > _______________________________________________ > Nuke-python mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python -- Tim BOWMAN +61 4 8766 1415 +1 347 692 0839 http://netherlogic.com _______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
