Honestly Nuke’s caching for “playback” has never been good. The caching mentioned here makes working on the comp a lot faster but for playback I still say it’s a lot better to just flipbook it.
John Vanderbeck Technical Artist Digital Domain Media Group NOTICE: This communication may contain privileged or other confidential information. If you have received it in error, please advise the sender by reply email and immediately delete the message and any attachments without copying or disclosing the contents. Thank you. From: [email protected] [mailto:[email protected]] On Behalf Of chrissowa Sent: Thursday, May 10, 2012 9:13 AM To: [email protected] Subject: [Nuke-users] Re: DiskCache node ok didnt do the "cache" --> "local file cache" --> "Update all" now i see that the auto path setting is not needed if i m setting read nodes manually to "always" that s ok. after that i push "update all" and the progress bar appears if i start to play the readnode, it s still very slow for the first play is it doing a "ram caching" at the first play? double waiting (progress bar + 1 playthrough) is a little bit much? this is all a mysterium .... performance and stuff like that ....
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
