I got NMS working yesterday after upgrading my memory card, and everything was running like silky butter for a while. I even was able to rebuild my ship and fly around with no problems.

Then today I noticed as soon as I climb into my ship (I'm still on my starter planet, BTW), the framerate goes to pot. Like 3 FPS, it's barely playable.

I know there are a lot of problems with the early build, but I'm wondering if something else is going on that I could fix. I don't remember adjusting any settings that would've caused it.

I'll try playing around with some to see if that fixes it, but thought I would post here to see if others experienced this and figured out what was up.
Never mind, figured it out. Looks like adjusting the texture detail from medium to high caused it. Dropping it back to medium makes it silky smooth again.

But still, I shouldn't see *that* much of a difference just climbing in my ship (even navigating the menu is about 3 FPS). I'm sure it's a bug they'll fix, but thought I would update for others that run into issues.

did you restart the game this morning or did you leave it paused all night?

Have you tryed turning off g-sync and turning the Frames up in the options to 90???

goto goggames folder > no mans sky > binaries > settings

edit TKGRAPHICSSETTINGS

change g-sync to false

I could've sworn that I responded right after I posted, but it's gone (though I did just see that GOG Galaxy had crashed, so maybe it crashed when I tried to post).

Anyway, I figured it out. I remembered I had upped my texture detail from medium to high, and I tried dropping it back down and that fixed it.

Not sure why that would cause such a huge difference, especially just jumping in my ship (not even flying). Assuming it's some bad code that will get fixed.

Hey, I've just found this thread searching for "frame rate drop".

I also suffer it but randomly. Sometimes when I jump into my ship the game gets somehow corrupted and frame rates drop from my usual 30fps (due to V-sync) to about 10 fps. And, more over, all the game interface goes veeeery slow from that point on. It really seems as if a x0.33 slow-mode factor is applied overall.

No solution but re-start the game. Then it works fine again (till the next occurrence).

My system and settings are:
W10 1511 build 64 bit
i5 4590
16 GB RAM
nVidia GTX 960 2GB with latest drivers 372.54
NMS GOG-5 aka 1289496
1920 x 1200 with everything maxed up.

This game have a serious problem of memory leaking, the FPS drop is becuase the game runs out of VRam from the GPU, restart the game solves it, also you can lower the graphics settings like texture or resolution.

I have exact same problem. Usually happens after i played after an hour or two. I also saw some streamers on Twitch have similar problems.

I get absolutely no problems with this, even after like 6+ hours, playing since release. Getting into the ship is always swift (too fast if you ask me).

Maybe my system details will help.

Win 10.
R9 390 ( 8 gig).
16 gig ram.
I5 4690K @ 3.50 ghz.
3200 X 1800

The OP said he lowered some of the graphics options settings to help the fps drop.. Did you try all Medium to see if that makes a difference? Borderless seems to help boost my fps by 5 - 10 fps. I also have my Radeon drivers doing the Vsync plus OpenGL triple buffering while setting Vsync off in game. I also have Shadows and Reflections set to Medium, but the rest at High and FPS set to MAX.

For what it's worth I am getting 40 - 60 fps for the most part:
W10 64 bit
i5 4590
8 GB RAM
AMD R9 280 3gb
1920X1080

Since it goes away after a restart, I've been taking the slowdown point as my cue to stop playing for a bit (coincidentally, it often happens at about the time I ought to be going to bed).

If, as suggested by other user it were a memory leak kind of bug, I suppose lowering the graphic footprint will help. Nevertheless as I can live with it for now.

But, maybe the interesting point would be reporting if this is only a nVidia issue or if it also affects AMD GPUs. Because maybe, (quite improbable nevertheless) that the issue is in the drivers rather than in the game.

I can confirm that the beta 1302131 has not solved the issue.