b0uncyfr0
Member
My hero! Though after i turned off Hyper-threading i havent crashed for four hours.
No Mans Sky | PC Performance Thread
- Thread starter noomi
- Start date
My hero! Though after i turned off Hyper-threading i havent crashed for four hours.
Check the Options tab, there is a mouse smoothing option. Put the slider on 0 and give it a try
Leatherface
Member
never mind. misread.
Kaffeemann
Banned
Some people on Reddit say that the new experimental patch fixes the alleged resolution upscaling.
Is this true? I'm on GOG :/
Is this true? I'm on GOG :/
noomi
Member
Steps are in the OP
LostDonkey
Member
Yes I have done all those things. I'm running at 1440p as well, 60hz monitor.
I've disable shader caching and deleted the folder as others have suggested. It's not running smooth for me
Captain Pants
Killed by a goddamned Dredgeling
Thanks!
Kenzodielocke
Banned
I am getting stuttering at 60fps. I already use RTSS. Any tips? I am on the non experimental patch on the latest nVidia game ready driver.
With the experimental patch?
With the experimental patch?
Can't wait to try it myself. Res fix, AA working? Nice
For me yes; it's no longer a blurry mess, it defaults to FXAA, and you actually have to restart to apply SSAA 4x now.
Never thought I'd be so happy to see subpixel shimmering ;p
Downside? It's now locked 64.4 on my 144hz G-sync monitor, no matter the settings. It was running unlocked at 99% GPU usage before the update. A system restart unlocked it for a time, but then after traveling to a new planet it locked to 64.4 again. Weird.
They need to add an option to disable the internal framerate cap entirely, it's bugged.
Kaffeemann
Banned
What's the point of using RTSS? Just force vsync through the driver.
Dictator93
Member
Read Durante's "Alchemy of Smoothness" on PCgamer. RTSS can ensure proper frame pacing in cases where Vsync in / or out of game does not.
Kenzodielocke
Banned
I thought it eliminates frame pacing issues?
Good to know. Finally see how this game scales.They just added it in the latest driver. Each GPU is at ~80% here. 60 FPS. Some of the OSD is bugged though.
For reference, running the following:
i5 2500k at stock (I know, I know overclock it)
2x GTX 970
16GB RAM
1TB Samsung 850 EVO
Game has been running well at 1920 x 1080 with everything on high, though with the hitching/stuttering that everyone mentions (FPS above 60 except when flying, sometimes). Running the normal branch, as the experimental hit me for 5-10 frames. Still worth playing here over the PS4 locked at 30 FPS with the same hitching.
It does. What you should be doing is:
- Turn off in game v-sync
- Turn on v-sync at driver level
- Set FPS cap in RTSS
molnizzle
Member
Yep.
If you have a 60hz display just set a global 60fps cap in RTSS and you'll never have to touch it again. Unless you want to cap a specific game at 30fps, of course.
As for No Man's Sky, I've finally achieved locked 60fps at high settings on my 4690k/970 setup!
...at 900p
Welp. Tired of tinkering. On the original branch I was able to get a pretty stable 1440p/60 at max settings across the board once I'd disabled in-game V-sync, aniso, edited the .ini to increase max fps to 1000.
With the latest experimental branch, enabling SSAA4x cuts my framerate down to 30fps. Switching to FXAA gives me worse image quality than the original branch's AA solution.
Going to revert to the original, re-implement my first round of tweaks and just play the game as-is till it's patched well enough to run properly (on the original branch for instance, it feels like 4k/60 is within spitting distance).
Core i5 4570, GTX 1070 and 16GB of Ram.
With the latest experimental branch, enabling SSAA4x cuts my framerate down to 30fps. Switching to FXAA gives me worse image quality than the original branch's AA solution.
Going to revert to the original, re-implement my first round of tweaks and just play the game as-is till it's patched well enough to run properly (on the original branch for instance, it feels like 4k/60 is within spitting distance).
Core i5 4570, GTX 1070 and 16GB of Ram.
Kaffeemann
Banned
Interesting, I never had frame pacing issues after forcing vsync through the driver.
I also read in a priont mag that capping the framerate with RTSS puts additional stress on the CPU so that's something to be aware of.
I also read in a priont mag that capping the framerate with RTSS puts additional stress on the CPU so that's something to be aware of.
finalflame
Banned
FYI, here's what I've done to get my FPS to a locked 60 at 1440p on a GTX1080/i7-6700K:
In-Game:
2560x1440
Fullscreen
FXAA
AF Off
All other graphical options maxed
nVidia CPL
AF 2x
AA type: Enhance application settings
AA 2x
AA Transparency 2x (Supersample)
V-Sync: On
CheatEngine
HelmetFX Off
FOV on Foot: 140
And this has gotten the game to a state where I feel I can sit down at play it at 1440p on my 4K TV. It's worth noting that for some reason adding the 140 FOV to the config file did not work for me, but doing it via CheatEngine did. Night and day difference on foot. I need to investigate, but I think there are better (easier) and more permanent ways to disable HelmetFX and increase FOV permanently; as it stands I have to do it in CheatEngine every time I start the game, but it 100% works. FYI, it seems the game doesn't have issues alt+tabbing IF the fullscreen res is less than your desktop res. When I'm using fullscreen with my in-game res the same as desktop res, alt+tab does not work.
In-Game:
2560x1440
Fullscreen
FXAA
AF Off
All other graphical options maxed
nVidia CPL
AF 2x
AA type: Enhance application settings
AA 2x
AA Transparency 2x (Supersample)
V-Sync: On
CheatEngine
HelmetFX Off
FOV on Foot: 140
And this has gotten the game to a state where I feel I can sit down at play it at 1440p on my 4K TV. It's worth noting that for some reason adding the 140 FOV to the config file did not work for me, but doing it via CheatEngine did. Night and day difference on foot. I need to investigate, but I think there are better (easier) and more permanent ways to disable HelmetFX and increase FOV permanently; as it stands I have to do it in CheatEngine every time I start the game, but it 100% works. FYI, it seems the game doesn't have issues alt+tabbing IF the fullscreen res is less than your desktop res. When I'm using fullscreen with my in-game res the same as desktop res, alt+tab does not work.
molnizzle
Member
That's because SSAA 4x wasn't even doing anything in the original branch. It was broken. SSAA 4x should tank your performance as you're essentially rendering at 4K. And any difference you're seeing between the FXAA in each branch is placebo.
In the first experimental patch, they disabled G Sync by default. Have you checked the config files to fix that?
I have a OC'd 5820k and a OC'd Titan X Pascal and the performance is nowhere near smooth with maxed settings at 1440p. More hitches than a trailer park
I take any claims of "super smooth" with a big ass pile of salt.
The performance is poor but tolerable, the crashing is much worse. Fix that shit
I take any claims of "super smooth" with a big ass pile of salt.
The performance is poor but tolerable, the crashing is much worse. Fix that shit
finalflame
Banned
Check my post a couple of replies back. I had a lot of weird hitching on my 1080 -- until I arrived at the settings above. The things I found are that the game seems to take a HUGE hit from AF for some reason (at least when set via the nVidia control panel). If I can hit locked 60fps on a GTX1080 with an i7-6700K (and that IS what it's running at, I am extremely picky about performance and spent hours tweaking until I got it to a smooth locked 60), then you can do it with a TitanXP + 5820K.
With that said I am NOT on the experimental branch and have NOT updated to the newest nVidia drivers for this game.
molnizzle
Member
Your driver MSAA settings are doing jack shit unless you have a custom but or something. Just tested up to 8x MSAA with no performance hit, so it's not doing anything.
Yup. On or off, actual G-Sync is engaged and working either way. The "G-sync" setting in the config field doesn't do anything to fix the FPS lock.
finalflame
Banned
There was a performance difference between 4x MSAA and 2x MSAA for me, a pretty significant one (dips to 35-40fps at 4x vs. no dips whatsoever at 2x), so I assume it's doing something.
I realize that SSAA wasn't working I'm the original branch, however, there is significantly more sub pixel shimmer when using FXAA on the experimental branch than there is when using FXAA on the original branch. I know this because I just compared the two one after the other.
molnizzle
Member
Placebo man. Temporal shimmer is nasty as fuck on the original branch too. :-/
That's what you should have been seeing the entire time with FXAA. The original build had a rendering glitch. This created the illusion that there was less subpixel shimmering, but in reality, it was simply obscuring fine detail. Now that's it's fixed, you're seeing the full native output, and subpixel structure is restored. Upside, everything is way sharper, downside, full-on 1:1 subpixel shimmering is back.
It looks like TAA will be introduced in a future patch, which should remedy this. FXAA is known to do nothing for subpixel shimmering.
Ah, I see. Thanks for the explanation, I appreciate it.
BRocknRolla
Member
I'm unclear on this...
In the original build, are people saying that there simply was no AA or it wasn't working? And even when you shut it off and turn it on using the Nvidia control panel, you weren't actually doing anything?
In the original build, are people saying that there simply was no AA or it wasn't working? And even when you shut it off and turn it on using the Nvidia control panel, you weren't actually doing anything?
molnizzle
Member
SSAA wasn't doing anything, no. FXAA was doing FXAA as usual.
As for Nvidia AA, jacking it up to 8x MSAA doesn't have any affect on my performance so I'm inclined to think that it has no effect. Latest driver / experimental.
I doubt it would, unless you had a compatibility bit specifically for the game's engine, which you'd have to input into the game's profile in Nvidia inspector. Short of ancient games, you usually can't just force MSAA via the control panel and expect it to work. That, and this game uses a deferred renderer, which doesn't traditionally support MSAA; the devs would have to code support in, which they have yet to do, so.
molnizzle
Member
I know, I just attempted it because someone else was claiming success with it a few posts back. Couldn't replicate.
Did he provide screenshot proof?
BRocknRolla
Member
Can you force SSAA through the panel? I know I have mine shut off, but I could have sworn that my AA isn't presenting me with a large issue in game as far as image quality. I don't recall which setting I put in the panel (I don't think it was FXAA), but I seem to recall it having some kind of effect, whatever setting I chose (Unless it really was just a placebo, but I doubt it). And if I'm mixing up my AA terms, my apologies. They've always thrown me for a bit of a loop.
SirMossyBloke
Member
Got my first ever CTD with the new ex patch. 20 hours in.
During what please? Talking to someone and selecting between multitool and suit upgrade?
Have you tried to pickup multitool or new blueprint? Warp?
finalflame
Banned
No, but I noticed a significant performance impact increasing MSAA to 4x from 2x. So I assumed it was working. I'll investigate further once I'm home.
Herr Starr
Member
Holy crap, not only does the game look better now due to its improved resolution, but this latest patch seems to have eliminated the horrible stuttering I've been suffering since launch. The game is now completely smooth in 1440p Ultra on my GTX 1080, as it should be. Awesome!
Edit: This is also with the latest Nvidia driver.
Edit: This is also with the latest Nvidia driver.
Short of Nvidia DSR, or the AMD equivalent, I don't think so at this time, no.
Even without a compatibility bit or engine support, it's possible forcing MSAA can have a performance impact. Doesn't mean it's actually doing anything though.
I'd recommended doing a before and after screenshot for confirmation, regardless.
SirMossyBloke
Member
I found a Gek signal and it was zooming up above the planet to find a way point. Game just vanished and I was staring at steam.
For whatever reason, screenshotcomparison.com isn't working for me lately. So I'll have to post them individually. Just open each in a new tab, do a full zoom for both, and switch between the tabs to compare.
Original Build max settings + FXAA
Experimental Build max settings + FXAA