hello fellow goggers, ive got following problem:

it seems the framerate is generally bad but it gets worse over time...it started with 100fps at the beginning but the longer i did play the fps drops more and more till it reached a constant 34fps when i stopped the game...

does anyone know about that problem or a solution for the bad framerate in general?

the computer hardware is i7-8700K, 32gig ram, gtx 1080ti and i play with a res of 1600x900 with low light and shadows...medium distance and rest on high but no aa or vsync...

thx alot

Edit: ok i restartet and tried it again...the framerate is now at 30 and doesnt rise anymore and drops further....is this game so extremely bad optimized or is it a known issue....if it doesnt run smooth with a hardware like that, what do you need to play it properly??

I've noticed that when the game autosaves it slows the framerate way down, even to the point of 0 sometimes until the autosave finishes.

thx for the suggestion but i dont mean the freezes because of the saving...the framerate in general is extremely low...it estays at 60 then 40 and then drops into unplayable numbers like 20-15.....

either something is wrong with my computer or the game is extremely bad optimized..

btw i reduced the viewrange details etc but it changes absolutely nothing....

I just fired it up after shelving it for a bit because Discord showed an update. Frame rate is garbage. I'm trying to do the tutorial and I can't even turn a corner without coming to a near halt.

My CPU is barely being taxed (i7-8700k), my ram isn't even hitting the 50% mark (16GB), my GPU (GTX1060 6GB) never exceeds 60% usage and the vram never exceeds 2.5GB. Something is VERY wrong. I'm TRYING to play at 1080 on Ultra, as every other AAA title works fine.

Any updates from the developers?

for me it helped to set all the graphics to medium or low, especially the view distance....now it looks like shit but at least the framerate is at 140 at the beginning....at the beginning...after a while it drops down to around 50-40...till i tried out my first flying big thingy.....then i was at around 11-30...

this game is literally unplayable in its current state or something is wrong with my comp

I run the same graphics card and core memory as you do, and my CPU is 4770 and I run decent frame rate at Ultra and keep the sync on. (although I disable Aniso completely) get a temp monitor -HWmonitor works for me! and make certain your graphics card has proper air flow. I also have a full tower case(ICON2 and decent air flow) also set the Nv software to "prefer maximum power" and turn graphic texture filtering to "High performance" it might be a heating issue. do you have a "Founder's" card or another variaty of the 1080 GTX? during the weather in the game my FPS will drop too I just restart the save at the menu, no need to exit the game either! there is a memory leak and it is likely the devs but also Windows 10! a big mess IMO! I began having frame rate issues but found it was a cooliing issue and set my case out from under the table its heating as building up down there. and got it to run at a decent frame rate for about an hour. the biggest performance hit is Anisotopic filtering.

This game is a piece of crap, no wonder its only £4.95, its not worth half of that! Slow? I've had faster games on my old original ZX Spectrum back in the 80's, totally unplayable, this is probably the last time I purchase anything from GOG.

Well, the game is also on other online sellers so ....
but yhea, it's one of those badly coded unity games

For me, the stuttering starts quite suddenly after traveling some distance. IIRC the main trigger for that was the Terrain Visibilty Distance, and reducing it helped a great deal. Of course that's not an acceptable solution for those with high end rigs, but things do work pretty well on my potato -- unless I'm trying to handle grids with literally thousands of blocks.

I've posted my specs / settings in this thread.

My experience has been that this is one of those games that performs worse and worse the longer a play-session is. Like has memory leaks or similar issues that build-up over time.

For me, if I quit and restart the game every two-three hours, that problem is alleviated. Not sure it applies to this situation, but just in case..

It's a unity game, so performance is fucked by design as that shitty engine cannot handle large-scale open worlds due to its shitty handling of rendering assets, and the only solution is to either get a refund or beg the developers to better optimize the game...

I have to run the fuckin' game on low settings and I have a Ryzen 9 3900x|64Gb RAM|and an RTX 3090, I cannot even run it on high settings as my frames will tank to the 20s!

As it stands just beware of large-scaled 3D worlds using the unity engine, as it's best suited to smaller-scaled/top-down 3D worlds, 2D games, and mobile, unfortunately too many unity cultists continue to develop for that shitty engine instead of the 100% free unreal engine!

The previous poster is right about the prognosis, but wrong about the dianogsis. :)

Unityi is crap, but the low framerate is due some very stupid decisions on handling waits - the idiots are doing busy waits in tens of threads at once, and this is what's tanking the machine. The "funny" thing is that the more cores you have on your CPU die, worst the problem gets because with all the cores spinning like crazy your CPU will have to throttle down due thermals.

There's not a fix for this, but we can mitigate a bit the problem. Run the program with a environment variable called MONO_THREADS_PER_CPU set to 1.

If you are on a MacOS machine, the following command line will do the trick:

> MONO_THREADS_PER_CPU=1 ./PlanetNomads.app/Contents/MacOS/PlanetNomads