[2.0.20] [Performance] UPS / FPS drop 60 -> 30 Blueprint Preview

[Gummiente27]

Hi,

I have a performance problem during big (204x204) blueprint preview (FullHD, AMD 5600x, Nvidia 1660 Super).

UPS/FPS go from 60 to 44 in new game (and in my actual game save from 60 to ~35) just by previewing the blueprint.

You can find the blueprint in the inventory/hotbar of the save file (Test) or in the dedicated file.

Slowdown does not occurr in map view.
I noticed I other F4 options enabled when taking the screenshot (show-clock, show-blueprint-grid and show-fluid-box-fluid-info), but in later tests I did not notice any performance impact difference when reproducing this issue with those two options disabled as well.

FPS doesn't improve whether the blueprint is completely on the screen or not, also zoom level doesn't change it.
All the extra time is spent in "Game render preparation".

Edit:
Filling up the blueprint with lots of solar/akkumulators, causes fps to tank even more, I've seen FPS below 20.
Also gets worse when hovering blueprint over area where it was already built.
I have not found any setting in graphics section which fixes this problem.

[Titan Uranus]

This seems related to the issue I have, I get low UPS when placing a blueprint over water, which is about the size of 3x3 roboport coverage.
(1440p, Ryzen 5800X3D, 4x8GB 3200Mhz RAM, Nvidia 3070)

When holding the shift key to place landfill and remove trees etc. with the blueprint, CPU usage on one core jumps to 95-99% and I get as low as 13.9 UPS, when not over water and holding shift CPU usage is still quite a bit higher on one core at about 42%, but still 60 UPS.

When not holding shift, wheather over water or not, CPU usage is only about 25% on the higest core. it is usually about 20% when just walking around and doing stuff or in remote mode, so 5% higher with a blueprint and not holding shift.

I am on version 2.0.20.

[Gummiente27]

I noticed it gets even worse with "Game render preparation" when the blueprint is hovered above a place where it got built already (i.e. hovering-over-empty -> hovering-over-built: 23ms -> 34ms, fps/ups 33 -> 25)