E3FxGaming
Published
Fantastic out-of-the-box experience with this game. Behaves 1:1 like I would expect it to run on Windows.
I played the game for 94 minutes and didn't encounter any bugs at all so far. Physics were fine, graphics were fine and I had a fun time so far.
I didn't encounter any bugs I would attribute to the game running on Linux in the 12 hours it took me to complete the campaign.
Campaign and Sandbox mode work. I haven't tested Arena mode yet, but I honestly don't have a reason to expect problems there.
If you're only interested in the multiplayer, don't even try it.
Multiplayer isn't just dead (no players) - Activision shut down the matchmaking servers for everyone.
Uses Easy Anti Cheat, an anti cheat technology that doesn't work on Linux in Wine environments.
It literally says that it's installing Easy Anti Cheat during the steam game installation process.
Disabling Esync did not fix the audio looping problem, which other users mentioned here, for me.
Steam Remote Play together didn't work either, audio was transmitted but the person streaming the game would wait forever for the video stream to start.
I also tested this with the newest Proton version (as of writing this - 5.0.9), with the same audio looping problem.
Had to disable both Esync and Fsync to get rid of the audio loop problem.
If you're willing to go through the (quite lengthy) installation process, it leads to an enjoyable experience
Proton-5.6-GE-2 GloriousEggroll
Install dtonet472 and VC2019
Install libeslinux (on Linux)
Install .NET Core 2 with Lutris in the Proton prefix
More detailed instructions here: https://gist.github.com/E3FxGaming/aa47732251bab9663e3490a6210350bd
Make sure to use the Glorious Eggroll Proton version, it includes fixes for M&B II Bannerlord since Proton-5.5-GE-1 (do use the newest Glorious Eggroll Proton release available though)
Had no problems with it except the last cutscene before the A ending didn't play (got skipped automatically).
Used custom proton build made by Github user jpgay https://github.com/ValveSoftware/Proton/issues/4777#issuecomment-829859050
The cutscene at the end of the A ending doesn't play, but you do get to save the game. After that you return to the title screen and can load the savegame for the B route.
Only got to the A ending so far. Loading the savegame for the B route works, but haven't played anything from the B route yet.
Absolutely fantastic experience that is comparable to the experience a Windows user would get.
Can be fixed with the launch command others have already written about in their report
Modding: I followed guide someone else posted here about Vortex Mod manager through Lutris, which allowed me to get the mod files (.esp, .esm, ...) into my /steamapps/common/Skyrim Special Edition/Data directory.
However upon starting the game, SKSE64 would pop up and only load the plugins found Skyrim Special Edition/Data/Plugins, while ignoring all the other mods that use esp files in the /Skyrim Special Edition/Data directory.
The solution was hard to find, but easy to implement: In the Wine prefix Lutris created for Vortex Mod Manager (this is important - I'm not talking about the prefix Proton created here), you can find in drive_c/users//Local Settings/Appication Data/Skyrim Special Edition/ two files, loadorder.txt and plugins.txt. Those files are fundamentally important for telling Skyrim SE which .esp mods to load and in which order.
In the prefix Proton created those files are missing. So what I ended up doing was deleting the directory found in /steamapps/compatdata/489830/pfx/drive_c/users/steamuser/Local Settings/Application Data/Skyrim Speical Edition (should be an empty directory) and then creating a symbolic link between the Lutris Wine prefix and the Steam Proton Prefix, to make it look like the directory from the Lutris prefix is part of the Steam Proton prefix. The command for this is somethign similar to
ln -s '/vortex-mod-manager/drive_c/users//Local Settings/Application Data/Skyrim Special Edition' '/steamapps/compatdata/489830/pfx/drive_c/users/steamuser/Local Settings/Application Data/Skyrim Special Edition'
Symbolic linking those locations compared to just copying the two files allows you to use Vortex Mod Manager in the future to change stuff (e. g. install new mods) while not having to fiddle with the files again and again.
After doing the linking .esp mods loaded as expected.
Game runs absolutely fine, with a performance comparable to the one I experienced with Windows.
It should be noted that you won't be able to give your wingmen voice commands, like you can on WIndows, because that game feature relies on the Windows 10 Speech-To-Text functionality which obviously isn't emulated with Proton. You can give your wingemen the same commands using the UI on your aircraft screens in-game, so you're not missing out on any functionality, it's just the tip-of-the-iceberg comfort you're missing out on.
When I started the game for the first time I was greeted with a black screen for round about 3 minutes. You just have to patiently wait for the main menu. I assume it's pre-caching something in the background, because this loading time doesn't reappear for subsequent launches. It's just the first launch where your patience is tested.
Version 1.0 of VTOL VR released after 3 years of development time and the result speaks for itself - I give it perfect marks.
The long loading time at the beginning of the game is gone (freshly installed the game to check out version 1.0 and there was no freezing), voice commands obviously still don't work since that's a Windows thing (wingmen can be commanded with the MFDs in your aircraft instead of your voice, don't worry to much about it).
I played the game with a Valve Index VR headset and knuckles controllers.
