Which GPU do you use? I believe mint defaults to the nouveau drivers for Nvidia GPU’s, which generally has significantly worse performance compared to the proprietary driver.
As mentioned above, usually, it is preferred to try installing the recommended driver. In order to do that, you just type in: sudo ubuntu-drivers autoinstallIf you want something specific, type in: sudo apt install nvidia-driver-450You just have to replace “450” with the driver version that you want and it will install the driver in the same way that you install an application via the terminal.
You have a 16xx series card, Proton 8+ have a problem with these cards (thanks to Nvidia), so switch to an older Proton version like Proton 7, should work.
Good. So you’ve confirmed that games can and do run on your system, both natively and using proton.
Next, I would try deleting the corresponding compatdata and shadercache folders for the games, to reset the games prefix and shaders. These are one folder up from the folder where the actual game files are, and the folders within have numbered names that match the ID of the game. (Which you can see in the update tab in game properties).
Simply delete the correct folders and steam will redo the proton setup for a game and recompile the shaders.
On a sidenote, I recommend installing proton-ge-custom from the AUR, it installs, keeps up to date, and makes available proton GE for you to use in steam and heroic, should you ever need a version with fixes that valve proton doesn’t come with.
At this point I’d be looking at logs. Two ways to go about this.
The first is to launch steam from a terminal (close it, then just enter steam in a terminal) and then try to launch the game. Steam will spew out lines about what is going on into the terminal.
The other way is to enable proton logs, which can be done by adding PROTON_LOG=1 %command% in the launch options for the game. Then when you attempt to run the game, a logfile should appear in you home folder.
I’m also assuming you’ve tried multiple proton versions? If you haven’t, do that.
maybe add PROTON_LOG=1 %command% to launch option to enable log? Try launching the game again, and see if anything weird logged on steam-xxxxx.log file in your home directory.
There is nothing in Borderlands 2 that requires proton-ge. Using default native should absolutely work, and so should proton for the Windows version. His system is fucked up somehow.
My usual ‘shot in the dark’ when someone mentions windows versions: Is the game data on a shared NTFS partition? If so, move it to a native linux FS like ext4 and try again.
Proton just doesn’t seem to like any data on an NTFS partition, but the error message is ugly and buried so I mentioned it in all of these types of posts.
This is good advise. My husband just installed Linux as a dual boot on his system over the weekend. He was having trouble with games that worked fine on my system until we re-downloaded them onto the Linux drive. Then they worked fine.
You want to be using Proton for BL2 regardless. The Linux client isn't updated, meaning no cross play and you can't use the final DLC. Also it's performance is shit compared to Proton
Do you have MangoHud installed? Last week I couldn’t run any proton game on my system until I uninstalled it/ removed the MANGOHUD=1 variable haven’t had this problem before, but something broke. Proton and wine were stuck at launching, no error messages/ logs, etc. drove me nuts.
Little note, the Borderlands 2 Linux & Mac port as been abandonned …aspyr.com/…/360020727692-Borderlands-2-Linux-FAQSo, do consider switching to the Windows version version via Proton for co-op play, HD Texture pack support and that last DLC too.
Those 2 games are extremely solid in my experience, haven’t had a crash ever in either of them.
I’ve played Borderlands 2 for 744 hours over many years with different hardware without a problem, except that I can’t get SHiFT keys to work in the Linux version, so if I want to use SHiFT, I switch to Proton for that. Both work flawlessly otherwise. I have only tried Portal native though.
I’m currently using the Manjaro distro with an old Ryzen 5 1600 CPU, Radeon RX 6800 XT GPU, and 16 Gig Ram.
My wife however uses Nvidia GTX 1080 ti and earlier GTX 970, and both games worked perfectly for her too using Debian with both cards. My wife also played lots of portal both 1 and 2 with Nvidia cards.
In short those 2 games should work fine out of the box, with both Nvidia and Radeon. So maybe you have some hardware problem? Or something with your installation was screwed up somehow?
You can see it looks for a script to shutdown steam or defaults to normal shutdown. I pointed os-session-select to a script that restarts my sddm service, before shutting down steam, so it returns me into the default session. It was a bit finicky though and I hacked a systemd service into it to ensure the script didn’t get killed.
Hope this helps. Might clean it up some time and put it in a repository/on the aur.
EDIT: I was inspired by ChimeraOS; it uses that os-session-select for its main project as well to return to the gnome desktop.
That helps a lot, thank you! I will look at it. Would really appreciate if you shared your work. Do you have the problem where you don’t see the menu or is this only me?
I haven’t had the issue with the menu, never had as far as I remember. It might be because of the way you set up the session. If you try installing the aur package I linked and start that session, the menu hopefully just works as it did for me.
That session does not work for me at all, or to be precise, it works only when I disconnect my second display. I might have to search for an option to disable that before launching the session.
Oh interesting & unfortunate. I can confirm I use one display, running it on my TV. I must say, big picture on my desktop session gets closer to the experience than when I initially set this up. I hope they add the quick settings overlay to the normal big picture mode some time. I might switch back to running on my desktop session.
To play Proton games you only need the latest gamescope from git, the HDR layer and environment variables are no longer needed for gamescope
Just set the launch arguments on Steam for any game to: gamescope --hdr-enabled --nested-refresh 165 --fullscreen --steam -w 3440 -W 3440 -h 1440 -H 1440 – %command%.
Don’t forget to set your refresh rate and resolution.
If you want to play videos files in HDR (YouTube also works) you need to use mpv together with the HDR layer.
After installing the layer you can run mpv like this: ENABLE_HDR_WSI=1 mpv --vo=gpu-next --target-colorspace-hint --gpu-api=vulkan --gpu-context=waylandvk “https://www.youtube.com/watch?v=dQw4w9WgXcQ”.
Thanks, appreciate the write up. Definitely sounds like HDR under Linux has a long way to go to reach the “just works” level.
I asked this in another thread but I would be curious to get different perspectives; could you use gamescope and mpv under Gnome and get HDR support or is KDE’s HDR support essential here?
Thanks, appreciate the write up. Definitely sounds like HDR under Linux has a long way to go to reach the “just works” level.
It’s not as long as you might think, by the end of the year we should have out of the box HDR on Linux. At least for Proton games. All the puzzle pieces are there, they just need to be put in place.
could you use gamescope and mpv under Gnome and get HDR support or is KDE’s HDR support essential here?
No, not until GNOME implements their HDR support. You can however run gamescope and mpv directly in tty instead of KDE/GNOME.
On the Steam Deck it already “just works” for a lot of games (with an OLED or an external display). So we’re not that far off for those changes propagating to Desktop.
I finally got a chance to try this out and couldn’t get it to work then I realized you mentioned this was git only right now, and I am all Flatpak’d up, so I need to wait.
What is the specific commit that adds the magic since the last release?
I also normally run in Flatpak but I switched to native until everything settles in. Turns out the config files are compatible now so you can run either and they will pick up the others config with no issue. Just have to watch out with shader pre-compilation because if you have different Mesa versions the clients will pre-compile back and forth all the time.
linux_gaming
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.