Forum Replies Created
-
Posts
-
Foundry 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.