[2.1.11] Low fps after update from 2.1.9

[tpasqual]

Hi all,

I noticed on my experimental playthrough (2.1.11) that I have a big drop in FPS and UPS in my game when zoomed out that wasn't occurring before. After doing some investigating finally, here's what I've noticed:

• This occurs when I've zoomed out from my character (or on remote view) to a few levels before the game switches to radar. There is no issue when I'm on the map or zoomed in close to the group (character or remote).

• It occurs on a freshly created map as well.

• It seems to occur in the presence of trees, a treeless desert area is unaffected.

• It was perfectly fine in 2.1.9, the issues only starts in 2.1.10 and 2.1.11

I rolled back my game to 2.1.9, unchecked all mods, made a fresh map, and the FPS and UPS are fine. When I switched to 2.1.10 and created a new map (same seed), the FPS and UPS drop.

I've included logs, screenshots, and save games of the two worlds I tested.

Any ideas?

[SteveofDoom]

Since I've been having some framerate issues since 2.1, I went ahead and tested this on 2.0.77 and 2.1.11.
I found a very small difference between the versions, around 0.5 ms extra draw call time for 2.1.11, both versions just barely keeping up with 60 FPS.

I created a map with seed 123456 and maximum tree coverage then entered editor mode and zoomed all the way out. I have tested this on Linux though, that might cause some difference compared to OP's results but I wanted to provide another data point. Also, I have not tested any 2.1 version prior to 2.1.11 for this specific case.

[Rseding91]

How does it perform if you change the graphics setting "video memory usage" from "all" to "high" or "medium"?

[Jap2.0]

What graphics card do you have?

OP has a GTX 1050, which has 2GB of VRAM. I was talking with someone I know a couple days ago and he alleges that he's been seeing decreased performance between 2.1.9 and 2.1.11; he has a GTX 770 (also 2GB VRAM), so I'm wondering if it's something to do with that.

(I suggested that he turn down some graphical settings so that more fits in VRAM rather than RAM, but it changing between minor versions is strange. I think he had video memory usage set to high. Most of the rendering time during spikes occurred was in "flip", which—in my experience as a layman—seems to be a notoriously opaque place for time to go. I'm checking with him to see if trees are also a common thread for him.)

[Jap2.0]

Screenshots he sent me:

[SteveofDoom]

What graphics card do you have?

OP has a GTX 1050, which has 2GB of VRAM. I was talking with someone I know a couple days ago and he alleges that he's been seeing decreased performance between 2.1.9 and 2.1.11; he has a GTX 770 (also 2GB VRAM), so I'm wondering if it's something to do with that.

(I suggested that he turn down some graphical settings so that more fits in VRAM rather than RAM, but it changing between minor versions is strange. I think he had video memory usage set to high. Most of the rendering time during spikes occurred was in "flip", which—in my experience as a layman—seems to be a notoriously opaque place for time to go. I'm checking with him to see if trees are also a common thread for him.)

I have na RTX 4090. The FPS problems I am having are on the CPU side with a lot of expensive draw calls causing a slowdown. The update which fixed Vulcanus decoratives performance might've broken something in low VRAM situations.

[tpasqual]

UPDATE: It isn't the trees. I updated to 2.1.14 to see if something has been resolved. Unfortunately at my standard settings, there is still a significant framerate drop. However, going into graphic settings and unchecking ONLY "Show decoratives" and leaving everything else at full graphics settings makes the framerate issue disappear. So something funny is going on with decoratives, at least in my system.

[SteveofDoom]

So it's decoratives for you as well? Looks like a common cause of performance issues since 2.1. Hopefully the devs can figure out what's going on with them.

[Jap2.0]

My person also says turning off decoratives fixed it for him. Thanks for the tip, weird it changed so much in a minor version though.