<\/p>\n\r
The File Cache \/ Substitutions<\/span> tab allows you to specify the following: <\/p>\n\r <\/p>\n\r •<\/span>set where cached information is stored and when it gets cleared <\/span><\/p> •<\/span>file path substitutions to handle copying builds from build machines to development or test machines <\/span><\/p> <\/p>\n\r The default settings are shown below:<\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r •<\/span>Cache Directory<\/span> type directly or Browse<\/span> to find a directory for Memory Validator to cache its information <\/span><\/p> <\/p>\n\r <\/p>\n\r By default, the cache is only flushed when the executable changes between sessions<\/p>\n\r <\/p>\n\r •<\/span>Flush cache at each new session<\/span> tick to flush the cache every session <\/span><\/p> <\/p>\n\r This slightly slows down relaunch of the same executable, as the cache needs rebuilding.<\/p>\n\r <\/p>\n\r •<\/span>Flush cache when executable changes<\/span> untick to prevent the cache being flushed at all <\/span><\/p> <\/p>\n\r <\/p>\n\r When not automatically flushing, you can manually flush the cache if necessary<\/p>\n\r <\/p>\n\r <\/span><\/h1>\n\r
Caching file locations<\/span><\/h1>\n\r
<\/span><\/h1>\n\r
Memory Validator keeps a cache of known locations for files for which it needed to search, improving the speed at which files can be found. <\/h1>\n\r