Steam Deck performance fix

General
1

Thanks user LilLillyFox on the LE Discord for digging up a fix.

Pre-season 2, LE ran decently well on my LCD Steam Deck. Depending on area and build I was getting between 40-60fps on medium graphics. CryoUtilities helped overcome the memory leak that plagued the first few patches. However, improvements to SteamOS and proton let me run LE well without the need for CryoUtilities and all was good for awhile.

Post-season 2 update, I began encouraging massive fps drops and lag, specifically in the new endgame weaver monos and cemeteries.

Tried reinstalling CryoUtilities but still had big frame drops. Switching proton versions did not help either.

The solution (perhaps only temporary) was suggested on Discord. It simply requires Steam Deck users to increase the UMA buffer size from the default 1GB to 4GB in the bios.

After doing that, I uninstalled CryoUtilities and set my proton back to experimental. Now I am able to play endgame monos with no issues.

I played for about 3 hours with no major issues or frame drops, so I would call this fix good enough to make the game playable. Hope this helps other Steam Deck users enjoy the new update.

Cheers!

2 Likes
2

Thank you, I tried similar things as you but nothing worked. I dropped my settings to low and it somewhat helped at least to do the content but it was def not ideal lol. Great game for the deck, very gg.

3

Thank you so much, this fixed it for me too

4

Can you point me to where I can find instructions on updating the BIOS?
BTW what graphics settings are you using?

1 Like
5

I feel like this is definitely a software issue that should be fixed on the developer side. What I have seen that helps is immediately turning on the record feature when I experience the frame drops and stuttering after 3-5 seconds it acts back to normal it doesn’t stutter or do any frame drops for the rest of the echo. After you leave the echo and go into a new one the stuttering and frame drop starts again. Then I do the same thing by setting up the record feature and it acts like it is back to normal. Homely the developers fix this issue.