Probably, yeah. There has been radio silence on the github issue about it for a long time.They haven’t shared any of the relevant issues in xwayland, which tells me they don’t want a bunch of angry tryhard gamers harassing the X.org folks. And you all shouldn’t harass the gamescope folks about it either; this issue is probably complex to solve because there are a lot of moving parts.
It’s probably not even a consistent phenomenon. Some games are improved by having the frame limiter on. For example, SoulCalibur VI has absolutely garbage frame pacing without the limiter, and the latency increase from turning it on isn’t noticeable.
Yes of course, it’s unlikely that will ever be fixed. For now just bypass it completely and use Mango hud commands for an actually usable limiter with low latency.
Yes of course, it’s unlikely that will ever be fixed. For now just bypass it completely and use Mango hud commands for an actually usable limiter with low latency.
Is there a way to shorten the command? Or make something default for all?
Since the latency of Gamescope’s FPS limiter still seems to be a problem, and we’re still doing a pretty slapdash thing of using MangoHUD’s limiter instead, I went ahead and made a script that makes it just a little cleaner.
After you save it and update your PATH variable as documented there, you can just use mangolimiter [-f FPS] %command% as the launch command.
So FYI, the path addition did not work. The folder environments.d wasn’t there, and even after I created, nothing happened, it did not recognize it.
So I ended up adding the following line to .bashrc directly. Also, “mangolimiter” is quite long to type in Deck’s screen, so I’ve shorten to “fps”. I’ll remove the -f parameter, probably, so in the end is going to be just “fps 40 %command%” , but thanks for it
If you created the folder environments.d, then you did it wrong; that directory doesn’t have an s in it. It’s $HOME/.config/environment.d. That will be why it didn’t work. Also, you likely have to at least restart Steam after making a change there, because those configuration files are read at session start.
Did i set it up wrong? my game keeps crashing when I try it. I made a mangolimiter folder inside bin, but was that just supposed to be the file itself? also its saved as a .sav that wouldn’t let me execute it no matter what, so I just did the chmod command
Is the input lag still bad with the FPS limiter enabled?
Probably, yeah. There has been radio silence on the github issue about it for a long time.They haven’t shared any of the relevant issues in xwayland, which tells me they don’t want a bunch of angry tryhard gamers harassing the X.org folks. And you all shouldn’t harass the gamescope folks about it either; this issue is probably complex to solve because there are a lot of moving parts.
It’s probably not even a consistent phenomenon. Some games are improved by having the frame limiter on. For example, SoulCalibur VI has absolutely garbage frame pacing without the limiter, and the latency increase from turning it on isn’t noticeable.
If we had VRR then this would be pretty much a non-issue.
I don’t think VRR is the silver bullet that you think it is.
The real question.
The input delay is when we’re docked? Bluetooth controller?
Yes of course, it’s unlikely that will ever be fixed. For now just bypass it completely and use Mango hud commands for an actually usable limiter with low latency.
What are the commands for this?
Paste this in launch options for any game:
MANGOHUD_CONFIG=fps_limit=40, no_display mangohud %command%Thank you!
Is there a way to shorten the command? Or make something default for all?
Since the latency of Gamescope’s FPS limiter still seems to be a problem, and we’re still doing a pretty slapdash thing of using MangoHUD’s limiter instead, I went ahead and made a script that makes it just a little cleaner.
After you save it and update your
PATHvariable as documented there, you can just usemangolimiter [-f FPS] %command%as the launch command.So FYI, the path addition did not work. The folder environments.d wasn’t there, and even after I created, nothing happened, it did not recognize it.
So I ended up adding the following line to .bashrc directly. Also, “mangolimiter” is quite long to type in Deck’s screen, so I’ve shorten to “fps”. I’ll remove the -f parameter, probably, so in the end is going to be just “fps 40 %command%” , but thanks for it
export PATH=“/home/deck/.local/bin:$PATH”
If you created the folder
environments.d, then you did it wrong; that directory doesn’t have an s in it. It’s$HOME/.config/environment.d. That will be why it didn’t work. Also, you likely have to at least restart Steam after making a change there, because those configuration files are read at session start.Did i set it up wrong? my game keeps crashing when I try it. I made a mangolimiter folder inside bin, but was that just supposed to be the file itself? also its saved as a .sav that wouldn’t let me execute it no matter what, so I just did the chmod command
if it’s a linux command, look up aliasing
Its an environment variable I believe, something like this:
MANGOHUD_CONFIG=fps_limit=40, no_display mangohud %command%Latency might suck but the built in frame limiter seems to have overall more consistent timing than other ones I’ve tried.
I’m not sure, but it feels a bit better. At least for me. But I didn’t touch my deck for some time, so it may just be my imagination