
_/Stixx
Published
LD_PRELOAD= __GL_THREADED_OPTIMIZATIONS=1 %command% -nosplash -nostartupmovies
Switch to DX12 in /pfx/drive_c/users/steamuser/Documents/My Games/Borderlands 3/Saved/Config/WindowsNoEditor/GameUserSettings.ini : PreferredGraphicsAPI=DX12
Use Media Foundation Scripts: https://github.com/z0z0z/mf-installcab https://github.com/z0z0z/mf-install
Only one disconnection within 8 hrs.
General Information
Using DX11 causes the game to crash on boot for me in any configuration. I've tried proton 7-8, Experimental, and various GE protons starting from version 6. Game does not boot for me in Proton 8 at all, and freezes after 30 seconds in any scenario with proton 7, GE or not.
Modding Notes
For modding I had to use mitmproxy to host a script on a server (a windows device on my local network) that sends hotfixes to the client (my linux computer), and add this to the bottom of /etc/hosts
:
# Borderlands 3 Hotfix Patcher
[IP of Server] discovery.services.gearboxsoftware.com
After a reboot, everything works as intended.
Multiplayer With Mods
If playing with others, multiplayer modding works, you can port forward your server and have windows or linux users redirect hotfixes by editing their hosts in the same way, using your external ip address. Windows users will require a certification - you'll have to google how to do this.
Make a BAT file that contains the following one-liner (on windows):
mitmdump -m reverse:https://discovery.services.gearboxsoftware.com/ -p 443 -s hfinject.py
Linux users should be able to figure out the shell script version of this.
While it takes a few steps to get the Linux-Native version working correctly, afterwards there are zero issues.
/path/to/linux/binary # %command%
Game is Modded using CCLoader v2.22.1
Fullscreening has incorrect coordinates.
Running the game through Steam with mods enabled causes some weird behavior. Instead use the above launch option to launch the game directly through terminal and bypass steam hooks.
If modded, It's worth mentioning if the game crashes on launch, try removing the chromium-args from ./CrossCode/package.json. This file is added by CCLoader
Fullscreening to any resolution that isnt 16:9 offsets the cursor and sometimes prevents the cursor from being positioned over portions of the screen.
Originally running the vanilla game using Proton (any version), the game experiences severe microstuttering after about an hour of play. The native version does not have this issue.
I've heard there are issues with controllers not working out of the box with the Linux-Native version. I can't confirm since I've never tried.
mangohud %command%
Completely cuts out intermittantly, eventually leading to a complete X-Session freeze.
Complete system freeze, switching to a different Virtual Console (CTRL+ALT+F1 in my case) then back again will sometimes unfreeze the game. This happens quite often.
Crashes to desktop frequently if I don't change Virtual consoles right as the freeze happens. (After every other dialog or Encounter where the combat music changes)
I've tried various proton versions (Experimental, GE_9-4/8-32/7-55, and 8.0-5) same problem throughout each version. Denuvo prevented me from troubleshooting more since changing proton changes the "Computer" you play on.
Requires GE7-42 to run - any other proton fails at EAC Instantiation. Requires ProtonEAC tool installation from Steam Store.
Otherwise, game boots, runs and performs same or better than Windows. You may or may not be disconnected more frequently than you would otherwise on Windows it seems.
Runs - No Multiplayer
PROTON_EAC_RUNTIME
The tutorials play and work correctly. FPS locked at 60. Seems a patch caused a regression, the game no longer plays any multiplayer matches.
Proof it runs: https://i.imgur.com/y1eA8O6.jpg
Disconnection after match starts: https://i.imgur.com/fa5AdYf.jpg
Please see this screenshotted post I made on the official Discord Server for this game. Raw Link to Post
This game's servers are not the best in general, and the netcode is pretty bad with skills that propel you in a direction. (eg. Dashing)
Unsure if the aforementioned bug is a game thing or Proton/Wine thing - I haven't seen anyone post about it nor anyone that I play with have ever had it happen to them.
Seamless, just like Windows.
This game doesn't seem to work after first install for some people (Including me), setting to experimental and restarting Steam allowed the game to launch.
Pretty much just runs out of the box. Use "PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1" to enable DLSS; game isn't optimized yet.
VKD3D_CONFIG=dxr11,dxr,force_static_cbv PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_FEATURE_LEVEL=12_2 mangohud %command%
Flickering grass/foliage independant of Foliage settings
Seems alright so far. Few crashes here and there - but nothing outside the norm for a new game that just released.
VKD3D_CONFIG=dxr11,dxr,force_static_cbv PROTON_HIDE_NVIDIA_GPU=0 PROTON_ENABLE_NVAPI=1 VKD3D_FEATURE_LEVEL=12_2 mangohud %command%
Geometry of moving platforms appears glitched, or transparent.
After a while of playing, exiting menus sometimes causes a micro-freeze.
Rarely, alt tabbing crashes the game
This audio bug exists in Windows as well. Game voice lines do not play when samplerate is set to anything besides 44100/24bit or 48000/24bit
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 PROTON_NO_ESYNC=1 DXVK_ASYNC=1 voiceLD_PRELOAD= __GL_THREADED_OPTIMIZATIONS=1 gamemoderun %command% -nosplash -nostartupmovies
change sound=alsa in protontricks (may not be needed, mileage may vary), edit /etc/pipewire/pipewire.conf
:
## Properties for the DSP configuration.
default.clock.rate = 48000
default.clock.allowed-rates = [ 44100, 48000 ]
resample-method = soxr-vhq
resample.quality = 24
If you do not have this file, create it using /usr/share/pipewire/pipewire.conf
as a template.
All voice line dialogue is missing. Use fixes to pipewire.conf
and potentially change audio driver to ALSA in protontricks.
Note: These settings change your audio preferences system wide, and may create unseen issues elsewhere with other applications audio.
Research:
Unsure what samplerate is by default on my system - its unreported anywhere through any GUI and in various CLI applications. Bitrate settings in pipewire.conf are NOT there by default, and were removed at some point in pipewire's lifetime. These settings should be able to be swapped easily through a GUI for ease of use. Linux elitists cause issues like this, and gatekeep solutions simply because they do not believe it's worth the time to do so.