Remix.run Logo
tuetuopay 8 hours ago

Outside of gaming, not much. However, now that I'm used to a 144Hz main monitor, there is no world where I would get back. You just feel the difference.

So basically, no use when you've not tasted 120+Hz displays. And don't because once you do, you won't go back.

bogwog 8 hours ago | parent [-]

I have a 165hz display that I use at 60hz. Running it at max speed while all I'm doing is writing code or browsing the web feels like a waste of electricity, and might even be bad for the display's longevity.

But for gaming, it really is hard to go back to 60.

tuetuopay 4 hours ago | parent [-]

Mine supports variable refresh rate, which means for most desktops tasks (I.e when nothing is moving), it runs at 48Hz.

Incredibly, Linux has better support than windows for it on the desktop: DWM runs full blast, while sway supports VRR on the desktop. Windows will only enable it for games (and games that support it). Disclaimer: Wayland compositor required.

It’s not enabled by default on e.g. sway because on some GPU and monitor combos, it can make the display flicker. But if you can, give it a try!

jasomill 17 minutes ago | parent | next [-]

Windows 11 idles at around 60 Hz in 120 Hz modes on my VRR ("G-SYNC Compatible") display when the "Dynamic refresh rate" option is enabled, and supports VRR for applications other than games (e.g., fullscreen 24 FPS video playback runs at 48 Hz* via VRR rather than mode switching, even with "Dynamic refresh rate" disabled).

* The minimum variable refresh rate my display (LG C4) supports is 40 Hz.

bogwog 2 hours ago | parent | prev [-]

I use KDE + Nvidia, and last I looked into it, it only worked if you had one monitor enabled. That's fine for gaming, not for working.

But it has been a while since I've tried it, maybe I should look into it again