YellowApple
Published
With the sole exception of the main menu freezing for about 15-30 seconds immediately after pressing Enter/Start (compiling shaders, maybe? Or otherwise loading something?) and a thin white outline sometimes showing around the player plane during replays (only noticed it when the plane's flying through clouds and the replay's zoomed out a bit from the player's plane), AC7's single-player campaign runs absolutely flawlessly. My Logitech F310 gamepad was fully compatible out-of-the-box. Graphics look great, game runs great (no lag, crashes, major graphical glitches, etc.).
Lots of mods; runs smooth about 95% of the time.
Single player freezes after a couple hours of gameplay, almost always while trying to place a building (and once while exiting a dungeon); have to switch to a text console to close it (responds to SIGTERM). Most recent crash left it stuck in a "Running" state in Steam.
Occasional stuttering when looking around in a new area. Can't really correlate it with anything in particular; maybe some kind of hangup when loading things into the world? Goes away after a few seconds.
Launcher loads, but configuration program and the game itself both silently crash on launch
When launched from Steam, the launcher runs fine, but both "Configure" and "Play" result in a brief error report window popping up before that disappears, leaving a stuck launcher process running (Steam can't kill it itself; I have to kill it on an OS-level, e.g. with "htop" in my case).
When running in the terminal with the SteamPlay-generated wineprefix, both DAOrigins.exe and DAOriginsConfig.exe crash with "wine: Unhandled division by zero at address 0x470631) (thread NNNN), starting debugger..." (where "NNNN" is consistently "0039" for DAOriginsConfig.exe or "0034" for DAOrigins.exe), regardless of whether they are run directly or through the launcher.
Launcher is (again) a bit crashy when doing a lot of downloading, but the actual gameplay is excellent.
Launcher crashed/exited occasionally during initial download, but after a few attempts it finished and I was able to launch the game perfectly fine.
Exactly as it is on Windows
Game runs smoother than it does on Windows 10 with the exact same hardware.
Pops up a message stating "Cannot find 640x480 video mode". Game doesn't start at all.
Some tweaking is indeed necessary. In particular, this might count as Borked because the .NET-based launcher is still broken (and therefore clicking the "Play" button still doesn't work). HOWEVER, using a script by Steam user emmet (https://steamcommunity.com/app/244160/discussions/0/2727382174641131600/), the Remastered portion runs almost perfectly on my machine (no separate Wine install necessary; this uses whatever version of Proton Steam provides). I was able to complete all tutorials and the first mission without issue, even on max graphics settings. Performance is acceptable (I have low standards re: framerate; it's a bit choppy here and there, like in the glamor shots of the Mothership+Scaffold in the Mission 1 intro, but nothing particularly "terrible" IMO). Gearbox intro video has an audio loop glitch of some sort. Have not yet tested skirmishes (single/multi player), the bonus mission, or mods at all. Further discussions leading up to this success: https://steamcommunity.com/app/244160/discussions/0/1733213724914674457/
Affected by the invisible unit bug. Also pretty laggy. Downloading the 3.16-4 beta right now; will re-test.
The game sucks, but it does technically work "perfectly" on Proton
I felt like I'm on drugs. I don't know if this was a Proton bug, a game bug, a design choice, or some combination of all three.
Laggy as all hell, though apparently this is an issue on Windows, too.
Game launches, but mouse doesn't respond to clicks (cursor visible)
Needed to bypass the launcher (rename TaleWorlds.MountAndBlade.Launcher.exe to something else, then copy Bannerlord.exe to the launcher's original filename).
Game starts up and shows the intro video, but gets stuck on the brightness calibration screen due to an inability to recognize mouse input. Bypassing this in "~/.steam/steam/steamapps/compatdata/261550/pfx/drive_c/users/steamuser/My Documents/Mount and Blade II Bannerlord/Configs/engine_config.txt" (change "brightness_calibrated = 0" to "brightness_calibrated = 1") brings me to the main menu, but the inability to recognize mouse input persists.
But hey, it seems to be rendering the main menu's 3D warrior and such with a good framerate at the default settings (whatever those may be), so there's a bright side, at least :)
About as stable as I'd expect under Windows (that is: not very, but welcome to Early Access)
5.5-GE-1 GloriousEggroll
Using the latest GloriousEggroll Proton release (5.5-GE-1) and protontricks 261550 dotnet472
Very crashy, but it's crashy under Windows, too, so ¯_(ツ)_/¯
Just works
Tutorials all seem to work fine. Haven't tested campaign/skirmish/multiplayer.
Stuck on "Loading"
Tried it on both "Fantastic" and "Fastest" graphics settings. Didn't seem to make a difference.
Interestingly, in both cases the game had all 16 cores / 32 threads on my Threadripper in moderate use, so it was clearly doing something, but no idea what.
Had to apply the usual swkotor.ini workarounds (disable fullscreen, enable windowed) and disable the Steam overlay to get it to a playable state. Also had to enable v-sync to prevent a chronic issue where the player character would be unable to move via the keyboard after certain cutscenes or fights (though this reportedly affects Windows, too). Still crashes to desktop every couple hours immediately after the loading screen between areas / after cutscenes, but thankfully my PC's beefy enough to get me back into the game reasonably quickly.
Weird glowing rendering artifact in/near water. Otherwise plays perfectly (Just Like The Simulations™). Mods work great, too (albeit with a bit of elbow grease sometimes, since they're not usually packaged with Wine/Proton in mind).
Works perfectly out of the box
There didn't seem to be any multiplayer servers in the list; not sure if it's a Proton bug or if there's just nobody running servers. Either way, was unable to test multiplayer for that reason.
Seemed to run reasonably well with a mix of low and ultra settings (in particular: left textures and anti-aliasing at ultra, set the resolution of the outside world to full, and enabled NPCs and animated screens; dropped everything else to low).
Had to do the launcher/main executable switcharoo like everyone else here. Vanilla works fine otherwise, as does my increasingly-heavily-modded game.
Only issue is that the in-game browser is really finicky, so I haven't been able to use it to create or log into an online account (let alone try to buy anything with it). Also crashed once, but that's more likely from one of the 100+ .package files I've got installed.
Also, since I ain't using the launcher, I've had to use a different approach to installing .Sims3Pack files (i.e. extract them out into .package files). Lepid Llama's Pack Unpacker (http://fan.prosims.ru/soft/item/sims3/lepid-llama-unpacker.html - don't mind the Russian; app's in English) seemed to be the most Linux-friendly (extract the RAR, then java -jar PackExtractor.jar in a terminal); Delphi's Sims3Pack Multi Installer (http://www.modthesims.info/download.php?t=364038) also technically works (download/extract the .exe and run it from the terminal with mono "Sims3Pack Multi Installer.exe"), but it seems to hardcode Windows path separators (''), so you'll end up with .package files in weird places and with backslashes in the filenames (note to self: see about sending in a patch for that...).
