Captain_Wreckus
Member
GOG.com purchaser here and I can save & load w/ no problems after the patch.
No Mans Sky | PC Performance Thread
- Thread starter noomi
- Start date
GOG.com purchaser here and I can save & load w/ no problems after the patch.
dgrdsv
Member
Can't say that the patch did much to frametime stability on my end:
That's with driver vsync btw. In-game vsync result is similar. Same results with borderless and with RTSS limit set to anything from 60 to 65. It's basically impossible to run the game with vsync and no stuttering at the moment on a GTX1080.
That's with driver vsync btw. In-game vsync result is similar. Same results with borderless and with RTSS limit set to anything from 60 to 65. It's basically impossible to run the game with vsync and no stuttering at the moment on a GTX1080.
simatron3000
Member
Any G-Sync users? Tried this on release day and whilst my frame rate was at about 100fps, The game constantly hitched and stuttered.
Yeah, I currently have (2) MSI Gaming X 1080's in SLI and a PG348Q.
I can confirm that G-Sync did seem to cause some issues prior to the latest NVIDIA drivers, but after applying the patch alongside these drivers, stuttering is virtually non-existent (for me).
It's not perfect quite yet, but it's certainly coming along...
D
Deleted member 752119
Unconfirmed Member
Update on GOG made a big improvement for me. FPS stays around 75-85 now. I was kind of getting that before the NVIDIA driver update, but even then it still stuttered way down every once in awhile. Post NVIDIA update is stuttered more and FPS was more 55-65 range.
I haven't had any crashes yet, before or after update (*knocks on wood).
And yay, Alt-Tabbing works now after the patch.
I haven't had any crashes yet, before or after update (*knocks on wood).
And yay, Alt-Tabbing works now after the patch.
Had nothing to do with G-SYNC. Try the new patch and see if it fixes it.
dgrdsv
Member
Game is using deferred shading so MSAA is either impossible or would lead to same performance hit as SSAA. The devs mentioned something about TAA coming in future updates though.
I've been on experimental nearly the entire time. I backup up my save just in case, opted out of experimental, and it reverted without a download, which means, yes, it is indeed the same patch made public.
I launched the game, went to a different base, saved my game, relaunched, and it loaded up successfully. Not sure what their issue is.
Can't say that the patch did much to frametime stability on my end:
That's with driver vsync btw. In-game vsync result is similar. Same results with borderless and with RTSS limit set to anything from 60 to 65. It's basically impossible to run the game with vsync and no stuttering at the moment on a GTX1080.
Yeah I'm still getting loads of stuttering, not as frequent as before, but still enough to be annoying.
Slackbladder
Member
4790k@4.4ghz. I have been playing at 4K mind. That said I tried The Division@1440p and my temp was getting to around 61-63c. I've never seen my CPU temp higher than +60c usually. NMS just seemed a little high.
The GOG patch basically did nothing for me.
Still garbage performance when flying over a planet with hitching every second or so, even on the absolutely lowest settings.
i5-3550, 980GTX, 16 GB RAM, Windows 7.
It feels like the game is programmed so that it must pop in at a specific distance, and it absolutely will not continue rendering frames until that new terrain has been generated. Which is frustrating because those times the CPU hits 100% everything grinds to a halt, but the CPU sits at 50% otherwise. Seems like they would benefit from doing speculative terrain generation in the background.
They also didn't fix the issue where mouse sensitivity is bound to your frame rate.
Still garbage performance when flying over a planet with hitching every second or so, even on the absolutely lowest settings.
i5-3550, 980GTX, 16 GB RAM, Windows 7.
It feels like the game is programmed so that it must pop in at a specific distance, and it absolutely will not continue rendering frames until that new terrain has been generated. Which is frustrating because those times the CPU hits 100% everything grinds to a halt, but the CPU sits at 50% otherwise. Seems like they would benefit from doing speculative terrain generation in the background.
They also didn't fix the issue where mouse sensitivity is bound to your frame rate.
Haswell is know to run hot (relative to other CPUs). It also depends what kind of cooling system you're running, what your ambient (room) temps average, and if you have Hyper-threading enabled or disabled. If you're on air, your temps sound fine to me, especially with that overclock.
I'm air cooling with a Hyper 212 Evo and two Noctua NF-F12 fans. In the fall/winter, my average temp on load rarely goes above 60c, but in the summer (when ambient temps go up), I get 5-8c increase on average.
SMAA tanks me to 30fps on a 1070 if there is a storm, with fxaa its a smooth 60.
CarbonFire
Member
The Experimental patch has definitely given me a better experience (higher framerates, smoother, less blur), but I can't say the same for the latest Nvidia Drivers. I was getting very smooth, consistent frametimes and good framerates with 368.81, but updated to the latest and the framerate didn't change much, but the frametimes went to shit and it felt way less smooth.
i5 3570k@ 4.4Ghz
780ti (OC)
16GB DDR3-2400
i5 3570k@ 4.4Ghz
780ti (OC)
16GB DDR3-2400
The driver update making things worse might be caused by the shader cache being wiped. I noticed it took like a minute to start the game first time after a driver update compared to 10 seconds before.
It's "SSAA x4," which is 4x your selected resolution downsampled internally. Thus the reason for the massive peformance hit. For instance, if you're running at 1080p, it's effectively 4k, 1440p, it's 5k, etc.
CarbonFire
Member
I deleted the shader cache folder after updating the drivers, tried with both shader cache enabled and disabled forced in the driver settings. Still felt way smoother in the older drivers. YMMV of course, I'm still running that busted up ol' Keplar.
The mod description says you can't.
sleazefrenzy
Member
Tried new patch and drivers and game is completely unplayable now.
I wasn't that happy with the 30-60fps I was getting before, but now I'm lucky to pass 15-20.
Think I'm done with the game now. Seen most of what you can do in it and had some fun, but I've spent as much time trying to fix their game as I have enjoying it. I give up.
I wasn't that happy with the 30-60fps I was getting before, but now I'm lucky to pass 15-20.
Think I'm done with the game now. Seen most of what you can do in it and had some fun, but I've spent as much time trying to fix their game as I have enjoying it. I give up.
Doh!
I'm surprised they made zero changes between the experimental build and live build. Still needs more optimization but I feel like it's "ok enough" to work on fixing game breaking bugs also. Especially the bug with it telling me I already have the blueprint, when I don't, along with some really weird stuff when loading prior saves.
The patch tankes my performance ( cant get it above 20 fps) and deleted my saves. Those statements about "1%" of people having issues seen damage control as hell.
Just an FYI to anyone currently forcing SMAA via Reshade in No Man's Sky; it has up to a 12 fps performance impact over in-game FXAA, which has a 2-3 frame impact over no AA. This is even with SMAA Luma detection (the less expensive when compared to Color), and Depth Settings off. It shouldn't be so expensive, but is currently for whatever reason.
Also in-game AF is still broken, and appears to apply no AF. Forcing Quality level 16x AF in Nvidia Inspector has up to a 10 fps impact on my 980 Ti, when compared to in-game 16x AF (again, not working). Interestingly, I did some screenshot comparisons, and there appears to be no visual difference between Nvidia Quality and High Quality AF, unlike some other games. However, High Quality has a 3 fps performance impact compared to Quality.
So, basically, if you have High Quality AF forced via Nvidia Inspector, and SMAA forced via Reshade, you could gain back up to 15 fps, depending on your setup.
Also in-game AF is still broken, and appears to apply no AF. Forcing Quality level 16x AF in Nvidia Inspector has up to a 10 fps impact on my 980 Ti, when compared to in-game 16x AF (again, not working). Interestingly, I did some screenshot comparisons, and there appears to be no visual difference between Nvidia Quality and High Quality AF, unlike some other games. However, High Quality has a 3 fps performance impact compared to Quality.
So, basically, if you have High Quality AF forced via Nvidia Inspector, and SMAA forced via Reshade, you could gain back up to 15 fps, depending on your setup.
noomi
Member
Does using reshade have any impact on the color scheme of the game, I would only want to apply the SMAA and nothing else.
Maybe there is a preset somewhere...?
No, you can apply as much or as little as you want in Reshade.
There are some presets here:
https://sfx.thelazy.net/games/game/1418/
Again though, SMAA is having a heavier performance impact in this game than usual; for most other games, it often only has a 1-2 frames performance impact over FXAA, if that.
There are some presets here:
https://sfx.thelazy.net/games/game/1418/
Again though, SMAA is having a heavier performance impact in this game than usual; for most other games, it often only has a 1-2 frames performance impact over FXAA, if that.
Handy Fake
Member
To be fair, those 15 people are working their arses off. The AK issue was only really addressed after the backlash.
Agent_ShortBus
Member
I updated my Nvidia drivers yesterday and my game just tanked in fps especially when getting into a ship. Game was running fine before and now it's completely unplayable. Guess I'll just rollback or just wait for a patch :/
Just downloaded it also. First impressions; no new options, performance from where I loaded up was the same. Nothing worse, at least, though it's been working well for me since the experimental patch released two days ago.
Guess we'll have to wait for patch notes.
Maintenance
Member
robgrab
Member
Me too. I need to expand my storage just so I can carry more to sell. I'm gonna call it home for a while to amass as much wealth as possible.
RadioactiveLobster
Member
Experimental Branch just downloaded a 66MB patch for me.
Kadayi
Banned
Anyone on Win10 find that they suffer a hardlock system crash generally a few minutes into the game the first time they fire it up? I've had this happen the last 4 days. No crashes after I've rebooted etc, but the next day, same deal (I do shut down my PC when I'm not home).
Drivers are all up to date and everything (Nvidia) and my machine more than meets the specs. I'm also using the experimental patch.
Validated files (no errors) and going to reinstall the Nvidia drivers Fresh. But the certainty that it's going to happen is the annoying part.
Drivers are all up to date and everything (Nvidia) and my machine more than meets the specs. I'm also using the experimental patch.
Validated files (no errors) and going to reinstall the Nvidia drivers Fresh. But the certainty that it's going to happen is the annoying part.
If it's anything like the PS4 patch notes..
(Gertsmann picture)
And I thought Dark Souls patch notes were criptic.
"-- Magic was changed
"-- Improvements"
Tranqueris
Banned
Well, time to see if the patch? (Steam only downloaded a 20.7 mb file) Does anything for the two things really annoying me at the moment. The fact that the framerate basically dies a slow dead after playing about 2 hours straight, meaning I have to restart the game every two hours, and the fact that my ship loves to blast me high off the planet every time I try to launch off the surface and fly to another spot in the planet.
Leatherface
Member
Not I. Windows 10 Pro Edition here. 1080GTX w/ latest drivers and experimental patch. In fact the game runs a lot better than it did when it launched now, thankfully.
