Patola [Linux]
Published
Flawless experience out of the box. Tested with Oculus Quest 2 wireless via ALVR.
There was some lag regarding ALVR itself, that I need to tinker to resolve. But that had nothing whatsoever to do with the game, it didn't add to the interface lag. I will also send another report with this game with the Valve Index once my knuckles controllers return from RMA.
Flawless experience out of the box. Tested with Oculus Quest 2 wireless via ALVR.
There was some lag regarding ALVR itself, that I need to tinker to resolve. But that had nothing whatsoever to do with the game, it didn’t add to the interface lag. I will also send another report with this game with the Valve Index once my knuckles controllers return from RMA.
Flawless experience out of the box. Tested with Oculus Quest 2 wireless via ALVR.
There was some lag regarding ALVR itself, that I need to tinker to resolve. But that had nothing whatsoever to do with the game, it didn’t add to the interface lag. I will also send another report with this game with the Valve Index once my knuckles controllers return from RMA.
Worked out of the box with my Valve Index. As it's free, you lose nothing by trying.
Apart from the missing cutscenes/movies, flawless experience. Played in VR (Valve Index).
It does not play some movies (a test pattern appears instead). Seems to be related to mfplat/wmvcore, which means at some time proton will be able to do it (it's in heavy development).
Even the haptic controls work perfectly. Although the control mappings are crap, the game supports their use very well.
No issues, just works out of the box.
For the first time, you have to log in to Uplay on the PC screen, since this is an Ubisoft game. After that, it should work ok. Please take note that when you leave the game uplay keeps running, so you might with to "stop" the game via Steam which kills uplay.
Provided it works after the first few attempts, from then it's flawless.
The first time I launched the game with Proton 6.3-6: crashed just when I tried to skip the slapsh screen by pressing the controller trigger. Then I changed to Proton Experimental: wouldn't even start. Then I changed back to Proton 6.3-6: worked perfectly, no issues. So your mileage may vary and you might have to start is a few times. Ran the game via option "Launch HTC VIVE in Steam VR Mode" on my Valve Index after SteamVR was running. Starting from the SteamVR Home interface also seems to work.
The game is Linux native but as expected the Linux native build does not work in VR, you have to use Proton. Truth be said, not fault of the developers, at the time the game launched the native SteamVR API did not even exist.
Game starts, briefly flashes the HMD screen dark but never actually loads.
Other than the missing cinematics, game runs perfectly both in DX11 and DX12 modes.
Does not play cinematics (even by installing mfplat through mf-install and mf-installcab).
Cinematics do not play, you have to press ESC to skip the black screen.
Please note that according to the developers the Linux native version should be out in 3 to 6 weeks, that is, somewhere in June 2020.
Runs perfectly in DX11 without tinkering and runs in DX12 if you run the protontricks line
protontricks 427410 win10 vcrun2022
The protontricks line is necessary for DX12 mode to work.
With current proton 6.3-5, the game (including the launcher) will start but when you press "play" on the launcher it will give you a dialog with "Failed to initialize render module". This occurs because the game tries to compile using vertex shader 4.1, which wine doesn't currently support. So, to fix that, use the command "protontricks 718850 d3dcompiler_47" (install protontricks before, of course). I would also advise to change the initial program from the launcher to the game itself. Go to the /steamapps/common/"Age of Wonders Planetfall" directory and "mv dowser.exe dowser.orig.exe && ln -s AowPF.exe dowser.exe". You'll likely have to do this again after every update, though. After that, everything should work. I can't guarantee, of course, because a new update can break things again.
As a curiosity, the previous installment of the game series, Age of Wonders III, is linux native. On the Paradox forums, the developer took a long time to acknowledge there would not be a linux version, and gave no good reasons for that. It seems that paradox's long history of linux support has been dwindling. But at least we have proton now.
Starts well, makes it seems it will work, but doesn't. (Valve Index)
Game kind of starts but everything gets dark and the only thing you see is your feet symbol in the ground. Gets stuck there, although it responds to your movement. Tried different versions of Proton to no avail.
Works ouf of the box, using Valve Index.
There is a bug that happens with windows too -- game is kind of stuck in the minimal graphical settings. You have to click a lot of times to "unstick" it.
Runs flawlessly. Proton 5.13-4, Valve Index, Ryzen 7 3700X, Radeon RX 6800 XT.
Works out of the box. Using Meta Quest 3 via ALVR.
Recorded the initial gameplay of the game here: https://youtu.be/eMaagMXvB9o
Works out of the box with Proton 5.0-7. Absolutely no issues.
Works out of the box. Using Valve Index.
I had had some issues with matches disconnecting in the middle but according to the forums that's the same as for windows players. There doesn't seem to be any anti-cheat getting in the way specifically for Linux.
Apparently it doesn't work anymore, at least on current proton.
Still have to do more tests, but it's possible that the anticheat stopped working.
Seems to work, provided you start first in windowed mode.
First time I ran the game in fullscreen it would not work. After I changed it back to windowed and set the language, it would work normally.
Game starts, shows a black screen on the monitor, then crashes.
Created a bug report on Valve's github: https://github.com/ValveSoftware/Proton/issues/4366
Well, it's not a game but a free-form sandbox / engineering application.
It uses raytracing extensively even if it has non-detailed terrain and plain textures.
This game wouldn't even work in Windows with AMD cards, but works on Linux with AMD cards (besides NVIDIA). It has a native Linux version even. It seems it works now on Windows on AMD too. However, to be frank, running it on AMD might not be worth it unless you turn off raytracing, it's quite taxative
Game just doesn't start. It briefly flashes a black window then exits. Meta Quest 3 via ALVR.
Once you copy the OpenCL.dll files from Windows 10, it should work correctly. Played with Meta Quest 3 via ALVR.
Copied OpenCL.dll files from windows (system32/OpenCL.dll and syswow64/OpenCL.dll) and put them into the proper directories of the game's wineprefix - compatdata/2274200/pfx/drive_c/windows/{system32,syswow64}
My previous report had it borked, but I got it to work. I'll try and see if there's a way to get these OpenCL.dll files on the next or something, they do not seem to be in winetricks and wine's opencl.dll doesn't work. You can see the game's tutorial and introduction here: https://youtu.be/0pzA-48Vn9A
This VR game starts and seems to respond correctly, but never appears in the headset.
Opened a bug report at Valve's tracker: https://github.com/ValveSoftware/Proton/issues/5336 -- tested the game with Oculus Quest 2 via ALVR. Will later test it with the Valve Index.
Just use the aforementioned launch options and you'll be fine. Of course, disable origin overlay too.
To avoid the infinite "looking for patches" loop, use the following launch options: WINEDLLOVERRIDES="crypt32=b,n" %command%
It wouldn't work with vanilla proton or any proton at version 9. Other than that ir runs fine in GE-Proton8.
Game starts, show the dialog with initial options on screen, then after it the game crashes
Opened a bug report at Valve: https://github.com/ValveSoftware/Proton/issues/4610
Worked out of the box. Flawless experience, including network connectivity.
Works flawlessly out of the box, no issues whatsoever.
Notice that multiplayer is indirect, so you don't actually interact with players directly.
Works flawlessly out of the box with Valve Index. Everything works with great performance.
It seems this game did not work in the past, but now it's working perfectly -- Proton 6.3-7.
Image in eyes look inverted. Also the controllers don't seem to respond to buttons.
Opened a bug report for it on Valve's bugtracker: https://github.com/ValveSoftware/Proton/issues/4646
Needs Proton Experimental. With this, works perfectly out of the box. Valve Index
Absolutely flawless. Using Proton-5.0-9 and the Valve Index VR headset.
If shadows are turned on, it slows a lot and starts making reprojections. Every other setting does not have an onservable impact on performance.
Movies don't work, you have to resort to the old trick of mf-install https://github.com/z0z0z/mf-install then after that it works great.
Even if you don't use mf-install, when it would be playing the movies you just press ESC and everything else works. I am playing it with the Steam Controller via sc-controller. Bought the game with all DLCs.
Worked out of the box, including all movies and animations.
I have tried applying the .reg fix with regedit to play the game in ultrawide and so far (in my first attempt) it did not work, although it added the correct entries to the registry. Will still look further into this. BTW, there are some reports saying the game starts with a black screen; this is due to outdated drivers and libraries. Upgrade your distro, people!
Works well, small movies in the tutorial don't play yet, without harm to the gameplay.
A couple of in-game movies in the tutorials don't play but this does not preclude gameplay. This is a problem that will soon be over since the libraries that do this (mfplat, Microsoft Platform Foundation Libraries) is one of the most worked wine areas recently. But in the meanwhile you can fully play the game without these small movies.
Works perfectly both in VR and on the screen. VR via Valve Index, and for the screen I used a Steam Controller.
Seems borked in pancake and VR modes. Tried various proton versions.
Wasn't working with previous protons. Started working on 6.3-1. Valve Index
Black screen at the start, just press the controller buttons and it will get to the game.
Every works flawlessly out of the box. Valve Index with Three Vive Trackers (Full Body VR)
It starts perfectly and shows the configuration screen, but gets to a black screen when starting a new game.
Opened a bug report at Proton bugtracker: https://github.com/ValveSoftware/Proton/issues/5188 -- if this game is fixed I'll send a new report with the positive rating.
If you just try and run it with proton, the game starts but gives a black screen after you try to start a new game. That’s because the script relies in mfplat (Microsoft Platform Foundation Classes), which is still only partially implemented in proton and wine. So you need to install original microsoft DLLs. z0z0z made a script which did it but it was not updated for current proton. I forked his script and made the needed update (created a PR on his repository but I don’t know if he will accept). So for the moment after you have installed the game you should use the script with the prefix of the game: mkdir /tmp/x && cd /tmp/x && git clone https://github.com/Patola/mf-install.git && cd mf-install && WINEPREFIX=$HOME/.steam/steam/steamapps/compatdata/1576350/pfx ./mf-install.sh -- of course, substitute the steam prefix of your choice if you use a different one; the script will use your locally installed wine to add to proton, and it might take a while to complete. After that you can just play the game and it will work. NOTE: do not run random stuff from people from the internet, please check my history here, on Steam and on github to ensure I am a reliable person. Or you can read the script if you’re savvy enough.
Works well (but without some movies) if you install the game and add mfplat libraries to it.
Movies on the in-game camera and in between episodes don't play. Still an mfplat issue, to be resolved in an eventual update of proton. I hadn't played too much of the game at the time and did not notice this so I gave a flawless rating to it.
If you just try and run it with proton, the game starts but gives a black screen after you try to start a new game. That’s because the script relies in mfplat (Microsoft Platform Foundation Classes), which is still only partially implemented in proton and wine. So you need to install original microsoft DLLs. z0z0z made a script which properly install the libraries. After you have installed the game you should use the script with the prefix of the game: mkdir /tmp/x && cd /tmp/x && git clone https://github.com/z0z0z/mf-install.git && cd mf-install && WINEPREFIX=$HOME/.steam/steam/steamapps/compatdata/1576350/pfx ./mf-install.sh -- of course, substitute the steam prefix of your choice if you use a different one; the script will use your locally installed wine to add to proton, and it might take a while to complete. After that you can just play the game and it will work.
Works flawlessly in single player and multiplayer matches. Valve Index.
I couldn't test voice chat because my opponent did not have it on.
Almost flawless, there's the mild input inaccuracy when turning but nothing that actually hinders the experience. Highly recommended.
The turning joystick somewhat would be mildly unresponsive. Not something game-breaking. Might be due to SteamVR.
Doesn't even start.
I couldn't stop laughing hysterically while playing the game. Everything worked perfectly out of the box.
Worked out of the Box with my Valve Index.
The graphical fanciness of these game made me dizzy and nauseated frequently. So beware of your gag reflex.
Works perfectly well out of the box. Best adult game in all steam and it's free. If you liked this one try bonecraft too.
Works perfectly in VR too (using Valve Index).
Great performance due to the low-poly aesthetic.
Everything worked out of the box. Using Meta Quest 3 via ALVR.
The game has a couple bugs at launch. Not Linux exclusive.
Everything works out of the box. Using a Valve Index
Game still has a few bugs when released, like a slight weapon angle with the Valve Index (about 20°). Unfortunately this is making this game be scored down to oblivion, but don't believe the reviews, this is a fun, good VR game.
You can play it flawlessly with regular proton 6.3-7, but you need some adjustments. Keep reading.
The game needs mfplat (Microsoft Platform Foundations Libraries) which are not yet fully implemented in proton and the game will crash at start. To avoid that, first you need any version of wine installed in your distro, preferrably an official one from its package manager; then go to the terminal: cd /tmp ; git clone https://github.com/Patola/mf-install.git && cd mf-install (you can also use https://github.com/z0z0z/mf-install.git instead). Find out the steam prefix used by the game - let's call it , replace it accordingly. Here my steam prefix for the game is /games/steam, the default one is ~/.steam. Then, continue from the previous commands: WINEPREFIX="<STEAMPREFIX>/steamapps/compatdata/501590/pfx" ./mf-install.sh -- this command will use your locally installed wine and add and register the original microsoft libraries to proton. It will take a long time, might take hours even. In the meanwhile, right-click on the game entry, select properties, go to the "GENERAL" tab and in launch options, use that: %command% -nostartupmovies -- this will prevent the game from trying to play the initial movies which crash it. Note: I also tried using Proton-GE which has a bleeding-edge open-source version of mfplat but it didn't work.
You can play it flawlessly with regular proton 6.3-7, but you need some adjustments. Keep reading.
MY PREVIOUS REPORT WAS INCOMPLETE, USE THIS ONE The game needs mfplat (Microsoft Platform Foundations Libraries) which are not yet fully implemented in proton and the game will crash at start. To avoid that, first you need any version of wine installed in your distro, preferrably an official one from its package manager. First, install the game normally and try to run it, it will crash but at least it will create the steam prefix. Then go to the terminal: cd /tmp ; git clone https://github.com/Patola/mf-install.git && cd mf-install (you can also use https://github.com/z0z0z/mf-install.git instead). Find out the steam prefix used by the game - let’s call it (STEAM_PREFIX), replace it accordingly. As an example, my own steam prefix for the game is /games/steam, and the default one (if you haven't added other prefixes) is ~/.steam. Then, continue from the previous commands: WINEPREFIX="(STEAM_PREFIX)/steamapps/compatdata/501590/pfx" ./mf-install.sh -- this command will use your locally installed wine and add and register the original microsoft libraries to proton. It will take a long time, might take hours even. In the meanwhile, right-click on the game entry, select properties, go to the “GENERAL” tab and in launch options, use that: %command% -nostartupmovies -- this will prevent the game from trying to play the initial movies which crash it, but it will still crash on some cutscenes. To prevent crashing in cutscenes, edit "(STEAM_PREFIX)/steamapps/compatdata/501590/pfx/drive_c/users/steamuser/My Documents/My Games/Bulletstorm Full Clip Edition/StormGame/Config/StormPCCookedEngine.ini" and "(STEAM_PREFIX)/steamapps/compatdata/501590/pfx/drive_c/users/steamuser/My Documents/My Games/Bulletstorm Full Clip Edition/StormGame/Config/StormEngine.ini" and change all occurences of bForceNoMovies=FALSE to bForceNoMovies=True -- now you can fully play the game to the end.
Gives a "Fatal Error" at startup. Playing with Valve Index.
Opened a bug report at Valve's bugtracker https://github.com/ValveSoftware/Proton/issues/6413
Flawless experience with Valve Index. No issues whatsoever.
Worked out of the box with Proton 6.3-7, including the movies/cutscenes.
Some people report using Proton-GE to view the movies. Maybe this was fixed by Valve in the latest Proton but I did not use Proton-GE and I was able to watch them normally.
Apart from the mfplat issue, the game runs flawlessly out of the box. Valve Index.
In the splash screen, tutorial and some TVs, you cannot see some videos, a test pattern appears instead. That happens because of mfplat (Microsoft Platform Foundation Libraries), which is a part of wine/proton that is being heavily worked on, meaning this should be fixed soon. However, there's no impact of this issue in the gameplay: what you have to do in the tutorial is pretty obvious, and you don't miss anything relevant by not watching these short videos.
protontricks 963930 vcrun2019
Won't run without the protontricks preparation. Run the game once so it can initialize the proton prefix, then run the protontricks line, it will take some time, then you can run the game from now on.
Works flawlessly out of the box (Vive Index). Seems the developer is considering porting to Linux.
This report is for the game with the VR mod. It works under Proton 5.13, Vive Index.
While you turn, audio changes the pitch dramatically.
Initial Menu is a black screen, but it responds to input and you can start / continue a game.
Flashlight on/off is mapped to the same button as going forward, so you keep turning it on and off. Nothing game-breaking but it's annoying.
Mod is here: https://github.com/KozGit/DOOM-3-BFG-VR/releases -- just unzip it to Doom 3's directory, then make steam run Doom3BFGVR.exe instead of Doom3BFG.exe (might be done easily with steamtinkerlaunch, for example)
There is a tweak regarding joystick bindings, but it is the same in Windows and in Linux. The default Valve Index bindings are very bad. I went to the community bindings and found one named "DOOM VFR Configuration for the Index Controller". It requires you to once having started the game, use these commands in the console: "bind STEAMVR_PRIMARY_AXIS2 _lookLeft; bind STEAMVR_PRIMARY_AXIS3 _lookRight; bind STEAMVR_PRIMARY_AXIS4 _jump; bind STEAMVR_PRIMARY_A _weapnext; bind STEAMVR_SECONDARY_A _weapprev". Then it goes smoothly and you can turn smoothly instead of instant, which makes the game much better to play. Teleport still works, which you might need to reach some areas. If you like these bindings, you can just locate the /steamapps/common/DOOM VFR/base/vr_default.cfg, edit it with a text editor and add these bindings one each line at the end of the file
On AMD, it crashes after you click "Launch DARK VOID" on the launcher. On NVIDIA, it works.
Tried in two different PCs but my main one uses an AMD GPU (RX 7900 XTX), and the game did not work. On the secondary one, with an NVIDIA, it worked. Opened a bug report at valve's bugtracker: https://github.com/ValveSoftware/Proton/issues/7680 -- not sure they will do anything because this game will be delisted on May 8, 2024.
Runs semi-flawlessly. If you have a modern PC you have to restrict cores for the game to play.
taskset -c 0-5 %command%
There was some weird shrinking of the screen the first time I ran the game when it was in fullscreen, but changing to windowed fullscreen solved the issue.
The game won't run on a PC with too many cores. I have an AMD 5900X with 12 x2 (SMT) cores and a 5800H with 8 x2 (SMT) cores. If I tried to run the game with all cores on, it would only run with textures set to low. Restricting to the first 6 (0 to 5) virtual cores solved the issue (see launch options).
It works on PC with many cores provided you use the aforementioned launch parameters: taskset -c 0-5 %command%
Everything works out of the box with great performance. Valve Index.
You can see the potential of the game. The initial setting is ok. But you can't play it.
Seems to be missing movies, probably some mfplat stuff. Tried z0z0z's scripts, Proton-GE (which do not even start the game) and Proton Experimental, completely uninstalling the game after each attempt (even removing the compatdata wineprefix), but couldn't make it properly display the hologram that would tell you about the clues. This makes the game effectively unplayable.
It's difficult to say what the problem is with input due to the input scheme of this game being so weird, but it seems it incorrectly detect boundaries and have an odd choice for buttons and movement, and doesn't show any configuration options.
Frametime were consistently above 11ms, which is bad even for 90Hz.
It's a free game. Probably will not have any updates, and the discussion forums are empty. Also, it's oddly forbidden for some countries like Brazil, for no discernible reason.
Tried in VR, it worked with the Valve Index and Proton 5.13-1, not 5.0-9.
I tried in VR only. It was not working before, with Proton 5.0-9 and others, it started worked recently with 5.13 and it works perfectly, although the VR control scheme is weird (you have to push the Index stick up to select, instead of pressing a button) -- but it is completely playable, once you get used to it. Also, it seems you can't turn using the controls, you have to turn "for real". Probably someone on Steam has already published a control scheme that "fixes" those issues.
Worked right out of the box with great performance at maximum settings. Valve Index.
It's not a game. More of a (boring) experience, even with multiplayer support.
Stuck when exiting, have to stop it manually. Otherwise works wonders. Valve Index
Runs out of the box, even in VR (with Valve Index). Doesn't support knuckles though.
In-game movies show the test pattern, which means unimplemented mfplat (Microsoft Platform Foundation Libraries). These libraries are being heavily worked on in proton currently and this problem in all games which have it will likely be fixed soon. So don't let this act against buying the game. I have not gone too far in the game to know if that will be an impediment, but it doesn't seem so, from the gameplays I've watched.
That's not an "issue" because on Windows it's the same way, but the VR images around you are not stereoscopic, meaning you have the feeling that it's all flat around you (no depth information). Even with the game having a very cheap price, if I knew this beforehand I would not have bought it.
Everything works out of the box. Played in VR with the Valve Index.
It's quite a short game and doesn't have stereoscopic vision in VR, it's visibly flat. I regret having bought it, even with the low price at a discount.
Crashes with a brief unreal engine dialog at start.
Opened a bug report at Valve, but with little hope that they fix it. They don't work on bug reports like before. https://github.com/ValveSoftware/Proton/issues/6533
It doesn't get to the first screen in VR, it plays some small intro then crashes.
Seems to work in pancake mode but I bought this game for the VR mode. Opened a bug report in Valve's github: https://github.com/ValveSoftware/Proton/issues/4251
Game runs but seems crappy though, controls are bad.
If you use the Valve Index: you have to go to the controllers bindings for Dragon VR and choose the Dragonlord community binding for the Index. If you don't to that, you can't click on the menus.
Starts, but not in VR -- appears on the screen and it's unresponsive to input.
At first the steam overlay complains about the game lacking an actions.json file which I then borrowed from other game (Shadow Legends VR) and it stopped complaining. It didn't make the game work, though. Bug report here: https://github.com/ValveSoftware/Proton/issues/5037
Game currently doesn't work apparently due to an in unimplemented call.
Opened bug report at Valve at https://github.com/ValveSoftware/Proton/issues/5037 and explained the problems (action.json dialogue and XR_KHR_win32_convert_performance_counter_time function uninplemented). These are actually small issues and from previous bug reports I think Valve or voluntaries will be quick to fix that, maybe 2 weeks to one month. As soon as I notice it has been resolved, I will post a new protondb report with the positive results.
The game complains about an "actions.json" at the start, which would be used for input mapping. You don't actually need this file, but you can copy it from other games to the EVERSLAUGHT steam directory. In my proton build page you'll be able to download an actions.json file for convenience.
When exiting the game, it doesn't exit properly. You have to focus the steam window and click on the green "EXIT" button for it to completely exit.
Regular proton at the time of this report does not work with the game, so based on instruction from the bug report I have made my own proton build capable of running it, which you can check here: https://github.com/Patola/wine/releases/tag/6.3-everslaught -- all the instructions are there. Do not download and run random stuff from the internet: first verify my profile and my history of contributions, both here on protondb and on github, for assurance that I have been doing that for a long time already and will have no malicious intent with my build.
Graphical artifacts make the game very unwieldy.
The game screens are very garbled. It can be momentarily fixed by going to extras -> settings, get the graphical settings to low, then back to high or ultra or whatever. But then you start playing and they become garbled again.
Flawless experience, worked right out of the box with Proton 6.3-6.
Some people report some "slowness" on the game that I did not experience. On 2560x1080 with ultra settings I was getting 140 to 150 fps average. Although that's not stellar for such simple graphics, it's not painfully slow like others reported. Maybe they do not use a kernel with fsync compiled?
Apart from a few cutscenes, everything works out of the box, with great performance. Valve Index.
Some initial cutscenes/movies are not played, instead a test pattern is shown. This shows that the game uses mfplat (Microsoft Platform Foundations Classes, a Windows multimedia library), which is currently one of the most worked on parts of wine and proton. So with proper time this will definitely be solved. Nevertheless, the lack of these movies does not prevent anything in the game from working.
Worked out of the box, no issues. Played through the first mission with no hiccups. Proton 5.13-5
This game has been working for a long time, but it now works in VR too. Meta Quest 3 via ALVR.
Enabling VR to work on this game is very recent, due to a fix in Proton Experimental bleeding-edge branch that should soon be in Proton Experimental and then Proton stable. If you are reading this in 2025+ it might have already been comitted to Proton stable.
Works perfectly out of the box, except if you turn freesync on using a NVIDIA.
If I turn on freesync mode on my nvidia game goes black. Otherwise everything works perfectly.
Game runs great out of the box with regular proton, but not in VR.
For VR, there is a series of patches from Paul Gofman from Valve that fix VR initialization. They will be eventually integrated into regular Proton but as of 6.3-6 they still aren't. But you can use my build of proton that runs the game (and a few others): https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd -- before doing that, please see my history of contributions here and in github to ensure I am a reliable person, you should not download and run random stuff from the internet. If you uninstall the game, set my proton build for this game, and reinstall it, it should work correctly in VR. Tested with the Valve Index.
After a recent patch (as of 16/Sep/2021), it stopped working in VR even with gofman's patches. So I created a new build of my custom proton capable of running it, with the help of EsdrasTarsis who made the code patch.
This is a new report because the game stopped working in VR after the last one. My original report had this: "For VR, there is a series of patches from Paul Gofman from Valve that fix VR initialization. They will be eventually integrated into regular Proton but as of 6.3-6 they still aren’t. But you can use my build of proton that runs the game (and a few others): https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd -- before doing that, please see my history of contributions here and in github to ensure I am a reliable person, you should not download and run random stuff from the internet. If you uninstall the game, set my proton build for this game, and reinstall it, it should work correctly in VR. Tested with the Valve Index." -- what changed now is that the game started requiring Windows.Perception.Spatial.Surfaces.SpatialSurfaceObserver to work, so EsdrasTarsis implemented stubs for this and a few other arrangements (like a default actions.json for the manifest), the game runs again. You can get the new build, along with full instructions, here: https://github.com/Patola/wine/releases/tag/protola_6.3-6-6_rbespbgvwd
Doesn't start under proton. Shows a black screen, then exits.
It might not seem useful to have it running under proton if there is a native version, but there are reasons for wanting it that way. My own reason is that the Linux version is not VR capable while the windows version is. Also, it might use libraries that other games without a native version need to run under wine, so since it is free, it is easy to test it. I opened a bug report in Valve's bugtracker: https://github.com/ValveSoftware/Proton/issues/5106
Needed to run the proton build to have VR (it has a native build), but it worked 100% with no issues.
It is possible to run the game right, but it takes a lot of manual preparation with protontricks and by editting configuration files.
Had to install xact and faudio via winetricks/protontricks. However my winetricks package lacked the "faudio" verb and I had first to manually update winetricks to the latest version (from its github page) then call protontricks: protontricks 377160 xact faudio -- after that, all audio started to work, including NPC voices.
Would not recognize my display and always started in 1280x720. Had to manually edit "/steamapps/compatdata/377160/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout4/Fallout4Prefs.ini" and use iSize H=1080 and iSize W=2560 in the [Display] section to make my ultrawide work.
Input was very laggy at first execution but then it stopped. I don't know what I did which fixed it. Also, I use sc-controller for my steam controller which creates a "virtual joystick" device which Fallout 4 was insisting on using as main input, so I had to create a script to remove permissions from that device before executing the game.
Apart from the two tips, this game runs flawlessly, specially compared to flatscreen Fallout VR.
I use Valve Index, so to get a proper behavior of the controller you must put the openvr_api.dll in the Fallout 4 VR steam folder -- you get it from here: https://www.nexusmods.com/fallout4/mods/41931 -- and then you also have to choose the appropriate controller bindings via steamvr menus.
In one of the beginning scenes, the salesman will ask your name and you will see a virtual keyboard to type it in. Or you won't, if you are using SteamVR beta. So, to pass this part of the game, revert back to regular SteamVR, after that I think you can go back to the beta because as I understand there are not many places where you have to type in the game.
Ubisoft Connect might not run properly if you have the FUTEX2 (fsync) enabled. Typically, only a transparent frame of the splash screen will appear. So, if you experience that, try using that as launch options: WINEDLLOVERRIDES="crypt32=b,n" WINEFSYNC_FUTEX2=0 %command%
It works. Often out of the box. Sometimes not. Read the notes below.
The thing about Ubisoft games is that they require Ubisoft Connect (formerly uplay), their own launcher. So it often works, but not always. When it doesn’t work it’s usually the initial screen of the launcher “looking for updates”. So far, I’ve noticed that there are two things that can greatly decrease the probability of this happening: (1) use the following launch options: WINEDLLOVERRIDES=”crypt32=b,n” %command% (2) use Proton Experimental. (Proton-GE might be a good option too).
Works out of the box. First time running it crashes, but after that it starts gracefully.
Flawless experience. Runs out of the box. Using Valve Index for the VR.
Flawless experience. Runs out of the box. Using Valve Index for the VR.
Flawless experience. Runs out of the box. Using Valve Index for the VR.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
If you don't disable fsync/esync, game would start with a black screen. Also, I didn't play the game for too long, might be that GE-Proton is needed for some in-game movie or whatever but so far I haven't noticed it.
launch options WINEDLLOVERRIDES="winhttp=n,b" %command%
Could not find the Index bindings for GTFO VR when looking for custom community keybindings.
The game is Platinum in pancake mode, but turns out if can run in VR with the proper BepInEx mod, here: https://github.com/DSprtn/GTFO_VR_Plugin -- just follow the instructions in the video in the README and they should be pretty much the same for linux, except that: for launch options, use WINEDLLOVERRIDES="winhttp=n,b" %command% aaaand after having installed the files (bepinex, the vr mod and the multiple dlls), run it once so it creates /steamapps/common/GTFO/BepInEx/config/com.Spartan.GTFO_VR_Plugin.cfg -- then exit and edit this file accordingly, changing the options as you wish (I always set smooth turning on), and more importantly: set option "Start in pancake if SteamVR is off?" to false (default is true). Kudos to corben78 for this finding! Do not forget to turn off the settings as indicated in the mod's instructional video!!! This game is graphically heavy and even a powerful PC cannot handle all the effects in VR.
Flawless experience out of the box. Valve Index.
There is a report saying missing audio, but I couldn't notice any missing sound during my playthrough.
Starts up, show splash screen, show waiting screen and then crashes to the desktop.
Well, it now starts at least. Previously it wouldn't even do that, according to the older reports. I opened a bug report at proton's bugtracker: https://github.com/ValveSoftware/Proton/issues/4937 -- I'm using Valve Index for the VR.
My build of Proton with the bluetooth functions needed for the game to not crash is here: https://github.com/Patola/wine/releases/tag/6.3-5 -- you should not install random software from the internet on your PC, so first please look my profile on steam and github and see that I have a long history of contributions, I would not do harm to anyone. Nevertheless you can also try and create your own proton build with esdrastarsis patch from bug report https://github.com/ValveSoftware/Proton/issues/4937
Ok, so this build was developed because kisak-valve noted on the bugreport https://github.com/ValveSoftware/Proton/issues/4937 that the issue making the game crash was unimplemented bluetooth functions. Then EsdrasTarsis which subscribes to my bug reports on proton saw this and developed the stubs (empty functions, just to avoid crashes) for wine and gave me the patch to test. I applied the patch in proton and compiled it, tested it for two hours and it worked perfectly, then I made it available on my github.
Starts up, show splash screen, show waiting screen and then crashes to the desktop.
Well, it now starts at least. Previously it wouldn't even do that, according to the older reports. I opened a bug report at proton's bugtracker: https://github.com/ValveSoftware/Proton/issues/4937 -- I'm using Valve Index for the VR.
It works perfectly with Proton 5.13-6.
The game doesn't seem to work properly with never versions of Proton (>= 6.x), including Proton-GE and Experimental. It starts, show two copyright screens then crashes.
It works with Proton 5.13-6. Be sure to make a clean install (uninstall via Steam or rm -rf compatdata/1449280), then change proton to 5.13-6, then install or run it again.
Works well. A couple of in-game movie don't play, see the notes.
A couple of in-game movies in the tutorials don't play but this does not preclude gameplay. This is a problem that will soon be over since the libraries that do this (mfplat, Microsoft Platform Foundation Libraries) is one of the most worked wine areas recently. But in the meanwhile you can fully play the game without these small movies.
Works out of the box with the Valve Index.
For a brief moment when the movie is loading a test pattern appears. Must be a small flat animation played by mfplat (Microsoft Foundation Platform Libraries), which at this moment are not 100% on proton, although being heavily worked on. But the moment is so brief -- a couple seconds -- that it really doesn't make any difference.
Worked out of the box. I played it in VR with the Valve Index. Everything works.
Works flawless, but not sure if multiplayer works. Valve Index.
This is a relatively new game with a very small public. So I could not find an online server to play a match and test multiplayer. If might not be any problem with Linux/Proton, might be due just to the small size of the game. But there's a single-player mode anyways...
Flawless out-of-the box experience
Very frantic game, I cut my hand playing it.
Flawless out-of-the box experience
Very frantic game, I cut my hand playing it.
Game does not start and/or perform ok unless you disable ESYNC, FSYNC (I have a kernel with fsync enabled) and lastly, in the configurations, vsync. For that in properties, launch options use the string: PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
One year later and the apparently simple issue preventing the game from working is not resolved.
The bug report is here: https://github.com/ValveSoftware/Proton/issues/4024 -- there has not been any activity in one year. Issue seems simple, just get a default binding for the game to work -- everything else seems to be in order, you can see the menu and options and even your own hands, you just cannot interact. But the most unnerving part of the experience is that you have no resource to try and fix yourself -- if you call the steam overlay to change the bindings, the Create Binding button does not work. The bindings screen shows an error message. The "choose another binding" button also does not work. I asked why it's this way on the steam bug report and got no response.
As the controls do not work, the game is basically unplayable.
It seems the headset position was switched with the controllers position. The weapon and teleport beam would be right in front of the headset and the menus would also appear at its sides. Opened a bug report for that: https://github.com/ValveSoftware/Proton/issues/4946 -- however, the game is unplayable this way.
It works with the special build of Proton Experimental made by Paul Gofman, a Valve employee.
Besides the position of the controllers sometimes drifting, they would not stop vibrating, even with haptics turned off in-game.
This is my second proton report now that the game is playable. Bug report on proton's github is here: https://github.com/ValveSoftware/Proton/issues/4946#issuecomment-878244774 -- as you can see in the bug report, Paul Gofman came up with a solution that makes the game playable and made his fixes available through a proton experimental build here: https://www.dropbox.com/s/lfnhf7466owwjr3/experimental-6.3-MR15-554-20210712-p1e0b6d-w0c53d20-ded3aac.tar.gz?dl=0 -- you unpack it to ~/.steam/root/compatibilitytools.d, restart steam and choose this version in the compatibility tab of the game properties. If you are reading this report months after it has been made, the fixes will probably already be in regular proton. When they do I will create a third report.
It works with the special build of Proton Experimental made by Paul Gofman, a Valve employee.
Controller always vibrates when you press the grip. This is discussed in the bug report by @gofman and it's unlikely that it will have a solution.
This is my second proton report now that the game is playable. Bug report on proton's github is here: https://github.com/ValveSoftware/Proton/issues/4946#issuecomment-878244774 -- as you can see in the bug report, Paul Gofman came up with a solution that makes the game playable and made his fixes available through a proton experimental build here: https://www.dropbox.com/s/lfnhf7466owwjr3/experimental-6.3-MR15-554-20210712-p1e0b6d-w0c53d20-ded3aac.tar.gz?dl=0 -- you unpack it to ~/.steam/root/compatibilitytools.d, restart steam and choose this version in the compatibility tab of the game properties. If you are reading this report months after it has been made, the fixes will probably already be in regular proton. When they do I will create a third report.
Works out of the box. Player with Meta Quest 3 via ALVR.
Also tested two DLCs, they work great too.
Game is playable, the working multiplayer seems to be similar to the single-player experience
Intro videos would not run, this is resolved by applying the mf-install trick for installing Microsoft Media Foundation libraries in the game's pfx path. https://github.com/z0z0z/mf-install
Singleplayer does not seem to work. It gives an "unknown error" OK dialog, then bugs out and stays at an unresponsive screen, you have to kill the game process.
Worked flawless out of the box, using Valve Index.
The game has a slight performance issue, but it is the same on Linux as it is on Windows. So it's the game fault, not proton's.
This game now works in VR on Linux, including controls. Played with Meta Quest 3 via ALVR.
Good experience, if it does not work out of the box try running with Proton Experimental.
First time I ran the VR hands would not appear, couple times later it worked (with Proton Experimental).
Played with the Valve Index.
Everything works out of the box. Played on Meta Quest 3 via ALVR.
Absolutely flawless execution out of the box with Proton 6.3-6. Valve Index.
There is a report from other user where it says it did not work on Proton 6.3. For me it worked right out of the box, freshly installed. No issues, very performant, no instability.
Worked out of the box. Flawless gameplay. Valve Index
I was invited to try a pre-release version of the game, that's why this is an early report.
Works flawlessly now, after Valve has updated Proton to handle CEG DRM.
This game is one of the games which use the old Steam DRM CEG (Custom Executable-Generation). Proton Experimental bleeding-edge has been recently upgraded to be able to run them, and it will soon land in Proton Stable. So that's why it did not work before, but now it's running well.
Does not seem to work in VR (Valve Index, Proton 5.13-1 and 5.09-1)
A black window appears and some background voices are heard and it gets stuck there. Cursor is locked to the window, so you have to interrupt it to get out and it then crashes SteamVR.
Worked out of the box. No adjustments needed. Even automatically detected my ultrawide screen, impressive that a 2013 game is that good.
I did not experience game not exiting (no exe remained, checked through ps) like some other person here. Everything went really flawless.
Crashes with an unreal crash screen at the start (Valve Index).
Opened a bug report for it here: https://github.com/ValveSoftware/Proton/issues/6351 -- will resent a report if it ever becomes playable.
It seems that it doesn't run in regular proton yet but it's just a matter of time until it's updated.
Everything worked out of the box.
Game is still in a rough state, almost beta, but this is not exclusive to Linux.
There is some quirkiness to start the game, but otherwise it works well.
There's some audio without subtitles, some audio which is not heard at all, and in the intro there are some weird desynch noises which eventually disappear. Most of it seem to be bugs from the game itself.
Calling the Steam Overlay with shift-tab most times lead to the game crashing. Which is mildly annoying since I had to call it to dismiss the "key activation" message. But I eventually did it.
Problems with the Steam Overlay. Also, the first time the game is run it only shows Ubisoft Connect, not the game window. Had to quit ubisoft connect and press play again for the game to launch.
The game uses Ubisoft Connect, which (as the name says) connects to the Internet. Might not work offline.
No cutscenes, otherwise very good compatibility
Cutscenes would not play because of lack of mfplat (Microsoft Foundations Platform). Installed mfplat using a rogue mfplat.dll 64 bits I have around and https://github.com/z0z0z/mf-installcab but it still did not work.
First, in the game properties, set it to the latest proton (at this time, 8.0-2) and run it once. Then, in desktop mode, open firefox and download this ja2.reg file: https://drive.google.com/file/d/1L8GRDqhVa0cy1XWP5WN0a8gsKSopBHFS/view?usp=sharing -- put it under the default Downloads folder. Then via discover install protontricks and in the console run it via: flatpak run com.github.Matoking.protontricks 215930 regedit and you will be in the regedit window. Go to the menus and Import Registry file, go to the downloads folder and choose the ja2.reg file and import it. If you are curious, these are the contents of this file (in DOS format): https://gist.github.com/Patola/23139357904e1a23140dc873006157f8 -- after you import this key, you can exit the registry editor (no need to save) and change back to gaming mode to run your game. It will work for Wildfire but if you have the Classic JA2 DLC it will work for that one too.
Game won't start if you don't add a registry key. Weirdly enough, on a regular Linux desktop it automatically adds that registry key and game runs ok.
This game just does not start with versions of Proton I've tried
I've tried current Proton (6.3-7), Proton Experimental, Proton-GE-6.15-GE-2, Proton 5.13-6, and all of them have my GPU driver crash at the first splash screen, right after I set the graphical settings in the dialog -- for any settings that I choose.
Works (almost) perfectly out of the box. Might hang on first launch, but afterwards everything works flawlessly.
First time I launched the game shortly after having installed it, it would stay "running" in the background. I had to "stop" it and launch again, and then everything worked perfectly.
Played with the Valve Index, Proton 5.0-7. Game ran out of the box, but again, media files won't play.
Some media files would not play (e.g. in the computer screens of the tutorial), probably due to Microsoft Platform Foundation Classes (mfplat). Tried to use mf-install, mf-installcab and Proton-5.8-GE-2-MF to no avail.
Almost everything works correctly out of the box, only the movies in screens throughout the game need mfplat. Performance is very good.
Movies in screens throughout the game will not play without mfplat (Microsoft Foundation Platform Libraries) installed. Currently you need to use https://github.com/z0z0z/mf-install for it to work, incoming versions of Wine will try and fix that. Even with mf-install (and mf-installcab), the small window on the laptop from the start will not play though.
Runs out of the box, no tweaks, no crashes. Proton 5.0-8, Valve Index, Ubuntu 20.04
Apart from sparse minor graphical artifacts, works perfectly. Valve Index.
There are some flickering textures and things like branches changing shape. But I think that's from the game itself, not particular to Linux.
Multiplayer (coop) works, but it's very difficult to find someone to play with. Also, this game was not working in previous proton versions but it's now fixed.
Works perfectly out of the box.
My previous report was on Valve Index, now I tested it on Meta Quest 3 via ALVR.
Played in VR -- needs the windows version. Works perfectly out of the box with the Valve Index.
Although it uses the gamepad/keyboard instead of the haptic controllers, the controls are very intuitive and comfortable.
Works out of the box but has weird controls. Using Meta Quest 3 via ALVR.
Mapping is not exactly pristine and game's controls are cumbersome and if you change them (using Steam Input) during the gameplay, it may need a restart lest inputs will not work.
Everything worked out of the box with regular proton.
I recommend turning off Async Reprojection on this game because it can get very flickery. Bring up the overlay and on the settings choose per-application video settings. If you only see a throttle option, wait for the actual options to appear, it might take a few seconds.
Tried on the Deck and on a Linux PC. Both have the same behaviour. Opened a bug report at Valve's bugtracker: https://github.com/ValveSoftware/Proton/issues/6003
For the game to start properly, you have to delete one movie file and a directory with movies. Go to /home/deck/.local/share/Steam/steamapps/common/Lost Ember/LostEmber/Content/Movies/ and delete file Mooneye_Reveal_Logo_1920.mp4 and the entire directory MooneyeLogoAnim. After that, the game starts and works as normal.
The same game as regular Lost Ember, but with VR, third person.
The Valve Index controllers are as of now not yet supported, the same as Windows (joystick works). Not sure it will work with the Oculus Controllers (via ALVR) that it supports, I will have to try it later.
Runs OK in proton.
I had to run it under Proton because for some reason the native version would only present a black screen.
Got it from itch, game runs perfectly on Valve Index. Excellent performence too.
Added by "Add a Non-Steam Game" dialog, then pointed to the executable and in the properties selected Proton 5.13-5 and the VR option. Then just pressed play when SteamVR was running. Easy Peasy!
You might know me from other protondb reports -- I enjoy creating builds that allow games to run, and in the case of larcenauts, this is the build: https://github.com/Patola/wine/releases/tag/wine-experimental-patched -- it includes some patches that aren't still in proton but enable some games -- specially VR games -- to work. You just need to add it to Steam it like you do with Proton-GE. Before downloading random stuff from the internet, see my history on github, on steam and here on protondb to ensure I am trustworthy. BTW: I also opened the bug report for Larcenauts on the proton bugtracker, https://github.com/ValveSoftware/Proton/issues/5452
It crashes shortly after the first game scene and takes SteamVR down with it, needing a reboot to settle.
Opened a bug report at valve's bugtracker: https://github.com/ValveSoftware/Proton/issues/4614
It crashes shortly after the first game scene and takes SteamVR down with it, needing a reboot to settle.
Opened a bug report at valve's bugtracker: https://github.com/ValveSoftware/Proton/issues/4614
With Proton up to 5.13-6, the game crashes usually at the start. There's a bug report for that at https://github.com/ValveSoftware/Proton/issues/4614 -- if you have a later proton, chances are it is already fixed. I was able to run the game with the following launch options: "PROTON_NO_FSYNC=1 %command", using Proton Experimental as of March 5, 2021.
Valve Index
Be sure to use an updated proton (later than 5.13-6) and turn off FSYNC. This way the game will run great.
With Proton up to 5.13-6, the game crashes usually at the start. There's a bug report for that at https://github.com/ValveSoftware/Proton/issues/4614 -- if you have a later proton, chances are it is already fixed. I was able to run the game with the following launch options: "PROTON_NO_FSYNC=1 %command", using Proton Experimental as of March 5, 2021.
Played with a Valve Index VR kit.
Great experience, with great performance too and it allows using FSR. Valve Index.
- At first execution, it wouldn't let me set the graphical options. I quit the game then launched it again, then it worked.
- As usual with OpenXR games, the game doesn't exit completely, you have to force it to exit through Steam.
Game works OK, the controls are wonky though. Valve Index.
I don't understand exactly what's going on in the game, but it seems that it's just bad controls -- Windows seems to have the same problems.
Worked perfectly out of the box.
It's getting boring doing these reports, everything is working out of the box
Just installed and play. No issues whatsoever. No adjustments/tricks. Worked as a purely native game, on ultrawide display 2560x1080.
In Proton 8, 9 Beta and Experimental the screen gets black and you see your hands in the shape of yellow arrows, but it never passes from this part.
vcrun2015
If you do not install vcrun2015, game gives you a black screen at the start and won't proceed from there.
Works out of the box with Proton stable, but has performance issues.
Jitter and stutter due to the horrible performance. Turn linux async reprojection off on ALVR or if you use Valve Index go to video settings after starting the game and turn legacy reprojection on.
As some people have noted here, the performance of this game is quite bad. Additionally, due to the bad performance, if you use ALVR to stream and have Extra → Linux async reprojection turned on, the screen gets jittery and stuttery, so TURN IT OFF at least for playing this game. I would advise turning antialiasing off. Use render scale in the middle or lower for better performance.
I also turned up brightness to the maximum, otherwise I just couldn't see anything. My headset (Quest 3) is not particularly dark and works well with other games.
It works very well with good performance on patched WiVRn. Using a Meta Quest 3 via WiVRn. Under ALVR it is almost unplayable.
I was running the game via ALVR but it was really nigh unplayable. The performance hit of SteamVR on this game is huge even in my RX 7900 XTX with a bit of overclocking. So for the game to be playable, the best option would be to ditch SteamVR using monado/wivrn. So I installed envision and ran wivrn but it failed to run it. I opened a bug report here: https://github.com/WiVRn/WiVRn/issues/232 and also on the monado bugtracker here: https://gitlab.freedesktop.org/monado/monado/-/issues/479 -- and I have also generated a patch to be used with envision, download it by clicking on "raw" on this gist: https://gist.github.com/Patola/4a033c9df7da8f7c388ca33012419efc -- on WiVRn, it runs MUCH faster than ALVR and virtually no stutter or reprojection. After putting the .patch file under ~/.local/share/envision/wivrn/patches/monado/, call envision, click on the burger menu, select "Clean Build Profile" and wait for it to finish then click on 'start'. Now you will be able to play Metro Awakening
Worked out of the box, no adjustments needed. Took a while for steam initial setup though.
Works out of the box with Proton Experimental. Valve Index.
Does not work with Proton 6.3-5. Works only with Proton Experimental.
Provided you don't care much for thumbstick turning, game runs flawless.
There is a known problem on Valve Index and HTC Vive where it doesn't do thumbstick turning. This is the same on Linux and Windows. Last message from developer about this is in 2019. The game is completely playable but you might need to keep turning around physically.
Some people are saying to run with old versions of proton (e.g. 4.11). Don't do that, you can make it work with current versions. Just run "protontricks 275850 win7" and protontricks will change proton to disguise as Windows 7 instead of Windows 10, and then the multiplayer parts will work perfectly.
The controllers appear below the ground, so you can't interact with anything.
This is a known issue for Windows too and the developer stopped updating the game, so this is unlilkely to get fixed. Windows users have different VR streaming options like Virtual Desktop and Steam link and one of them works, but we only have ALVR so it's no hope for us. Tried with a Meta Quest 3 via ALVR.
Aside from mfplat issues, game seems completely playable. VR with Valve Index used.
mfplat (Microsoft Platform Foundations Libraries) problem, so some videos don't play. So far does not seem to prevent progress and this is going to be resolved soon in Proton, with heavy development promising to fix that.
Flawless experience. Worked out of the box and without any issues.
Works out of the box. Small problem with videos. Valve Index.
A few movies show the test pattern, mfplat problem. Should be fixed in future proton version (current one is 6.3-5). Does not preclude the rest of the 'game' - which is a noninteractive experience, actually.
Tried in flat and VR mode (Valve Index). Both work wonderfully and out of the box.
The mirror image of the game in the screen does not show the overlay, which makes that view unsuitable for streaming or youtube recording.
Works out of the box. At start, it might seem to hang, just wait some time. Valve Index.
Absolutely flawless experience out of the box. Played with a Valve Index.
At the start of the game it might seem that the controls are not working, because you stay a couple minutes in the same spot without being able to move around. But this is just part of the game, and works the same way as in Windows.
Games was broken on Linux since June 2023 due to Easy AntiCheat.
The steam forum thread, no response from the developer. Like other reports said, it should be very easy for the developer to fix it, but Linux invisibility probably has a role in that continued issue: https://steamcommunity.com/app/555160/discussions/0/6516193260178494399/
PLUGIN_FEATURE_RANK=protonaudioconverterbin:NONE %command%
If you don't use a proper version of GE-Proton after the little hat you'll have a black screen. I haven't tested it much but it seems to be playable, in the proton github issue there is talk of graphical artifacts but I didn't notice any so far.
Do not believe naysayers who say this game has performance problems.
This game has basically the same performance as Windows, with a difference. When you run it for the first time, or when you change graphical settings, it slows to a crawl. Maybe it's compiling shaders? I don't know, but just keep playing the game and the performance will catch up.
Do not believe the naysayers about "performance problems", read my explanation.
This game has basically the same performance as Windows, with a difference. When you run it for the first time, or when you change graphical settings, it slows to a crawl. Maybe it's compiling shaders? I don't know, but just keep playing the game and the performance will catch up.
Also, I mostly play the game in VR (using the Valve Index), and everything worked out of the box, from the controls to the voice input. No fiddling necessary.
This game suffered a regression, in an update it started depending on three microsoft libraries which were not implemented in wine-proton. So I opened a bug report for documenting that regression and a friend (EsdrasTarsis) helped by developing patches for two of these libraries and reusing a wine patch for the third one. The bug report is here: https://github.com/ValveSoftware/Proton/issues/4969 -- and the patched proton that can run this game is here: https://github.com/Patola/wine/releases/tag/6.3-pickupbasketball -- if you are reading this protondb report months after it has been created, it is likely that the current proton version already implemented this fix.
Works flawlessly under Proton Experimental. Valve Index.
At this time does not work under Proton 6.3-5, only Proton Experimental. Apart from that, it works flawlessly.
Games works flawlessly out of the box. No issues
Take note that the game is a little raw and lacks options. Nevertheless, it's free, so at worst you would lose your time and 1.23 GB on your disk...
Game works flawlessly out of the box.
Take note that the game is somewhat raw and lacks options. But as it is a free title, the most you'd lose is a bit of your time and about 1.23 GB on disk.
Game is unplayable. Can't play it for 15 seconds.
It hangs a few random seconds after every game is started. Sometimes it hangs even in the menu. And it crashes hard hanging SteamVR with it, most times I have to reboot my PC. I am using a Valve Index with the game.
Fades to black, then either hangs or crashes.
Opened bug report at valve's github: https://github.com/ValveSoftware/Proton/issues/4492 -- also talking with the game's developer to make it work: https://steamcommunity.com/app/810500/discussions/0/2985287984615866234/
Game needs "-noradio" flag to start. Otherwise it will crash after a black screen. The developer fixed that for us Linux users, I am just updating my report.
Works out of the box. Played with Meta Quest 3 via ALVR.
This is a great indie alternative to the Powerwash Simulator and even has pretty girls on it.
Everythimg works out of the box, including the online account if you choose so. Valve Index.
Played in VR, which works perfectly on Linux with the Valve Index. This is an awesome VR game.
As others noted, you'll need a bethesda.net account and the registering process is kind of awkward, but feasible.
Works great out of the box. Played on Meta Quest 3 via ALVR.
There is another report saying something about video playback problems. I haven't seen these but I completed the tutorial with no issues.
Everything works flawlessly out of the box. Played with a Valve Index.
Everything works flawlessly out of the box. Played with a Valve Index.
cmd=(%command%); cmd[-1]="$(echo "${cmd[-1]}" | sed 's#RFVR/RFVR#RFVR/RFVR/Binaries/Win64/RFVR-Win64-Shipping.exe#')"; "${cmd[@]}"
The game initially starts with a file explorer window in the screen (not in VR). You can navigate to Binaries/Win64 and run RFVR-Win64-Shipping.exe by clicking on it and the game will start, or you can save the effort and use the launch options I provided that will always run the correct executable.
Online multiplayer works correctly including voice communication. But please note that due to this being a VR title with few players, usually you don't even find a server to connect. I was lucky to find one.
Doesn't start in the laptop with NVIDIA. Using Meta Quest 3 via ALVR.
I have the exact same setup with an AMD Radeon and there it works.
Flawless, out of the box experience on my Valve Index.
Beware, it has no thumbstick turning (whether on Windows or Linux).
Flawless, out of the box experience on my Valve Index.
Beware, it has no thumbstick turning (whether on Windows or Linux).
Works flawlessly out of the box.
Please note that on the Valve Index the game does not have turning by controller. It's the same way on Windows, it seems.
Works flawlessly out of the box.
Please note that on the Valve Index the game does not have turning by controller. It's the same way on Windows, it seems.
Flawless experience, aside from the Valve Index incompatibility it's perfectly playable even in multiplayer.
On Valve Index, you can't turn with the controller -- the same thing happens on Windows since the Valve Index is unsupported. You have to turn in real life. This might be a minor annoyance depending on your setup.
I have not experienced the performance problems other reporters say they do. Game is fluid and responsive.
Audio works wonderfully for anything from 5 to 30 minutes, then stops. Restarting the game fixes it. It's annoying.
Almost flawless, including no performance problems and no glaring reprojections on a NVIDIA RTX 2070 SUPER + Valve Index. The only flaw is indeed the sound stopping.
Game starts in the screen instead of the headset. Controllers still work (Valve Index)
Opened a bug report for it: https://github.com/ValveSoftware/Proton/issues/6106
-dx11
If you don't use the -dx11 flag it crashes with a "fatal error!" dialog window.
Works well with some tinkering. Complete instructions are included.
This game would work out of the box if not for the need of wmp11 libraries from Windows. To install them, fallow the instructions below.
you'd use protontricks, but due to Proton 5.13 and later versions using symbolic link on their prefixes to save spaces (with the target being protected against writing), the installation fails to overwrite them. So you need to do this: 1: before installing, ensure you set it to Proton 5.0-9 on the compatibility tab. If you have it installed, uninstall it first. 2: run the game once, you can set options like resolution and antialiasing if you like. Don't start the campaign. 3: run protontricks -q wmp11, wait for it to finish (lots of output, hopefully no "Permission Denied" errors and lots of deadbeef stub warnings). 4. On the properties/compatibility tab, change it to the current proton version, or just uncheck "Force the use of a specific Steam Play compatibility tool" and it will use the one in the general steam settings (hopefully the latest one). 5. Launch the game. At the time, everything should work. You should see the cutscenes and you can play the game. 6. If you use widescreen, there's an additional fix: edit (STEAM PREFIX)/steamapps/compatdata/222480/pfx/drive_c/users/steamuser/AppData/Local/CAPCOM/RESIDENT EVIL REVELATIONS/config.ini and change the Resolution field to the resolution of your monitor, then change Aspect to DEFAULT, then make this file read-only (chmod a-w (STEAM PREFIX)/steamapps/compatdata/222480/pfx/drive_c/users/steamuser/AppData/Local/CAPCOM/RESIDENT EVIL REVELATIONS/config.ini, of course change (STEAM PREFIX) to your game's steam prefix.
Shows a "failed to initialize graphics" error message. Playing with Valve Index.
Opened a bug report for this issue at the proton bugtracker, https://github.com/ValveSoftware/Proton/issues/8210
The game works but the controls are bad and it is a very short experience. Valve Index.
Played through Proton because of VR, which is not present in the Linux version. I am using a Valve Index.
Movies in screens throughout the game would not play. Probably because of lack of mfplat (Microsoft Foundation Platform libraries). Incoming Proton versions will address this issue.
Framerate was low in VR, I did not see the numbers but I estimate about 30 fps, even in low graphical settings.
Works flawlessly on the Valve Index.
I couldn't test multiplayer, seems there is little public so it's difficult to find anyone online.
If you apply my procedure, the game runs flawlessly, no issues.
The game won't start if you just click play, so don't to it the first time. For it to work, it has to be in the same WINEPREFIX as Spore. To accomplish that: 1 - first install Spore, run it, fill in the settings, exist; 2 - install SPORE Creepy & Cute Parts Pack (using the same Steam Library Folder, that is, don't change the library; by default steam installs in the same library as before if you don't select other), but don't run it.
Then, go to the library compatdata directory. If it's home, it's ~/.local/share/Steam/steamapps/compatdata; if it's something else, say /games, it's /games/SteamLibrary/steamapps/compatdata -- and then link this game appid (17440) to the spore appid (17390), e.g.
cd ~/.local/share/Steam/steamapps/compatdata;
rm -rf 17440; (this is just to erase any remaining wineprefix for this game)
ln -s 17390 17440 (this links spore and this game together)
Works right out of the box. Absolutely no issues. Valve Index.
Works out of the box with Valve Index. Flawless experience.
Works out of the box, flawlessly. I was able to log in to EA, just haven't even tried multiplayer because of previous reports.
I have a Valve Index and it also works flawlessly in VR with my Radeon RX 6800 XT. It does not support the use of the knuckles controllers (it is clearly said in the game store page), but it's the same as Windows, so no problem. Proton 5.13-4.
Game seems to run flawlessly. Valve Index.
It's a very short game, it seems you can complete it in 7 minutes. That was not my case, in my first playthrough I died after the 15 minutes time.
At this time regular proton doesn't work, my patched proton does. Read below. Valve Index
This game has the same prerequisite to work as GangV, a patch that adds a few bluetooth functions (e.g. bthprops.cpl.BluetoothFindNextRadio) to wine, created by @EsdrasTarsis. Currently it does not work with regular proton (6.3-6b), so you'll have to use my patched build: https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd -- first look at my contributions here and in github to ensure I'm trustworthy, because you should not run random stuff from the internet. You can also check the compatibility bug report for the game that I also created: https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd -- so, in short, game fully works, including the coop multiplayer and voice communication. Note: I made a previous report saying the game was not working, because I had only started to test it. Disregard that report.
Almost flawless experience.
Occasional disconnections, the old known problem of "fresh supplies". Just keep trying.
Now with the latest Proton Experimental which I used, VOICE CHAT works correctly! I'm in Poland and my friend is in Brazil and we noticed no lag, everything went smooth!
Absolutely flawless gameplay, graphics and controls. And the game is amazing.
Valve Index, Proton 5.13-5
Works very well, although needs remapping of inputs. Meta Quest 3 via ALVR.
If you use meta quest via ALVR, the game will ask you to keep pressing the thumbstick to move and turn, which is annoying. Instead, go to the steam overlay, click on the game's thumbnail, go to the controllers binding and choose a community mapping that will fix this issue.
Also tried through WiVRn in place of ALVR/SteamVR, but it didn't work. Will try again in the future as WiVRn improves. I wonder how the input remapping will be done.
No movies played, used both mf-install and mf-installcab
Videos do not play which precludes the game from starting but you have to (1) use proton 4.11-13 (maybe change to windows 7 via protontricks 471010 winecfg) (2) use both mf-install and mf-installcab from https://github.com/z0z0z
Works out of the box. Played with Meta Quest 3 via ALVR.
Impressive performance and graphics for a VR game, with detailed asteroids and ships.
I always customize the controls further, for every game. This is not a demerit for this one.
Cloud saves are currently not supported.
Need mf-install as per the other entries (https://github.com/z0z0z/mf-installcab), however it must be said that the game stopped working again after an update (the "Fatal Error" dialog window appeared) so you might have to re-install mfplat or even the whole game after updates.
Blanks the screen and plays some music, but the menu never appears in headset or screen.
Opened a compatibility bug report for it: https://github.com/ValveSoftware/Proton/issues/6626
Flawless experience, runs out of the box and it's very performant. Valve Index.
Flawless experience. Just install and play. Using Valve Index
Everything works out of the box, including the startup screen/dialog. Played all DLCs on Ultra, no issues at all.
Works amazingly well if you use the right adjustments. It might worth trying running it via gamemode too, although I haven't tested it.
Ok, here is the thing. I am sending this particular report because another report said to limit the game to 3-6 physical cores, but did not provide the means to do so. Here is the way to do it, with an explanation: you'd wait for the main process "Subnautica.exe" to spawn and would then use taskset to set is cpu affinity. You'd choose starting from CPU 2 (because CPU 1 is CPU 0 hyperthreaded) and go up in even numbers to step over the hyperthreaded cores. So if you have 12 cores, you'd use: 2,4,6,8,10. If you have 16, you can go up to 15. I have tried several combinations of cores, from 3 to 6 as the original poster said, and none of these attempts would have more FPS or smoother gameplay, on the contrary, they were reliably slower and with small lockups. So it seems Subnautica does indeed runs well in multicore -- at least in a kernel with fsync() (Valve's mfutex) patched in and enabled like liquorix or tkg.
But if you want to try the CPU affinity tip nevertheless, here's how: in steam properties -> launch options, if you want cores 2,4,6,8,10 to be used, use the string: (while ! ps -A | grep 'Subnautica.exe'; do sleep 1; done; sleep 1; taskset -c -p 2,4,6,8,10 "$(ps -A | grep 'Subnautica.exe' | awk '{print $1}')") & %command%
I am running the game with Proton-4.11-13, because I mostly run the game in VR (yes, VR works perfectly in this game) and this is the only build that works, I added this detail to the bug report here - https://github.com/ValveSoftware/Proton/issues/613
Game works well, still a little crude, with no matchmaking. Playing with the Valve Index.
The game sometimes crashes to the desktop. It's expected, it's early access at this time. Nevertheless, works well under Proton 6.3-5.
Be warned that it has super long waiting times, like 5-10 minutes between transitions. Better install it in a SSD.
I always customize my game controls. I never use defaults.
DXVK_ASYNC=1 %command%
Changed a few keybindings like using the left trackpad for zoom (T and G). It works best as K&M; joystick controls are cumbersome.
Once it hung while trying to quit the game.
If you use the regular Steam for this game, the game is stuttery all the time, in a quite unpleasant way that interferes with gameplay. For the stutter to be completely gone, you need to uninstall the game (so that it cleans the shader cache and pipelines), install GE-Proton (I used 7-38) and enable dxvk-async on the launch options, then install and play the game.
Apart from a couple videos not playing, game runs flawless.
A few movies won't play due to mfplat issues (which will be resolved in a future version of Proton -- current is 6.3-5). But this does not prevent any gameplay.
Shows a black screen then a dialog with "Fatal Error", then bails out. Using Quest3 via ALVR.
Added the diagnostic comments and proton log to the proton bug report: https://github.com/ValveSoftware/Proton/issues/7627
Changing graphical details, specially fullscreen/windowed caused the game to crash in regular Steam Proton. In Proton-GE however it worked flawlessly.
Changing to fullscreen (ultrawide display) crashed always in steam proton. In Proton-GE (from GloriousEggroll) it worked flawlessly.
Black screen at start (Proton-5.13-4). Also tried with Proton 5.0-10 (does not even start) and others. Tried z0z0z's mfplat too.
I always create a bug report at Valve when the game does not work, so here you have, you can follow the troubleshooting here: https://github.com/ValveSoftware/Proton/issues/4511
The game uses mfplat, so to be able to run it I had to enforce Proton 5.0-10 on the compatibilty tab and run the cursed mfplat scripts for the prefix: https://github.com/z0z0z/mf-install and https://github.com/z0z0z/mf-installcab -- after that everything worked, including the unskippable cutscenes.
SteamDeck=0 %command%
Configured my own buttons so that no gamepad input was sent to the game.
30 fps lock
The default configuration for this game on the deck is nothing short of terrible, to the point that I consider it sabotaged. Read the thread here: https://steamcommunity.com/app/979690/discussions/3/3320862598750530211/ -- ok, so to just magically fix most problems, you have to provide the SteamDeck=0 variable to the launch options, and also use an input configuration for mouse and keyboard (not physical ones, but e.g. the touchpad as mouse). It doesn't fix the 30fps lock though, but at least with that the game is playable and you have an "exit to desktop" option!
Works flawlessly now, after Valve has updated Proton to handle CEG.
This game is one of the games which use the old Steam DRM CEG (Custom Executable-Generation). Proton Experimental bleeding-edge has been recently upgraded to be able to run them, and it will soon land in Proton Stable. So that's why it did not work before, but now it's running well.
Runs perfectly now, after proton has been updated to handle CEG games.
This game is one of the games which use the old Steam DRM CEG (Custom Executable-Generation). Proton Experimental bleeding-edge has been recently upgraded to be able to run them, and it will soon land in Proton Stable. So that's why it did not work before, but now it's running well.
Apart from the voices, game works great out of the box.
Audio work but voices don't. To fix it install xact: protontricks 611670 xact and in properties/general/launch options use WINEDLLOVERRIDES="xaudio2_7=n,b" %command%
Probably a future version of proton will not require the xact trick since faudio2 is progressing rapidly. For the record, I used Proton-5.0-9 to run it.
Most sounds including conversations do not work without using that command: protontricks 611670 xact
Ok, Skyrim VR runs great out of the box with Proton 4.11-13 and Proton 5.0-9 and possibly others, but it is a crude game without too much of VR customization, specially for powers and weapons. The VRIK mod does this but it asks for a DLL injector called SKSEVR (Skyrim Skript Extender VR) at http://skse.silverlock.org/. However, for a DLL injector to work, you need a very small patch for proton's wine that can be found here: https://github.com/hdmap/wine-hackery/tree/master/f4se -- so I forked Proton's wine, I applied a patch I am making for recognizing all HOTAS buttons, and this small patch, and I made a github release in my proton's wine fork here: https://github.com/Patola/wine/releases/tag/proton_skyrimvr -- you just need to download the tar.gz and uncompress it under ~/.steam/compatibilitytools.d/, then go to Skyrim VR (I guess it might work with Fallout VR too, or Skyrim SE, etc.), properties, "Force the use of a specific Steam Play compatibility tool", and choose proton-skyrimvr-5.0-9. Then you will be able to use SKSEVR to extend functionality and install VRIK. I recommend you install all your mods with the Nexus Mod Manager via Lutris, that's what I do and it works great. For installing SKSE though you will need to do it partly outside of NMM, because it needs two dll's and an exe in SkyrimVR directory. Also, for launch options you have to use that: WINEDLLOVERRIDES="xaudio2_7=n,b" %command% You can also download the tar.gz from mega: https://mega.nz/file/SdIChKiD#QXI5U5GKtmS2d_XWMdnnJGFpYzrZqjvwhNodASqQmX8 -- I am not anonymous, the file can be compared to the github release, the code is there in github, so you are safe, this is not a trojan. You can always contact me on Steam or github for doubts and help on this, if needed.
protontricks 3193770 vcrun2022
If you don't install vcrun2022 via protontricks it will show a dialog box in the screen saying you the Microsoft's Visual C++ runtime installed and exit after you press OK.
Works out of the box and has no stability / disconnection issues. Valve Index.
There were only old reports of the game (2+ years), so I reinstalled from scratch with Proton 6.3-5. No issues at all, besides the braindead control scheme of this game (which is the same as on Windows). No controller disconnection, no flickering, no crashes.
Works out of the box and has no stability / disconnection issues. Valve Index.
There were only old reports of the game (2+ years), so I reinstalled from scratch with Proton 6.3-5. No issues at all, besides the braindead control scheme of this game (which is the same as on Windows). No controller disconnection, no flickering, no crashes.
Works out of the box with Valve Index, notwithstanding the weird control schemes.
Not sure if controllers are not mapped incorrectly, but this game has some inconsistency in handling controls in Windows too, so it's the same.
There were only old reports for this game, so I reinstalled from scratch with a modern proton version to see whether it would work.
Works out of the box with Valve Index, notwithstanding the weird control schemes.
Not sure if controllers are not mapped incorrectly, but this game has some inconsistency in handling controls in Windows too, so it's the same.
There were only old reports for this game, so I reinstalled from scratch with a modern proton version (6.3-5) to see whether it would work. It did.
The game works but not in VR. Valve Index.
Tried the VR mode of the game. Does not work. Opened bug report at https://github.com/ValveSoftware/Proton/issues/5115
Sometimes with details on ultra, the game hangs. Seems to not occur on medium and low settings.
This demo/free prologue stopped working due to a new dependency of an application notify API, not implemented in wine. @EsdrasTarsis made a patch with stubs (empty functions) for that API and now the game works. I have made a build with the patch (and a few other patches for other games). Before considering downloading, please see my history here and in github, you should not download executable stuff from random people in the internet. https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd
I reassign controls for all my games, I prefer my own layout always.
A very minor glitch when saving the game is that for a brief moment at the right panel the thumbnail of the game screen appears then disappears. But the thumbnail does appear when loading savegames. It has no impact on gameplay whatsoever.
Different from the desktop, on the Deck it doesn't require turning off fsync and esync with launch parameters. Also, it has writings with small letters at some scenes but I found them to be perfectly legible, but I reckon some people with vision problems might not be ok with them.
The game runs in low resolution if some conditions are not met, like 60Hz. To prevent this, edit the the file "/home/deck/.local/share/Steam/steamapps/compatdata/24880/pfx/drive_c/users/steamuser/Documents/My Games/The Saboteur™/SaveGames/config.ini" and ensure that: ScreenWidth 1280, ScreenHeight 800, RefreshRate 60 and add the line Windowed 1. If you don't add this last line it will likely run in low resolution, even in the Deck OLED.
Game crashes to an unreal crash report dialog. Tried with Meta Quest 3 via ALVR.
Created a compatibility report here: https://github.com/ValveSoftware/Proton/issues/8338
Some movies (like the initial splash screen) don't play in current proton (6.3-6). If you change to a proton that has mfplat (Microsoft Foundations Platform libraries) enabled, like the latest Proton-GE, they work. But that's not a big deal. Even without the movies, the game is fully playable with no issues.
Apart from the dumb VR issue, game runs great out of the box.
For VR users, this game just presents a black screen when you press play. That's because it tries to open the VR channel and gets stuck. If you start SteamVR, it will work (in the main screen, not in VR).
Couldn't even start the game.
physx
Opened a bug report on valve's bugtracker: https://github.com/ValveSoftware/Proton/issues/7606
In Wayland, the game only starts if using gamescope with the monitor resolution. In Xorg, it doesn't need any launch parameters.
gamescope -w 3440 -h 1440 %command%
physx
If you are using Wayland, for some reason this particular game cannot initialize the video and doesn't even start. So after some attempts, I found out that using gamescope with my monitor's resolution (3440x1440) makes the game work correctly (adapt the launch parameters to your resolution, of course). Also, don't forget to use protontricks to install physx, and click on the dialogue for the installation to complete.
As with the others, got a "Fatal error" at the start.
Different from the others, I actually created a proper compatibility bug report at proton's bugtracker: https://github.com/ValveSoftware/Proton/issues/6356
Just fix the controller bindings as I instruct and you should be fine. Game runs beautifully.
With the Aftershock update, the Valve Index knuckles stopped working not only on Linux, but on Windows too. The symptoms are clear, your VR hands do not appear in-game and you obviously cannot interact with menus and controls, so you can't even start a game. To fix that, call the overlay menu by pressing the system button, then choose "controller bindings". The top of the Window should indicate "Walking Dead: Saints & Sinners" and not "OpenXR Test Instance", if it does not, wait a little or exit this window and select controller bindings again. Then select "Custom" on the slider, and press the button to choose the bindings. You might have to wait a little more for that window to populate with the Community Bindings; amongst them, choose "Liam's Foot" that makes the game work again. You might have to exit the game and restart SteamVR after ensuring this binding is correctly activated.
This one works out of the box. Meta Quest 3 via ALVR.
Although it is not as severe as the previous installment, this one also has a problem with weird mappings on the quest touch controllers. You might change some inputs or choose a different mapping via ALVR.
protontricks 34330 d3dx11_42
The protontricks fix is necessary to play the game with directx 11. If you instead choose directx 9, it should run with no tinkering. The fix was taken from the proton compatibility report: https://github.com/ValveSoftware/Proton/issues/7110 -- and also, if you prefer to run the native version which doesn't work anymore, another bug reports has a potential fix: https://github.com/ValveSoftware/steam-runtime/issues/613
Worked perfectly right out of the box.
The current game has received massive patches and it's very different from the old one. It's a complete game now.
Works out of the box. Valve Index.
I could not try multiplayer - the server finder could not find any public server. I guess that's expected with such a low population.
The game runs perfectly.
It's still in early access. I hope the developers do not add options like speech recognition from microsoft libraries that do not work on Linux.
Apart from the dreaded uplay, game works great. Using Valve Index kit.
As others noted, the couple first attempts to run the game fail because of uplay. Once you get it working, though, the game should run fine, and everything works, from graphics to controls.
Just fails to start. Using Oculus Quest 2 via ALVR to play the game.
Opened a bug report to track this issue: https://github.com/ValveSoftware/Proton/issues/5335 -- when my Valve Index gets back I will test with it.
It now works with my proton experimental build. Read below.
The game still doesn't work with regular Proton, but my proton experimental build runs it, at https://github.com/Patola/wine/releases/tag/wine-experimental-patched -- installation instructions included there. As usual: don't download random stuff from the internet without checking, first ensure I am trustworthy by looking at my github history and if needed, protondb and steam status.
Worked out of the box, absolutely no issues. Played the first mission with no hiccups. Proton 5.13-5
Dark Souls of VR! LOL.
It went into a black screen and made my steamvr crash once or twice when leaving the game. But only then. Playing the game did not show any issues whatsoever.
Just take note of the asynchronous reprojection settings and the game should run fine.
This game has conflicts with Asynchronous Reprojection on AMD and won't work if it is turned on. You can turn off only for this particular game by opening up the steamvr overlay when the splash screen appears, then selecting video settings, then change "Legacy Reprojection" to on. This way the game will work even on AMD hardware. For NVIDIA, you don't need to do that, it will work regardless of the setting. Currently I am running under Proton Experimental, but I think the fix has already been committed to Proton 6.3-6.
Played the game on Valve Index with both AMD RX 6800 XT and NVIDIA RTX 2070 SUPER.
Everything works out of the box. Played with Valve Index.
Flawless experience, except for the weird splash screen in the screen instead of VR.
When the game starts, it presents a window in the screen instead of VR. But shortly afterwards the game starts in VR correctly. This is a small weirdness that in the end is harmless.
Works flawlessly out of the box. Valve Index
Works well but doesn't play tutorial movies.
A couple of in-game movies in the tutorials don't play but this does not preclude gameplay. This is a problem that will soon be over since the libraries that do this (mfplat, Microsoft Platform Foundation Libraries) is one of the most worked wine areas recently. But in the meanwhile you can fully play the game without these small movies. You can also watch the movies on youtube if you need to know what they say.
-game Unofficial_Patch
Used protontricks (running .exe in the wine path) to run the installer for the Unofficial Patch. After that, added the -game Unofficial_Patch to the parameters.
The game has a known problem with input when it runs in gaming mode. It won't register any keystroke, be it with the virtual keyboard, a key configured in the input settings from the buttons, or a USB keyboard. For these to work, you have to play the game in desktop mode, it works well BUT if the input configuration you selected has a graphical menu overlay it won't show, so that's why I have to create my own with no use of menus.
Well, this game is bugged par excellence, so that are lots of little quirks and annoyances, but it's sort of the same in Windows. Often I can't tell if a bug is from running on Deck or intrinsic to the game. But it's playable and so far has good performance on regular Proton 7.0-4 in desktop mode.
After you go to all the trouble to make the game playable, it is worth it.
Everything works absolutely perfectly. And it's a great Dishonored-like game. (Using Valve Index)
You can't start the game from SteamVR, you have to launch from Steam and select the option from the dialog "Launch Vermillion with system default OpenXR runtime", otherwise it won't work. Also, you HAVE to have the steamvr overlay working (press the system button once to check) when launching the game.
Videos don't play. Tried installing mfplat (mf-install, mf-installcab) but then it prevented the game from starting, and I had to remove the proton prefix for it to play. Also tried running with Proton-GE and ther was no difference.
It's quite fragile with the conditions to start. Besides only starting with the "default OpenXR runtime" option, sometimes I would have to restart SteamVR for it to work.
The tutorial videos can be found on youtube, so it's not a big issue for them not to play in-game.
WINEDLLOVERRIDES="MSVCR80=n,b;MSVCP80=n,b;SpeedTreeRT_Yup=n,b" %command%
protontricks 211160 vcrun2015
BEFORE you can run the protontricks, you have to remove two files in the /steamapps/compatdata/211160 prefix that are actually symbolic links: pfx/drive_c/windows/system32/msvcr80.dll and pfx/drive_c/windows/syswow64/msvcr80.dll -- the msvc2015 tries to overwrite these, and as the link target is protected against rewrite, the msvc2015 installer will fail. If you do remove these just prior to run protontricks, it should work and the game will start normally.
Opened a bug report: https://github.com/ValveSoftware/Proton/issues/6297 -- will update if fixed.
Prior to that report, with Proton 7.0-4, the game was not leaving its splash screen. Now it's working normally and fully.
Works perfectly without any issues with regular Proton 6.3-7.
Runs flawlessly. No issues at all. Proton 5.13-4, Valve Index, Ryzen 7 3700X, Radeon RX 6800 XT.
Shows a Unity window crashing.
This is just my first report. Next steps are to open a bug report at the proton bugtracker and try to fix it up myself, either with parameters, code or different versions of proton. I'll send a new report if I can get it working.
As promised from my previous report (if it is published at all), it was not working but together with a friend (Esdras Tarsis) we were able to patch proton to make it work. So, as for other games, I have made a proton build with the patches while it doesn't get to official proton. Please look at my history here in protondb and github first to ensure I am reliable, do not download random stuff from anyone from the internet. Build is here: https://github.com/Patola/wine/releases/tag/protola_6.3_rbespbgvwd -- and the bug report is here: https://github.com/ValveSoftware/Proton/issues/5072
Works out of the box.
It works on my main gaming PC but it's not currently working on the Steam Deck, it loads the initial screen for a couple minutes then crashes. It seems like a memory leak bug with the steam client and it might be solved quickly, I will send a new report when it's working. Meanwhile, the bug report can be seen here: https://github.com/ValveSoftware/Proton/issues/6463
There is the odd crash that occurs but that's because it's early access, occurs for everyone. It's getting more stable by the day.
The VR eyes are shifted, making it impossible to play.
There's a bug report open for it: https://github.com/ValveSoftware/Proton/issues/6449 -- it seems some people get it to run with various workarounds, like setting resolution to 150% then back to 100% again. These tricks did not work for me.
PRESSURE_VESSEL_FILESYSTEMS_RW=$XDG_RUNTIME_DIR/wivrn/comp_ipc:/var/lib/flatpak/app/io.github.wivrn.wivrn %command%
If you have a Meta Quest headset, instead of ALVR use WiVRn -- it doesn't even use SteamVR: https://wivrn.github.io/ -- that was the only way I could solve the "eyes apart" bug which otherwise made the game unplayable. Its setup is nice and easy and should not interfere with your other VR games.
If you try and use ALVR, the game will show the two eyes wide apart, to the point it makes the game unplayable. Instead of ALVR, use WiVRn at https://wivrn.github.io/ -- its setup is easy and simple with autodetection, it's available as flatpak and it doesn't even use SteamVR, having lots more performance due to that.
Don't worry too much about that launch parameters strings -- if you use WiVRn, it will show it to you and allow you to copy it with one click.
For some reason, Warframe doesn't even start in my rig.
Tried with many different protons, reinstalled in different locations, tried many parameters and variables, no change. Reported the issue on Valve's bugtracker for the game, https://github.com/ValveSoftware/Proton/issues/167 -- note: I have thousands of other games currently running in the very same rig.
Everything worked out of the box. No tinkering. VR game, using Valve Index.
Not sure if protondb will say I don't have the game on Steam, but I do. I bought the game as soon as it was released, played about one hour of it and created the report.
Runs out of the box and everything works with great performance.
It seems older versions of proton did not run this, but the current one does great. Proton-GE is not needed.
I always customize all my controls
Currently the game is not working in gaming mode due to a gamescope issue: https://github.com/ValveSoftware/gamescope/issues/993 -- for the game to pass the shader compilation progress bar, you have to play the game in Desktop mode.
Game has performance issues but that's universal, not particular to the Steam Deck. It also uses Easy Anticheat but different from Vermintide, it's compatible with Linux. Do not forget to have the Easy Anticheat Runtime installed to run.
Absolutely perfect. Stellar performance, no crashes, everything just works.
Game is fun as hell. Highly recommended.
It's not working with Meta headsets (via ALVR).
I also have a Valve Index and the game works with that one. The issue with this is known by the developers and also affects Windows, where only if you use Virtual Desktop you can play using a Meta Quest 2/3 -- Steam Link does not work. Maybe there is a way to make it work but I've tried fiddling with ALVR options and even emulating Vive/Knuckles controllers to no avail. Might be worth it to try via WiVRn.
Shows a black screen at the monitor and not in the headset. Using Valve Index.
Opened a compatibility report at https://github.com/ValveSoftware/Proton/issues/7629
Free MOBA, tried with Valve Index. Seems to work ok, although the input scheme is weird.
An input issue makes the game unplayable, you can't walk or turn.
With the Valve Index, you can’t walk or turn, the left and right thumbsticks do not work. When you go to the bindings window, the game name appears as “OPENXR TEST INSTANCE”. This way the game is utterly unplayable and can be considered BORKED. Opened a bug report at https://github.com/ValveSoftware/Proton/issues/5192
Several other games face a similar issue, including the “OPENXR TEST INSTANCE” classification. Valve never explained that.
An input issue makes the game unplayable, you can't walk or turn.
With the Valve Index, you can’t walk or turn, the left and right thumbsticks do not work. When you go to the bindings window, the game name appears as “OPENXR TEST INSTANCE”. This way the game is utterly unplayable and can be considered BORKED. Opened a bug report at https://github.com/ValveSoftware/Proton/issues/5192
Several other games face a similar issue, including the “OPENXR TEST INSTANCE” classification. Valve never explained that.
Proton 5.0-9, Valve Index. Game crashes right at the start, taking SteamVR with it.
The game supports Vive-like (including Index) controllers only, because the oculus executable depends on the oculus runtime thus does not run on Linux. But if you use ALVR for streaming to e.g. Meta Quest 2 or Meta Quest 3, you can change the controller emulation to be for Vive Wands or Valve Knuckles and the game will work correctly. As it also accepts mouse and keyboard entries, you can also map your controllers via steam input to work.
At this moment it is only working with Proton Experimental branch bleeding-edge, but with time the fix (from gofman) is going to reach regular experimental and then Proton stable.
Apart from the slight stuttering, everything works great.
There is some stutter in cutscenes. Nothing too concerning.
Apart from the slight stuttering, everything works great.
There is some stutter in cutscenes. Nothing too concerning.
As have already been told here, you need to skip the 2K Launcher with the following launch options: bash -c 'exec "${@/2KLauncher/LauncherPatcher.exe/Binaries/Win64/xcom.exe}"' -- %command% -- Once you do that, game starts successfully. Tested with Proton 6.3-2, you don't need Proton 5.0-10 for the game to work now.
Runs out of the box now, with Proton 6.3-5. No adjustments needed.
Take note that previous reports tells the game only runs without the 2K launcher, but this is in the past, now everything works. However, I feel that it is important to mention the option to skip the launcher as a "comfort" option. Go to the game properties, and in the "General" tab, use these launch options, exactly as written: bash -c 'exec "${@/2KLauncher/LauncherPatcher.exe/Binaries/Win64/xcom.exe}"' -- %command%
Runs out of the box now, with Proton 6.3-5. No adjustments needed.
Take note that previous reports tells the game only runs without the 2K launcher, but this is in the past, now everything works. However, I feel that it is important to mention the option to skip the launcher as a "comfort" option. Go to the game properties, and in the "General" tab, use these launch options, exactly as written: bash -c 'exec "${@/2KLauncher/LauncherPatcher.exe/Binaries/Win64/xcom.exe}"' -- %command%
Works OUT OF THE BOX with Proton 5.0-6. Everything works, from cinematics to gameplay.
Works flawlessly out of the box with great performance. Valve Index.
Its multiplayer is "asynchronous", which means you race against "ghosts" of other people who raced the track. That worked perfectly. Player vs. player was not implemented at the time of this report so I could not test it. And the tournament was over too.
With regular Proton 6.3-7, a few movies don't play due to the old mfplat problem. This does not preclude gameplay, and other cutscenes and animations play just fine. Nevertheless, if you are adamant on getting them to play, just use Proton-GE instead -- I tried with Proton-6.15-GE-2 and the movies worked fine.
Zueirama has a native Linux version which gives a Black screen. Just use the proton version.
Go to properties, compatibility, then set proton to the latest version. Other than that, the game runs exceptionally well and the controls are very cmfortable on the Deck.
