I have seen native versions tank as the default distro setups change over the years. As weird as it sounds it feels more reliable to use the windows version under proton/wine. Often game modding communities stick to the windows version.
Once M$ inevitably introduces Windows Cloud with subscriptions and the lowest tier being ad supported with anti-adblock and a registration fee, then Linux will become the preferred experience native or otherwise.
For the time being though wine and proton are good enough. I have been doing all my gaming on the steam deck and there haven’t been any games that make me feel like it’s a lesser experience in any way. The few games I have any difficulty running tend to be shitty games with micro transactions and kernel anticheat that doesn’t even prevent cheaters. Several can be made to work anyways. You can even install poorly made games and mods using the case folding toggle in ext4 that steam deck does have access to.
I am admittedly still waiting for someone to tell me that Wayland incompatibilities are a thing of the past…
It could have consequences should something happen to Valve. In many cases the linux ports of yesteryear were inferior, anyway.
Better to have the game at all. And it is understandable that they don’t want to put in a bunch of extra work given they can’t just pay a department’s worth of people to handle it for them.
If you don’t have to put up with Nvidia and there’s nothing tying you to X11 I recommend making the jump to Wayland, a lot of these sorts of issues have been solved over there
I haven’t had any problems with gaming in Wayland. Perhaps you haven’t configured it properly, especially if it wasn’t default installed on your system.
I would highly recommend trying again and sharing logs if you continue to have problems. People on here or the PopOS forums should be able to help. Wayland on AMD should function just as well as X11, and I would expect PopOS to ship all the necessary dependencies.
Only Wayland correctly supports multiple refresh rates. If you use to refresh rates on X11, it will refresh the screen at the highest rate. This is likely to cause tearing on the lower refresh rate screen.
Personally I have never had issues with my monitors having different refresh rates, at least not while using Gnome. Maybe it is more of a X11 KDE issue.
Hmm, I’ve just tried a fresh install of Manjaro and it’s exhibiting the same problems as Pop. It could be something to do with my setup? Or maybe there’s some other Linux fuckery going on? It’s strange though, since Windows works just fine.
What kind of problems are you seeing? The only issue I had was stuttering but I fixed that with corectrl. I have an AMD GPU and running Wayland if that helps.
When launching SteamVR my headset turns on but all I see is a grey screen. In the left eye there’s a very glitchy image of my desktop that flickers rapidly. Disabling asynchronous reprojection fixes the flickering desktop but the view is still completely grey.
Also, my base stations don’t wake up when launching SteamVR. Trying to scan for them results in it find them but being unable to connect (with an unhelpful error message that says “failed to connect” or something along those lines). I assume the lack of base station connectivity is causing the grey screen in the headset, but I’m not sure how to get them to connect.
I’ve tried using lh.py to get them to wake up, but there’s some Bluetooth error that happens that I haven’t figured out yet: bluepy.btle.BTLEManagementError: Failed to execute management command ‘le on’ (code: 17, error: Invalid Index). I read somewhere that this might be because the Index’s Bluetooth chip doesn’t work on Linux and that I may have to buy a separate Bluetooth adapter :/
I’ve followed the Bluetooth instructions but now SteamVR crashes on launch.
I get a 109 error on the 1.14 Linux branch (no change from before).
On the beta branch it crashes as soon as I launch it (nothing specific, just a message saying SteamVR is disabled because it crashed and a Retry button). Upon retrying my entire system froze and I had to hard reset. Upon rebooting and trying again it broke the window manager so now I have no window chromes (if that’s what you call them on Linux? the top bar and title and min/max/close buttons) so I had to reboot again.
On the stable branch it seems to now work but there’s a very noticeable delay in my head movements, which is very nauseating. Disabling asynchronous reprojection seemed to slightly improve this, but it’s still noticeable.
If I can’t find a fix for that, it seems like Linux VR is still a pipe dream for me. But in any case, thanks for your help so far!
Regarding the lag, to fix that I had to make sure the gpu was using it’s full capacity which I managed to do by using the Corectrl app to add a SteamVR profile and setting it to max. Without it I would see the same issue where it didn’t move fast enough with my head movement.
It seems CoreCtrl doesn’t support Nvidia GPUs, which is unfortunate. I did also attempt to set PowerMizer mode to Maximum Performance in nvidia-settings but that didn’t help. I suppose I’ll need an AMD card to have a good Linux VR experience?
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.
I’d sooner believe shit is a harmless and beneficial food additive, than I’d believe DRM harmless. and no, I’m not a pirate, but that doesnt mean DRM hasnt fucked me, and not even in a DRM/Proton fashion because it was before I even switched to linux
Right now, you can use xorg or wayland with multiple monitors and different refresh rates without problems. What is really the problem, at least for me, it is the VRR( variable refresh rate) like freesync. If one of your monitor has it, and you need it while playing, for xorg with gnome you must have to turn off the other monitors, while with wayland the patch for it it’s not merged yet.
Did you manage to get similar performance on Linux? Halo Infinite on windows 10 gives me an average of 150fps with medium settings, on Linux I get 70fps with he low prest and more stuttering. I use gamemode as well. My GPU is rtx 3070.
Really wish i knew about this before buying the game, had a lot of fun, but i’m not going back to Windows just so i can play battlebit, really regret recommending this game to my friends now…
And for anyone having even a sliver of hope, the devs don’t care about us, we only make about 1,6% of Battlebit’s Player Count and they have already stated that they will implement it in their game and thats non-negotiable.
In the future they might implement linux support again, but as of now, i cannot in good faith recommend a game that restricts players choices and has an intrusive AC like Faceit.
When I was on X11 (kde), my 144hz monitor would frequently feel like it was operating at 60hz but I could never figure out what the cause was. I used to turn off my 60hz monitor before gaming as a workaround. I quickly switched to wayland and haven’t had to deal with it since.
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.