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.
20 Replies
@Kyle Gospo so the vrr revert breaks the legion go?
Nope, works fine here
Let me know if you disagree on your hardware
i dont have your gamescope version on it
and im not running to compile it tbh
works great on the Ally
pushed the ally fixes and i think thats it for today
Very nice
Run a build tonight
btw i hate the updates in steamui
its so confusing
we have to fix it
How can I resolve this or am I just stuck on 8/19. @antheas I thought you were on an April build or something.
i maintained that build until may
all issues with itshould be fixed now
Is 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.
we 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
what game do you have issues in?
Aye, very important detail
Kingdom 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.
I’ll try reinstalling Bazzite and see if that fixes the issue
hi, 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
No
We will experiment with the frame limiter soon
The launch args work great on the ally
I 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.
fsr is not good
It’s always worked ok for me. What would you suggest?
im not using it
dunno
Just tested on my end, legion go running Forza Horizon 5 and Crysis 2
both using gamescope FSR
both at 48 fps frame limits
no issues
If there's a problem it's in gamescope and might get fixed by valve, but I can't seen to reproduce this
might be the reversal
That’s fair Kyle