Are my PC specs good enough for this game?

[_TEGI_]

I got ryzen 5 7600, 2060 super, 16 gb DDR5 and its all on nvme ssd. Why im hitting unstable 30 fps on 120-150 settlers?

No matter how i tweak settings im getting no improvement. Whats the initial problem with my case?

[_TEGI_]

Overall i i'll try to test stuff. Thought my rig will be fine for at least middle size map simulation.
Now i at least hope it will be enough for small size map with maximum population enough to hit req for 4th tier with stable 60fps

I'll try to test it myself... maybe it will help drastically

[Zephyr]

This is definitely not as it should be. You should be easily getting 60+FPS up to somewhere between 600-1000 ppl, except if you play on higher than 1080P resolution. I could only imagine that your GPU is having problems, honestly.

Can you provide a screenshot? Something like this with an overlay?

https://steamcommunity.com/sharedfiles/filedetails/?id=3390486445

This is with a Ryzen 7800X3d and a RX 7900XT. 4K native resolution.

Quick steps: Clean GPU driver installation with DDU (Display driver uninstaller), verifying of game files, update other drivers.

[Qoojo]

Most likely, it's the GPU. What resolution are you trying to play at?

[_TEGI_]

Ok this is weird. Now its all back to normal.

(I think core count is weird and this is threads. For clarification to identify use odd numbers for ... cores? i guess)
https://steamcommunity.com/sharedfiles/filedetails/?id=3394400496

I think its something to do with playtime... Like time after long sessions there's maybe still mem leak somethere.

I'll dig into it more

[_TEGI_]

Qoojo の投稿を引用：

Most likely, it's the GPU. What resolution are you trying to play at?

1080p 60hz (so. 60fps)

edit: One monitor. Nothing fancy yet

[Zephyr]

_TEGI_ の投稿を引用：

Ok this is weird. Now its all back to normal.

(I think core count is weird and this is threads. For clarification to identify use odd numbers for ... cores? i guess)
https://steamcommunity.com/sharedfiles/filedetails/?id=3394400496

I think its something to do with playtime... Like time after long sessions there's maybe still mem leak somethere.

I'll dig into it more

Looks all good here I think. In this shot neither the CPU nor the GPU are limiting. You have the average CPU usage/telemetry and then 6 physical core+6 threads due to hyperthreading (each core 2 threads). That is why you have an odd number of lines for the CPU (13). Individual cores are much more important to assess CPU limits than average CPU load btw, so nice to see them in the shot. I usually do not put hyperthreading threads in overlays (only physical cores in my shots), the effect for gaming is neglible in most cases anyway.

Maybe just some sort of weird hickup for your problem :). What you show is what I would expect with your hardware. Should be good enough to make some relatively large settlements with several hundred people at least, maybe even up to 1000. Just do not expect 60 FPS then necessarily. something between 30 and 60 then, but should be still quite playable.

If it happens again just try to make a shot and post it :).

[_TEGI_]

Zephyr の投稿を引用：

If it happens again just try to make a shot and post it :).

Got that thing at 290 civs. 5hr's into session ~~3-4hr of gameplay (got game open while running around house here and there)
https://steamcommunity.com/sharedfiles/filedetails/?id=3395316716
30fps.

Seems game start getting less ram.
Forgot to check if true after game restart without interference
Done some clearing of bloatware. Again 60fps after game restart.

I'll continue to check

[Zephyr]

_TEGI_ の投稿を引用：

Zephyr の投稿を引用：

If it happens again just try to make a shot and post it :).

Got that thing at 290 civs. 5hr's into session ~~3-4hr of gameplay (got game open while running around house here and there)
https://steamcommunity.com/sharedfiles/filedetails/?id=3395316716
30fps.

Seems game start getting less ram.
Forgot to check if true after game restart without interference
Done some clearing of bloatware. Again 60fps after game restart.

I'll continue to check

Hm ok that does not look pleasant. Quite certainly this is not because of the CPU or GPU per se. Should not happen like this, 99 % certain. In theory it could be that the GPU perhaps has too little VRAM buffer, but I would hope it does not cripple performance this much then :).

Does it stay like this if you do not restart the game? Can you try to replicate if this happens after 2-4 hours only?

If so I really would guess the VRAM is the problem. The system RAM should be enough at 16 GB for this application. Windows does not eat that much :). You could try to increase the page-file, just in case perhaps... .

You could also test with more VRAM intensive settings (reduce them).

can you post the graphics settings?

[_TEGI_]

Zephyr の投稿を引用：

can you post the graphics settings?

W. Fullscreen

Resolution : 1920*1080 / 100% / 60hz

Run in background + Edge Scroll
bg FPS = 10

Shadows - Medium
Anti-Aliasing - 8x MSAA
Soft Shadows + Foliage

[Zephyr]

_TEGI_ の投稿を引用：

Zephyr の投稿を引用：

can you post the graphics settings?

W. Fullscreen

Resolution : 1920*1080 / 100% / 60hz

Run in background + Edge Scroll
bg FPS = 10

Shadows - Medium
Anti-Aliasing - 8x MSAA
Soft Shadows + Foliage

Ok I think I found your issue, fingers crossed :).

Matching settings:
https://steamcommunity.com/sharedfiles/filedetails/?id=3395372672

VRAM is at almost 6GB use from the start, allocated is 8 GB on my GPU. AMD GPUs use somewhat more VRAM sometimes, but likely you get too close to your 6 GB limit of VRAM.
https://steamcommunity.com/sharedfiles/filedetails/?id=3395372726

Solution:
Set 8x MSAA to 2x or perhaps 4. I show the next shot with 2X.

While it still allocates about 7 GB VRAM only 3-4 are now used.
https://steamcommunity.com/sharedfiles/filedetails/?id=3395372767

So, set MSAA at 2-4X instead of 8 and you issue is hopefully fixed :).

At least it is a good idea..., I hope. MSAA uses quite a bit of VRAM... .

[_TEGI_]

Zephyr の投稿を引用：

Does it stay like this if you do not restart the game? Can you try to replicate if this happens after 2-4 hours only?

I'll try to replicate it. I forgot to try if it stay like that after

Zephyr の投稿を引用：

You could try to increase the page-file, just in case perhaps... .

I'll try

Right now problem could be anywhere, but in theory the thing i done should work. Keep on keeping on.
~I will play more right now~ :)

[Zephyr]

_TEGI_ の投稿を引用：

Zephyr の投稿を引用：

Does it stay like this if you do not restart the game? Can you try to replicate if this happens after 2-4 hours only?

I'll try to replicate it. I forgot to try if it stay like that after

Zephyr の投稿を引用：

You could try to increase the page-file, just in case perhaps... .

I'll try

Right now problem could be anywhere, but in theory the thing i done should work. Keep on keeping on.
~I will play more right now~ :)

Look at my last post :). I think it is the VRAM. Solution included :).

Hm, small caveat: The game does not really allow me to change resolution properly and shows inconsistent behavior with the VRAM between trials. I still think it is the most likely reason in your case, though. The buffer fills up over time, at least to a degree.

[_TEGI_]

Zephyr の投稿を引用：

Look at my last post :). I think it is the VRAM. Solution included :).

Thanks! Time will tell. I'll try MSAA 4x

[_TEGI_]

Ok. Just here to tell that im here and everything works fine. Don't really know what exactly caused the issue.
Basically i did 3 things:

- Deleted Motherboard (Asus) bloatware because i noticed that it duplicated and reserved more RAM at my machine over time (low fps issues happened after long hour sessions)

- Lowered my Anti-Aliasing one bar lower (to MSAA 4x)

Suddenly i started to get screentearing. V-SYNC fixes that issue but overloads my 2060S so i
- Fixed my FPS to lower cap of 50hz and tearing stopped

Anything from this list possibly could fix that problem, but i tend to lean on first option
Let your system have some spare ram space because everything starts to run slowly

Did a rig update recently, changing everything besides Monitor and GPU. Now they're weak spots. Monitor older that GPU and i chose Gigabytes problematic 2060S and realized it only after RMA time (during MB+CPU upgrade).