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
Check CPU/GPU usages. The GPU is probably not running at 100% usage.
My GTX 1080 does this too. I'm running it with an i7-6800K@4.2GHz. Most games aren't as CPU-bound as SN, or rather the Unity 5 engine, is. Once it's couple threads are maxed out on the CPU, specifically the pre-rendering thread, some portion of the GPU's potential is overkill and doesn't get used because the pre-rendering thread is itself a bottleneck.
Nvidia Boost 3.0 is a lot more complex than the previous Boost algorithm and one of it's features is the ability to balance core clock against usage and thermal headroom on the fly. There is no longer only two clocks: standard and boost clock, as there used to be. The drivers can set the clock to anywhere within that range in multiples of 12MHz and can even exceed it if the usage demand is there and the voltage and thermal headroom are low enough to allow for 2100Mhz+. If you adjust the power target up to 120% using PrecisionX OC / Afterburner and put it under a heavy load like Superposition benchmark, you'll see that the card will overclock itself well above whatever the factory OC is advertised as and it will do so without you having to add an explicit offset to the core clock so long as it has voltage and thermal headroom to spare.
If the GPU isn't hitting full 99%-100% usage though, which depends on both the CPU and the game's ability to multithread the pre-rendering pipe, it will downclock from it's max boost clock a bit to save on waste heat/electricity when those higher clocks aren't needed.
Drive speed has little effect on loading stutter right now. Though the SSD is nice to have, even a RAMdrive won't clear up the I/O bottleneck. It's nice to have Obraxis verify either way.