Orb Wife
Published
Ran fine on Native with Medium graphics settings. Runs perfectly on Ultra under Proton 6.3-4 out of the box.
When the game launches, it does not immediately assert fullscreen, and doesn't respond uniformly to attempts to manually assert fullscreen. Eventually, it will work (usually by some combination of double-clicking the window title or spam clicking inside the window itself), but it's annoying and causes problems with alt-tabbing, too.
Tried launching with Proton 6.3-8 initially (my current default), but although it got through all of the Origin setup, the game never launched. Have not tried on default Proton 7.0.1.
No multiplayer (EAC), but otherwise nearly-native singleplayer gameplay with 6.3-4.
This launch flag, mentioned by other reporters, fixed issues with connecting to online multiplayer games in Proton 6.3-4: WINEDLLOVERRIDES="mfplay.dll=d" %command%
OOTB Proton 6.3-8. Very reliable title for SteamPlay.
The only knock I've ever heard about with this game is voice chat not working. I did not try this, as I normally communicate via text chat.
Takes about 10 minutes after downloading the game via Heroic Games Launcher to unbork EAC problems.
PROTON_EAC_RUNTIME="/home/diana/.local/share/Steam/steamapps/common/Proton EasyAntiCheat Runtime/" %command%
Followed this guide.
Grabbed this for free on EGS, and am threading it through Steam to leverage the Proton EAC service.
Used these launch options (as suggested by other contributors) to get menu and in-game sounds to work:
WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%
It happens that for me, on the same hardware and Proton version, these same launch options solved the same issues for Skyrim: Special Edition.
Game runs perfectly on 7.0-1 with the exception of windowing issues on launch. No issues at all on 6.3-8.
Refocusing the window on 7.0-1 a few times brings the game back into proper focus. It's minor enough that I don't mind playing on that version of Proton, but it's good to know that reverting to 6.3-8 resolves the issue entirely.
Installed the DEP, which contains many of the QoL mods others list here.
Literally just drop the files from the DEP into the game install directory on a fresh install. It plays very smoothly.
-provider Portal
The -provider Portal launch option was something I was very pleased to discover on here, since I already have a GW2 account and did not want to link my SteamID to play on a blank slate. I only briefly tested, but it looks to be at least as performant as running through Wine was for me.
Still need to pick the EAC disabled launch option to play multiplayer, but seems to work fine
Other reporters have said that you can now launch MCC via the default "Play" option. That may be true for them, but it was not for me. Selecting the "EAC Disabled" launcher allowed me to matchmake like I normally would have, indicating that the launcher choices are still switched or otherwise bugged.
EAC compatibility still seems incomplete.
The game now ships with easyanticheat_x64.so. I have tried running it under several different Proton runtimes (7.0-1, Experimental (both bleeding edge and default), and 7.5-GE) and have installed the Proton EasyAntiCheat Runtime as well. None of these steps allowed me to get past the EAC splash screen, which (glitchily) loaded the EAC progress bar to completion and then did nothing else, even after several minutes of waiting (on one iteration of this testing process, I waited nearly 20 minutes before giving up).
Minor detail: on launch, the game minimizes to the panel. Clicking into the game through the panel brings it up normally.
Slowed down during intro cutscene and very occasionally during other scene transitions
Played using a Steam Controller (along with Big Picture Mode Overlay enabled) with no issues.
gamemoderun %command%
Only worth mentioning because it happened while I was writing this report: alt-tabbing caused the launcher program to hang, but the game can be freely cycled to and from with alt-tab otherwise, since it runs in a separate process from the launcher.
I had installed and played the game on my desktop previously. However, after a recent patch (I assume to the EA Launcher/App), like others, I was not able to simply launch the game, even when switching to another Proton version. The key for me was to delete the Proton files: Big Picture Mode/Deck UI has an easy way to do this by navigating to the game's library entry, clicking on the options gearbox, and then selecting Developer > Delete Proton files. You can also manually delete the steam/steamapps/compatdata/1328670 folder.
This will prompt some of the first-time setup processes, but in my case, I didn't even have to re-login to EA. I played about 15 minutes, then successfully exited and re-launched the game to confirm that I wasn't guaranteed to have to delete Proton files between each session (barring yet another breaking change from EA - seriously, this is silly).
My graphics settings defaulted to high, but combat wasn't playable with the FPS drops I was experiencing there. I didn't have these issues on Windows. Setting the graphics down to medium and turning off antialiasing helped immensely, but some drops still occur when loading new areas or encountering larger groups of enemies for the first time.
Entering Steam's in-game overlay crashed the game for me.
Pretty much OOTB on Proton 6.3-8.
Not even sure that this artifacting isn't present on Windows.
After saving and exiting, there was an overflow of "async loading" errors that greeted me on my desktop. Pressing OK on all of them didn't do much other than allow them to continue. Stopping the game through Steam killed the process and no more errors popped up.
Outside of the weird error on closing the game, I experienced absolutely no issues during gameplay. This is a massive improvement from about 6 months ago, where it was nearly unplayable due to performance issues.
This was OOTB on Proton 6.3-8 for me.
Like others here, I disabled "On Demand Patching" in the launcher options. I have apparently been lucky, in that I did not experience issues with needing to delete the gameprefs file between sessions of play. I will update my report if I experience that (or any other) issue.
gamemoderun %command%
Prior to the most recent update, Native seemed to work perfectly well, but now the native client has some variety of memory leak when loading a save or starting a new game that forces me to fully reset my desktop. The same save I tried to load in Native functioned normally and without incident under Proton.
Out of the box, 6.3-4.
Native works fine, from what I could tell. The reason I decided to use Proton was because, apparently, cloud saves are not cross-platform from Windows.
Game won't launch with Summer 2021 Update.
It's a real shame, because it worked perfectly fine OOTB before the update. I'd wager it's the fault of the new anti-cheat measures they put in place.
My primary fire button (default LMB) seemed to occasionally stick between lives or frame stutters. Clicking again manually solved it, but it is annoying.
Others have noted this: the first time you play on a given map, the first minute or two of the match is extremely stuttery and slow, I think because the GPU creates the shader cache as necessary. Once you play that map again, unless you update graphics drivers or delete the cache somehow, it's fine.
I never crashed during gameplay, but the game generates the crash report dialog box every time I close it.
Another ProtonDB reporter linked this guide. It's very helpful. I only used DXVK_ASYNC=1 %command% as my launch options, but others may be helpful depending on setup. I also had to turn down graphics from their default high settings to medium settings, where I wouldn't have needed to on Windows.
Previously worked flawlessly, but now getting a Vulkan error.
gamescope -w 1920 -h 1080 -W 1920 -H 1080 -f --force-grab-cursor %command%
Not sure what changed, but about a week or two ago the game was working perfectly. I now get this error every time I try to launch the game: https://ibb.co/C8R2bWD
OOTB Proton 6.3-8. Went in expecting to troubleshoot and forgot I was running under Proton.
Furthest I got was main menu, 5.13-6.
PROTON_USE_WINED3D=1 gamemoderun %command% alongside disabling the in-game overlay actually got me past the opening cutscene (site of previous crashes) and it began trying to load some assets. The process eventually froze and stopped responding completely. I've tried many versions of Proton and attempted to use a symlink systemd-resolved fix noted by an Arch user, all to no avail. Maybe I missed something somewhere, though.
Out of the box with Proton 6.3-4. No other tinkering required for me.
Alt tabbing was a little weird, but I didn't explore further after an initial attempt.
gamemoderun %command%
Before I added gamemoderun and changed my in-game graphics settings from "auto" to "low," the game ran generally fine barring some occasional frame dips on certain maps in multiplayer. Those dips have improved considerably since changing those settings, and I hardly notice them now.
EAC splashscreen at launch even acts like you would expect it to on Windows. Matchmaking is apparently unaffected by my use of Linux.
DOS is a little slower than I would expect it to have been on Windows. In addition, I sometimes have to relaunch the game because the DOS boot menu fails to show up, but I usually only need to do this once.
I followed instructions here to install UniWS and achieve widescreen resolutions without having to disable Steam's in-game overlay. I ran the uniws.exe in the terminal with WINEPREFIX=/path/to/steamapps/compatdata/32370/pfx/ wine uniws.exe in order to keep my default wine-prefix isolated, but running it in this way may not be necessary for this mod to function. I also enabled showing dot files via winecfg targeting that prefix, to be able to navigate to my distro's default Steam directory.
I also installed textures that UniWS/WSGF recommended and another mod, nearly identically following the instructions to extract their files to KoTOR's /Override/ directory. The mods are working without issue.
OOTB Proton 7.0-2
During my first session, I earned an achievement while playing with the Big Picture Overlay. The achievement notification remained frozen over the game until I ended the session. I changed no settings, and have earned achievements since without a repeat of this issue.
Singleplayer works just fine on current. If you can't get on MP, try an older Proton version.
On newer versions of Proton (namely 6.3-8 and above), clicking on the Multiplayer tab yielded a "Not signed in" error and I wasn't able to access the server browser or join ongoing matches. I did not test hosting. Switching to 4.11-13 resolved that.
On all tested versions, other than the multiplayer issue, windowing was a little weird. The game would default to my secondary monitor when launching. On newer versions, the game would occasionally switch back from my primary monitor to the secondary monitor during loading screens or transitions to and from the menu. Nothing a little alt-tabbing/panel icon clicking wouldn't fix.
The default driver for my installation of Linux Mint 20.1 was xorg-xserver-video-nouveau. While that driver was properly picking up my dual monitor setup, it didn't work out for Oblivion. I switched to the proprietary nVidia driver, version 450, and then eventually landed on Proton 4.11-13. This combination allowed me to load and play Oblivion as I would on Windows. No other configuration was necessary.
Very easy to get running with launch commands, and plays nearly identically to Windows on Proton 6.3-8.
The following launch options were necessary for install (other users have listed these too):
PROTON_ENABLE_NVAPI=1 PROTON_SET_GAME_DRIVE=1 gamemoderun %command%
I have left these options enabled, but others have said you can disable them after installation.
The launcher needs to be manually minimized or it will layer itself over the game. Not a big deal, but worth mentioning.
The first installation popup was a black screen for me. Pressing enter here allowed me to continue the installation process normally and properly see the rest of the menus.
