[2.0.24] FPS drops in remote view

[fi5hii]

I noticed when I was in my fulgora base that has over 20k bots I have usually around 55-60 fps and ups but when I'm in the same spot and same zoom on map view the fps drops significantly going to as low as 35 and ups to as low as 45

save file here

Normal View

normal view.png (4.55 MiB) Viewed 174 times

Map View

map view.png (3.94 MiB) Viewed 174 times

[Rseding91]

Thanks for the report. I’m not seeing any bug here, asking the game to render more of course takes more time. As you keep asking it to do more and more eventually it can’t keep up. Map view has to render the normal view and the map view at the same time which takes even more time.

[fi5hii]

oh okay, yeah that makes sense if it's rendering both at once, thank you for the explanation.

[IsaacOscar]

Map view has to render the normal view and the map view at the same time which takes even more time.

Why does it have to render twice as much as the normal view? The screenshots in this bug report look like it's showing exactly the same content in both cases (the only difference being the remote view GUI).

[Hares]

See also: 123470: [2.0.23] FPS drops on Gleba
If your CPU is not loaded fully (one core at least) then consider changing graphics engine settings (see Rseding's answers on the topic mentioned).

[Rseding91]

Map view has to render the normal view and the map view at the same time which takes even more time.

Why does it have to render twice as much as the normal view? The screenshots in this bug report look like it's showing exactly the same content in both cases (the only difference being the remote view GUI).

Because the way "zoomed in" map vie works is to first render the normal view, then render map view on top of any chunks not radar revealed. This means the map view logic still runs, just the end result doesn't end up rendering for the chunks you see directly on screen. Ones off-screen, and logic that had to be computed to start the map process but got discarded still takes up time.

[IsaacOscar]

Map view has to render the normal view and the map view at the same time which takes even more time.

Why does it have to render twice as much as the normal view? The screenshots in this bug report look like it's showing exactly the same content in both cases (the only difference being the remote view GUI).

Because the way "zoomed in" map vie works is to first render the normal view, then render map view on top of any chunks not radar revealed. This means the map view logic still runs, just the end result doesn't end up rendering for the chunks you see directly on screen. Ones off-screen, and logic that had to be computed to start the map process but got discarded still takes up time.

Aaah cool, thanks that makes sense. If this extra rendering does cause problems for people, perhaps rendering the map view only for unrevealed chunks might work.