Hi Jean-Luc,
Nuke does stat both the local and original versions of the files before
loading, so if the non-local version is updated Nuke *should* load that
one. If you see different behaviour, then that's a bug, so you should
probably send a report to support.
However, if Nuke does detect that the non-local version is more recent,
it won't automatically update the locally cached version. In this case
you need to click on the "Update all" option to get your local cache up
to date.
It would be possible to change this behaviour to either re-cache, or
warn the user (this is a first iteration of this feature, so we're
expecting to make changes based on user feedback). Perhaps a warning by
default, with an optional "re-cache now?" dialog in gui mode might be
the safest way to do it? (With a user preference to disable the dialog
and just show the warning)
Regards,
Peter.
On 25/10/2011 21:58, jean-luc wrote:
ok good to know
One more question regarding updates. If a new version of a sequence is
rendered with the same name, Nuke wouldn't see it would it?
For instance is a roto is updated but overwritten with the same files
name/path, we would have to manually update the local copy? Would it
be possible to incorporate a automatic check that would ensure the
local copy is always more recent than the original file? (and either
delete copy with a warning or update the copy)
On Tue, Oct 25, 2011 at 10:32 PM, Peter Crossley
<[email protected] <mailto:[email protected]>> wrote:
Hi,
Yes, Frank is correct. Currently Nuke doesn't do any clean-up
management on the local cache folder and it must be done manually.
This issue is already logged as a feature request:
*Bug 21091*
<https://secure.thefoundry.co.uk/bugzilla/show_bug.cgi?id=21091>
-Add ability to delete locally cached files from within Nuke.
Regards,
Peter.
On 25/10/2011 03:25, Frank Rueter wrote:
yes, I guess it's a good idea to manually remove the cache files
when done. Don't think there is a mechanism built in for that
(which would be a nice option though to keep your disk tidy)
On Oct 25, 2011, at 12:45 PM, jean-luc wrote:
Ok got it!
I thought the localising process was automatic... I didn't
realise you had to manually make it cache...
So what happens when the files are marked "always" and you're
finished with your shot. Do you have to manually un-cache the
files too? There's no size limit on the localise folder so I
wonder if it's going to slowly fill up my local disk until it
chokes!
Cheers
jean-luc
On Tue, Oct 25, 2011 at 11:55 AM, Frank Rueter
<[email protected] <mailto:[email protected]>> wrote:
Hi Jean-Luc,
you either have to set the Read nodes you want to localise
to "cache locally" = "always" or set the "local file
auto-cache path" in the preferences to the root directory
shared by all file paths you want to localise (i.e.
'/server/shows/' ). In the latter case the Read nodes' set
to "cache locally" = "auto" will be checked if they point to
the server path and if they do, they will be localised.
Once set use one of the options in "Cache/Local File Cache"
to start the localising process.
It took me a moment to figure out as well, but the tooltips
helped.
Cheers,
frank
On Oct 25, 2011, at 11:24 AM, jean-luc wrote:
> Hi There
>
> I am trying to use the localizing and caching Nuke 6.3 but
even after changing my preferences it does nothing.
> attached is a snapshot of my prefs.
> When I start Nuke It still tells me that I am using around
94% of my 100Gb of disk cache (it should be 1000Gb)
> When I go to the /local1/NukeLocalise folder, it is
completely empty
>
> Is there something else I should be doing?
>
> Thanks
> Jean-luc
>
> <prefs.jpeg>_______________________________________________
> Nuke-users mailing list
> [email protected]
<mailto:[email protected]>,
http://forums.thefoundry.co.uk/
>
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected]
<mailto:[email protected]>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected]
<mailto:[email protected]>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected]
<mailto:[email protected]>,http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected]
<mailto:[email protected]>,
http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
_______________________________________________
Nuke-users mailing list
[email protected], http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
