Disabling file cache is done via mod's .cfg file, relevant section needs to contain the line:
[io]
file_first = true
disable_file_cache = true
It's vital if you play a mod that's frequently updated, in many cases you wouldn't be able to continue your previously saved campaign with cache enabled - my recent research shows that the game will allow you to play on in "compatibility mode" when cache is disabled, whereas normally some battles wouldn't load. And there might be more to it.
A known symptom that could indicate disabling file cache would help is a CTD preceded by random texture errors found in game's log, directly before its end.
To make sure your error log contains enough data mod's .cfg file needs to be edited (extended logging courtesy of wilddog and Augustus Lucifer):
Detailed research here. |