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
feel free to draw your own conclusion from them and test some around :)
edit: followed by majority:
https://steamcommunity.com/sharedfiles/filedetails/?id=1450968623
i still have it set up like i have in my own guide, (4 cores 4 threads, and i have set it to
NumLowThreads=1, high=3) and its running perfect right now. a stable 40-60 fps without cpu spikes
You either have a low grade computer for gaming or do not know how to optimize your system for games.
They're not crooks
So if I set v-sync and tripe buffering in my Nvidia CP, do I turn them off in game.
How would you set the thread thing if you have coffee-lake with 6 cores?
It's really strange but somehow this seems related to something in the OS being corrupted. Maybe NMS utilizes resources that other games don't which is why we only notice it while playing NMS. I can't say for certain what it is. Maybe try completely uninstalling your graphics drivers and installing updated ones.
For reference, I'm running a 750ti, i5 6400, 8GB and I'm getting between 30 and 50 FPS depending on where I'm at, sometimes less on certain planets. After PF update and before the reinstall I was getting between 10 and 20 FPS.
NumHighThreads seems to be high priority threads. NumLowThreads seems to be low priority threads. Threads are lines of orders for a core to solve. Hyperthreading allows you to split the core functions in two, so if the first thread stalls, you just move on to the second on the same core. What has worked for me is the standard setting of 2 high and 4 low, on a 4 core hyperthreading cpu. Which sets 2 threads not used (if they are to be added which I think it seems they should be), which are probably used for background system services. No other setting has helped. In traditional testing on other software, assigning ALL threads is overcommitment and stalls background services, leading to a 5-8% DROP in performance in general. So, don't assign ALL threads, at least for hyperthreaded CPUs (which is what I have and have tested on).
I have seen TexturePageSizeKb interpreted as VRAM, that is ram on your GFX card. It is not, this is a page file. Setting the size to correspond with VRAM size is almost 100% certainly wrong (more VRAM should mean SMALLER page file, less VRAM should mean BIGGER page file). I got 8GB VRAM and the game defaults to 64kb for me.
I have Nvidia, so I have no advice for AMD. But the TWO only settings I have found that have helped me are Maximum pre-rendered frames at 1 (which has been a champion setting for years and years with many games). Pre-rendered frames smoothes out pacing (better timing between frames, the reason why 24FPS works brilliantly in the movie theater), but if something changes before the frame is shown, then it is discarded and your GPU wasted all that work. If the frame is not ready, it is skipped, dropping performance and looking like stutter.
The second setting is threaded optimization ON. For some reason, leaving it on auto does not see NMS activate it.
Everything else I have tried did nothing or was worse.
YMMV, so DYOR!
4790K No OC
MSI 1070 gtx gaming x
16 GB ram.
FPS capped at 60 to allow the system to breathe a bit, but I can run between 60-100+ uncapped. Everything maxed at 1080p, no vSync. Only ONE episode of freeze/frame drop, on many, many hours of gaming on NEXT. Did a complete wipe and reinstall for NEXT.
especially the TexturePageSizeKb=64 should NOT be messed with as it defines the quality of initial streamed textures before your pc can load in high-res textures. setting this number higher defeats the purpose of texture streaming and causes stuttering. setting it too high will result in a crash on start up even because people put vallues that are higher than the actual supported texture size.
Your cpu has 6 cores, that is 12 threads with hyperthreading enabled.
Given the previous ratio for mine (8 threads, 2 not used + 2 high + 4 low = 8 total)... 2 reserved for background stuff is the starting point, which leaves 10 total to work with. 10 does not split into a 1 to 2 ratio, but these are close: 3/6 (3 not assigned), or 4/6 (2 not assigned), or 3/7 (2 not assigned).... all seem plausible to me.