Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It could be that there are other factors at work here, maybe when the shader cache is built, certain parts are being retained in memory or indexing for a short while afterwards, resulting in increased access times but then over time these are replaced which then results in some FPS drops when they are accessed later.
After that, shader cache builds up in less than 3s, and the performance doesnt improve.
Interesting, maybe its something like that.
My experiences come from some games (was it no mans sky for example?) where deleting the shader cache usually improved frames.
The additional thing is, nvidia has its own folder of shader cache, but I havent tinkered with it.
From how I understand it, the shader cache is mainly intended to take some of the load off of the CPU.
You could try monitoring your CPU usage during a few missions following a full shader rebuild and then again after a few days to see if there is any noticeable difference.
Lower worker thread count by 1 from default.
Scroll all the way down and check the actual sliders for Blood impact etc, Hover over those settings and check to see which one's specifically are CPU intensive, ONLY REDUCE THOSE AND TEST AGAIN.