- This topic has 2 replies, 3 voices, and was last updated 5 years, 8 months ago by .
-
Posts
-
Hey there!
I’m doing a lot of roto work in nuke right now and have been experiencing some speed-problems when using the roto&paint node. My nodes hold about 50 or so shapes and after working with the setup for a couple of hours, the whole computer just slows down rapidly and reacts only with great delay. it seems almost, that nuke eats up all the RAM…
anyone else having these problems? is that a bug? information on that would be very much appreciated 🙂
heres my specs:
Nuke 6.0v4 64 Bit
Running on Fedora Linux
6 GB RAM / 4 cpu-cores (dont know how many GHZ..)cheers,
seanFoundry graced us with a better to handle but still horrible to use roto paint node.
What you are feeling is a memory / disk cache handling issue. They did try to circumvent it by using your tmp folder for caching paint strokes (there are two cache folders now, one for the image and another one, or more for the paint strokes).
If you’re in a pipeline like I am make sure your nuke cache folder is not on the network. Won’t help a lot ’cause its just the worst coded node in Nuke, but it might help a bit on the speed issue. And give Nuke a lot of RAM for cache, too. Pump it up to 80%.
Cheers and hope it helped. If it didn’t we’ll just have to wait for the update. Most of us are, anyway. Having roto/paint node fixed some issues, but every single coleague I have thinks we should have a devoted paint node and a roto node, rather than this awkward combination. Which is unclone-able, to put the cherry on the cake.
Hey !
I discovered that if you maintain your properties pane of the Roto Piaint Node not expanded, I mean showing as little as possible of strokes, It works much more faster!
- You must be logged in to reply to this topic.