Jens
Published
Works great.
Loading new rooms sometimes causes a lag spike, but this probably happens regardless of platform.
Forced the game's SDL to use XWayland instead of Wayland by setting the Launch Options to: env SDL_VIDEODRIVER=x11 %command%
Shows up on monitor, but not in the Vive.
The VR view turned very low fps while the game was open as well, so I doubt it would run very well even if it did show up in my hmd. Might just be that my graphics card isn't good enough (lack of vram or something?).
Launch Error: Failed to load the anti-cheat module.
Same results on Proton 6.3-8, 7.0-1, and Experimental as of 25.2.2022 1:47 AM GMT+2. Renaming the dlls to EOSSDK-Win64-Shipping.{so,dll} (according to commit https://github.com/ValveSoftware/Proton/commit/35a4101ac8bbf914304d35dc8d1d965aa7d29773) did not help.
I needed to turn the settings to minimum and resolution to 1280x720 to run this on my 1060 (3GB). This may be intended or Linux glitches, but when looking around in an open area, there's lots of flickering shadows and lods. AMD was right, 4GB (let alone 3GB) isn't enough VRAM for today's games.
With Arch's regular Steam (Runtime), gamepad worked great out of the box, but online did not. With flatpak Steam, online worked, but gamepad did not. Got it working by going View -> Settings -> Controller -> General Controller Settings, checking off my (PS5) controller, then under the same Controller menu, Desktop Configuration -> Browser Configs -> Templates -> Gamepad -> Apply Configuration. After this, it worked great. Steam Input and Overlay on, as they are by default.
I hope they'll fix EAC not working outside of Flatpak Steam, as it seems to sometimes simply not launch the game. Haven't had this issue with non-Flatpak Steam. Bleeding-edge experimental Proton should not be needed after a few days too, so if you're reading this in a few days, you can probably just use the latest stable Proton.
During launch, there were some rough edges, but now the game works great on regular old Proton Experimental (no bleeding edge required). The latest patch improved performance even further, even though with the shader precaching stuff, the Linux experience was already better than on Windows (I never got the stutters). Running on maximum settings, the game drops noticeably under 60 fps pretty infrequently after 1.03.
5.21-GE-1 GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/5.21-GE-1
Almost all sounds in the game didn't play for me without adding WINEDLLOVERRIDES="xaudio2_7=n,b" to the custom launch command.
The game runs almost at 90 Hz (dropping a lot when there's enemies or more complex areas) if I run it at the minimum resolution SteamVR settings let me set it to, on my GTX 1060 3GB. I'm also running some mods that supposedly help with performance, such as Wasteland 512, Optimized Vanilla Textures, and Fog Remover II. The game admittedly looks extremely pixelated, but it's playable. I also have a mod that adds FidelityFX contrast adaptive sharpening, which probably helps with the normal TAA blurriness. Without any AA, the low resolution is hilariously aliased, and my framerate was the same with and without. Check out reddit.com/r/Fallout_VR "Most important mods for fallout vr" thread for good recommendations, I use most of the top ones.
The game requires quite a bit of restarting to get it working, but once it launches properly, it does work.
Lower FPS than on Windows, I could play without noticeable lag on there, but on Linux I get some spikes and generally the game feels a little sluggish.
The game doesn't work at all if Vulkan is selected (I presume that's why the native version doesn't work at all either), running on DirectX 11 the game randomly just gets stuck in the initial "loading room". I have to restart the game 1-3 times to get it running. The mirror on my monitor looks just fine, the headset just renders the dark rubble scene used for loading screens(?).
I've also had SteamVR crash multiple times, though it mostly seems to happen when loading in new areas, and moving to a new chapter consistently crashes. I'd guess this is because I have too little VRAM (3GB).
Manually forced the use of Proton (as the game is native by default).
In the native (default) version of the game, pressing buttons on my controller in the main menu registered maybe 20% of the time. Like, tapping down on the dpad did nothing until it suddenly did, and the selection moved down one. I could reliably navigate the menus by just spamming a button until it worked. Running the Windows version of the game via Proton does not have this issue.
Works great after you remove SpeechSynthesisWrapper.dll in the Pentiment_Data/Plugins/x86_64 directory.
Removed SpeechSynthesisWrapper.dll as mentioned in other reviews.
Seems to start up but instantly crashes if the DLL isn't removed.
Very poor performance on my system.
I have an NVIDIA GTX 1060, and fresh drivers from the Arch Linux repositories. I'm using X11 and have Discord open on the other screen, so it might be stealing some performance. The game runs very slow, I'd guess ~10-20 fps on the lowest settings.
I'll try again after getting an AMD gpu, I'll be switching to Wayland as well.
With the fixes mentioned, it's a pretty smooth experience. Mods work too, with the patched sksevr, I have SkyUI, USSEP and VRIK.
Installed xact (note: this is very needed, I managed to get the game to open but not appear in the headset without this):
protontricks 611670 xact
Added the following to my launch command (gamemoderun probably not required, but this config is apparently needed for audio problems):
gamemoderun WINEDLLOVERRIDES=”xaudio2_7=n,b” %command%
And used the custom version of sksevr from allgator on github, because the official one does not have a fix required for running it in wine (crashed when loading SkyUI otherwise): https://github.com/ValveSoftware/Proton/issues/170#issuecomment-799702546
Don't know yet if it's crash-prone during gameplay, but it does crash SteamVR when exiting the game through the in-game menu.
The game doesn't seem to run that differently from windows from what I remember, hovers near 11ms with 1216x1352 resolution (65% resolution multiplier for the vive on my hardware).
With the fixes mentioned, it's a pretty smooth experience. Mods work too, with the patched sksevr, I have SkyUI, USSEP and VRIK.
Installed xact (note: this is very needed, I managed to get the game to open but not appear in the headset without this):
protontricks 611670 xact
The xaudio fix with the launch command recommended in other reviews did not work for me. However, the "Last straw" option in this guide did: https://askubuntu.com/a/1302789
WINEPREFIX=~/.steam/root/steamapps/compatdata/611670/pfx WINE=~/.steam/root/steamapps/common/Proton\ 6.3/dist/bin/wine bash wine_setup_faudio.sh
And used the custom version of sksevr from allgator on github, because the official one does not have a fix required for running it in wine (crashed when loading SkyUI otherwise): https://github.com/ValveSoftware/Proton/issues/170#issuecomment-799702546
Crashes SteamVR (and the graphics driver?) when exiting the game from in-game: my entire system seemed to freeze for a while. Exiting SteamVR and then closing skyrim seems to work fine though.
The game doesn’t seem to run that differently from windows from what I remember, hovers near 11ms with 1216x1352 resolution (65% resolution multiplier for the vive on my hardware).
Works great!
Haven't played for very long, but I thought I'd write up the report so I don't forget, as this game seems to have few of them. The only problem with the game I've had is that some modded maps perform a bit poorly, but I imagine that's more about the content than the game.
The game itself is great, love the real controls that you get to flick, and the panels that can e.g. show your spectator camera and stuff. Didn't do any combat though, I'm more here for just the civilian-type flying.
