Borderlands 3 (397540)

[NTMan]

Compatibility Report

• Name of the game with compatibility issues: Borderlands 3
• Steam AppID of the game: 397540

System Information

• GPU: AMD Radeon VII
• Driver/LLVM version: Mesa 20.0.99/10.0.0
• Kernel version: 5.6.0 rc5
• Link to full system information report
• Proton version: 5.0-4

I confirm:

• that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

steam-397540-DX12.log
steam-397540.log

Symptoms

1. The game didn't launch if selected DX12 API
2. With DX11 API looks like all work fine (I passed internal benchmark), but I noted some graphic glitches see ballons on 2:23
   
3. I couldn't connect to Gearbox Software SHiFT.
   

Reproduction

1. Just launch the game
2. Run internal benchmark
3. Select group privacy: Friends Only, Invite Only or Open to Public
   

[jalabb]

The game runs fine for me, benchmark passes with no glitches in both DX11 and DX12 modes.
I do have an issue with in-game videos though and I got the "Watch Monitor" game-breaking bug that was also reported on Windows. It seems to be related to Media Feature Pack, I tried using <Workaround removed by moderator> in the prefix but it doesn't help at all.
https://forums.gearboxsoftware.com/t/watch-monitor-bug/3119409/30

Nvidia 435, Proton 5.0.4

SHIFT isn't connected either.

[NTMan]

I do have an issue with in-game videos though and I got the "Watch Monitor" game-breaking bug that was also reported on Windows.

I have the same issue.

[jalabb]

<Workaround removed by moderator>

You should see the logo videos when the game starts and after loading your game it will be unstuck.

EDIT : Sorry :/

[kisak-valve]

Hello @poke86, the workaround you linked is legally problematic and has been removed.

The previous comment tells us the game uses Media Foundation, and the game would benefit from support for the framework maturing.

[ashmonger]

Got an issue too, game don't even launch nor creates config files
steam_profile

Can't post the log file, 1.3GB heavy.

[7HEPOW]

So after running the game a lot of times it'll crash when opening the inventory/stores etc.
This is aside from videos not working due to Media Foundation as it seems.
Steam Sys Info
steam-397540.log.zip (43MB extracted)
Edit: Resetting the prefix helps to run the game for an hour and a bit until it reaches the inv/store crash. I'm 'trying' to play it with a few friends in coop, so I could skip the 'look at screen' bug. 😄

[Semperverus]

I would like to add my experiences here as well, and mine are almost identical to the original poster of this bug. The one that is most aggravating to me is the Network bug preventing me from playing with friends.

I did manage to get the game to launch, but each time I launch it, it says that it has "crashed" multiple times and that it needs to reset the settings to launch again. If I click No, it will not launch at all.

[Patola]

Apart from the graphical issues, there is also a connection issue -- I can't get into multiplayer at all. I try to change to Public, it won't allow me. I log in to Shift using my browser and I even linked my steam account to gearbox, but it will not recognize that I am online (and of course I am not invisible or anything on Steam, I am online).

[KayEss]

Got an issue too, game don't even launch nor creates config files
steam_profile

Can't post the log file, 1.3GB heavy.

Had the same problem on my daughter's computer. Seems to be caused by an illegal instruction problem on some AMD Ryzen CPUs. Look at: #2927

Adding the clearcpuid=514 workaround to grub fixed it for us.

Worked out with help from Newbyte over on the Gaming on Linux Telegram chat.

Edit to add, this is the log for a client connect failure on LAN mode in case it helps anybody: https://gist.github.com/KayEss/04d502d09803392044e9493852039664 The log is for a connection attempt to another machine on the same LAN which has a game in progress

[Patola]

The connection issue works like that. I am online on Steam, logged in to SHiFT through the browser, I try the upper-right menu changing to "Public", it gives this message:

I also go to options, Network and Social, and try to change the Group Privacy to "Open to Public":

But as soon as I leave the menu, the connection error appears again:

steam-397540.log from these attempts is attached.
steam-397540.log

[sergisi]

I have the same problem with multiplayer. I've made the SHiFT account and linked with steam. My friends see me with matchmaking tools. Invitations won't work with the error message "Connection Failed: Could not connect to host". It also seems to affect LAN. Although they see me connected and can launch a petition to join, they will never enter and I can not see them.

[lwi19]

With no simple work around solution for my 'watch monitor' bug, I will now watch Proton.

[kisak-valve]

Hello @Hnaguski, @poke86, your comments were removed because that workaround is legally problematic. It's not okay to encourage other players to use it, either directly or indirectly.

[cqcallaw]

@kisak-valve Seems like folks are posting legally problematic work-arounds out of ignorance. I don't see how to educate the community about legal ramifications if all references to the work-arounds are scrubbed, though; seems like a reference scrub means mods like you are doomed to play an endless game of work-around whack-a-mole. Any way to avoid that?

[Hnaguski]

Alright I was aware about the legal issues with what I mentioned but wasn't aware of what was okay and what wasn't, since other people in this thread mentioned it, but not as in depth as I was.

[7HEPOW]

The network issues are a thing, even though I managed to connect, which seemed to happen out of luck. The first times launching the game yesterday it also didn't connect to SHiFT. First thing popping up for that is the Cross-Play thingie.

Further testing on various Proton versions brought me to the point of having the game run with videos under the freshly released tkg-5.4.r0. Videos will not work out of the box there, even though wine 5.4 has Media Foundation patches now.

As it seems, there's a shader or locale issue as well when the game's running for 60-90 minutes. This is running in DX11 mode and happens when either opening the inventory or any random box ingame. I found these lines in the crash logs of the game:

[2020.03.15-03.59.45:761][  0]LogStandaloneRenderer: SlateD3DShaders::CompileShader() - D3DCompilerFunc Result: DXGI_ERROR_88760B59 [88760B59]
[2020.03.15-03.59.45:764][  0]LogStandaloneRenderer: GammaCorrectionCommon.hlsl:6:11: error: syntax error, unexpected NEW_IDENTIFIER
 Result: DXGI_ERROR_88760B59 [88760B59]

Full Log: CrashReportClient-backup-2020.03.15-06.33.37.log

According to a thread in the Steam forums it might have to do something with non-UTF8 characters in the game's packages.

Proton versions leading to the same error are: 5.0-4 / 5.0-GE-1 / 5.2-GE-2 / TKG-5.4.r0

[grahammitchell]

I guess I should add my report here, because the game won't launch at all for me.

System Information

• GPU: GTX 1070
• Driver version: nvidia 440.64
• Kernel version: 5.3.0-40-generic
• Link to full system information report
• Proton version: 5.0-4

Symptoms

I just click the green "Play" button in Steam, it changes to a blue Cancel button for a second, then a blue Stop button for ~45 seconds, then it changes back to the green Play button. Literally nothing else happens; no black screen, no sounds, no menu, no dialogs.

Things I've tried:

• Verify game files
• Uninstalled Borderlands 3 and re-downloaded
• Verified re-downloaded files
• Proton 5.0-4 and 4.11-13
• rebooting Ubuntu
• installing all system updates (there aren't any)
• with and without various MF workarounds
• blowing away the Proton prefix and letting it recreate
• switching graphics drivers (tried proprietary nvidia-driver-435 and open source nvidia-driver-440

The raw Proton log file from PROTON_LOG=1 is 1.4GB(!) but I've uploaded a gzipped version here: steam-397540.log.gz

I'm relatively sure that my graphics drivers and Vulkan are installed correctly, because I can play Shadow of the Tomb Raider (native) just fine and it says I'm using Vulkan, and I can play DOOM via Proton in Vulkan mode as well.

Hoping somebody has some clue, since apparently most people can at least play the game at all!

[kisak-valve]

Hello @grahammitchell, looks like your system is affected by #2927, you can try a workaround by adding clearcpuid=514 to grub, which was reported to help at #3635 (comment).

[fabianbieler]

The problem with multiplayer seems to be missing ALPN support in schannel.
The attached patch hacks around that.

0001-schannel-ALPN-hack.patch.gz

Note that this hack is a potential security risk.

[kisak-valve]

Hello @fabianbieler, can you send that patch to upstream wine's mailing list for evaluation? Ideally we'd like to see fixes like that land upstream, then a merge request to backport it to Proton.

[fabianbieler]

That patch won't be accepted upstream, as it's a potential security rist. I should have mentioned that, sorry.
I will try to write a proper patch. That may take another week or two, however.

[grahammitchell]

Thanks, @kisak-valve, that did the trick! Don't know how I missed that. I haven't tried online multiplayer but now everything works except the benchmark.

Much appreciated.

[robertc]

Networking/SHiFT logon works in Proton 4.11-13. Note that I had to delete the prefix used by my 5.0/5.2GE attempts before the game would launch with 4.11.

[hjri]

Can confirm that Networking works with 4.11-13 but does not with 5.0-4. Also all the fixes for videos not playing on 5.0-4 stopped working on 4.11-13 however.

[KayEss]

but now everything works except the benchmark

I thought the benchmark wasn't working, but it turns out that it just takes a really long time to load, and the sounds start quite some time before the video fades in. Have you just tried waiting longer?

[kakra]

There may be an issue/conflict if you previously used a third-party Proton version, or applied the MF hack. You should retry with a clean prefix in that case. Current Proton Experimental should play the videos just fine (although some users report they are played in the wrong language). At least it works for me with Proton Experimental, both the shader compiling video (walking robot) and the logo videos, even in-game videos. I didn't test the introduction video because I never started a new play-through yet.

[CSahajdacny]

There may be an issue/conflict if you previously used a third-party Proton version, or applied the MF hack. You should retry with a clean prefix in that case.

@kakra, @iWeaker4you said He used Proton Experimental-BleedingEdge with a clean prefix

I confirm the same error using Bleeding Edge: steam-397540.log

I didn't test the introduction video because I never started a new play-through yet.

Well, do it. Change the language to Spanish (or French, German or Italian) and start a new play-through and see what happen with Marcus intro. After that, don't choose a character, just close the game with alt-F4 and the previous save game will be untouched.

[kakra]

I didn't switch language as German is my native language. When I tried a new game, the Marcus intro audio is English, so it's actually not working as you say.

In-game audio is still correctly localized, even the top overlay videos that sometimes play. Looking at the movies folder, this is actually easily resolved: Those movies have no audio track at all so it will probably be played by the game from a separate audio track.

I didn't use BleedingEdge, just normal Proton Experimental.

Are there other games to try which have multi-language audio tracks in videos? Maybe this is specific to BL3? Because looking at the video converter code it looks like it properly handles multiple audio tracks.

[ruineka]

This game constantly downloads 8.6GB every time steam is restarted. It eats up a tremendous amount of your internet data usage if not watched closely.

[iWeaker]

This game constantly downloads 8.6GB every time steam is restarted. It eats up a tremendous amount of your internet data usage if not watched closely.

This problem happens, when you install the game in another directory than the default. My solution is to create a symlink folder from the "common" folder to another path or hard drive where to install the game

[ruineka]

This game constantly downloads 8.6GB every time steam is restarted. It eats up a tremendous amount of your internet data usage if not watched closely.

This problem happens, when you install the game in another directory than the default. My solution is to create a symlink folder from the "common" folder to another path or hard drive where to install the game

🤔 On my OneXPlayer the game is at the default directory on the only available SSD and it does this still.

[kakra]

I think there are bugs in the Shader Pre-Caching downloader currently which downloads redundant data, or doesn't properly detect which version of the shader cache is already downloaded. For me, this behavior has currently stopped and most games only download a few MBs (but each time Steam starts). Clearing the download cache and shaders may fix this, or at least bring it down to a more usable situation. It affects multiple games, BL3 is one of the worst - I can confirm at least that.

[CSahajdacny]

Well.. Proton 7.0-1 is here and I tested Borderlands 3 again...
And again Marcus intro audio is English only, but is not a Proton issue by itself, because if I check the file transcoded_video.foz file with the program MediaInfo, like in the picture, the fossilized file has only one audio Stream....

.....instead of the eight audio streams of the original Marcus MP4 file

So, that specific issue is an issue of the remote transcoder and not a Proton issue.

Now, according to the Proton 7.0 release info:

Added support for local decoding of H264 videos.

So, I tried the game with Proton 7.0 without the transcoded_video.foz file for to check if that is true...
But no, no video is shown, only the TV adjust signal.
The Proton log complain about some missing Gstreamer plugins.
steam-397540.log

wine:27277): GStreamer-WARNING **: 13:02:32.613: Failed to load plugin '/home/carlos/.local/share/Steam/steamapps/common/Proton 7.0/dist/lib64/gstreamer-1.0/libgstlibav.so': libavfilter.so.7: no se puede abrir el fichero del objeto compartido: No existe el fichero o el directorio

After A LOT of further testings I discovered that these files are missing from Proton 7.0/dist/lib64/ folder:
libavfilter.so.7
libavformat.so.58
libavcodec.so.58
libavutil.so.56
libswscale.so.5
libswresample.so.3
libavresample.so.4

With those files in the mentioned folder, Marcus Intro now works perfect!
I wonder why those Gstreamer files are missing from Proton 7

[SmiVan]

After A LOT of further testings I discovered that these files are missing from Proton 7.0/dist/lib64/ folder: libavfilter.so.7 libavformat.so.58 libavcodec.so.58 libavutil.so.56 libswscale.so.5 libswresample.so.3 libavresample.so.4

With those files in the mentioned folder, Marcus Intro now works perfect!

Followed your steps and also had to add these into the aforementioned folder:

View list

libpostproc.so.55
libbs2b.so.0
liblilv-0.so.0
librubberband.so.2
libmysofa.so.1
libflite_cmu_us_awb.so.1
libflite_cmu_us_kal.so.1
libflite_cmu_us_kal16.so.1
libflite_cmu_us_rms.so.1
libflite_cmu_us_slt.so.1
libflite.so.1
libass.so.9
libvidstab.so.1.1
libzmq.so.5
libgme.so.0
libopenmpt.so.0
libchromaprint.so.1
libbluray.so.2
libssh-gcrypt.so.4
libvpx.so.6
libwebpmux.so.3
librsvg-2.so.2
libzvbi.so.0
libsnappy.so.1
libaom.so.0
libcodec2.so.0.9
libgsm.so.1
libmp3lame.so.0
libopenjp2.so.7
libshine.so.3
libtwolame.so.0
libwavpack.so.1
libx264.so.155
libx265.so.179
libxvidcore.so.4
libsoxr.so.0
libserd-0.so.0
libsord-0.so.0
libsratom-0.so.0
libfftw3.so.3
libflite_usenglish.so.1
libflite_cmulex.so.1
libsodium.so.23
libpgm-5.2.so.0
libnorm.so.1
libgssapi_krb5.so.2
libnuma.so.1
libkrb5.so.3
libk5crypto.so.3
libkrb5support.so.0
libkeyutils.so.1

After this - gstreamer plugin warnings disappeared and all videos started working at long last!

This has also fixed similar issues with video that I've been having in Psychonauts 2! Thank you for the lead.

[kisak-valve]

[need help]: borderlands 3 killed by systemd-oomd because of huge memory usage

Issue transferred from #5854.
@lumingzh posted on 2022-05-22T22:25:59:

borderlands 3 runs with DirectX 12 API on a 16GB RAM laptop, but after some time like 20 minutes the memory usage will rise up to the whole RAM and killed by systemd-oomd.

Is there any way to limit or reduce the memory usage of borderlands 3 or fix this issue?

Is this relates to DirectX 12 or unreal Engine? Or it is borderlands' own bug?

Thank you.

[lumingzh]

Replying to #3635 (comment)

Looks like lower graphic settings can delay the out of memory kill.

[lumingzh]

Stop systemd-oomd.socket can delay OOM kill much longer on high graphic settings, but still will be killed by kernel OOM killer after all.

However, there is no system freeze when memory usage is very high, weird.

[Zorrototo]

Is the issue only on my side or is there a problem with mouse movement suddenly acting weird (roughly after 45 minutes of gameplay each time). This is not a problem of settings, vsync, mouse acceleration, mouse smoothing, mouse polling rate, or any other relevant 'solution' that comes on Google for mouse issue on this game.

The game still keeps its good performance, if I run straight forward it is absolutely normal, but when I move the camera with the mouse, then it is like the mouse input is acquired periodically instead of continuously. Imagine a grid of 50x100 squares in the screen, and the mouse 'cursor' snaps on the intersection of each line (or each square's corner), instead of freely and smoothly moving everywhere.

Only restarting the game fixes the issue. I tried a mouse with 125Hz polling rate, and another one with 1000Hz and 500Hz, I tried switching mouse when issue occurs, changing USB port, absolutely nothing seems to workaround the issue. It is kinda annoying because when it happens I need to finish what I'm doing, with the mouse bug active, then restart/load the game.

[kakra]

I don't play this with mouse but rather a controller. But I may see similar behavior with other games that I use a mouse for, e.g. Elite Dangerous: The longer I play, the more often the mouse starts to jump. This only affects some parts of the game: The mouse cursor on menus is not affected but using the mouse, e.g. for the FSS scanner (where the mouse works like in an FPS game, turning the camera with it), the mouse starts jumping at random occasions, making it difficult to precisely navigate on the scanner. It looks like input events are not delivered to the game for a brief moment, probably even skipped, and when they do again, some sort of mouse acceleration kicks in and jumps the mouse position a great distance. Setting relative or absolute mouse mode in the game makes no difference (except that one mode may be even worse).

I'm not sure if this is something wine could do about, it may be an issue in the kernel or some blocking in user-space, as I'm also seeing messages like this in Xorg.log:

[403223.695] (EE) client bug: timer event8 debounce short: scheduled expiry is in the past (-27ms), your system is too slow
[403223.695] (EE) WARNING: log rate limit exceeded (5 msgs per 3600000ms). Discarding future messages.
[403305.700] (EE) event13 - Logitech K360: client bug: event processing lagging behind by 28ms, your system is too slow
[458754.532] (EE) client bug: timer event8 debounce short: scheduled expiry is in the past (-24ms), your system is too slow

As this is an i7-12700K, I doubt my "system is too slow". Rather, some timers seem to be off, or threads are being delayed. This also becomes visible in the game performance by seeing the frame time graph showing more and more spikes. The latter may be a problem of Elite Dangerous itself but it may show the effects of the same underlying problem.

I wonder if BL3 shows similar messages in Xorg.log, or if the weird mouse acting also applies to the menus when you have a real mouse cursor to navigate.

[kakra]

borderlands 3 runs with DirectX 12 API on a 16GB RAM laptop, but after some time like 20 minutes the memory usage will rise up to the whole RAM and killed by systemd-oomd.

As far as I know, systemd-oomd triggers on memory latency when memory usage is above a certain threshold, especially when swap is above a certain threshold (90% by default). Do you use a very small swap partition (1 GB is certainly too small, for your system I'd recommend about 4 GB). If you don't use swap at all: Linux memory management is not well suited for working without swap, you should add a swap partition then.

For my system (32 GB of memory, oomd enabled), swap usually hovers around 2-3 GB which seems dead memory and is unlikely to be swapped in again. The game works fine for me with oomd enabled.

If the problem still persists, you might want to lower the texture quality. Also, some kernels adjust vfs cache pressure in sysctl, this may have a negative impact on your experience. Adjusting that value may improve things (lower values prefer the cache and thus increase swap/memory pressure, the default value is "100"). If you're running from SSD, there's probably no point in lowering the value.

[lumingzh]

Replying to #3635 (comment)

I'm using Fedora silverblue, the default swap method is zram at 8GB size, so there is no physical swap partition.

But I don't think 16GB memory is enough, because the game will be killed by kernel if I disable systemd-oomd.

[Zorrototo]

As this is an i7-12700K, I doubt my "system is too slow".

Indeed, these messages are common in my experience, don't worry about them I think. I have similar messages for my keyboard.

For my issue I have some progress, not posting details right now ,but I think I shouldn't have posted here, but on the Steam For Linux issues tracker probably. Will post more details when I will fully troubleshoot the issue and properly narrowed it down to Steam (or its overlay) and/or the method I start my game with.

[kakra]

I'm using Fedora silverblue, the default swap method is zram at 8GB size, so there is no physical swap partition.

But I don't think 16GB memory is enough, because the game will be killed by kernel if I disable systemd-oomd.

Maybe try reducing zram size to 2 or 4 GB, or completely avoid it and add a physical swap partition - maybe just "in the name of science". I had problems with too big compressed swap (but I'm using zswap instead of zram).

[lumingzh]

I'm using Fedora silverblue, the default swap method is zram at 8GB size, so there is no physical swap partition.
But I don't think 16GB memory is enough, because the game will be killed by kernel if I disable systemd-oomd.

Maybe try reducing zram size to 2 or 4 GB, or completely avoid it and at a phyiscal swap partition - maybe just "in the name of science". I had problems with too big compressed swap (but I'm using zswap instead of zram).

I increased zram size to my whole memory, and works normally now.

[Shotweb]

Replying to #3635 (comment)

Is there any easy way to do this? I have no idea where all those files are

[CSahajdacny]

Replying to #3635 (comment)

Is there any easy way to do this? I have no idea where all those files are

Yesterday I tested the game it using a clean Proton 7.0-4 and the problem seems to be fixed.

[KhazAkar]

Proton 7.0-6 (Next),
Ryzen 5 4600H
RX 5500M
Slackware64-current, Sway, Steam running through flatpak
Issue observed:
Mouse buttons does not work, plus mouse movement in multi-monitor setups is going out of the display borders where game is.
Is there any fix for that?

[kakra]

plus mouse movement in multi-monitor setups is going out of the display borders where game is.

I can prevent that by setting the game to fullscreen instead of borderless window. But games should also be able to properly capture the mouse, so that may actually be a bug, either in the game or in Proton. For this particular game, I use fullscreen mode and the mouse is properly captured.

[KhazAkar]

I can prevent that by setting the game to fullscreen instead of borderless window.

This solution does not work for me unfortunately, instead of grabbing mouse - after moving it out of main monitor it goes full dark.

[evenfrost]

The game processes Vulkan shaders every time I start the game. Other games are not doing that. The game is installed in the default directory. My launch parameters are:

DXVK_FILTER_DEVICE_NAME="1650" gamemoderun %command% -nostartupmovies -nosplash

[perroboc]

System Information

• GPU: RX 7900 XTX
• Driver/LLVM version: 4.6 (Compatibility Profile) Mesa 22.3.5
• Kernel version: 6.2.6-76060206-generic
• Link to full system information report as Gist: https://gist.github.com/alvaromunoz/ae7c9dec0f5a87de1da27831443451ed
• Proton version: 8.0-1

steam-397540.log

Symptoms

Game continually freezes from a couple seconds to almost a minute. It seems it's loading assets on the fly? I'm running the game from an NTSC partition on an M.2 SSD (980 pro). This happens more often if hosting a game session.

[KayEss]

from an NTSC partition

Presumably you mean NTFS? This is not a great idea. NTFS is pretty slow even on Windows and is a terrible match for how Linux machines want a file system to work. You should move the game over to a standard Linux file formatted disk and see what difference that makes.

[perroboc]

from an NTSC partition

Presumably you mean NTFS? This is not a great idea. NTFS is pretty slow even on Windows and is a terrible match for how Linux machines want a file system to work. You should move the game over to a standard Linux file formatted disk and see what difference that makes.

Damn... my brain was on auto pilot at the time, mixing NTFS with NTSC (the TV standard). Sorry about that hahaha. And well, you know, PCMCIA (people can't memorize complicated industry acronyms)

Anyway, thanks for the tip, the game now works without issues! So long NTSC NTFS! I'll move all my games that run on Linux to my ext4 partition.