Very Low CPU and GPU utilization causing poor framerate

[TheJasenSensation]

Specs: 8700k, 1080 ti, 32gb ram, 250GB Samsung 970 EVO(OS drive), 1TB Samsung 860 EVO(game drive), 1440p 165hz Gsync monitor

Frame rate was a little low prior to Frontiers, but now booting it up for the first time I noticed FPS has dropped drastically with CPU utilization at 20% and GPU below 50% resulting in 20-30 FPS on planets and 40 fps in space. Setting everything to low and resolution to 480p does not make a difference. I have recently installed the latest Nvidia driver and used DDU to do a clean install. I have all of the latest Windows updates, I have tried game mode and HAGS both on and off. Gsync on/off. Resetting game settings to default or deleting config files so they regenerate back to default doesn't do anything either. Multiplayer on/off doesn't affect performance either. Also just wiped the game completely from my drive and reinstalled it on Steam.

I do nothing but game and light video editing on this PC. Even did a fresh install of Windows a month ago. I can't find any information at all regarding such poor performance. I did submit a ticket to Hello Games, but they never respond to any issues I've ever had.

So if anyone has any input I would greatly appreciate it!

[Zak]

BulletMagnet の投稿を引用：

Was going to drop back in to NMS after a time away. Something is really broken.

AMD 5900X, 23GB, 4090: 10% CPU, 5% GPU utilization. Horrible perf.

How do you asses GPU and CPU performance in NMS? If you alt-tab out of NMS to view the Task Manager then keep in mind that NMS.exe pauses in the background so its CPU and GPU usage drops to nearly nothing. You need in-game performance monitoring to see the real picture while the game is running.

On a 13900K and a 4080 I normally see way less than 20% CPU usage and maybe around 50-60% GPU usage while playing NMS according to RTSS overlay and the game runs very well, maxed out with no hiccups. Have you updated your drivers? Also, I'm not familiar with AMD hardware, but NMS is suspected to have issues with E-cores on some recent Intel CPUs. Does your AMD CPU have the equivalent of E-cores? Then look into setting the affinity to force the game to run on performance cores only. Some people say that helped them with low performance and stutters.

[I Am Groot]

Zak の投稿を引用：

BulletMagnet の投稿を引用：

Was going to drop back in to NMS after a time away. Something is really broken.

AMD 5900X, 23GB, 4090: 10% CPU, 5% GPU utilization. Horrible perf.

How do you asses GPU and CPU performance in NMS? If you alt-tab out of NMS to view the Task Manager then keep in mind that NMS.exe pauses in the background so its CPU and GPU usage drops to nearly nothing. You need in-game performance monitoring to see the real picture while the game is running.

On a 13900K and a 4080 I normally see way less than 20% CPU usage and maybe around 50-60% GPU usage while playing NMS according to RTSS overlay and the game runs very well, maxed out with no hiccups. Have you updated your drivers? Also, I'm not familiar with AMD hardware, but NMS is suspected to have issues with E-cores on some recent Intel CPUs. Does your AMD CPU have the equivalent of E-cores? Then look into setting the affinity to force the game to run on performance cores only. Some people say that helped them with low performance and stutters.

he uses AMD, that is the problem.

[Tatwi]

Daemonjax の投稿を引用：

Kernel_Picnic の投稿を引用：

Stuttering and poor performance always happen for a while after every driver or game update, due to the game compiling shaders in the background. I can't offer any insight into the low CPU and GPU utilization though.

The game no longer stores cached shaders. Check your shader cache folder -- it's always empty now. Been like that since 2019.

It now compiles shaders whenever it needs them and stored them in vram and forgets them when you exit the game. So any performance hit from compiling shaders never goes away.

Yeah that sucks, a lot.

In Linux the shaders are still compiled before running the game and as a result the game play is waaaaay smoother than in Windows. Sadly there are a bunch of other things that are annoying about gaming on Linux. Love Linux, used it for 25 years, but I'd still rather play Windows games in Windows; 100% of the performance/functionality, 0% of the effort/troubles. I really miss Win7/XP/2000/98SE though, where I didn't have to disable a load of things I don't want and would never use...

Sigh... rant over.

I noticed yesterday that using the screen shot mode in NMS tanks performance after exiting the mode. Closing the game and restarting it fixes the issue. Totally reproducible and the performance issue seems to be in line with what the OP described. No idea why it happens though.

[BeefyBearded]

Tatwi の投稿を引用：

Daemonjax の投稿を引用：

The game no longer stores cached shaders. Check your shader cache folder -- it's always empty now. Been like that since 2019.

It now compiles shaders whenever it needs them and stored them in vram and forgets them when you exit the game. So any performance hit from compiling shaders never goes away.

Yeah that sucks, a lot.

In Linux the shaders are still compiled before running the game and as a result the game play is waaaaay smoother than in Windows. Sadly there are a bunch of other things that are annoying about gaming on Linux. Love Linux, used it for 25 years, but I'd still rather play Windows games in Windows; 100% of the performance/functionality, 0% of the effort/troubles. I really miss Win7/XP/2000/98SE though, where I didn't have to disable a load of things I don't want and would never use...

Sigh... rant over.

I noticed yesterday that using the screen shot mode in NMS tanks performance after exiting the mode. Closing the game and restarting it fixes the issue. Totally reproducible and the performance issue seems to be in line with what the OP described. No idea why it happens though.

likely memory leak

[taniwhat]

No issues here on Linux but maybe I'm just not picky. (2070plus). The only hassle is sometimes manually forcing a driver upgrade,

I did notice cleaner graphics going from 535->545 Nvidia driver but that may just have been not playing much for a week or so.

[CatPerson]

Haven't had any issues, game or photomode, with my 9900k/2080ti/32 ram/win10, either. Been playing at 4k/60 Ultra, Steam overlay off. Although the 11gb of vram on the gpu probably helps vs. anyone with older 8gb or less gpu's. gpu's going at 90% or up most of the time I guess (I have multiple displays, no need to alt-tab out to see it).

That said the longer I play a single save I notice a bit more stutter-lag when first loading the save/chr. drops into the world. Sometimes deleting all the stuff in the cache folder seems to help with that temporarily but eh. After that 2 seconds of first loading stutter it's fine so.

I also have MP off and I like a sense of isolation, so I don't like/go to any systems where there's a ton of other player bases spawning in. I thought I wouldn't see that at all with MP off, actually, but then I went to that Living Ship quest planet with its small player bases and save beacons visible every 10 feet. Ugh, what an ugly sight (and that did seem to affect frame-pacing somewhat even if fps # was stable). Never going anywhere near there again.

[taniwhat]

^^^^ Which is a very good point. With MP on the game will be waiting for messages/responses from servers. Which matches with low GPU/CPU load.

Those of you having problems, turn MP off and see if things improve.

[Lystent]

//REDACTED//*UNKNOWN*// の投稿を引用：

Zak の投稿を引用：

How do you asses GPU and CPU performance in NMS? If you alt-tab out of NMS to view the Task Manager then keep in mind that NMS.exe pauses in the background so its CPU and GPU usage drops to nearly nothing. You need in-game performance monitoring to see the real picture while the game is running.

On a 13900K and a 4080 I normally see way less than 20% CPU usage and maybe around 50-60% GPU usage while playing NMS according to RTSS overlay and the game runs very well, maxed out with no hiccups. Have you updated your drivers? Also, I'm not familiar with AMD hardware, but NMS is suspected to have issues with E-cores on some recent Intel CPUs. Does your AMD CPU have the equivalent of E-cores? Then look into setting the affinity to force the game to run on performance cores only. Some people say that helped them with low performance and stutters.

he uses AMD, that is the problem.

just the CPU (?). Also, last I knew, AMD was invested in vulcan.

taniwhat の投稿を引用：

No issues here on Linux but maybe I'm just not picky. (2070plus). The only hassle is sometimes manually forcing a driver upgrade,

I did notice cleaner graphics going from 535->545 Nvidia driver but that may just have been not playing much for a week or so.

I have lower tiered specs than a previous poster (Ryzen 7 5800x, RTX 3050), on windows 10, and also don't notice any real issue after giving it a while to update the all shaders. I also play with MP disabled.

[I Am Groot]

Lystent の投稿を引用：

//REDACTED//*UNKNOWN*// の投稿を引用：

he uses AMD, that is the problem.

just the CPU (?). Also, last I knew, AMD was invested in vulcan.

taniwhat の投稿を引用：

No issues here on Linux but maybe I'm just not picky. (2070plus). The only hassle is sometimes manually forcing a driver upgrade,

I did notice cleaner graphics going from 535->545 Nvidia driver but that may just have been not playing much for a week or so.

I have lower tiered specs than a previous poster (Ryzen 7 5800x, RTX 3050), on windows 10, and also don't notice any real issue after giving it a while to update the all shaders. I also play with MP disabled.

No, AMD made Mantle it is poorly made and not widely used outside EA game using DICE's FrostBite engine. AMD cannot continue to maintain it to compete with DX12 and Vulkan which is from Khonos using Mantle idea(but they made it in a better way), so they killed it.
Your AMD literally cannot made anything good. FSR? just half-@ TAA.

[Lystent]

//REDACTED//*UNKNOWN*// の投稿を引用：

...Your AMD literally cannot made anything good. FSR? just half-@ TAA.

I said I'm running a RTX 3050...

If you are gonna start machine shaming, atleast get the parts right...