Tyfuzzle
Published
Broken EA App overlay
Tried many different proton versions, deleting the prefix between changes, and on my Deck and desktop.
Broken overlay meant my friends list on the EA overlay was always errored, so I couldn't join or invite anyone. Tried various versions of proton and GE and both on my Steam Deck and desktop to no avail. Running the EA App separately in bottles had a functioning friends list, so not sure what the problem is.
Problems with trashy EA App not ever working
Tried various Proton versions, between Steam's Proton and GE
Could not join a friend's game or my own because the EA App would alway error out on the friends list. Completely unplayable.
Various Proton version between Steam's Proton and GE
Could not join a friend's game or my own because the EA App would alway error out on the friends list. Completely unplayable. Issues experienced both on my desktop running Void Linux and my Steam Deck.
Black screen on startup after a couple of spash screens
Can't even get to the main menu. Initially I could, but now after a week-ish, the game shows a couple of splash screens and then freezes on a black screen. Don't know if it's an EAC problem or just the game itself. Tried different proton versions, clearing the prefix etc. Nothing works. Not worth the time to debug.
6.5-GE-2 GloriousEggroll
GloriousEggroll 6.5-GE-2
I was getting about 40 to 50 FPS where my friends were getting 70 to 90.
In the main menus, the cursor couldn't reach the bottom or the top of the screen. This might be to do with ultrawide compatibility as the game has none.
Occasional stuttering but frame rates are mostly in the 70s to 80s
Constantly kicked due to easy anti-cheat
Tried different proton versions. Always kicked by EAC.
mangohud gamemoderun PULSE_LATENCY_MSEC=100 %command%
Consistent slight crackling
Video playback stuttered and froze in places
EAC errors about unknown file version
No amount of tinkering I did could get EAC to work consistently. If I did manage to get it working, it would break the next week. It got to a point where no amount of deleting the prefix, reinstalling the EAC runtime, verifying files, deleting B4B's EAC files and verifying would get it working again.
GCONV_PATH="/usr/lib/gconv" mangohud gamemoderun PULSE_LATENCY_MSEC=100 %command%
EAC file version errors. Void Linux currently has an issue with some EAC games resulting in EAC not working. The fix is the first part of my launch options, which worked for a session and then it went back to breaking with unknown file version EAC errors the next week.
EAC bad
PULSE_LATENCY_MSEC=100 %command%
Slight stuttering about every second
Will try again next week. Don't trust EAC to not give more more file version errors in this game.
EAC broken again
PULSE_LATENCY_MSEC=100 %command%
EAC in this game is flaky as hell and I'm done with it. At first, it might work, but after a couple of weeks, it always spews errors about unknown file versions. No matter what I try, I cannot get it to work. Reinstalling, deleting the prefix, verifying game files, deleting EAC game files and verifying etc. I even changed distros hoping for better anti-cheat compatibility. This game is a dumpster fire in more ways than 1.
protontricks 35140 d3dcompiler_43 d3dx9 d3dx9_43 mfc80 vcrun2005
Does not work without additional dependencies
mangohud
Mangohud for hardware usage stats and specific frame limiting
Some bugs that might put a new player off. Otherwise, it runs really well, possibly better than on windows.
I used the following launch options:
strangle 112 PROTON_LOG=1 __GL_THREADED_OPTIMIZATIONS=1 PROTON_USE_D9VK=1 %command% -nomoviestartup
During Marcus's story intro cutscene, the audio was stretched out and had lowered pitch. Otherwise, the audio was fine.
Some cell shading didn't seem to render correctly resulting in some shaking just looking like either spaced out lines or dots. There were also some objects that looked like they permanently had shadows rendered on them such as portions of the metal center thing in sanctuary.
At first, full screen was enabled in game but was actually running in fake fullscreen. Changing to to fullscreen windowed back to fullscreen fixed that.
NPC intro scenes sometimes didn't play. Not an issue for me since I've seen them a million times at this point but might detract from the experience for a new player.
The load times were practically unnoticeable in Linux (less than a second) compared to windows which would take half a minute or so on my SSD.
During combat, the game would be incredibly stuttery with framerates dipping down into the low 10s, with framerates between 80 and 110 outside of combat (with libstrangle, a framerate limiter). I also had occasional crashes. I used the specified launch option and set physx to low in the video settings of the game to fix both:
strangle 112 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 %command%
libstrangle isn't used to fix anything. It's just to make sure I'm not going above my monitor's GSync range.
5.9-GE-5-SE GloriousEggroll
strangle 112 %command% -NoStartupMovies
Although the game stutters anyway under windows, the stuttering was far worse under linux, making me feel to nauseous to play for any length of time.
6.1-GE-2 (GloriousEggroll) GloriousEggroll
Proton 6.1 GloriousEggroll was used for media foundation fixes.
Alt-tabbing on startup can break the game, forcing you to reload it.
Slight input delay on the mouse made aiming difficult.
Harder stuttering than on windows in places. Also some slowdowns that lead to crashes.
In the 3 attempts I made on different versions of Proton GE, I got 3 crashes. 2 of which which were following major slowdowns, the third on 6.1-GE was during a loading screen after the tutorial boss, Shiv.
Launch options: strangle 112 PROTON_NO_ESYNC=1 DXVK_ASYNC=1 %command% -NoStartupMovies -notexturestreaming
Proton-5.21-GE-1 (Glorious Eggroll) GloriousEggroll
The launcher doesn't work so you have to rename the launcher and link the game executable to the launcher's original name:
cd {game_dir}/Binaries/Win64(go to game's binaries directory)mv Launcher.exe Launcher.exe.bak(rename launcher to backup name)ln -s BorderlandsGOTY.exe Launcher.exe(create a hard link between the game binary and the launcher's original name)
The game would launch in borderless windowed even though it was configured to run fullscreen. You can just use alt + enter to swap between fullscreen and borderless.
The game would constantly output in what felt like 1024x768. Usually it would launch with the screen centred and unstretched. If I then changed to fullscreen in the display settings, it would stretch the image even though it was set to output at my monitor's native resolution. To fix this, I had to:
- Go to the game's compatdata
drive_c/users/steamuser/My Documents/My Games/Borderlands Game of the Year/WillowGame/Config - Edit
WillowEngine.iniso thatResXandResYunder the[SystemSettings]section matched my native resolution.
So far, I've only configured the game to run as it would under windows, loaded into a previous save and ran around for a minute or so. Seems stable so far.
Works great out of the box
Some rare minor stuttering from shader caching, but runs great otherwise at high frame rates consistently.
Works great out of the box
A post processing filter is not aligned to the screen throughout the whole session. This might be to do with lack of ultrawide support.
Works relatively well. Crashed once in about 3 hours. Odd mouse behaviour.
Odd mouse behaviour, reduced when FPS capped to 60.
Due to odd mouse behaviour, I would recommend using a controller if you cannot be bothered to tinker. This can be mitigated slightly by capping the framerate to 60, but it's still a bit of a problem.
Various proton versions between Steam's Proton and GE
Crashes when loading the 4th level, no matter what proton version I use and even after verifying game files
mangohud %command% --launcher-skip
Modified the exe to force the game to display keyboard icons rather than controller icons:
echo '2C45C6: EB' | xxd -r - Cyberpunk2077.exe
Also modified some keyboard bindings that the restricts (cannot reassign scroll up or down for example) in compatdata/1091500/pfx/drive_c/users/steamuser/AppData/Local/CD Projekt Red/Cyberpunk 2077/UserSettings.json.
Nvidia users currently have frequent crashing seemingly caused by the driver. See this nvidia forum thread for details and updates. Some user trail and error has suggested that driver 510 is the latest that doesn't have the crashes but doesn't support DLSS (details on that here in the protondb thread.
Could be playable if the nvidia driver is downgraded. This is more effort than it's worth on my distro.
Stale configs from a year ago caused startup issues. Fixed by disabling steam cloud saves and deleting the prefix.
%command% --launcher-skip
I was getting stuck on the first frame of the first startup video. I think there was a problematic graphics setting from the last time I tried to play the game over a year ago and steam cloud saves kept restoring the config files after clearing the prefix. I had to disable steam cloud saves to stop it doing it, so I could start the game from a clean slate. After starting over with fresh game settings, changing a few and playing for a while, I turned cloud saves back on and resolved the conflics by selecting the local option every time.
Some flickering/texture issues here and there.
Custom key bindings would reset. I think this is an issue with the game itself rather than linux. I think my bindings have stabilised now after making sure every action had a binding.
Stuttering when the GPU was maxed out. Ended up setting a framerate cap below what the max would be to give it some headroom, which reduced the stuttering somewhat.
Kinda biased report here, but I couldn't launch the game without tinkering seemingly because of some stale configs.
Works perfectly out of the box
Using a PS4 controller through steam play worked great as well.
Sometimes on startup, the game would freeze straight away on a white screen before all the dev splashcreens.
Disabled network connection at the OS level improved performance
Incorrect reflection rendering (non-raytraced)
Reduced perfomance when my network connection was enabled.
mangohud %command%
Mangohud for hardware usage stats and granular frame caps
dhewm3 +set fs_basepath /mnt/ssd1/SteamLibrary/steamapps/common/Doom\ 3/ +set r_customWidth 3440 +set r_customHeight 1440 +set r_fullscreenDesktop 0 +set r_mode -1 # %command%
Dhewm3 source port. It has a linux native build so technically, you're running the game natively without proton or wine. Some distros have it in their repositories (mine did), so you might be able to install it through your package manager. The main reason for using it was for better resolutions. Doom 3 is an old game with a lack for support of modern resolutions, so it's basically required. Once installed, you just need to either copy the game's pak files to where doom expects them or point it to where Steam installed them to.
+set fs_basepath /mnt/ssd1/SteamLibrary/steamapps/common/Doom\ 3/
is to point it to where the game files are.+set r_customWidth 3440 +set r_customHeight 1440 +set r_fullscreenDesktop 0 +set r_mode -1
configures fullscreen to borderless and my custom resolution. The last bit is to enable custom resolutions.
The most important part is this:# %command%
The # basically just comments (disables) out the part of the command that steam inserts that triggers proton. Since dhewm3 has a native port, we just need to disable it. This has the added side effect of disabling the steam overlay, even if you have it enabled. Alternatively, you can just run dhewm3 from your terminal. You just won't get playtime tracking.
Game freezes on alt-tab
Some alt-tab issues as mentioned before. If you're having audio issues after a recent update to DRG, switch to proton 5.13-1. That fixed it for me.
Works well enough as long as you restart between games to avoid loss of progress if you're playing single player
Alt-tab would cause a freeze forcing me to kill the game or just crash.
Crashes some time between 1 and 2 hours of playtime. Enough time for more than 1 mission. I suggested restarting between missions. If you're playing multiplayer, do not be the host as this will end your game. You can rejoin as a client and continue your progress. If you play single player, the game will not remember your progress.
Alt-tabbing may freeze the game (although I haven't experienced this since using 5.13-5).
Game doesn't start properly
Game starts with either a black screen, odd green and yellow scan lines, or nothing at all. Might be an Nvidia drivers thing. Doesn't matter what proton version I use or whether I use GE.
Works well enough out of the box
Occasional stutters consistent throughout the 2 hour session uncharacteristic of compiling shaders.
Works well with no tinkering, with some stuttering
Some stuttering, more common when in the flying saucer, seems to be due to loading world assets as you move around. The last mission of the game seems especially bad/noticeable because of how much you move around for the last boss fight.
Runs native by default. Switched to proton to force the windows build as native wasn't recognising my external controller.
Mightve been FSR 2, but there was some flickering every now and then.
Resolution limited to 1080p
I believe this is more of a problem with the port than proton. Basically the game won't go higher than 1080p (or 1920x1200, 16:10). Apparently there's a way of getting higher resolutions using the special k mod, but I couldn't be bothered to work out how to do it, according to the PC Gaming Wiki page for the game. Apparently the port has other problems like no VSync.
mangohud
Mangohud for hardware usage stats and more granular frame caps
Seemed fine in the short time I tried it. I will submit another report when I get a larger session in.
Proton-5.9-GE-5-ST GloriousEggroll GloriousEggroll
Proton-5.9-GE-5-ST
Fillscreen would cause the game to come in and out of focus for a split second occasionally. Fake fullscreen stops this but stops G-SYNC from working.
I used PROTON_NO_ESYNC=1. Apparently this stops random lock-ups and freezes.
Proton-5.9-GE-5-ST GloriousEggroll
GloriousEggroll 5.9
Very occasional when starting the game. Not noticeable after loading into a game.
Crashed once in the main menu when sitting there for a while. None in-game so far after disabling ESync.
I had to do some manual tinkering with files:
1- Start the game from steam after install and let it perform the first time setup stuff. The game will fail to start after that.
2- cd to the game directory and run the following command:
mv ./bin ./bin.bak && ln -s DefEd/bin bin && cd bin && mv ./SupportTool.exe ./SupportTool.bak && ln -s EoCApp.exe SupportTool.exe
After doing this, the game should run through Steam.
Works great out of the box. Has a launcher but no workaround is required as it works fine.
Lighting flickering issues on the character model on the stats window. Very minor. Doesn't impact gameplay.
6.18-GE-2 GloriousEggroll
GloriousEggroll 6.18-GE-2
Occasional pop-in/out of models in the middle of the camera view. Pretty rare. Not sure if it occurs under windows.
During dialogue or tutorial screens, sometimes the game would ignore inputs for between a few seconds and half a minute. Not sure if this occurs under windows.
With my default proton version (6.3-7), cutscenes would not play and there was no audio. With proton GE, cutscenes played fine and audio worked.
On a 4K TV, the game runs perfectly fine, but some text does not scale with the UI scaling options and is too small to read.
5.21-GE-1 GloriousEggroll
- Glorious Eggroll 5.21-GE-1
- strangle frame limiter
mangohud %command%
lower than expected framerate, but that might be more to do with the game than proton
strangle 112 %command% to limit the frame rate. In-game settings aren't granular enough.
Mouse would be viewable for the whole session after the first time it becomes visible after being invisible.
Somewhat frequent (once every 45 ish minutes) unreported disconnects during the "qualified" screen that also wouldn't let me quit the session or the game. Had to alt F4 to exit the game and it sometimes removed my friends from the game if they had also qualified. Might have something to do with playing in a party.
I'd say this is enjoyable for me regardless of the disconnects as the gameplay loop is relatively short so jumping back in is quick and you don't lose much from it. I'm also playing with friends and am not too bothered about winning so the impact is minimal for me. The disconnects may be bothersome to other people especially if you play solo.
Because of the disconnect issue, you will be missing out on one in every 3 ish games due to disconnects.
Proton-5.9-GE-5-ST GloriousEggroll
Proton-5.9-GE-5-ST
Cursor visible when it's not supposed to be.
Somewhat frequent (once every 45 ish minutes) unreported disconnects during the "qualified" screen that also wouldn't let me quit the session or the game. Had to alt F4 to exit the game and it sometimes removed my friends from the game if they had also qualified. Might have something to do with playing in a party. Does the same with default proton.
I'd say this is enjoyable for me regardless of the disconnects as the gameplay loop is relatively short so jumping back in is quick and you don't lose much from it. I'm also playing with friends and am not too bothered about winning so the impact is minimal for me. The disconnects may be bothersome to other people especially if you play solo.
Mouse would appear on screen after first "unlock"
Somewhat frequent (once every 45 ish minutes) unreported disconnects during the "qualified" screen that also wouldn't let me quit the session or the game. Had to alt F4 to exit the game and it sometimes removed my friends from the game if they had also qualified. Might have something to do with playing in a party.
I'd say this is enjoyable for me regardless of the disconnects as the gameplay loop is relatively short so jumping back in is quick and you don't lose much from it. I'm also playing with friends and am not too bothered about winning so the impact is minimal for me. The disconnects will be bothersome to other people especially if you play solo. Also, normal (not on the qualified screen) disconnects seem to happen when you ping goes above 150ms which is relatively low but nothing to do with linux, rather the servers themselves.
Borked by EAC
EAC was added in the last update. You can load up the main menu but you can't queue up because EAC doesn't initialise.
Mouse wasn't hidden after the first time the game shows it. Apparently you can fix it with winetricks but I haven't found the solution.
The game runs so poorly that I couldn't stand playing it for more than 15 minutes after character creation before refunding it.
6.5-GE-2 GloriousEggroll GloriousEggroll
GloriousEggroll
Along with delayed inputs, where a cursor was visible in menus, the cursor would become desynced from where it's actually pointing.
Performance after the character creation screen was around 10 to 25 FPS with long and frequent stutters and inconsistent frametimes.
Your mileage may vary, but for my 2070 super and R5 1600, performance was unacceptable, even after disabling VSYNC in the game's INI file, which is a commonly accepted fix for poor performance.
Cannot get past Ubisoft Connect, doesn't render and isn't clickable
mangohud
Ubisoft Connect shows up as a transparent window with a visible border, but I cannot click it at all. Clicks go through it to the window behind. I've tried a few proton versions including older ones and ProtonGE. None make a difference.
Near perfect. Only issue was some slight hitching every few minutes. Nothing that impacted the experience on the whole though.
5.9-GE-5-ST (Glorious Eggroll) GloriousEggroll
Some settings such as key binding would reset between sessions, but only a subset of all input settings. Sometimes it would just be mouse sensitivity, other times it would be just key bindings. Not a huge issue as there aren't many settings and bindings but still annoying.
Framerate isn't great but that doesn't matter much for this kind of game
In game, I was getting about 35~ FPS. Not sure if this is any better on windows. Also, load times felt a little high for a game like this.
Occasionally would have issues with X server causing a freeze during the initial load screen. Restarting my computer (which restarted X server) fixed it. My X server instance may have just gotten into a bad state.
Works well enough as long as you're not the host. Possibly not stable enough for single player.
Framerate ranged from low 30s to high 50s during scenarios.
1 crash in a 2 hour session. The game slowly ground my system to a halt. Had to restart as nothing was responding.
Somewhat lower framerates than expected, around the 45 mark, sometimes achieving higher or lower. Some, pretty big stutters between rounds, but playable.
Playable. Take that with a grain of salt though.
If a controller is plugged in when the game starts, you cannot use KB+M until you restart the game, even if you disconnect the controller.
Framerates jumped all over the place between 20 ish to 50 ish FPS. Sometimes, I would get drops as low as 10 FPS.
Although there are performance issues, this isn't a twitch shooter, it's turn-based, so lower framerates are less of an issue. I experiences crashes on a very infrequent basis. Maybe 3/4 in the 146 hours I have. There are occasional buggy situations but I'm pretty sure they're down to the game being in early access.
Works well enough for the type of game it is
Poor framerate, but not sure if that's due to proton or the game
Worked well out of the box. Could not decline data collection & selling though
Unable to decline data collection/selling. The button seemingly either only opens a browser tab to the WB's data collection policy or doesn't work. The rest of the game works fine though. Only tried single player.
Initially I experienced some issues around Alt-Tabbing where the game wouldn't return to full screen when tabbing back in which could be fixed by going into the graphics settings, setting the window mode to windowed or borderless and then back to fullscreen. This was rather difficult as the mouse would be off relative to where the mouse would've been had the game still been in fullscreen. I don't have that issue anymore though. Not sure what fixed it.
Issue described in the fullscreen notes
Latest update breaks the game. No longer launches
The patch notes mention some preliminary anti-cheat function so might be an anti-cheat problem.
As of the patch on 25/09/2020, the game works almost flawlessly again
I experienced some issues around Alt-Tabbing where the game wouldn't return to full screen when tabbing back in which could be fixed by going into the graphics settings, setting the window mode to windowed or borderless and then back to fullscreen. This was rather difficult as the mouse would be off relative to where the mouse would've been had the game still been in fullscreen.
Excerpt from the patch notes: "...we have fixed the issue where players using Linux could not launch the game with Proton"
Almost flawless. Runs great
I experienced some issues around Alt-Tabbing where the game wouldn't return to full screen when tabbing back in which could be fixed by going into the graphics settings, setting the window mode to windowed or borderless and then back to fullscreen. This was rather difficult as the mouse would be off relative to where the mouse would've been had the game still been in fullscreen.
Detailed in the windowing/fullscreen problems
PULSE_LATENCY_MSEC=85 %command%
Fixed with launch argument added. Experienced on both Pulse and Pipewire
EAC unknown file version errors
EAC unknown file version errors, meaning multiplayer and xbox-pc cross platform didn't work
EAC unknown file version errors. Multiplayer wouldn't work crossplatform because of EAC errors. Disabling EAC renders crossplay broken.
Works fine if you're playing solo or with other PC player in campaign only. Crossplay and multiplayer will not work due to a broken EAC implementation.
6.20-GE-1 GloriousEggroll
Proton Fork: 6.20-GE-1 GloriousEggroll
Launch Options: strangle 112 %command%
Proton GE is required for the video cutscenes
strangle frame limiter
Tabbing in and out would sometimes cause the game to lose the mouse. Tabbing out and back in would fix this.
Works pretty well out of the box bar some stuttering and minor mouse issues
Loss of mouse tracking when the game stuttered, which was rare.
Slight stuttering towards the end which affected mouse accuracy
Occasional disconnects in loading screens during co-op sessions but great otherwise
mangohud %command%
Lots of stuttering, although this might be consistent with the windows version, based on some other steam reviews which also mentioned lots of stuttering.
Marked positive, because I could see people putting up with the level of stuttering I experienced and still having fun with it.
Mangohud for granular frame limiting.
Works well out of the box. Alt-tab'ing breaks the game though.
Alt-tab'ing freezes the game window and requires a force close. xkill would not properly kill it. I needed to do so in steam by pressing the "stop" button.
Slight stuttering here and there (possibly from shader compilation)
Weird problems with some controls where the triggers weren't mapped properly, but it couldn't be fixed as the problem seemed to be with the game mapping multiple controls to a single button. Ended up switching to KB+M. I imagine it could be fixed if you configured steam input to map gamepad buttons to key presses.
Regular stuttering. Still playable, but far from the smoothest experience.
I wouldn't recommend this if you want to play this with an external controller as there are significant problems with mappings. I never tested handheld, so it might not be a problem there. I ended up just playing with a keyboard and mouse and docked.
Runs great out of the box, no tinkering
The game currently doesn't scale to ultrawide, but that's a game problem, not proton's fault.
Play in fullscreen if you can to avoid rendering and cursor bounding issues.
After an hour or 2 of playing in windowed mode, about 2/3 of the middle of the window would stop rendering so you could only see the edges. Only restarting the game would fix it. You can save anywhere so this isn't a huge issue, but annoying nonetheless.
Graphical issues in windowed mode mentioned before.
Cursor was not locked to the window in windowed mode.
Don't play in windowed mode if you can avoid it. Otherwise works fine.
In windowed mode, after an hour or 2, 2/3 of the middle of the screen would freeze and stop rendering. The edges would continue rendering. This was fixed by restarting the game and isn't much of an issue because you can save almost any time by holding e.
Rendering issues mentioned before.
In windowed mode, the mouse wasn't bound to the window, so it's quite easy to click outside the window, where the game will continue running and you will die due to loss of input.
Run the game to get proton to create the prefix. Run this to fix the black screen intro and exit:
protontricks 559620 cnc_ddraw
Download nglide wrapper and extract it:
cd ~/Downloads/
7z x ./nGlide210_setup.exe
Copy the extracted DLLs and nglide_config.exe to the game location and overwrite the originals:
mv -f ./*.dll /mnt/hdd2/Steam/steamapps/common/Outlaws/
mv -f ./nglide_config.exe /mnt/hdd2/Steam/steamapps/common/Outlaws/
Run nglide_config.exe:
WINEPREFIX=/mnt/hdd2/Steam/steamapps/compatdata/559620/pfx/ wine /mnt/hdd2/Steam/steamapps/common/Outlaws/nglide_config.exe
Set your desired resolution and Video backend to Vulkan to fix the mission cutscenes. Then apply and exit.
To fix the music, run the following:
protontricks 559620 --gui
then select run winecfg and navigate to the Libraries tab, input winmm in the New override box, press Add, then Apply.
6.1-GE-2 (Glorious Eggroll) GloriousEggroll
I wanted to use mods which requires winhttp to be installed using proton tricks.
Proton-6.1-GE-2 (GloriousEggroll) was used to boot the game. Intro videos ran with this fork. I'm not sure about the cutscenes post-menu, as I didn't go past the main menu.
Alt tabbing would make the game go into windowed mode. Using alt+enter would trigger the game to go back in full screen.
I've only booted into the menus so far, just to get the game running and install mods, so take this report with a grain of salt. I'm only filing this to show how to get mods working and to report my resolution issue and fix.
Mods using BepInEx need some additional tinkering. Follow this guild here for the required configuration.
WINEDLLOVERRIDES="dinput8=n,b" %command%
Various change for installing the Reloaded II mod manager. Steam guide for installing it on Deck here.
I set up the game with mods to fix this mess of a port, mostly to fix the incredibly poor audio quality (somehow they made PSP-quality audio worse). The game works fine without any tinkering though if you can't be bothered.
Stuttering when in windowed mode and whilst in full screen, there's a slight stutter when the dialogue for an all out attack appears.
The game would register keyboard and mouse inputs when the steam overlay was active
Out of the box the game would hang on a black screen after an initial loading screen where the intro video is played. To fix this, like others have suggested, run the following protontricks command:
protontricks 1113000 wmp9 quartz devenum
You can find protontricks here: https://github.com/Matoking/protontricks
Protontricks requires winetricks, which can be found here: https://github.com/Winetricks/winetricks
Stuttering when in windowed mode.
After playing for a while, some areas experienced slowdowns from 110+ FPS to just north of 70 FPS. Some dungeons showed drops to around 60 FPS.
Out of the box the game would hang on a black screen after an initial loading screen where the intro video is played. To fix this, like others have suggested, run the following protontricks command:
protontricks 1113000 wmp9 quartz devenum
You can find protontricks here:
https://github.com/Matoking/protontricks
Protontricks requires winetricks, which can be found here:
https://github.com/Winetricks/winetricks
Made right trackpad a mouse to make it easier to interact with network disconnect dialogue when docked with an external display.
Sometimes when there were network blips (or after waking from sleep), a popup would show saying the game has disconnected and I'd have to either use the touch screen or trackpad to dismiss it. You can reconnect in the game's settings menu.
GST_PLUGIN_FEATURE_RANK=protonaudioconverterbin:NONE %command%
Seems to work okay with GE 8-23 but any other Proton version, GE or default, results in a black screen. Controller doesn't seem to work, but other reports mentioned it does on GE 9, which I confirm because of the black screen issue. Default control scheme for keyboard is pretty bad and button promps/icons seem to ignore the mouse controls. Mouse sensitivity controls are bad too.
mangohud %command%
Poor performance makes for a poor experience
Lots of drops below 30 FPS. Not sure what the performance is like on Windows but I found it incredibly distracting and a poor experience.
Works nice out of the box with some slight stuttering
Slight stuttering here and there. FPS peaked at about 62fps at 1440p ultrawide with dips down into the 30s.
If you can put up with the occasional stutters, it's an enjoyable game
The game would come out of full screen between missions and when alt-tabbing and then behave as if it were but would only show the top left quarter. I had to play in windowed mode. Sometimes I could fix it but it would break it self again shortly after so just stuck with windowed mode.
Long stutters occasionally. Not sure if that's how the game runs under windows.
Used GameMode with it for better performance: https://github.com/FeralInteractive/gamemode
Works great with some minor tearing issues
V-sync doesn't work and the frame limited wouldn't work, so I got tearing
Mostly works if you can push through the early crashes when joining a lobby
When attempting to join a co-op lobby, the game would sometimes (more often than not) crash. Once I was loaded into a lobby, the game worked fine.
If I wanted a longer session, I would drop the screen's refresh rate to 30-40Hz.
Can be played at up to 60 FPS. Around 2 hours battery life if playing at 60FPS (on a 2.5YO Deck).
(Reported experimental version: Proton Experimental as of 2021/04/29)
Strangle frame limiter
Rare stuttering (not sure if present under Windows)
Occasionally, between transitions, the game would just show a black screen, but alt-tabbing out and back in would nudge the game along. Also, between some transitions and prior to the main menu, I would get some odd screen with colour samples (I assume) covering the top of the screen. Neither of these are game breaking but worth mentioning, none the less.
Sometimes the game would have periods where it would freeze and lock up my system for a few mins frequently. Didn't really matter what proton version I was using between vanilla, GE, 8, 9, experimental etc. and deleting the prefix between changes. Eventually, the game would just decide to stop crashing, but it would always happen in waves. I'd recommend getting used to quick saving frequently, especially between scene transitions, i.e. from location to location, overworld to fight or vice versa. This is typically when the game would have issues.
Can work well enough if you know going into it you'll have to tinker every now and then to get it to stop crashing. Initially, it worked fine, but it started to have waves of freezing, so I started changing proton versions and deleting the prefix until it stopped. Next session on that proton version might be fine. It might also decide that it doesn't like that proton version anymore. Not sure proton versions were making much of a difference compared to deleting the prefix and going through first time setup again. If you decide to do this, make sure you have cloud saves enabled before deleting a prefix, otherwise you'll lose your save data.
Proton-5.21-GE-1 GloriousEggroll
Slight stuttering every 20 seconds or so but that might be present under windows too.
With basic proton, some of the main menu screens would not be rendered or would be invisible. GE fixes that.
Runs native by default which seems to have not been updated. Game's launcher is missing graphics options and many newer resolutions. I forced proton 9 to make it run the windows version which allowed me to choose my monitor's resolution of 3440x1440 (21:9 ultrawide).
I've put no due to the missing resolution options, but it seemed perform okay with a lower resolution selected and windowed mode.
Works well out of the box
Some slight stuttering in areas and a slight drop in FPS overall but fine otherwise
Alt-tabing would make the game go windowed. Borderless fullscreen wouldn't see this issue.
Also used mangohud for granular frame caps
Proton-5.9-GE-5-ST GloriousEggroll
Glorious Eggroll
Proton-5.9-GE-5-ST GloriousEggroll
GloriousEggroll (probably not needed, base proton 5.9 should be fine)
Slight flickering on some water which is barely noticeable and doesn't impact gameplay.
Crashes first time after restarting Steam. The game seems to require me to verify game files every time I go back to it, otherwise it crashed over corrupt game files during the initial loading screen.
Need to regularly run verify integrity of game files, as the game seems to complain about corrupt game files between play sessions.
If you don't mind the stuttering between gameplay and cutscenes, you'll be fine.
Slow texture steaming and very noticeable model and texture popins
Large stutters when transitioning between gameplay and cutscenes. Runs at a solid 60 FPS otherwise. The FPS lock can be removed but I can't be bothered given the length of the game.
Unplayable due to constant stuttering
Inputs ignored when stuttering.
Ridiculous levels of stuttering that weren't reducing at all. Unplayable.
