
Cookington
Published
Runs flawlessly out of the box, on par with Windows besides opening splash audio.
Crackling in the opening splash videos (probably due to Media Foundation?) only. No issues in-game otherwise.
Both the regular DX11 mode (with DXVK) and the DX12 mode (with VKD3D) run well on my setup, although DXVK runs significantly better at around 150~ FPS, while VKD3D generally ran around 100~ FPS or so. RTX features do not work at the moment on Proton Experimental or GE even if you have a supported card, so you're likely better off just playing the regular DX11 mode with DXVK for the sake of performance.
Works out of the box as if it was native
No performance issues during a singleplayer campaign with bots. Game is locked to 100FPS by default and my hardware had no troubles keeping that at all times.
Does not launch due to CEG DRM
Neither the DX11 or DX9 modes launch properly due to the usage of Valve's CEG DRM, which is still currently an open issue on their GitHub tracker for Proton.
Fixing mouse input, disabling VOIP, and setting engine config as read-only to work around known issues with the remaster that are identical on Windows
Works out of the box just fine, but several known problems on the Enhanced remaster include wonky mouse smoothing with uneven vertical sensitivity, co-op desyncing because of VOIP packets and framerate caps, and some graphics settings that reset on every restart because of a poorly made launcher (even if you disable it in the in-game settings). These same issues are all present on Windows and can be resolved with editing the game's config files. These fixes can be found on PCGamingWiki, and the location of the config files are under:
~/.local/share/Steam/steamapps/compatdata/729040/pfx/drive_c/users/steamuser/Documents/My Games/Borderlands Game of the Year/WillowGame/Config
To resolve some of the graphics settings resetting on every start (such as the texture filtering setting), you'll have to set WillowEngine.ini as read only once you have everything set the way you want.
Set WillowEngine.ini as read-only after setting graphics settings the way I wanted them to prevent a known issue with Enhanced that resets several video settings on every start.
If the in-game VSync option is enabled, combat can cause inconsistent framerate dips that do not happen if you disable it. Turn off VSync and use SteamOS's own framerate limiter.
If you run into strange framerate drops during combat or looking around in certain locations, disable the in-game VSync setting and use SteamOS's own framerate limiter.
You can still do config edits to resolve certain known issues with the Enhanced remaster as listed on PCGamingWiki, but they're less neccessary on Steam Deck since you won't be using a mouse. If you're playing co-op you'll still want to disable VOIP through the config to solve the desync issue, and setting WillowEngine.ini as read-only is recommended to stop the game from resetting several graphics settings on every start but not a requirement.
Runs flawlessly, uses OpenGL natively. On par with Windows.
Didn't have any issues whatsoever using Proton Experimental. Everything works as it should, identically to Windows (AMD GPU users might actually want to consider trying it out on Linux for better performance, thanks to better OpenGL drivers). Only thing that should be noted is that the game doesn't support Steam Cloud, so if you already have progress on Windows, you should backup the save folder.
Cannot reach 60FPS and constant random judders
Has a tendency to randomly crash, but also not always? Sometimes stable with no issues, no rhyme or reason to when this happens
Consistent stable performance is a requirement for rhythm games and at the moment, there's a massive issue with the game's framerate that will never reach 60FPS the moment you're at the menus and in-game. There's supposedly a WINE patch that fixes this that you can find on the Proton GitHub issue tracker, but requries making your own custom build of Proton specifically for this game to fix.
There's also a random chance of the game just crashing within a minute of the game being open on the new stable SteamOS 3.5, but this is also incredibly inconsistent. Earlier I was having the crashing issue, but upon trying to post a report comment to the issue tracker and getting logs for the game I didn't run into a single crash. Your mileage may vary.
If using Vulkan, game tends to crash after 15-20 minutes of playing. OpenGL is stable without issues.
At least on my setup, the Vulkan renderer seemed to cause more issues with stability and didn't really run much better than the default OpenGL mode. Very consistent 140-150 FPS at Ultra settings at 1440p on OpenGL, Vulkan seemed to hover around 120-130 when it wasn't suddenly crashing after a period of time.
Either lock at 30FPS or change the Render Scale to 2 at 60FPS to reduce battery usage.
Fully playable including inviting friends and all. The splash screen videos play but have crackling audio.
There's crackling only in the opening splash videos, the rest of the game is fine.
Some framerate drops for major explosions and with a large number of enemies on screen; not as perfectly smooth as Windows is
Has some GPU usage problems, hovering around 60-70% and only spiking up to 90-100% in load screens, but still runs fine enough to be playable around the 60-80FPS range. Windows runs around 120FPS on my setup. Proton-6.12-GE-1 runs significantly worse however and GPU usage was locked to 30-40%, wouldn't recommend using it just to fix the splash screen.
Crashes after loading data on all three games
The initial launcher menu works and settings can be changed, and starting up each of the three games initially works. However, after the "Loading data" screen, all three games crash to the desktop due to using the WMV codec.
Removing the Videos folders for each game doesn't solve the problem (each game uses these videos for both cutscenes as well as menus), and changing to Proton-6.16-GE-1 did not solve the problem.
Launcher does not work, cutscene videos require Proton-GE, and default settings leave the game at a low resolution.
The launcher does not work, which means you cannot change any graphical options on Linux; stuck with defaults
The game's launcher does not properly work on Proton and since there's no launch option to skip it (as far as I'm aware), you have to go to the game's files and rename "Drake.exe" to "drakeshell.exe" (either removing or renaming the actual drakeshell.exe).
You also need to use Proton-GE or another method of getting Media Foundation working so that cutscene videos are playable, otherwise they're stuck showing a color test screen until you skip it.
The game is playable after doing all of this, but you're stuck with whatever default video settings the game uses on PC. There might be some way of copying over a config file from Windows to fix this, but it's not something I've tested (or care really much to try and figure out for this game).
Flawless, on par with the current experience on Windows
Game runs identically to how it does on Windows, including some of the game's own current bugs and issues which are still thankfully fixable on Linux.
- If you dislike the game's default font, you can follow this guide to quickly fix it by just renaming a couple files in the game's folder.
- The game at this time does not remember your setting for fullscreen/windowed, and will always launch windowed. You can either just press Alt-Enter to fullscreen again, or go into the game's settings and set it again. This behavior is the same on Windows.
- The game locks to 60FPS and does not enforce any V-Sync which can result in screen tearing. While on Windows you can force V-Sync through your GPU control panel, you can force it on Linux by going to the game's install location and creating dxvk.conf in the base folder (next to FINAL FANTASY.exe).
- Inside dxvk.conf, add the following and save:
dxgi.maxFrameRate = 60
dxgi.tearFree = True
Prerendered intro videos don't play back properly; black screen with sound only
You should install the San Andreas Definitive Edition patch, which comes with a multitude of mods for fixing issues with the PC port, adding modern controller support (which worked fine on Linux with an Xbox Series X|S controller), restoring missing effects from the PS2 version, among other improvements.
If you install the Definitive Edition patch, you should add the following as a launch option in Steam to make sure the mods properly load:
WINEDLLOVERRIDES="bass,vorbisFile,vorbisHooked=n,b" %command%
One of the included mods will cap the framerate to 30 FPS by default, this is meant to avoid game breaking glitches for certain missions; even if you don't use this patch, you should cap the framerate through an environment variable (DXVK_FRAME_RATE=30 %command%) or with libstrangle.
Only problem of note is that the opening logos and intro videos do not play properly on any version of Proton right now. Proton Experimental (6.3-6 at time of writing) will skip the videos straight to the main menu on startup, while applying mf-install or using a custom version of Proton with Media Foundation fixes will play the audio for these videos on a black screen. This isn't game breaking, but at the moment can't be fixed.
Demo plays smoothly, only minor issue is not fully closing on exit
Wine stays open after the game quits, have to click Stop in Steam
Demo ran at locked 120FPS on max settings and worked just fine with my DualSense controller. Only weird issue I ran into was when exiting to the desktop, Wine is still running in the background and Steam believed I was still in-game until I clicked Stop in the library.
Identical to how it runs on Windows, with all issues included
Long freezes that make the game unplayable if you're not using offline mode on Steam; this behavior is the same on Windows and is the game's fault, not Linux/Proton
The freezing issues are not due to Proton, they are from the game's own constant server checks that do not connect anymore. This is identical behavior to Windows, and the only fix is launching Steam in Offline mode which forces the game into a demo mode. Testing this demo mode, the game is fully playable and ran smoothly in the DX11 mode with max settings (around 110~ FPS). Again, the freezing issues are not from Proton, they are from the game itself and has never been patched; this is the reason I'm saying the game is technically playable as it functions identically to Windows and doesn't have any new issues from running through Proton.
A handful of the game's UI fonts seem to scale incredibly low-res at the Deck's 800p resolution, but nothing that makes the game unplayable. Namely the charge number in the top left, and the titles when entering an area are lower resolution than what I saw on my desktop.
No performance issues whatsoever, you can even raise the cap up to 90 FPS if you want the camera to feel smoother at the cost of battery (around 14-15 watts). A small handful of the game's text seem to scale themselves incredibly low-res compared to other elements of the UI, but they're not super important either.
If you're a controller user, Linux isn't currently the way to go for this game
Refused to play nicely with my Xbox Series X|S controller; HUD prompts wouldn't show, and every startup the bindings would reset itself
While the game ran smoothly (besides some brief small frame drops for shader compiling), serious controller issues stopped me from playing the game through Proton on Linux. Controller HUD prompts straight up never worked no matter if I used Big Picture mode, Steam Input enabled and disabled; it would always show keyboard prompts. The game would also reset all controls (controller and keyboard) on startup after launching the game for a second time, and you will have to go into Settings every time to reset to defaults.
Native version also doesn't seem to work anymore, at least on Manjaro. A black window would open for several seconds and immediately close on itself, so Proton is currently the only way to get the game playable at the moment on Linux. If you do play on Linux, you should cap the framerate to a max of 120 as physics issues can occur if it goes any higher.
Vanilla game works out of the box, no issues
Everything works as expected running the game vanilla without mods on current Proton Experimental at the time of this report. The prerendered cutscenes in Separate Ways works without needing Proton-GE, and my saves from Windows were transferred without hassle from Steam Cloud. As long as you're not using the community HD texture mod, the game works fine.
If you want to use the community HD textures mod, it currently doesn't install properly on Linux. Wine seems to struggle with the parentheses in the install bat the mod uses, and doesn't rename/move the files properly. Trying to copy over the files manually didn't work either, because the game would just crash on loading a level. I wouldn't be surprised if I just copied stuff over incorrectly that the bat installer is supposed to deal with though.
Change to Proton 5.0 and launch the game once, quit, then run in a terminal:
protontricks 21690 -q wmp11
Then change to Proton-6.19-GE-2
Follow the customization steps above and also install bh5fixes to fully disable GFWL and get a few extra bugfixes and improvements from the Xbone/PS4 console remaster.
Installing wmp11 with protontricks is required at the moment, even if you're using Proton-GE; if you do not install it, the game will soft-lock itself in the intro videos and never progress to the main menu, forcing you to quit.
After all that setup, the game does work normally besides some brief stutters caused by DXVK shader generation; I'd recommend running the variable benchmark in the main menu to get a lot of the shaders generated before playing. My completed save from Windows transferred normally from Steam Cloud without any issues, and played both Mercenaries and replayed a chapter. Did not test the co-op but I can't see there being any issues either with splitscreen or online. Framerate generally hovered around 110 FPS.
Launch the game once with Proton 5.0, then in a terminal with protontricks installed, run:
protontricks 287290 -q wmp11
Then change back to Proton Experimental.
Installing wmp11 is required at the moment to get in-game and other forks like Proton-GE do not fix it, similar to other RE games. Without wmp11, pressing Start Game on the title screen will soft-lock you into a black screen that never loads the main menu.
After wmp11 is installed, the game ran smoothly at max settings for me, around 100 FPS on average in Raid mode. Connecting to RE.NET worked fine and event missions were available like normal. My save from Windows transferred fine from Steam Cloud with no problems. Played with an Xbox Series X|S controller which was detected properly without issues.
Missing intro/outro video
Game can potentially crash on certain sound effects playing unless using GE-Proton
The game plays well and stable as long as you're using a current version of GE-Proton. Regular Proton (both 8.0 and Experimental) currently don't play the intro and outro videos properly, and there's a chance that the game will just suddenly close on certain events/sounds playing like when a boss is defeated. Can't confirm if it's a codec issue and the issues on desktop Linux is even stranger when the game plays perfectly fine on a Steam Deck, but it's at least fixable.
Proton doesn't open due to CEG DRM, and Native crashes after intro
This is part of the list of games that don't work on Proton due to Valve's CEG DRM. You could potentially get it working if you use a cracked EXE, but that's out of the scope of this report and what any user should reasonably have to do to get it working.
Works well out of the box on Proton
A black bar was initially on the bottom of the screen from Gnome and Dash to Panel, and the gamma was set incorrectly; fixable by enabling Fullscreen and No Border in the Video Options
Should run about as well as it does on Windows as the game natively uses OpenGL. If you have issues with fullscreen mode with either a part of the screen being cut off or the colors/gamma being wrong, enable "No Border" in the Video Options.
Runs smoothly on a Quest 3 via ALVR, no issues
Played smoothly with maxed out settings at ALVR's High resolution. Keep the graphics API at DirectX 11 because DXVK is more stable than the game's own Vulkan renderer; a lot of the Serious Engine 3 games worked better with DX11 in general until Serious Sam 4 was made.
Installed dotnetdesktop7 for SA Mod Manager
Vanilla game works fine, but the game is best played with mods if you're willing to tinker. Install the SA Mod Manager to the game's install directory or the mod loader will not load correctly on startup. Make sure you install dotnetdesktop7 as SA Mod Manager relies on it.
If you're modding the game, also make sure that you change from Borderless Windowed to Fullscreen in SA Mod Manager or you will encounter strange performance issues. There seems to be some kind of problem with GPU utilization if the game isn't running with exclusive Fullscreen. If you want anti-aliasing, make a DXVK config forcing MSAA.
WINEDLLOVERRIDES="d3d8=n,b" %command%
Installed 'dotnetdesktop7' for SA Mod Manager
Stock game works fine, but you really should play this using the SADX Mod Installer to restore the original Dreamcast assets and fix a huge number of issues with the PC version of the game. Before running the mod installer with a tool like Protontricks, use Protontricks to install dotnetdesktop7 so the included mod manager opens correctly.
If you're playing on a Steam Deck OLED, change the framerate cap to 60 FPS for proper smooth frame-pacing.
Performance is on par with Windows and is fully playable, but only if you're using keyboard or a controller
Mouse input would cause massive stutters and lag
Any mouse cursor movement would cause significant stutters and lag, making the game unplayable if you are not using keyboard or a controller.
Works wonderfully if you're playing with keyboard or a controller, but any mouse movements cause the framerate to nosedive and stutter making the game unplayable.
Works perfectly out of the box, runs better than Windows
Expect a lot of stuttering/freezing when first playing due to shader cache generation, especially in the Plaza. Eventually settles and disappears after a bit of playtime.
Noticeably runs better for me than it does on Windows 10 for my setup, especially in the Plaza. It does take a bit for the shader cache to generate so expect stuttering initially; it goes away fairly quickly after a few minutes. Areas like the Arcade which normally drop my laptop down to 20-30 FPS on Windows, run at 40-50 FPS through Proton. Videos on the in-game media players work fine, you can join all servers normally, and even controller support for some of the minigames works flawlessly.
Runs flawlessly with no issues, on par with playing on Windows. Even the opening splash plays properly without workarounds.
This could be an issue with the game itself and Steam Cloud, but weirdly despite remembering my level completions and what weapons I had unlocked from my Windows playthrough, all of the arms I unlocked were missing? Didn't take very long to unlock again but strange regardless.
Works perfectly with zero tweaking, no issues.
Co-op Exterminatus mode worked fine with a friend, no issues.
Dynamic resolution scaling does not seem to work as intended, no actual resolution scaling seems to trigger.
Changing any resolution that wasn't monitor native in Fullscreen creates visual artifacts.
Handful of crashes, one of which froze my entire system and forced me to reboot.
You must disable the Steam overlay in the game's Properties or the game will always crash. After the first hotfix update, MangoHud also started causing similar crashes. The game doesn't seem to like any overlays hooking into it period as of right now.
The whole game is playable but there's definitely stability issues and problems that may be due to the game or Proton or possibly both. The Steam overlay must be disabled to actually play and MangoHud also causes the game to crash now after the first hotfix update, so there's something very wrong with how the game handles overlays in general. Every time you quit the game it takes a while to actually close and you will always receive a crash error afterwards.
SteamDeck=1 VKD3D_CONFIG=no_upload_hvv %command%
Upwards of a 45% performance decrease compared to native Windows due to a GPU utilization issue. no_upload_hvv/disabling Resizable BAR only partially helps performance. Resolution upscaling makes no difference due to this problem.
Game does not exit cleanly; takes an extra minute or two to fully close and typically with a Wine crash.
Besides needing the SteamDeck variable to solve the anti-cheat/online login issue, performance is almost half of what it should be compared to playing natively on Windows. This has been an issue since the game launched, and there is very little you can do to make the game run better as of right now because the issue is tied to GPU utilization. More info can be found on my GitHub post on Proton's issue tracker.
Works fine out of the box on Proton
Intro video doesn't play; Media Foundation needed
Runs fine for a short free little UE4 game. Only minor issue I ran into is that the intro logo video doesn't play properly on vanilla Proton as it uses Media Foundation; shows a placeholder test video that stops quickly. You can either use mf-install or change to Proton-GE to get it working.