Ignore this if you’re on Wayland, it doesn’t have this problem. If you have two monitors, X11 throws a hissy fit over varying refresh rates. Ie, your main monitor runs at 144, the secondary runs at 60. If you launch a game on the 144hz monitor, it often locks it to the lowest refresh rate (60 in this example). Double check to make sure the game is actually running at the desired refresh rate (easiest way is to turn off the second, slower monitor and launch the game. 144hz would now be the lowest refresh rate).
Also look into CPU scheduling. Could be locked to a power saving governor. You want it on a dynamic or performance mode. Also check out if Resizable BAR is enabled in your BIOS.
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.
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?
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.
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.
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
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.
linux_gaming
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.