Thread: Nuke 4.7 V.5

Nuke 4.7v5 Released ! What is new ??

1.SplineWarp + Primatte: SplineWarp can?t draw curves when a
Primatte node is in the DAG. Note that if there is a control in the control
panel bin with an active color picker, it will still take precedence over other
manipulations, like drawing SplineWarp curves.
2.Bezier + Primatte : Beziers won't draw after adding Primatte,
and Nuke crashes. Fixed the crash. However, if there is a control in the con-
trol panel bin with an active color picker, it will still take precedence over
other manipulations, like laying down Bezier points.
3. Renders fail on large formats.
4.MacPro XP Bootcamp - crashes on some machines on opening
Nuke, then opening Viewer.
5.OFX cache always rebuilding in non-interactive mode.
6.Removed TCL function t () from the documentation.
7. Nuke not releasing memory correctly on some scripts.
8. BUG ID 2845 - Fixed Filter > Emboss node....

Download Win
Download Mac
Download Linux
Keylight 2.0v1 for Nuke


________
S Platform

2.Bezier + Primatte : Beziers won't draw after adding Primatte,
and Nuke crashes.

Gods be praised! My nuke has been crashing all afternoon and I couldn't figure out what was doing it... just tested v4 and sure enough that's been it!

• BUG ID 2920 - Nuke not releasing memory correctly on some scripts.

I hope this is my "too many files open" bug.

Originally Posted by im.thatoneguy

Gods be praised! My nuke has been crashing all afternoon and I couldn't figure out what was doing it... just tested v4 and sure enough that's been it!



I hope this is my "too many files open" bug.

I believe it's not. Should not say for sure though. But believe that bug resulted in crashing due to memory "owerflow". Had it here with largs source pics in earlier versions but they fixed the memory leaks and now it's 95% better.

"To many files open" sounds like you're running on windows? Seen that one to but thought it was a windows related problem and it went away when I restarted the comp. But maybe it is related to that nuke bug after all. When nuke not releasing some memory imprints or something so windows thought to much shizznitz was open. Well... Le't hpe it works for ya. =)

And I must ask... Was there something wrong with my thread about 4.7v5?

Too far down the list..

Oh... Now you were fast. =) I edited my post and added some things about your bug. dunno if you saw that when you answered...? =)

It's not windows specific it seems to be a problem with all operating systems where you have a limit on the number of concurrent open files.

I think 2048 used to be the limit pre-windows 2k so I'm not sure if it's a bug related to Nuke being more careful than it needs to be (The error message is a nuke dialog box) or if windows is actually hitting its limit. Either way Nuke should be intelligently managing its cache so that it starts closing unneeded disk calls.

I know nuke is very sloppy with with its hard drive access because if I cancel an execute before it's done it'll often forget to unregister frame_####.tmp and have it still flagged as "open" to the operating system preventing it from being deleted/modified and forcing me to change my execute directory. By this point I've set up 3 cache folders Flip1, Flip2 and Flip3 so that when one gets blocked I just change my temp folder and keep on chugging without having to close/reopen nuke.

I guess I'll find out tomorrow if v5 has improved cache management.

Edit: http://support.microsoft.com/kb/219956

This link says that windows 2k (and I assume by extension XP) can have 16,348 files... so that would be really really leaky if it left that many file calls open. Maybe the error message isn't actually reflecting the problem...

Update so fast