You are here: Getting Started > Managing Scripts > Image Caching > Caching Files Locally for Better Performance

Caching Files Locally for Better Performance

You may find that sometimes loading files from a remote server slows down your processing. In such a case, you can tell Nuke to bring down the files you’re frequently working with and store them on a local drive for speedier processing.

1.   You can set the location for your cached files, and specify any files you want automatically cached, using the Local File Cache controls in the Preferences:

localise to - enter the location for storing your cached files. You should construct the file path as follows:

Replace any leading forward or back slashes with underscores. For example, replace \\windowspath\to\my\network\file.dpx with __windowspath\to\my\network\file.dpx.

Replace any Windows drive signifiers (colons) with underscores. For example, replace t:\my\network\path\file.dpx with t_\my\network\path\file.dpx.

auto localise from - enter the location of the files you need automatically localized, unless otherwise specified. Commonly this would be your remote working folder. If you leave this field blank, automatic local file caching won’t take place.

2.   In the Read and ReadGeo node properties, you also have a cache locally dropdown that you can use to set a caching rule for the file being read in. Choose:

always - to always cache this file, even if other files aren’t cached.

auto - to cache this file along with other files you’re caching (default).

never - to never cache this file.

3.   Click the Cache menu next to the Help menu. Choose Local File Cache > Update All to update caching on all files that are set to be cached. Choose Update Selected to update caching on files you’ve selected in the Node Graph.