It does yeah, but not for applications running in XWayland. For example, I'm running a secondary 4k monitor with 1.5x scaling so it matches the other 1440p monitor. For native wayland applications, everything works just fine, but running an XWayland application on the 4k monitor will make it render at 1440p and become a blurry nasty mess. In KDE it will render in proper 4k (as if it was native a Wayland window), because they've somehow worked around that issue.
KDE's VRR and XWayland fractional scaling implementations are pretty dope. Wlroots pls
I love arch and I’m incredibly biased, but here goes. I have used Arch exclusively for the past n years. All of the things you’ve mentioned will work great. The AUR absolutely rules. It’s rather similiar to Void in the sense that it’s a completely blank slate, so it’s going to be as unique an experience as you make it.
Arch is really stable and reliable as long as you don’t break it, really. Out of the handful of times I’ve fucked up my install, all of them have been my own fault. Fortunately Arch is (relatively) easy to fix: keep a live USB on hand and chroot into your physical drive with arch-chroot and unfuck whatever needs unfucking. I haven’t ever had to completely start over from scratch a single time. It’s a learning experience!
Go for it, I say. Try it in a VM beforehand if you gotta.
I’ve been fucking around a lot with this same stuff on a similar setup (6900XT, sway, M27QP, Arch 6.4 tkg-pds). I managed to make it work more or less flawlessly. Here’s how I did it:
I use MANGOHUD=1 gamemoderun %command% in Steam to run my games.
When Gamemode runs, it’s configured to enable adaptive_sync, start gpu-screen-recorder, and run a script that sets pp_power_profile_mode to 1 and power_dpm_force_performance_level to high. As @Atemu mentioned, there’s some kind of bug with amdgpu, so by default the power management will be all over the place.
The built-in frame limiter in some games (e.g. Apex Legends, Risk of Rain 2) can cause stutter for some reason I don’t understand. V-Sync also had stutter and also caused noticeable input lag. The solution was to use MangoHud’s frame limiter with fps_limit=165 in MangoHud.conf.
This patch fixes the mouse move VRR issue. There’s instructions on how to apply it if you scroll down a bit. If it still doesn’t work right, try launching sway with WLR_NO_HARDWARE_CURSORS=1 sway. No need to disable direct scanout either.
Let me know if it works!
“Tuning” is a pretty good one really, since it’s also a car modding thing, right? (I’m not good with cars.)
Oh, shit, I never thought of that. Thanks for pointing it out
I wish I could go through life like this as well, damn. Never ever have to entertain the thought that maybe someone else’s wacky opinion is sincere and has a solid foundation to it, but nah man, it’s just a bot. Seems a lot less stressful.
Mint is cool, linux is cool, and you are cool too. Enjoy