No, but I had no major problem gaming with an Nvidia card on Tumbleweed. Just followed the wiki guide and added it to the zypper repos and everything was fine.
When I need a microphone I use my Cloud Alpha S, but most of the time I use my Letshuoer S12 with a CX-31993 and in the future I plan on getting an Audio Technica ATH-R70x.
If you want wireless, you could always get a good pair of headphones and pair them with either the FiiO BTR5 or the Qudelix5k.
I looked through the webpage and github repo but still don’t understand. What is the purpose of Proton-Qt? Lutris and Steam have their “which version to use” settings. What does this tool add?
To my knowledge it’s how you install the proton compatibility layer. That doesn’t just come with steam, right? You’re just telling the game which version to attempt to use, right?
Steam has a list of proton versions to choose from in the compatibility settings of the game. When you select one it downloads it automatically. You should only have to download a proton version manually if you want to use the Glorious Eggroll versions, or if you really need a specific version that steam doesn’t list, at least as far as i’m aware.
You may as well. Proton on Steam is really effective and with GE I haven’t had a game be unplayable for a while. I don’t really care for modern loot box gambling simulator paid public alpha type games though, so YMMV.
So, because Foza Horizon 5 was one of the first games to come out for the Steam Deck I bought it for my PC thinking it would run well. Turns out it won’t run with the current Linux Nvidia drivers and I had to get a refund.
I take it you’re aware of protondb and tried the suggestions there? There’s a few people reporting recently that it works fine for them. Maybe recent updates have fixed issues
Can someone explain what this means? I’m new to Linux gaming. Don’t really get what the difference is between wayland and x11. Will this improve performance in d4 on distros like fedora?
Simply put, X11 is the bottom of the graphics stack, i.e. everything that makes Linux have more than just a command line has historically been built on top of X11
X11 is OLD. Like really old. And has a bunch of problem because of it (no variable refresh rate, no good multi monitor support, no proper fractional scaling , tearing, no security etc) It’s also very mature. Somehow developers have managed to build a decent user experience out of the old X11
The Wayland protocol was designed to overcome the shortcomings of X11 and replace it. Wayland is now at the cusp of being a fully functional complete replacement for X11. It already is for many (most?) use cases.
Many Applications that are not made for Wayland will still run in Wayland, but they run in a fake X11 server inside called Xwayland. But native Wayland is better (performance, security, features)
Wayland very good on AMD and Intel these days. Nvidia was unsupported, but last year nVidia made a business decision to support EGL(?) so with fresh drives work has begun in Gnome and KDE to support Nvidia in Wayland. I’m not sure how mature Nvidia on Wayland is yet
yeah, wayland is awesome, unless you really need global shortcuts decided by the application, or a tun of other accessibility features. Still though, as you said, for most cases, wayland is good, and even the a11y features are getting ironed out, ever so slowly.
Wayland very good on AMD and Intel these days. Nvidia was unsupported, but last year nVidia made a business decision to support EGL(?) so with fresh drives work has begun in Gnome and KDE to support Nvidia in Wayland. I’m not sure how mature Nvidia on Wayland is yet
Clarification: GBM is what Intel, AMD and the general “nice players” of the Linux graphics ecosystem decided, whereas EGLStreams was something NVidia came up with because it worked better with their proprietary drivers (AFAIK)
Gnome and KDE were fine going out of their way to support both, but smaller implementations such as wlroots (the thing behind sway and Hyprland and other non-Weston “window managers”) didn’t feel the tradeoff was worth it (in both philosophical and manpower reasons) and stuck to GBM.
NVidia comparatively recently “caved in” and got GBM support working (alongside kernel mode setting & other terms you don’t really need to know about), and being one of the few proprietary players in the ecosystem they have not been able to benefit from help from the community, which is one of the reasons why their Wayland support is immature compared to the likes of Intel and AMD.
You’re mostly there, but the big issue now is their handling of Xwayland. nVidia also doesn’t expose VRR/GSync under Wayland (but an engineer remarked that it’s slated for the 545 series release on the nVidia Linux forums).
The most glaring issue currently that effectively blocks Wayland for nVidia users is the lack of implicit sync on their end, and the Xwayland developers refusal to merge nVidia’s proposed explicit sync method. This is oversimplifying but the short version is from nVidia “implicit sync is too slow, it architecturally conflicts with our driver forcing a comprehensive rewrite, and we don’t want to look bad with implicit sync’s performance”. The response from X devs boils down to “You weren’t there when we planned all this, implicit sync works fine, explicit sync won’t benefit how the Mesa drivers work so this would only be for your benefit, and you’ve been complete assholes”.
Neither side looks like it’s going to flinch, so getting Wine to run in Wayland is the only feasible solution for nVidia users. In an all-wayland environment with no applications running under Xwayland, Mutter and plasma-wayland run like a dream, it’s a great experience.
linux_gaming
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.