powergfx
Published
You need to rename Borderlands2.exe to Launcher.exe OR install dotnet40 using protontricks.
with HD texture pack Just install it and do the thing above. Just runs, but the performance goes down to about 25 fps in critical areas.
great performance using d9vk Here you need to disable the HD texture pack or you run into the "out of video memory" bug. And DO NOT use PROTON_NO_ESYNC=1, this basically negates the performance of d9vk. Also using Mesa 19.3 or 20.0 with ACO enabled gives some more fps.
Renamed Borderlands2.exe to Launcher.exe.
The game sometimes forgets the selected resolution.
Well, PhysX will never work on Linux ...
taskset -c 0-7 %command% -window-mode exclusive
Since the version 34.02 update the game has some serious FPS issues. You need to limit the cores count to 8 or less, or you end up having less than 10 fps in outside areas. After limiting the core count the game runs fine again.
The Proton version doesn't really matter, it is important the game does not use more than 8 cores.
taskset -c 0-7 %command% -window-mode exclusive
Since the version 34.02 update the game has some serious FPS issues. You need to limit the cores count to 8 or less, or you end up having less than 10 fps in outside areas. This is actually an Unity engine memory allocator issue.
If the effect of core count limiting wears off after playing some minutes you very likely ran into low-memory issues. To fight this you have to modify the file "Shadows of Doubt_Data/boot.config" and increase the memory pools to values actually used in the Unity editor itself: memorysetup-bucket-allocator-block-size=8388608 memorysetup-bucket-allocator-block-count=8 memorysetup-temp-allocator-size-preload-manager=33554432
Doesn't support ultra-wide resolution, sticks to a smaller width.
Latest Proton doesn't seem to work. Starts but hitting start in the menu results in a CTD.
RADV_DEBUG=nohiz,zerovram taskset -c 0-7 %command%
Current version 5.10 of the game shows some graphical glitches on very distant objects, which gets worse if a wide-screen resolution is used. Not sure if this is a game or MESA issue, but with the RADV_DEBUG=nohiz MESA option this problem is solved.
