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.
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.
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.
I don’t think VRR is the silver bullet that you think it is.