

There were literally huge G-Sync logos in the boxes of the last three TVs I helped people buy. When you plug in a game console and press the settings button on my current display in game mode it pops up a large HUD element that says “VRR” and displays the type of VRR currently active and the current framerate. Every other option and metric is hidden away in a sub-menu.
Not that this matters, because the point of VRR is you don’t need to know it’s there. If it’s working, the drivers and the display should talk to each other transparently. The end result if you have a Windows machine with VRR and a Linux machine that doesn’t support it and you plug them both to the same display is, again, that the Windows game will look smoother, regardless of how many fps it’s spitting out.
And as always, a reminder I’ve given many, many, many times in my life, both personally and professionally, “it works on my machine” means nothing and doesn’t mean there’s no bug or that your code isn’t crap. Your anecdotal experience and my anecdotal experience aren’t the same, because I have a showstopper bug and your seven friends don’t, which still means there’s a showstopper bug.

FFS. I mentioned G Sync because they have a logo. VRR is so common an ubiquitous that there is a VESA certification for it now and a default standard for it for both HDMI and Display Port, no Nvidia required. It doesn’t matter if you have G Sync, AMD’s Freesync (which is an open standard) and can be used by any brand of GPU or generic VRR.
You having had your head in a hole about what the average display features are in 2026 for even an entry level gaming display doesn’t mean they aren’t common, important or widely supported. When Nintendo has adopted a universal technology and you haven’t you know you’re behind the tech curve.
For the record, plenty of Linux distros have full support for HDR and VRR. Mint just happens to… not.