Have been unable to use frame limiter on Legion Go since 8/19
Starting sometime after the 20240819 build, I’ve been unable to use stable as my chosen frame limit isn’t being respected. Rolling back to 8-19 resolves the issue.
A@Kyle Gospo so the vrr revert breaks the legion go?
KNope, works fine here
KLet me know if you disagree on your hardware
Ai dont have your gamescope version on it
Aand im not running to compile it tbh
Aworks great on the Ally
Apushed the ally fixes and i think thats it for today
KVery nice
KRun a build tonight
Abtw i hate the updates in steamui
Aits so confusing
Awe have to fix it
THow can I resolve this or am I just stuck on 8/19. @antheas I thought you were on an April build or something.
Ai maintained that build until may
Aall issues with itshould be fixed now
TIs there something I can check? I thought updates were atomic so I shouldn’t have anything broken on my machine that wouldn’t be replicable on the same hardware by someone else. But it happens every time I go to stable, so I just revert to 8/19 where the issue doesn’t seem to occur. Unless MangoHUD is just lying to me.
Awe added a patch that fixes LFC on VRR and it seems like it might have messed with the Legion Go but Kyle says his legion go works fine
Awhat game do you have issues in?
KAye, very important detail
TKingdom Come: Deliverance I have it capped to 48 but the main menu will be 29 FPS and in game will fluctuate from 43 - 52 but never cap. In Cyberpunk the frame rate will be significantly below whatever I cap it at. If I cap it at 48 it hovers around 36 and if I cap it at 36 it hovers at 24. On the 8.19 release they’re all optimized settings so they are almost always at cap but never exceed it. These are the two games I notice it most on.
TI’ll try reinstalling Bazzite and see if that fixes the issue
Bhi, you mean frame limiter work well with vrr enabled on Ally? I haven't check since It broken when using both frame limiter and vrr at the same time
ANo
AWe will experiment with the frame limiter soon
AThe launch args work great on the ally
TI reinstalled and thought the issue was resolved. Then I enabled FSR for these games and the issue came back. It’s either a limiter issue or something changed with FSR that made it significantly worse or more taxing.
Afsr is not good
TIt’s always worked ok for me. What would you suggest?
Aim not using it
Adunno
KJust tested on my end, legion go running Forza Horizon 5 and Crysis 2
Kboth using gamescope FSR
Kboth at 48 fps frame limits
Kno issues
KIf there's a problem it's in gamescope and might get fixed by valve, but I can't seen to reproduce this
Amight be the reversal
TThat’s fair Kyle
