#Performance issue with 0.1.1
37 messages · Page 1 of 1 (latest)
i suspect it's actually a gpu issue, I'll test with mooncake v3 when I get home to see if it still runs at 2-3 fps (and 100smth when paused)
(mooncake is very cpu-intensive)
testing starting now
something's up
that should be about 3 fps
this should be closer to 150
Agreed, my machine is a beast with a 4090 but this new update has performance issues along with a freeze every time it saves
Mine is a small save
actually depends on how you define a big vs small save
big for me is 1-2 million, far beyond what most do
giant is like 8 million (the absolute limit for my system)
medium is like 500k to 1 million
small is less than 500k
so, under my classification, your save is probably small
ok mine is between 500 and 600
so like 550 buildings?
Yes. A brief freeze every auto-save since this new version.
Thank you for your report! 😄
Would you be willing to record a video of the game running with the following debug on each of your saves?
debug.show-charts 1
i could record right now but im about to go somewhere, so I don't quite have time. is it fine if I get it later today? (lemme think, about 6 pm my time) (it's currently 9:10)
Don't worry! If I don't see it today It'll be seen afterwards 🙂
okie
sending an update: can test in probably about an hour.
also, is recording from phone fine, as recording in game could slow things down
alright, finally settled down, so I can test soon (5 minutes or so soon)
now to wait for v3 to actually load
not having nitro means I now have to fit the video in 50 megabytes
(if you can't tell I gave up on that)
I've also noticed a lot of screen tearing with 0.1.1 were it has always been smooth as butter when panning around (on a small save). Now it even screen tears on pause when just scanning asteroids.
Sorry about that. It seems that there's some performance issue with the latest iteration on space view of MAMs on the latest update, especially in saves with more than 500k buildings. We're doing a follow up for performance testing on several saves to try to maintain a standard on performance and not get worse with further updates. There's no specific bug for it given that it's a work in progress to test performance, so I'll flag this post as not a bug