Feline Fowl
Published
- Game will show a black screen if using Proton 4+, as another report mentioned the game won't work. However, using D9VK, the game does work! Your launch option string should now look like
PROTON_USE_D9VK=1 %command%
Game audio stops after a while, but this is probably a bug with the game and nothing to do with Proton. If you know this game, then you'd probably assume the same...
4.21-GE-2 GloriousEggroll
I used Proton 4.21-GE-2, which for some reason works, but 4.11-11 does not. You no longer need the launch option PROTON_NO_D9VK=1 as DXVK and D9VK have been merged into one project. I'm not sure why 4.11-11 didn't work for me, but oh well! To install:
- Download the archive from the GitHub link above
- Make a folder in
~/.steam/steam/calledcompatibilitytools.d - Extract the folder in the archive to the newly created folder above. Note: The archive will extract into a folder automatically, so there is no need to extract into or create a subfolder
- Restart Steam, then select the game, click on the gear icon on the far right and go to "Properties"
- From here, tick the bottom box that says "Force the use of a specific Steam Play compatibility tool"
- Select "Proton-4.21-GE-2" from the dropdown
- Launch the game!
Later versions of Proton with more up-to-date libraries should work, but for now use this custom version of Proton to get up and running with the game.
I thought it was native until I checked the store page
It ran with absolutely no issues in my tests
Worked perfectly without problems
Had no issues playing this game on Linux, I did not even realise it wasn't a native game until checking for this report!
Tested at max settings, lowering could help. Performance varies from 50fps on the title screen, 70fps on the ship and 30fps in Mafia Town. Didn't try any other stages. There are some minor texture glitches that occur for a few seconds. It's definitely playable, just not as nice of an experience as on Windows.
Some strange graphical glitches, and even on my beefy PC the performance still isn't up to scratch with Windows. Putting the graphical settings at a little above console level gets the game to run at a fairly consistent 60fps in menus and the hub, but only about 45fps in levels (tested Mafia Town and the first level of the Seal the Deal DLC)
Performance isn't perfect, but you can get a solid 45fps+ at medium-high settings with V-Sync off. There are some missing textures here and there, but it's extremely minor and nothing game breaking (at least in Mafia Town). There is some small artifacting with textures every so often, but it only appears for a split second and then disappears. Something I'm experience in the latest version of Proton is a crash when finishing a level and trying to start a new one. It's quite irritating, but maybe I just need to reinstall the game. Overall, it's a nice experience - a perfectly playable one, but those minor issues bring it down to Silver.
tl;dr use D9VK and disable esync for near-native performance with max settings. No more crashes between levels, though performance isn't as good as using galliumnine. Steam Controller works perfect. Full report: Disable esync (right click > Properties > Set Launch Options > "PROTON_NO_ESYNC=1 %command%") as this fixes stuttering and slightly extended load times, and install D9VK for a massive performance bump. You can do this by either building Proton with D9VK yourself, or you can follow these instructions to install it to a pre-existing Proton prefix: Launch A Hat in Time at least once after installing if you haven't already, as Steam needs to create the Proton prefix. Go to this link (https://github.com/Joshua-Ashton/d9vk/releases) and download the latest package. At the time of writing, it's "0.12". Extract it anywhere, then set your WINE prefix to wherever the prefix for A Hat in Time is by running "export WINEPREFIX=/path/to/library/folder/steamapps/compatdata/253230/". In the same Bash session (i.e. same Terminal window), run "./setup_dxvk.sh install". This should take all of about 30 seconds. Again, run with esync disabled and you're good to go! At max settings (excluding motion blur, which I disabled for personal preference) and fps capped at 60 I got equivalent if not better performance to Windows - That is to say, occasional stutter when generating new effects i.e. using the Scooter or using the Witches Hat bomb thingy. With the framerate unlocked I stayed around 70-90fps. At the end of some time rifts, when you're hitting the rift with your Umbrella or whatever, framerate dips to 27-34fps. D9VK seems to fix the crashing every other level, which means you don't have to worry about game crashes. I didn't test any online features or anything beyond Mafia Town and Dead Bird Studio. Galliumnine did give about 120-140fps (Massively beyond native performance) but not only does this break the Steam overlay - making the Steam Controller unusable - but the load times are exceptionally long; about 2-4 minutes per level and 5 minutes for the game to start while running on a Samsung SSD. The game also crashed every other level, meaning you could only play one level at a time. The same issue is present with standard DXVK/WINE OpenGL. With D9VK, while CPU usage is a bit higher the experience is overall much better. A seamless experience with D9VK.
Install D9VK and install Esync to fix performance (see other reports on how to install D9VK, very quick and easy). Played through the entire base game (no DLC levels) and tried out one Death Wish level. In my 20 hours of playing, the game crashed about 7 times. 4 of those were on a loading screen, 2 were mid-game (one at the end of Chapter 3 Act 1, and one during the first Death Wish level) and one was in Chapter 2 Act 1 - This crash is an interesting one because it's the only consistent one. If you put on the sunglasses in Dead Bird Studio, the game will freeze after about 4 seconds. This not only crashes the game but also the entire system. You need to reboot after this crash. I don't know if this happens when DXVK or if it's a problem with Mesa or what, but I'm sure with updates to both it'll get fixed. Modded levels work fine, as do asset swap mods, custom hats, etc. Full workshop support in my testing. The game usually hovers around 70-90fps and has some stuttering when loading new effects, for example the explosion with the witch hat. Very very minor details. Perfectly playable and extremely enjoyable. If it weren't for the crashes I'd forget that the game wasn't native.
Install D9VK and disable esync, detailed in previous reports, for almost perfect performance. Playing a Chapter for the first time might take about 45 seconds to load, but subsequent loads will be about 15-20 seconds (depending on stage - Alpine Skyline and Nyakuza Metro take a little bit longer than the others). Played through a Challenge Road with no issues (just minor stutter) and the entire Artic Cruise DLC stage. I only experienced two crashes in the 10 or so hours it took to complete. I also played a couple of Death Wish levels and they worked fine - Including the one that initially crashed. Speaking of crashes, the lockup encountered in Dead Bird Studio with the sunglasses seems to now be fixed! That, combined with the reduction in crashes, means really the only thing keeping this game from having a Platinum rating is having to install D9VK. I played about 5 minutes of Nyakuza Metro and performance is decent. Hovers around the 45-60fps mark, compared to the rest of the game being 70-90fps. However I am playing the game at max settings, and I haven't tested this specific level on Windows. Don't let this deter you, as without the FPS counter it's not all that noticeable - and even with the counter the game is still fully playable. Again, if not for needing performance tweaks then the game would have a Platinum rating. DXVK on it's own gives such low performance for the game, hence why I recommend D9VK and subsequently disabling esync. I have yet to try the online multiplayer, though I plan to test it out soon. Most likely after completing and reporting back on the performance of the Nyakuza Metro chapter. A very small note: After installing the Challenge Road DLC stages and restarting the game ( only after restarting and not while playing), the game was using about 80% CPU. Exiting to the main menu and resuming the game fixed this issue. RAM usage also skyrocketed. It hit a peak of 6GB, though currently it's at 4.5GB. I only noticed this after playing the Nyakuza Metro chapter, so I can't say for sure if it's the mods or stage or something else entirely. I'll look into it some more. Some other misc points: No graphical glitches with D9VK, game runs at max with 70-90fps in most cases, mods work, controllers work (tested with Steam Controller), Steam API works (provided you don't use galliumnine), achievements work, all DLC works, game can be completed from start-to-finish. Overall, a very nice experience and thanks to Proton I'm getting addicted to the game all over again.
Install D9VK, disable esync, and you're good to go. D9VK fixes the rain flashing glitches, however performance still takes a hit (this happens on Windows also though). The Online Party multiplayer works, and cutscenes work - It seems it was an update to the game that fixed this. I believe it was sometimes broken on Windows too and the latest game update addressed it. Solid performance, fullscreen, borderless and windowed mode all work, and the Nyakuza Metro DLC chapter - while the worst offender in terms of performance - is fully and comfortably playable. Updates to DXVK/D9VK should only improve how this game runs.
Install D9VK (either through downloading it and pasting the DLL into the Hat in Time folder, or using the installer script that comes with D9VK), disable esync (PROTON_NO_ESYNC=1) and you'll get native performance. I get slightly better performance with D9VK, but it's marginal. Played with everything at max, including motion blur. Of course vsync is off as is recommended for pretty much all games even on Windows, and framerate locked to 60fps for my own preference. Some minor dips to 58 during gameplay, Nyakuza Metro brings the framerate down to about 40fps, loading screens are about 28fps, and the game has pretty much no crashes. Sometimes trying to load some Subcon Forest levels will crash the game but it's very rare. Tested two challenge roads and they all worked perfect, Death Wish works perfect, I have about 80 mods installed from the workshop and they all work, and the online multiplayer works as well. I've only played with a party of 3 (including myself). Local co-op works, console commands work, everything works. The game is basically running like native and it is a joy to play with Proton.
Using the builtin Proton tweaks, the game runs more than comfortably. If you install the third-party tool developed by Feral Interactive (they handle a lot of native-Linux and macOS game ports) called Feral GameMode (available in the AUR or here: https://github.com/FeralInteractive/gamemode) you can get that extra little bit of smooth performance. Online works, mods work (I have a ton installed), game may stutter a little bit the first time you load it up but I can run at max settings INCLUDING VSYNC at a full solid 60fps. I didn't have any of the online crashes mentioned in previous reports. Use the following launch options, leaving out "gamemoderun" if you do not intend to use the tool, to get pretty much native performance: "PROTON_NO_ESYNC=1 PROTON_USE_D9VK=1 PROTON_LARGE_ADDRESS PROTON_FORCE_LARGE_ADDRESS_AWARE=1gamemoderun %command%"
Disable esync, using the Large Address Aware flag, use D9VK, and you can run the game at max settings. Use Feral GameMode optionally for even better performance. I can run the game, including mod levels, with all settings at max without dipping below 60fps. Capping the framerate can help reduce stutter, but this goes for all games and not just A Hat in Time, and not even just Proton games. It basically runs like native - And I play with a ton of mods.
Large Address Aware fixes crashes when loading big levels e.g. Subcon Forest and Alpine Skyline, and also mod levels
CPU Governor set to "Performance" helps reduce stuttering. You can do that with this plasmoid or by using Feral Gamemode.
- Capping at 60fps helps with stuttering
- Tested using keyboard and mouse and a Steam Controller
- Tested with an ungodly amount of mods - Like with Windows, load times are increased as you add more mods (especially if you're launching the game after freshly installing a mod), but they all work. Challenge roads are included
Works flawlessly with D9VK, esync disabled, large address aware, ACO driver and CPU governor correctly set
- Use
PROTON_USE_D9VK=1to vastly improve game performance, fix some slightly broken textures and almost entirely fix every other issue with the game - Disable
PROTON_NO_ESYNC=1to help with stutter - Use
PROTON_USE_LARGE_ADDRESS_AWARE=1to fix crash when loading big levels i.e. Subcon Forest, Alpine Skyline or mod levels
- Use Valve ACO driver to completely remove stuttering (if you are able to use it)
- Use Feral Gamemode for the final fine-tuning of performance, including setting your CPU governor to "Performance" (which you can also do with this plasmoid)
Final thoughts:
- Tested the game with everything at max settings. Just like with Windows, frame capping at 60fps and/or vsync enabled will help with GPU load (I tested with both of these, haven't experienced any frame dips)
- Tested game with Steam Controller and an excessive amount of mods
- Game may become slightly more unstable with mods. I noticed that when I install a new mod, the game takes a long time to start up again and also CPU usage is way too high for the first 5 minutes or so of playing. A simple restart of the game fixes this completely and I believe it happens on Windows, too, but it's worth mentioning
- No Linux-specific issues when the tweaks I mentioned were applied. Assuming you plan to use them all, put this string in your launch options:
PROTON_USE_D9VK=1 PROTON_NO_ESYNC=1 PROTON_USE_LARGE_ADDRESS_AWARE=1 gamemoderun %command%
Base game, all DLC, local and online multiplayer, and mods all work perfect; performance requires tweaks
PROTON_NO_ESYNC=1: This massively helps to reduce stuttering for the gamePROTON_USE_LARGE_ADDRESS_AWARE=1: Stops crashes when loading large levels such as levels in the Nyakuza Metro DLC, or Subcon ForestPROTON_USE_D9VK=1: A Hat in Time uses Direct3D 9 and not Direct3D 10/11, which the standard DXVK is designed for use with. Using D9VK, which is optimised for Direct3D 9 games, gives A Hat in Time a HUGE performance boost
- For Intel processors at least, you'll want to set your processor P-State to "Performance" instead of "Powersave". Doing this will drastically reduce CPU load on the game, which can cause stuttering due to bottlenecking. Use Feral GameMode or this plasmoid to do this.
- Use Valve's ACO driver if possible to completely remove all performance issues
In total over the last year since my first report, I have tested the game for about 60-70 hours with Proton and it has steadily improved. Now we're at the stage where the game works like a dream with the right tweaks. Below are some extra notes about my setup while playing:
- Use tweaks mentioned to fix performance
- Ran the game at highest settings, including testing with vsync on. Once performance tweaks were applied, everything worked like native
- Tested with Steam Controller and some custom controller configurations, no issues
- Tested local co-op with Remote Play Together and encountered no issues
- Tested Remote Play to stream the game from my PC to my phone and then later to my laptop. No issues encountered
- Tested a lot of mods, loading times were increased but this is not related to Proton and happens on Windows too
- The high CPU usage when installing a new mod and launching the game for the first time seems to be fixed
- If you're using all launch options, including Feral Gamemode, your final launch option should look like this:
PROTON_USE_D9VK=1 PROTON_USE_LARGE_ADDRESS_AWARE=1 PROTON_NO_ESYNC=1 gamemoderun %command%. If not using Feral GameMode, simply removegamemoderun. Once applied, the game will work perfect!
For me, game worked great without any launch options, but adding them greatly improved the experience
- Disabling esync removes stutter on my Ryzen CPU
- Forcing Large Address Aware can help reduce crashing for larger levels (although I didn't experiencing crashing on my newer hardware)
- Using D9VK vastly improves performance
I'm using Mesa 19.3.0 with ACO enforced globally (a faster shader compiler developed by Valve). Right now, ACO is only for AMD cards. You can read more here, on Valve's official Steam blog post. For testing instructions with Valve's fork (based on Mesa 20.0.0-devel), see here.
If you're using Mesa 19.3.0, you can set Mesa to use ACO on a per-game basis by adding
RADV_PERFTEST=acoto your launch parameters. You can also set an environment variable to force Mesa globally (for all users). To do this, edit the file/etc/environment(with root privileges, e.g.sudo), and add the lineexport RADV_PERFTEST=aco
- On my hardware the game ran without any issues at the default settings, aside from low framerate in some mod levels and minor stuttering. But on my old hardware and for the majority of people, I highly recommend adding the launch options! That's why I opted to write a tinker report
- Tested with Valve ACO driver and with Mesa, and on my RX480 the ACO compiler made a huge difference. This is part of Mesa now. Use aforementioned tweak to get it to run with newer Mesa (I'm using Mesa 19.3.0 now with ACO enforced globally for all games)
- Tested with a Steam Controller, and it worked fine and was recognised out of the box. On Linux and Windows, it's recognised as an Xbox 360 Controller, but it doesn't impact gameplay at all
- Tested with a lot of mods installed and tested out some mod levels. They all worked great! In the past, I've played some Challenge Road stages and they worked fine too
- Tested with the Seal the Deal and Nyakuza Metro DLC. Online Party works great, have not recently tested local co-op but I intend to try it out with Steam Remote Play Together. I see no reason why it wouldn't work, however
- Note: RAM usage can reach up to 10GB from the game alone in my tests. This was during playing with some large mod levels and the Nyakuza Metro DLC. I haven't checked usage in Windows, so it could be the same. Keep it in mind, though
Your overall launch option string should look like: PROTON_NO_ESYNC=1 PROTON_FORCE_LARGE_ADDRESS_AWARE=1 PROTON_USE_D9VK=1 RADV_PERFTEST=aco %command%. If you're not using ACO, remove the RADV_PERFEST variable
PROTON_NO_ESYNC=1helps with some of the stuttering in the gamePROTON_FORCE_LARGE_ADDRESS_AWARE=1fixes the game crashing when loading larger maps such as Subcon Forest and mod levels
So long as you use the two launch flags, your game will run smooth as butter!
- Tested with a Steam Controller and Keyboard/Mouse
- Tested with all settings at max, no issues at all
- Tested with all the DLC, no problems
- I've played through the entire game on Proton, from a blank save file up to the end of Nyakuza Metro
- Online Party works great
- Local co-op works great
- Tested a wide array of workshop mods from asset replacements, to custom outfits, items, hats, and custom levels, they all work great
- Challenge Roads work no problem
- I've played a good 50+ hours under Proton and have only experienced a handful of crashes, all of which appear to be fixed now
Played with a ton of mods @ 900p60 Windowed (Low Settings)
Game works at a stable 60fps with Proton 6.3 on this laptop. Uses up a lot of RAM especially if you have a lot of mods. Tested with a Steam Controller and a huge assortment of random mods and custom levels, didn't experience one crash. Had to play with all the settings at low, but it worked really well!
gamemoderun %command%
Online Party mode works no problem even with mods
Brief test of local multiplayer over Remote Play Together worked
Played almost 100 hours of this game on Linux and for the last while it's worked out of the box without any tweaks. Feral GameMode might help a little with higher graphics settings and resolutions to get the most out of your GPU but overall it's a perfectly fine out-of-the-box experience as well. Just remember to enable the FPS cap!
- Played with KDE Plasma Wayland
- Played with a Steam Controller
- Played with 50+ mods enabled and had no problems
Flawless experience, controller works even though keyboard hints may be shown, but this is unrelated to Proton
Tested with Steam Controller and over various versions of Proton ranging back to 3.16 and onward. Never had any issues whatsoever.
Works out of the box with Proton 7.0-2, played at 1440p max settings
Very slight performance degredation in some areas but not overly noticeable
- Didn't try a controller.
- Played online (other player was on Windows) for over 3 hours without any issues other than what appears to be very slightly degredaded performance. Not that noticeable most of the time though. Overall, worked amazing!
Native and Proton have identical performance at max settings, native had some windowing problems that can be resolved with Gamescope
gamemoderun %command%
Tested native Linux and Proton, both performed identically.
- The native version didn't like my multi-monitor setup on KDE Plasma Wayland but Gamescope fixed this
- Needed framerate cap with both games as it put enormous strain on my GPU, MangoHUD or DXVK can cap the frameate, or you can use Vsync
After double clicking on the North America region, I was able to connect and play games online successfully
- Initially could not connect to multiplayer games and could only view one region. Resolved by clicking on the Region selection button (bottom right corner of the "Online" menu) and double clicking the North America region. This allowed me to connect to games and also, optionally, change my region.
- You may need to install
winbindon your system. This is available from different packages on different distributions.- On Arch Linux, it is in the
sambapackage (sudo pacman -S samba) - On Debian based distros, you can install the
winbindpackage (sudo apt install winbind)
- On Arch Linux, it is in the
- Did not need any additonal launch options, though if your GPU does not support Vulkan (or if you do not have Vulkan 32bit and 64bit installed) you may need to use
PROTON_USE_WINED3D=1 - Did not have any issues with alt+tab, no issues around input either. Other reports mentioned this, it seems to have been fixed
- All audio worked
Works great, online issues were probably my network and not Proton
Other player reported significant input lag but I doubt this was specific to Proton (played with Remote Play Together)
Native Linux works perfect, it detected my Steam Controller without any problems.
PROTON_NO_ESYNC=1- The game drops down to around 30fps while loading areas for the first time (even if it seems like it should have already been loaded in a cutscene). Disabling esync greatly mitigates though does not completely eliminate the issue.- It also massively helps with load times, cutting them down from 6-7 seconds to less than 2 usually on my SSD.
- Proton-6.12-GE-1 was used to fix the main menu backgrounds not displaying, audio sync issues, and give a noticeable performance boost.
- Feral GameMode was used to boost performance.
- Set the Windows version to "Windows 7" in
winecfgfor an additional performance bump.
- Game had a strange white border around it when windowed. This is a game bug however and not specific to Proton.
- Game does not adequately support keyboard/mouse. This is a design decision for the game, and completely unrelated to Proton.
- There is a bug on the materials section of the results screen where you are stuck to the last option and cannot move to select the other materials without being sent to the bottom of the list. It appears to be a game bug and not specific to Proton
I should preface my expeirence with the fact that I am running on a budget laptop, if it wasn't clear from my system specs. I'll retest on my main PC in future. The tl;dr is that the game runs very well with my specs and reasonably well overall.
- Game runs relatively well in my tests (up to the end of the first mission), once everything had loaded there was no real performance impact with esync disabled.
- Disconnecting my external monitor gave a more stable framerate, but it wasn't a big issue for me so I kept it connected
- Played at 720p windowed, with all settings at the lowest. Did not attempt to increase any settings.
- Tested with a Steam Controller
- Tested with desktop compositing enabled (KDE Plasma)
- Disabling may help with maintaining framerate
Overall, a very enjoyable experience on Linux with this hardware, so much so that I feel confident playing further.
With recent versions of Proton, the font and crashing issues have been fixed. Game runs like native out of the box.
Native works without any problems
Tested with a keyboard/mouse and a Steam Controller. Game works perfectly for me. Did not try Proton
A little bit of stutter at first, but once I played for a bit everything worked great
Workshop stuff works fine too
- Battlefield 4 uses "PunkBuster" Anti-Cheat, however the game has an issue (also happens on Windows) where even though during the install it says everything is fine, you'll get kicked from every multiplayer match. To fix this, you'll have to manually download PunkBuster for Windows from the site, and run the EXE via Wine: https://www.evenbalance.com/pbsetup.php
- I recommend putting this EXE in its own folder, as it downloads some extra files. Run it with the same prefix that Battlefield 4 uses, so run the game at least one time and then close it. Then run
WINEPREFIX="/path/to/library/compatdata/1238860" wine pbsetup.exe. Select "Battlefield 4" from the dropdown, and point it to the game's install folder if it didn't find it automatically. It might take a while to download, but it'll complete and Battlefield 4 multiplayer will work!
Make sure you're running Proton 5.0-9!
- Origin failed to run for me initially saying that it couldn't log me in, but after running the game again I could log in without issue
- Origin complains about not being able to find game files, but you can ignore this as it doesn't impact the game at all
- Battlefield 4 might take a while to appear, it takes about 10 seconds or so after Origin opens for the game window to appear
- I tested 20 minutes of the campaign and about 10 minutes of the multiplayer, they both worked fine. There's a tiny bit of stutter on the first load of a map if you play at max settings
- I played with all the graphics settings turned up, and while it worked fine I opted to turn motion blur off for my own personal preference
I haven't tested much of the game, but what I have tested works perfectly!
Fix the saving issue with this patch (https://bugs.winehq.org/show_bug.cgi?id=42982), and here's a guide on how to install custom Proton patches using Proton-tkg by TkGlitch (https://www.reddit.com/r/SteamPlay/comments/bgym4t/how_to_apply_a_wine_patch_to_proton_prefix/epqudl4/). - The game runs and runs with great performance out of the box, however you won't be able to change settings. The game will whine about not being able to save data, though you'll still be able to play. But the next time you try to launch the game, it'll just load to a black window. You'll need to delete the Proton prefix in "/path/to/steam library folder/steamapps/compatdata/460790". It's a folder just called "pfx" if you're unfamiliar. Install the patch mentioned above to fix this. Framerate stays at 60fps consistently, and cutscenes are locked at 30fps. This isn't anything to do with Proton, I just wanted to mention that in case you see it and panic. While I have not played the game myself on Windows it runs perfectly for me in the small hour I played, once the patch was applied. It also runs fine no matter what drive it's installed on, unlike with Windows where it whines if it's not in the default Steam install folder. tl;dr - install patch, game works at max settings, solid 60fps.
Use the patch mentioned previously in other reports (either with ProtonTKG or otherwise) and you can adjust settings. Regardless, framerate is a solid 60fps, excluding cutscenes which are locked at 30fps. If the patch was not needed, this would be a Platinum title.
Game runs flawlessly out of the box at max settings, without using D9VK. However, there are very very VERY minor dips to 55fps for about half a second in some areas. To fix these, you can use the launch option PROTON_USE_D9VK=1 %command%. It is unnecessary in my tests, but as it is technically a Direct3D 9 game, you'll get marginally better performance if you use it.
Works fine with the latest versions of Proton (4.11.1 and up)
Everything works out of the box now. No need for custom WINE patches to fix the game. Using PROTON_NO_D9VK=1 can improve performance ever so slightly, but it's not that noticeable unless you're constantly looking at that FPS counter. Overall, perfect compatibility with Proton.
Worked without any problems
- Tested with Steam Controller
- Achievements work
- The game has some bugs, but these are not related to Proton!
Works out of the box at max settings with 120fps+ without any launch options (Tested 8 hours of gameplay)
Use -nointro in the game's launch options to skip the annoying, lengthy opening splashes (you can do this on Windows, too). In my tests, disabling esync made no difference. Textures are blurry for about 5 seconds when loading new areas, but they load in very quickly.
Outside of this, runs out of the box.
Disabling esync is not required at all, it just speeds up texture load times and fixes random hangs when trying to hack or save
Some notes about how my setup when I tested the game, and things that could make your experience better:
- Locked the game at 60fps by creating a custom
dxvk.conffile inLibrary Folder/steamapps/common/BioShock Remastered/Build/Finalwith the linedxgi.syncInterval = 1. This locks the game to 60fps, vastly reducing GPU (and CPU) load. Note: As it is a DXVK configuration file, it requires you to use DXVK rather than WINE D3D - Added
-nointroto the end of the game's launch options, after%command%to skip the game's lengthy opening titles - Set CPU governor for my Intel processor to "Performance" using this plasmoid on KDE, but it can also be done through Feral Gamemode. Once configured how you like (follow instructions on GitHub for how to customise), enable by appending
gamemoderunto your launch options before%command% - For my tests, I used Valve's ACO Mesa driver. Unsure if it's made any difference to performance but if you're experiencing any kind of stutter or low performance given your hardware, I'd recommend using it. Only works on AMD GPUs, check this thread for instructions on how to check if your card is supported
PROTON_NO_ESYNC=1: Fixes some occasional low-res texture issues
-no-intro: skips the game's intro splashes and jumps you straight to the main menu. While these splashes work, they're rather annoying. Add this option to skip themRADV_PERFTEST=aco: If you're using a compatible AMD GPU and Mesa 19.3 or above, you can enforce the use of Valve's ACO shader compiler with this command. Add it to your launch options- Your final launch string should look like:
PROTON_NO_ESYNC=1 RADV_PERFTEST=aco -nointro %command%
- My Steam Controller worked fine
- The game did work out of the box, but as mentioned, disabling esync improves that peprformance
- I didn't try the INI tweak mentioned in other reports, but I didn't really experience any stuttering on this hardware or my previous RX480. It might be worth trying though if you do have issues!
Didn't need to disable esync, game launched with no tweaks. Performance is fantastic - enabling vsync gives the performance a major hit. Played at max settings with a fairly consistent 70fps - About equivalent to Windows. The game has some light stuttering, especially when loading new areas, but this happens on Windows too. Lowering some graphical settings would probably fix this.
Unplayable - No UI with Proton, crashes with Native
Main menu UI does not load with Proton, and unfortunately native does not work on Linux since 1.0 release due to frequent crashes when loading the game. Cannot get beyond the main menu with Proton as it does not render either the new UI or the "old" Source UI.
Perfect compatibility, didn't realise it wasn't native until I checked the store page again!
Game runs at about 1000fps on my system, you can limit this with a DXVK configuration file. Make a file called dxvk.conf in the same directory as the game's EXE (the main directory for the game when you choose "Browse Local Files") and add the following line: dxgi.syncInterval = 1
That's my only comment for the game. Everything else is perfect
Works as you'd expect
Took 11 minutes to complete, got all the art and achievements. Works just like you'd expect a typical game like this to work.
The tutorial doesn't play but you can press escape to cancel it (I assume if you wait the length of the tutorial that it'll eventually take you back to the main menu). Aside from this, the game runs flawless and with flawless performance. There may be a winetrick you can install to fix it, but honestly the tutorial isn't even that helpful anyway - and it comes with the DLC if you buy that (in the VIDEO folder). If you happen to own this AAA masterpiece of a game, you can rest easy knowing it works on Linux
Tutorial doesn't work, but comes with DLC. Works about as well as you'd expect. Full compatibility.
Runs great, using Valve's ACO Mesa driver fixes the stuttering and greatly improves performance but causes some weird error where the game will crash and say it's out of video memory. Though this only happens with the UHD texture DLC and the ACO driver. Install the driver by either adding the PPA or just using your favourite AUR package manager such as Pamac or Yay to install it (it'll automatically remove any existing Mesa installation). I'll have to look into why it runs out of vram, but I imagine this will be fixed before ACO is rolled into Mesa 19.3
This is a common tweak for games with launches (i.e. Sonic Adventure 2). Performance-wise, the game is perfect. I ran on max settings. Consistent 60fps if you set the framelock, about 120fps+ if you unlock it. I personally keep it at 60fps locked. You need to rename "Launcher.exe" to anything else, and rename "BorderlandsGOTY.exe" to "Launcher.exe." Even if you set Skip Launcher in the in-game settings, you still need to do this. I haven't tested performance on Windows but with the renaming the game is buttery smooth and I almost forgot I was playing with Proton.
Rename BorderlandsGOTY.exe to Launcher.exe. Runs at max settings with 120fps+. Played for almost 30 hours so far without a single crash.
Renaming BorderlandsGOTY.exe to Launcher.exe (and renaming Launcher.exe to something else beforehand) allows the game to launch. After this, the game runs perfect. Completed Playthrough 1 without a single crash and a stable 100fps+
Ran great, game stutters for a few seconds on the main menu but it isn't anything noticeable
I ran the DX11 version, didn't try the DX12 build. I'm not sure that performance would be massively affected. I didn't test a controller and I only played for about 40 minutes but I didn't have anything that I wouldn't expect to see playing any other game. Runs great with vanilla Proton 5.0-7
The game gets stuck at the loading screen with the yarn ball, but the launcher works. Tried installing the game on my main drive, my NTFS drives and my ext4 drive, got nothing. I tried enabling/disabling esync, using D9VK, I even tried using winecfg and setting the Windows version to Windows 10, but no luck. The launcher recognises my Steam Controller and can even be navigated, however switching between tabs too fast will cause it to crash. Also, it doesn't remember your settings. The game does, but the launcher displays everything at the default settings. So if you set vsync to off, the game will run with vsync off, but the launcher will tell you that vsync is on. I tried logging some Proton output but couldn't find anything as to why the game isn't working - Then again, I'm not an expert. Bottom line is, the game will just load to a blank loading screen for about 5 seconds. At this point, there's a very subtle and short clicking noise, almost as if a cutscene or theme is about to play. Maybe there's a WMF codec related issue here. The yarn ball will spin, but then it'll stop after 4-5 seconds. If you close the window, the process will remain running and you'll have to use your favourite task managing application/command to kill the process. Disappointing, hopefully it'll get fixed someday.
Completely borked, game won't go past the loading screen. Launcher works though.
Still does not start with 4.11-3. Tried installing the WMF workaround using mf-install but that didn't work
Does not work at all
Tried with mf-install, installcab (32bit and 64bit), using flags such as PROTON_USE_D9VK and forcing the game to run the DX9 version, but nothing seems to work. Unsure as to why the game isn't working. Tested with various versions of Proton 4.11 and no luck.
Game does not start, locks up when trying to play WMV files
Tried using mf-install and mfplat to fix the game, but no luck. Game seems to be broken in much the same way as Catherine Classic. No Bubsy on Linux :c
Does not work, most probably due to WMV playback issues
The launcher works fine, however
Game needs WMP9 winetrick verb, you can install it with:
protontricks 627910 -q wmp9
The reason this game did not work previously was due to the winetrick verb wmp9 not working on 64bit WINE prefixes - Which are required for Proton. However now that this works, the game will work after applying the WMP9 verb. In the report I opted to go with Protontricks as that is the simplest solution, but you can install it through regular winetricks if you wish.
- Tested with all settings at max
- Tested the tutorial level, had no issues
- Tested with Proton 5.0-9 and the latest Proton-5.9-GE-3-ST and both worked! However, the media foundation patches in Proton-GE did not fix the issue
- Tested with a Steam Controller
Out of the box, the game runs at about 800fps+ for me. This puts a lot of strain on the GPU, and isn't necessary. To fix this, I create a dxvk.conf file to limit the game's framerate to my refresh rate; 60fps. To do this, go to your game's local files and create a file called dxvk.conf. Inside, add dxgi.syncInterval=1. Now, the game will be limited to 60fps. However, this will slow down how fast you unlock the game's "achievements." If you really want them, leave the game running at the highest framerate and then cap it.
Optionally limit framerate with aforementioned DXVK tweak. The game's so-called "achievements" also work...
Use dxvk.conf file with this line to choke the game's FPS down to 60fps: dxgi.syncInterval = 1. The framerate runs incredibly high on Windows and Linux and is a common complaint with the game.
Game runs perfect, though I recommend adding a custom dxvk.conf file in the folder with the game's EXE, with the single line: dxgi.syncInterval = 1. On my display this locks the game to 60fps
WINEDLLOVERRIDES="dinput=n,b" %command%
The game worked flawlessly with and without the Committee of Zero improvement patch (which you should be using). This patch will install perfectly fine, and if you just installed the game onto one device and are not moving i.e. a microSD card between devices, then none the below applies. Everything is green, go ahead and enjoy! But if you're moving the game install (i.e. on an external drive or a microSD card), there is an extra step required.
- The CoZ patch does two things during installation: Moving its files into the game files (including the launcher), and exporting a Wine DLL override for dinput8 onto the prefix when it detects that it's running under Wine. However if you put the game onto a microSD card or external drive, and then try to run it on another Steam Deck or on a PC, the prefix will get re-created and thus will not have this DLL override that was applied when the patch was installed. The impact of this is that the CoZ launcher will show up, but the patch itself will not be loaded (evidenced immediately on starting the game by the untranslated logo on the main menu, different font, no mouse support). So even though the CoZ launcher will load and be used to start the game, the patch content itself will not be loaded!
- To fix this you can just manually export the DLL override in the launch options though, with "WINEDLLOVERRIDES="dinput8=n,b" %command%" (without the quotes). Reinstalling the patch wiill also work, but this may be more straightforward.
- There are other ways to set the DLL overrides, such as by manually setting the override in Winecfg or editing the prefix regisitry (which Winecfg does), so use your preferred method.
- This step is also required if you choose to manually install the patch by dragging the patch files over into the game files without using the CoZ installer.
If you install the patch on a fresh game install, none of this applies and it all works OOTB! But if you install it on a microSD card or SSD that you move between devices, you will need to set the DLL override so that the patch can be loaded. That's it!
As far as I can tell, it runs exactly like Windows
- The game stutters a little bit when loading new areas or sometimes during cutscenes, but it's only for half a second and relatively infrequent. The main thing, though, is that apparently this happens on Windows too. I asked my friend and he said he experiences similar, so I don't put the blame for this on Proton
- Tested with ACO enabled, you can use
RADV_PERFTEST=acoin the launch options for the game if you're using Mesa 19.3 and above - Tested with a Steam Controller
- Tested with all settings at max, and my framerate stayed at the maximum lock of 240fps at all times except during the mentioned stutter periods. I kept the game locked at 60fps most of the time though
Works out of the box
- Tested with a Steam Controller and with a keyboard/mouse
- Tested on various versions of Proton, performance has only improved with releases
- I plan to test co-op in the future, however there is no reason why it shouldn't work
- Played the game at max settings and had no problems
Tested Nazi Zombies briefly and had no issues
Heavy stuttering without vsync, enabling "Sync Every Frame" option in settings fixed this completely
Played at 1080p, enable vsync to fix stutter, but aside from that the game worked out of the box. I plan on testing more, including some co-op in the future. But for now, I haven't had any problems.
Tried many things to try and fix this game, but out of the box it does not work
The game will start up to a blank screen, and after about 10 seconds it'll show a dialog (sometimes under the main game window) saying "Fatal Error". It's an Unreal Engine 4 game and the store page says it requires at least Windows 8, and in my log file it complains about D3D11CoreCreateDevice: Adapter is not a DXVK adapter. Not sure how to go about fixing this...
Native release worked just as good as the first time I played it
Played this natively a long while ago and it still works great.
Native works out of the box
I have only played about half of this game and that was with the native release about 3 years ago. I tested briefly again from the beginning and it still works great.
- The original game, just titled "Carpe Diem", also works great
The game launches to a black screen, and if you press any button/key and wait a few seconds then the game will load into the main menu. From here, you can change settings and attempt to start the game. However, the game won't play and stalls on an infinite loading screen. However, if you change any game settings then these save. Proton currently doesn't support WMV playback and this is the cause for the game not starting and the black loading screen. If this was fixed, the game would run perfectly I imagine.
Some fading works on the mouse cursor at boot, and sound effects play. However, there is still a black screen. If you wait, you'll see a flash of the Criware logo - If you click to skip the game's titles, this will also happen. The main menu works fine, the problem with the game is that it locks up when you try to start a new game or load an existing game - Due to Proton lacking WMV support.
My experience hasn't changed with 4.11-1, I still have the black menu where I need to press enter to skip the cutscenes. The main menu works, settings can be changed and saved (something Bayonetta needs a patch for, but this game doesn't if anyone's curious). However, once I try to actually load the game by starting a new game, I get stuck on a loading screen with a Shakespeare quote. From what I understand, this is because of WMF codecs (though someone on a Steam forums thread said otherwise, so I'm honestly not too sure). Still sadly cannot start the main game.
Tried using mf-install and mf-installcab, but the former makes no difference and the latter causes the game to crash after moving the DLL it generates. I'm still going to experiment, but I don't expect to have much luck. Oh, I also tried D9VK but that just causes the game to crash (even on a clean prefix). Pity.
Still gets stuck trying to load a new game. Also, Steam Overlay support is now broken for some reason, meaning controller support is non-existent. Big oof
Unlike other reports, the game still does not go past the main loading screen when starting a new game for me with 4.2-9, or with 4.11-6. The screen as soon as I load up the game is still black with just music, a mouse cursor and a version number in the bottom left. Steam Overlay is still broken for me, meaning no FPS counter and no Steam Controller support. It worked once upon a time, I'm guessing something with the game broke support though rather than Proton. I made sure to try with a fresh prefix as well when switching Proton versions.
Game runs to main menu, but trying to start any gameplay will cause the game to infinitely load on the loading screen
The loading screen is animated, so the game doesn't crash, but it locks up when trying to play any sort of media. You have to click to skip the main menu animation as all you will hear it sound and afterwards, the game will just hang until you click to skip. This issue is not fixed with the mfinstall tweak unlike with Monster Hunter World. The installcab tweak also does not work, in fact this causes the game to outright crash. So far, I have been unable to find a fix.
Menu works, game gets stuck on loading screen and no Steam Overlay support
- When the game starts up, it shows a black screen with some music, a version number and a mouse cursor. Because it can't load the splash screen WMV file, you have to click to skip the loading screen (this was added in an update not long after launch, and it's why we can get to the game's initial menu)
- Steam Controller does NOT work, as the Steam Overlay does not seem to be working (no FPS counter, no Shift+Tab for Community access, etc). Other controllers may work fine, but I don't have any available to test with
- Game menus work fine, you can change and alter settings and they stay fine. All audio seems to work fine too
- Game gets stuck when trying to load any gamemode. Perhaps if you play the game on Windows or somehow use someone else's save file, the game may work? Assuming it doesn't need to play the WMV files. This would need investigating, though
mf-installandmf-installcabdid not work for me. I tried the 32bit and 64bit version for installcab, and it did not work. In fact, adding themfplat.dllcaused the game to crash
The main issue with Catherine Classic as it stands right now, is the lack of WMV support in WINE/Proton. If this was fixed, I imagine the game would work (and if the Steam Overlay worked, for us Steam Controller users). Unlike other reports mentioned, I don't think this is a GPU issue, as it seems people are having trouble on AMD and Nvidia hardware alike.
Menus work fine, game gets stuck on loading screen
- No Steam Overlay support, meaning Steam Controllers are borked
- Game menu works, but you can't start the games.Story Mode results in a softlock at the Shakespeare quote, and Arcade mode doesn't work either. You can set all options in the menu just fine, however, such as audio and resolution and so on
- Tried
mf-installandmf-installcabwith no luck - Tried removing the folder containing the game's cutscenes to see if they would be skipped (a fix people sometimes use for Dark Souls: Prepare to Die Edition). But that didn't work
I suspect if you load the game on Windows and get it to a point where it doesn't need to play any cutscenes, it would work. Perhaps that's where the other reports of the game working came from. I have no doubt that, if you could get past the WMV cutscenes, the game would be platinum. Other reports say it runs perfectly and it's a standard Criware game, meaning there shouldn't be any performance issues.
Something I didn't try is running the game in a 32bit prefix and installing something like wmp9, which I've heard is a potential fix for some games with this issue. wmp9 can be installed through the use of winetricks on 32bit prefixes, but Proton uses 64bit prefixes. Also, in doing this, you'd need to launch the game through a custom WINE prefix with WINE Steam installed. You can do this with Lutris, an all-in-one launcher for playing games on Linux. It's something that could work!
Proton-5.9-GE-3-ST allows the game to start to the main menu, but new game won't load
- The current latest release of Proton-GE fixes Catherine to load to the main menu, and you can adjust settings/etc. Also, depth of field now works correctly and so does the Steam Overlay, meaning I could use my Steam Controller to navigate the menus. However, trying to start a new save file causes the game to load infinitely. I expect this is something to do with Media Foundation compatibility, which work is being done on to improve. It likely will work in future, but as of right now it does not.
- From what I understand, if you have a save file you've already played, the game will load just fine.
- You can fix the opening credits so you don't have to press enter to skip them. You can view The Eccentric Ape, Gamebryo and Criware splashes when you open the game (though not the ATLUS splash). This can be done by using
protontricks 89310 -q wmp9 - I tried installing the additional verbs
quartzanddevenumwhich fixed another ATLUS title, Persona 4 Golden, but that did nothing. Only thewmp9verb mentioned had any impact on the game.
Someday we'll get this game working, and we can enjoy the strange tale of Catherine...
Cutscenes don't work and has windowing problems with Proton 7.0-2, Proton Experimental and GE-Proton7-20
The game window doesn't quite maximise properly and though sound works, cutscenes are entirely broken due to the codecs used for the video files. There are some workarounds to get the cutscenes to work using older Proton versions and some winetricks, but those still do not seem to produce an ideal experience.
Lots of work is happening with codecs and Proton so hopefully it'll be playable soon, more and more games are being fixed with each Proton Experimental release
Native port is a disgrace, use Proton instead
Sometimes a select few sprites in the game would get messed up when activating the Steam Overlay. The game needs restarted to fix this.
The native port has so many crashes, no controller support, fullscreen is broken if you have more than one monitor, it's just an all around disgrace. While Cave Story+ isn't a great port in general, it works a heck of a lot better running under Proton and I played for about 30 minutes. The only issues I encountered were related to the Steam Overlay breaking some sprites, but that's it (so far).
- Tested with a Steam Controller. Controller prompts for Cave Story+ are very generic, using terms like "Button 01". The controller will show up as "Gamepad 01", which I initially thought was an issue with Proton but it turns out it's just how the game is.
- Tested windowed and fullscreen and it actually worked
- Sound still dampens when you tab out, so that nifty feature still works.
Native and Proton work identically, both are a flawless experience
And since both are flawless you can stick with the native release, but Proton is an option if you have any problems :-)
Have only played a part of the game but so far works great
Have not experienced any issues so far with the native Linux release.
Great out of the box experience
Tested with the new Proton 4.11-11, and it worked without any tweaks. Navigated around the main menu and briefly played the start of the game. The animations seemed low framerate but when I checked the Steam trailers for some (spoiler free) gameplay, they matched up. So it isn't a Proton issue. Great compatibility!
Got a few endings, didn't encounter any issues with the game
Tried out the achievements sync and it worked without problems, got a few different endings, tried out both the Adventure and Simplified modes and made a save in all save slots. Game works perfectly with Proton!
Works perfect out of the box
Got a quite a few endings and achievements with the game so far, I doubt I'll run into any other issues running on Linux. The animations might look slow but if you watch the game's trailer that's how they're meant to look and isn't an issue with Proton.
New content updates still work, and so do the newer versions of Proton!
Still works out of the box, even with the new updates and there have been no regressions with Proton 5.0.
Works out of the box with no tweaks or launch options with Proton 6.3-7
Had no major issues with the game, did not need any launch options like other reports mentioned and had no issues with the game starting up. Tried 5 times and it opened each time. The game also remembered my windowing geometry and fullscreen preferences with each startup (running KDE Plasma). Did not have any crashing issues in my brief gameplay tests, nor any framerate issues.
- Minor mouse offset when the game initially opened
- Bottom of game window flickered if it lost focus, but stopped flickering when the window regained focus
Works perfect aside from cursor being offset slightly on a maximised window
- Cursor is offset in maximised window, windowed/fullscreen works fine (likely a KDE Plasma bug)
A pretty much perfect experience on Linux. I don't have any Windows experience to compare with but I had no issues. Notes:
- Dunk the cookie achievement works completely fine, I got this achievement on Linux
- Played on KDE Plasma Wayland
- Occasionally the cookie did not re-appear after ascention but this seems to be a game bug rather than a Proton bug
- Tested on desktop and laptop, worked fine including cloud saves
- No issues with mods
- Appears to work fine at higher refresh rates
- Steam Controller works fine
- Another report noted that the fonts are slightly different than on Windows and that appears to be the case, but they are still more the legible on the systems I tested on
Works perfectly but needs PROTON_LOG=1 on KDE Plasma 5.25 Wayland otherwise it will crash on launch
PROTON_LOG=1 %command%
When maximised the game would sometimes have an offset. This was not always the case, it seems like usually maximising on another monitor than the game was started on means the game won't have this UI offset. Playing windowed or fullscreen gets around this issue and its not a big deal as you'll probably want to play this game windowed anyway
Needs PROTON_LOG=1 %command% on KDE Plasma otherwise it will crash when trying to start the game. Otherwise works great on either older versions of KDE Plasma and probably other desktop environments too.
Experimental or GE-Proton7-23 are needed to fix having to add PROTON_LOG=1 %command% to your launch options
Needs PROTON_LOG=1 in launch options to work, has otherwise worked pretty flawlessly for over 1,000 hours
PROTON_LOG=1 %command%
- Game does not remember that it has been set to fullscreen when you open it after closing in fullscreen.
- Game will always start maximised
- Maximising the window on the display the game initially opens on causes a weird offset. Playing in windowed mode or fullscren fixes theissue.
Yes, I played 1,000 hours of this game on Linux. No, I am not ashamed. It works beautifully minus the few hiccups described :-)
Native game that works out of the box flawlessly
I didn't experience any issues with this game. I believe it's just a standard Unity game, so it works fine natively. If you experience issues, you can try forcing the Steam Linux Runtime in the compatibility tools dropdown, which can resolve some issues with some games on some distributions
Single player works perfect, didn't try multiplayer
Played for about half an hour and didn't encounter anything major. Game is still early access, but I got a solid 1080p60 with small drops down to 45fps when the game was autosaving (which is to be expected from an early access game). Overall, worked perfectly fine!
Works out of the box, consistent full 60fps on max settings. No issues encountered so far, played up to beating Ripper Roo. No crashes, no stuttering, everything works flawlessly.
Works like native, had no issues, runs at full 60fps with max settings
Tested with Steam Controller and played about half of Crash 1, approx. Haven't encountered any issues so far.
Works flawless for me - Did not encounter any issues
Unlike other reports, I didn't have any crashing at all in my tests. Everything worked flawlessly at max settings. I also tried streaming the game with Remote Play, worked great as well
Haven't had any issues in my tests
- Tested with Steam Controller
- Tested with Valve ACO enabled (
RADV_PERFTEST=aco, only works on supported GPUs) - Only tested about half of Crash Bandicoot 1 so far, but no issues
- Ran on max settings
With previous versions of the game, I needed to run the game in windowed mode. Now, the game works at max settings with no issues (and vsync off). This includes the game's launcher. Menus consistently get 60fps. In game, I tried with D9VK, and I got about 20-25fps. Then, I tried with D9VK (PROTON_USE_D9VK=1 %command%) and my processor PState set to "Performance" instead of "Powersave" and got a decent 15fps+ boost up to 35-40fps. Then, I tried with standard DXVK and the processor PState set to "Performance" and I got about 50-57fps. It didn't quite hit the 60fps mark, but that is most likely my hardware. CPU temperature hit about 75 degrees while playing, which made my laptop slightly uncomfortable to keep on my knee. I should note that if you lowered the resolution to 720p or turned FXAA off, you'd probably get better framerate. Also, on my PC I got 60fps before when I played in windowed mode with no dips. However if I didn't have the Steam FPS counter enabled I probably wouldn't have noticed the performance dips. The game is a perfectly fine experience on my low end laptop, and that's the main point I want to make in the end. Tested with a Steam Controller, by default it had some keyboard configuration selected but you can change this to a standard "Controller with Mouse" configuration in the Controller Configuration menu. You might also have to set it in the launcher. Overall, fantastic experience on my laptop.
Works great with DXVK and D9VK
Just like in Windows, if your controller disconnects for whatever reason, the game will lock up and need to be forced closed.
Great native experience
The native release works perfectly fine, I was able to 100% complete the game. I did not try Proton
Flawless native Linux port
Just like the original this one works perfectly native
Native worked without issues
Tested the first three puzzles and didn't have any problems. The Unity prompt to select resolution and display also worked correctly, showing the correct maximum resolution (a couple of games I have played show too many possible resolutions and end up displaying incorrectly if you choose a resolution too high). My displays were also correctly detected, showing up as XWAYLAND1-4 with the size of the monitor beside the name in inches. Overall a great native experience!
Runs FAR better than the native game
Gameplay is much smoother with Proton, and it works with more than one monitor unlike the native version. I couldn't tell if the game properly recognised my Steam Controller, since the game doesn't make that very clear. Overall, highly recommend using Proton over native!
Just audio; downloads fine with the game even when running through Proton
- Can be found in the same place as the native game's OST:
/path/to/steamapps/common/Crypt of the NecroDancer/soundtrack/ - If you came here looking for Crypt of the NecroDancer, see here
Works out of the box. A little stuttery when loading new areas but very playable. Disabling esync just caused more stutter. My CPU isn't the best, but setting the game's CPU option to "reduced" as opposed to "full" helped. I think if I had a better CPU the game would run better. Overall though, pretty good experience in terms of Proton compatibility
Almost forgot it wasn't native. 1080p60 and full controller support, at least with my Steam Controller tests.
Game works out of the box
No issues, buttery smooth, no launch options needed, recognised my controller straight away too!
Tested with default and latest version of Proton (4.11-9 right now), works flawlessly with both
Tested with Steam Controller and with Remote Play Together for local co-op. Works great!
Performance is a bit lower than what you'd get native, but it is more than playable @ 1080p60!
mesa-git is required to play the game. To install on Arch Linux, use the mesa-git and lib32-mesa-git packages.
Very, very, very infrequent artifacting
My top KDE panel would display over the game in Borderless Fullscreen. I fixed this by using regular Fullscreen.
Chugs around 50fps on utlra, a mix of high/ultra settings gets a pretty good 60fps though
Played about 80 minutes of the intro. My GPU and CPU were hanging around 75c each but the game ran really smooth on a mix of high/ultra settings. Overall, the game ran perfectly acceptably for my standards and I'm very excited to see potential performance improvements in future! A few notes:
- This game requires Proton 5.13-4
- This game requires Mesa-git
- This game requires an AMD GPU
- Tested a Steam Controller briefly, it was recognised fine
- Minor framedips when loading into new areas after cutscenes, but that's about all
- Did not experience a single crash in my 80 minute play session
Works perfectly out of the box with various versions of Proton
Worked out of the box with no tweaks at all. Previously this game had some issues mainly related to cutscenes, but in Proton 6.3-7, Proton Experimental and Proton-6.19-GE, there were no issues playing at least the intro cutscene. I am not very far into the game, but so far it has ran beautifully well. Some other notes:
- Tested on KDE Plasma with both Xorg and Wayland, no issues to report
- Tested with a Steam Controller and Nintendo Switch Pro Controller, no issues to report
- Tested at max settings, did not have any framerate issues
- Though I am currently using Mesa-git, the game works virtually the same with Mesa 21.2.4 (the current release)
- On the latest stable Mesa, upscaling to 4k on my hardware caused a few framerate issues. I tested with Proton-6.19-GE-2 and used AMD FidelityFX Super Resolution (FSR) to upscale with
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=2. Using Mesa-git eliminated these performance issues, and the game runs upscaled without performance issues. Though my time testing this was brief.
- On the latest stable Mesa, upscaling to 4k on my hardware caused a few framerate issues. I tested with Proton-6.19-GE-2 and used AMD FidelityFX Super Resolution (FSR) to upscale with
Game itself works perfectly, however it crashes on exit. This does not affect the game or save progress. I've seen reports of some saying the game doesn't start or needs a special launch option, but for me it works out of the box. However along with several other Proton games I could not get my Steam Controller to work. I'm not sure why this is and is most likely not a direct issue with Proton.
Still hangs on exit. Still hit and miss controller support (tested with Steam Controller). Some text still missing (notably the Screenshots Folder test and Feedback text on the main menu)
As of Proton 4.2-3, the game seems to run perfect. Some of the UI displays a little funny but for all I know this could be present in Windows. Steam Controller works perfect, all audio is fine, basically a flawless out of box experience.
Same issues as the original DEEP SPACE WAIFU; that is, no controller support, crashes upon exit, but the game itself is perfectly playable. No performance issues.
As of Proton 4.11-8, all issues are fixed
No longer hangs on exit, all text appears, full controller support
Played with Proton 4.11-9, no issues whatsoever
Unlike other reports, I did not experience any issues with Alt+Tab, audio or online play. A few extra notes:
- Used Valve ACO driver
- Played with all settings on max with backend renderer set to Vulkan (and vsync off, as my compositor enables vsync)
- Dipped below 60fps once, but didn't notice it aside from seeing the FPS count dip, the game ran silky smooth it's almost hard to believe it isn't running natively
Works with no issues for me
Tested with Valve ACO on a fresh Arch installation. Crashed before ACO, but I probably didn't have the Vulkan Mesa drivers in. Worth noting though!
Works like a native game, smooth as butter, consistent 200fps
- Tested with a Steam Controller without issue
- Tested over Remote Play Anywhere (with a Steam Controller also) and had no issues
- All settings were at max
- Tested with vsync on, no frame drops, and vsync off was a consistent 200fps, sometimes more
- Tested with sharpness at full and with various filters, worked great
Incredible performance with everything at max settings
The game works out of the box with no tweaks. Use the Vulkan backend in settings for the best performance. I've played with everything at max, plus some sharpening. I've tried various filters too and they all work (gritty, cinematic, etc). I'm playing with ACO enabled, and I've tested briefly with a Steam Controller which was recognised out of the box too.
It's DOOM on Linux!
Works OOTB, highly recommended to use Vulkan for even better performance
The OpenGL backend works but I recommend using the Vulkan renderer, as it gives much better performance!
- Tested with a Steam Controller for giggles, no problems
- Tested with Remote Play Anywhere and it worked great too
Proton-5.5-GE-1 GloriousEggroll
- Custom Fork: Proton-5.5-GE is the latest version of GloriousEggroll's Proton fork which includes patches for DOOM Eternal to get it to work. Proton 5.0-6-RC may also work but I haven't tested it
RADV_PERFTEST=llvm- Ensures that ACO shader compiler is not used as it currently does not work with the game+in_terminal 1 +com_skipIntroVideo 1- These two options are required to fix an instant crash. They seem to go hand-in-hand so you need both. The intro video likely has some form of codec issue, which may be fixed soon as patches for MP4 videos is being worked on at the moment
The %command% part of the string must go before the last two options exactly as shown in the string, as this is how the engine seems to recognise flags passed to it. Your final launch option string should be: RADV_PERFTEST=llvm PROTON_NO_ESYNC=1 %command% +in_terminal 1 +com_skipIntroVideo 1
There is very slight audio crackling. Other reports have shown that there is a way to fix this but I haven't tried this personally, as the upcoming Proton 5.0-6 has patched this. So while it is currently an issue, in the near future it will not be present
I didn't play that much but there were some slowdowns for me where the game would drop to a low of 38fps, but on average I kept above 80fps. Disable the Steam Overlay to fix this issue! This also seems to work on Windows as well, for what it's worth
The TL;DR is that this game works great after tweaks and it will only continue to improve as development on Proton and graphics drivers progresses!
- Add the launch options and disable the Steam Overlay and you'll have absolutely no issues! I played a bit of the first part of the game and didn't have any bugs, no major graphical errors to speak of, it would be very nitpicky to complain about them. I didn't need to use the proprietary AMD drivers but I'm using the latest stable version of Mesa - I've also heard Mesa 20.1 is giving big improvements to this game. Once it works with ACO I also imagine it'll get good performance
Denuvo Anti-Cheat has been removed, the game works like it did before!
- Denuvo Anti-Cheat has been removed from DOOM Eternal as of V1.1! This means the game plays again! And it plays great!
- Performance is extremely smooth, I haven't had any problems. Playing the game on max settings with vsync on (Triple Buffering also works) is recommended, though I get well over 180fps consistently it causes a strange whining noise when the game runs uncapped
Previously, DOOM Eternal needed a number of tweaks to work. As of right now, I can play without any tweaks at all - A full platinum rating! However, a few things to note:
- NVIDIA users may need to disable esync with
PROTON_NO_ESYNC=1in the Launch Options, but you also may not. Check to see how the game runs for you without this option, and if you're having problems you can disable it! - If you're running on AMD hardware and using a version of Mesa below 20.1.0, you'll need to use
RADV_PERFTEST=llvmto disable the ACO shader compiler, as it does not work with this game below Mesa 20.1.0. ACO gives a decent performance boost of about 10fps and reduces some slight stutter in some areas - The Steam Overlay previously caused really bad performance issues - It brought the game's performance down to below 40fps at times. This has since been fixed, and you can safely play the game with the Steam Overlay. For me, it did not give any performance boost with it disabled
- There used to be audio crackling issues, but these have been fixed in later versions of Proton. If you're using 5.0-9 (the latest at the time of writing), you'll not have any issues
- I've heard that GloriousEggroll's Proton build has some DOOM Eternal performance improvements, but I haven't tried this out myself. If you'd like, you could give that a go to see if it helps at all.
- You don't need this launch option, but for your own sanity you can use
%command% +com_skipIntroVideo 1to skip the intro credits, i.e. the Bethesda and id Software splashes, and the warning information. Make sure it goes after%command%!
Game currently does not work on Ryzen APUs
The game causes a system hang after starting on Ryzen APUs (e.g., 4700U). Renoir chips are unsupported at this time. All connected screens turn black and the system will require a reboot. However, note that the game will work fine on a dedicated GPU.
Native works perfectly
Did not have any problems completing the game using the native port. Did not try Proton.
Worked out of the box. Setting the game to fullscreen and using Alt+Tab to tab out caused the game to go back to a small window (using KDE Plasma), however setting the game to use Borderless Fullscreen worked. I'm unsure if there's meant to be an intro video or not, but regardless one does not play. I tried using mf-install to no avail. Kind of annoying, but it's whatever. Initial tests suggest the game runs like native.
Used mf-install to get the game to work. Once installed, the game worked flawlessly. See here: https://github.com/z0z0z/mf-install
Tested the game with a Steam Controller and it works perfectly fine.
Game actually does **not** need mf-install, works out of the box like native
Played for over 10 hours using Proton w/ Steam Controller with no issues
Played the whole main story, no issues at all
Tested with a Steam Controller. Worked out of the box, played the main story, all of it worked without issue
Works great with Proton
I played through the entire main story and did not experience any issues with cutscenes or with my Steam Controller.
Played through the full game with Proton and it works perfectly
Still works great with Proton 4.11-10, no changes
Full game and extras work perfect without any tweaks
- Tested with a Steam Controller
- Tested with Mesa ACO compiler, didn't make any difference for this game though (you can enable it on compatible hardware and Mesa 19.3 with the launch option
RADV_PERFTEST=aco)
Media Foundation- Had to usemf-installas the game opens to a Spike Chunsoft splash screen that seems to require this workaround (I assume the other cutscenes in the game require it also). You'll have to launch the game once to generate the Proton prefix (/path/to/steamapps/compatdata/567640/pfx, replacing/path/towith the actual path to yoursteamappsfolder), then close the game, install the workaround and launch the game again as normal
It can be a little awkward to tab out, and if you've set the game to "Fullscreen" it's particularly awkward. Set to "Borderless" for a much easier time (though I suspect this is regular behaviour for the game and not a WINE bug)
So far I've only played up to the Prologue Save Point. The game is very enjoyable with Proton, here are a few notes to do with my experience:
- The game's launcher works completely fine except for a button which seems to not render correctly. It probably says something like "Save and play", because clicking it will launch the game. You can set everything from the launcher and close it though, and everything will be saved. Or, launch the game from it and then close it again if you want to be extra sure
- High recommend setting the game to "Borderless" instead of "Fullscreen"
- Tested the game on "max" settings, in that I enabled FXAA. No issues with performance
- Tested with a Steam Controller. It worked great if you launch the game "normally" and not through the launcher. Probably due to the nature of the Steam Controller and how it generally handles launchers, it won't work if you launch the game through the launcher rather than through Steam the normal way. The Steam Controller works fine, though, once launched in this way
- When using the Steam Overlay, the game still registers input underneath. This could just be game behaviour though, as I've had other games (native and Proton) work this way. It isn't really anything to worry about but worth noting in case you experience it and get slightly frustrated like I did
- Another report mentioned the game not working on more than 16 cores. I haven't been able to test this, but running the game on my hardware with this tweak didn't cause any harm so you could use it if you wish
mf-install- Game opens to a WMV cutscene that WINE can't play natively, so a tool to install the Media Foundation libraries calledmf-install. I suspect cutscenes are used at other points in the game that use these as well, so you need to install this tweak for the game to work. Once installed, you won't run into any major issues.
- Set game to borderless fullscreen to avoid strange behaviours such as game registering input when it's not active
I've played all of the Prologue and Chapter 1, and some of Chapter 2. My experience so far has been pretty much perfect once tweaked slightly, here are some notes based on my experience so far:
- Played the game at "max" settings, which doesn't say a lot for a visual novel game but for those curious I haven't had any performance issues. I had one drop to 54fps for a few seconds during a part of Chapter 2, but it wasn't a big deal and I only noticed because I have the FPS counter enabled
- Launcher's main button for launching the game is seemingly invisible, but it's functionality works. All other parts of the launcher work, and you can just close the launcher window once you select all your settings and they'll be saved
- Steam Controller works, but cannot be used when you launch the game from the launcher. The game doesn't work properly. This is probably more a bug with the game itself, and a very insignificant one at that (hence why it wasn't mentioned in its own section). Setting the game to use a gamepad and closing the launcher, then launching the game normally through Steam will work no problem
- On the topic of bugs, sometimes the game doesn't respond to input for about 15 seconds. I suspect this to, once again, be a bug with the game's engine as I had a similar issue in Danganronpa 2: Goodbye Despair, a native game. Both games use the same engine as far as I'm aware
- I haven't experienced any crashes at all so far and none after cutscenes unlike other reports mentioned. I've played for about 20 hours so far, participated in a Class Trial (lots of cutscenes there), interacted with a lot of the characters, and haven't had problems
Overall, a very seamless experience with Proton once the relevant tweaks are applied! Solid as a rock and stable as heck
mf-install- The game uses WMV video files for cutscenes, which Proton can't play without a workaround. You can download the workaround here. This is absolutely required as the game plays a WMV for the Spike Chunsoft splash screen. Even if this could be worked around, other parts of the game depend on it
My notes were too long, but for a full breakdown see here: https://rentry.co/zuwgu
- Input was laggy: Sometimes input for keyboard/mouse only would drop out (does not affect controller). Only lasts for about 10 seconds and happens roughly every 20 minutes for me. It's present on Windows too and is not a Proton issue, and seems to occur less frequently under Proton. I have not tried tweaks to fix it.
- Controller(s) not detected: If using a Steam Controller, you cannot launch the game from the launcher. It won't register any input. Likely a Steam Controller bug and could happen under Windows too. Set input to "gamepad", close launcher (your setting will be saved) and launch normally. Your Steam Controller will work
Played the 90+ story thoroughly and tested as much as possible while playing. I did not encounter any issues that I weren't general bugs with the game (aside from a bug with the launcher). I'll give some notes on my experience:
- I played the game on "Very High" settings with FXAA at 1080p Borderless and also Fullscreen. I only had one framedrop. Cutscenes are locked at 30fps and this is not related to Proton
- Previously I had issues running the game in Fullscreen and had to use Borderless. I tested again and did not experience these problems. Maybe it's just hit and miss, so if you have problems you can use Borderless. But I tested for about 40 hours in Fullscreen and didn't have the issues I had earlier in my playthrough
- Launcher's "Start Game" button does not display for me. All functionality is still present though. It looks like this on Windows, but looks like this on Linux with Proton out of the box. I have not tried any tweaks to fix this and it isn't a big deal, but worth noting regardless
- Other reports mentioned a crash. After playing for 90+ hours and having sometimes 10+ hour long play sessions, I didn't experience any crashes at all
Overall, once mf-install tweak is applied, the game will work fantastically under Proton. The entire main story and casino minigames work perfectly.
Proton-5.8-GE-2-MF GloriousEggroll
GloriousEggroll's Proton-5.8-GE-2-MF build has some patches to fix Media Foundation issues, and when using this the game works out of the box without needing to install the Media Foundation DLL separately through mf-install
The Media Foundation work will likely get rolled into upstream once it's more complete, but for now use the GE builds and the game will work. I've completed the main story on Linux via Proton and tried out the minigame, it works just as good as the native ports of the first two games!
Native game runs perfectly
Played almost entirely on Linux and was able to 100% complete the game without problems. I did not try Proton
Did a full playthrough, got all the achievements and used the Steam Controller. Game launched and played perfectly. If you play fullscreen and Alt+Tab/lose focus on the game window, you have to maximise the window again - otherwise you'll just see a mostly blank window. This issue could be present on Windows as far as I'm aware anyway. As with all other entries in the series, the game now exists without any errors too.
Native works perfect
The resolution of the windowed mode changed to be slightly bigger when I fullscreened and then exited fullscreen, but could just be a game bug. Not a major issue, both resolutions are fine.
Kind of works, but causes system lockups
Some lines appear in the UI
Alt+Tab worked inconsistently and moving the window without changing the primary monitor in settings causes the window to move back to the display monitor. Attempting to change this can result in a system lockup.
Frequent, consistent and seemingly unavoidable system lockups
The game runs in its own window which has a black background, meaning it does not properly overlay over your desktop as intended. You could likely run the game in a virtual desktop configured via winecfg, but I didn't test that
- The "game" works, in that you can have a window and attempt to configure some settings. Workshop content also installs and can be used fine. The UI is a little slow and has some black lines through it but it's really a non-issue as you can see everything fine. The models dance on a black background, and I'm not sure if there's a way to fix this.
- The main issue is the system lockups, which made it difficult to test and explore to see what can/can't be fixed. After running the program for between 30secs to a few minutes at most, it'll cause my system to freeze and I need to press the reboot button.
- Overall, I cannot recommend because of the lockups. If these were fixed, though it doesn't work exactly as it would on Windows, I could still recommend to Linux users with an extra monitor to spare (which you probably have anyway for this type of game).
Proton-5.9-GE-5-ST GloriousEggroll
Use any recent version of Proton-5.9-GE, I opted to use Proton-5.9-GE-5.ST. This is required to fix Media Foundation issues in WINE, and outside of this the game works great.
- Tested with a Steam Controller
- Tested this with the default framecap of 120fps. I ran into absolutely no issues with performance and held a consistent 120fps at max settings, with only occasional drops down to 115fps if there was a lot happening on-screen
- Vsync also worked and I was able to maintain a constant 60fps
- Tested the first level with no issues
- Unlike Battle for Bikini Bottom Rehydrated, this game did not have any cutscene lip-sync issues
Runs exactly like it does on Windows 10, if not slightly smoother. That means any Windows 10 issues are also present; no Steam Controller support, maximum resolution of 1600x900 (though it can run fullscreen), and a framecap of 50fps.
Steam Controller now works if you set the Controller Configuration to use emulate the Keyboard and Mouse, which I couldn't get to work in Windows 10. However, the game will show keyboard prompts, as with any game you do this with. Otherwise, runs perfectly smooth.
Any issues I have with this game (50fps framelock, no 1920x1080 option, controller input prompts just show generic Xinput "button1, button2, button3 etc") are all present on Windows. It runs exactly how it does on Windows.
Perfect compatibility, the game has a few issues but they're not related to Proton and ARE PRESENT ON WINDOWS. Here are some: Game runs at a max of about 1600x900, and with a framecap of 50fps. No idea why. Game shows Xinput button prompts (Button1, Button2, etc) instead of actual labelled controller prompts such as A, B, X, Y, Start, Select (tested with my Steam Controller). Mouse has a bit of lag and stutter when moving it around on menus. The game runs pretty much identical to how it runs on Windows, including the issues present there too.
The game only displays a black screen. There is audio, and if you click around you'll activate stuff, but you have no way of playing the game.
Game still starts to a black screen. There are some sound effects, but it's hard to tell whether or not you can interact with the game. Completely unplayable. However the game seems to be pretty hit-and-miss on Windows, too.
Tried with "PROTON_USE_D9VK=1" but the game still has the same problem. The screen is black but sound effects play, and you can interact with the game - You just can't see anything.
Game runs now, it did not 4 years ago but new releases of Proton have fixed it
Crazy how compatibility improves overtime huh? :-)
Works flawlessly
Monika refers to you as "steamuser", this can be fixed by running the native version either through the launch option mentioned in previous reports or through Luxtorpeda
Can't say too much for spoilers, but the base game and DDLC Plus additions all work!
There is brief crackling in the main menu music. Not a major issue though.
If you change the game's resolution and switch it back, dialogue boxes will be offset.
The game works like a native release
You can play DDLC Plus on Linux with ease
Thanks to the efforts of the Linux community
There were some minor issues I went through
Such as minor audio crackling on the main menu
But I highly doubt this would bother you
The new additions to the game
Whether Windows or Linux, they work the same
Though I don't want to give too much away
For the new members of the club
After all, it is release day
All the new additions to this release work
So go ahead and have some fun!
All previous issues regarding dialogue boxes and resolution have disappeared, game works like native
Completed one playthrough of the game without any issues. A certain easter egg in a certain scene with a certain character also works as expected through Proton. Side stories work as well. Game runs as though it were native.
Runs just like the itch.io native version of Doki Doki Literature Club. Someone mentioned an issue with Monika reading the incorrect system name, but I have not experienced this.
Flawless, had an issue where I needed to reinstall to change the player's name though. This hasn't been present on my main PC though, nor on Windows. Strange.
Game runs perfect, though because the Steam prefix is called "steamuser" (and this can't easily be changed), Monika calls you "steamuser." There's a project called "Luxtorpeda" which is for multiple games and runs through Steam Play, and it probably fixes this issue since it just launches the native Linux version of the game that installs with the game. Once Luxtorpeda is installed: Right click -> Properties -> Force use of specific Steam Play compatibility tool -> Luxtorpeda (you may have to scroll to find it). This will actually make the game run like native, as though you were to run the Linux executable that downloads with the game or if you were to play the Itch.io version. But with Proton, aside from the Monika issue, the game is flawless.
As of Proton 4.11-3, the game will get to the loading screen. However, it hangs at the spinning circle. I assume this is because of the web browser fixes introduced in this latest version of Proton. I tried with D9VK as well, no luck.
Game starts up to a black screen, then closes after about 3 seconds. It does not play
Can't get this game to work
I believe it's just a web browser wrapper, so maybe it's an issue with how WINE handles these types of games. I remember seeing something about this being altered in a Proton changelog a while ago. I'd probably have to look into this more
Audio crackles and is severely slowed down. This makes the game annoyingly difficult to play.
I wouldn't recommend playing this game with Proton (if you must play it at all). It's simply not a nice experience.
Game runs great on Linux, optionally you can limit the framerate for a smoother experience
DXVK_FRAME_RATE=60 %command%
I chose to limit the framerate out of personal preference as the game was slightly stuttery without it, but this is not a Linux speciifc problem. The launch option listed is for limiting the framerate though there are several other ways to limit it, such as with MangoHud or Gamescope.
This game is surely the reason Valve elected to develop Proton... Just kidding, the game has buggy controls and not everything is translated into English (the exit game message is in another language). However the game works. Even my Steam Controller worked, however the controls for the game aren't that great. That's not a Proton issue though. If you own this game, you'll be glad to know it works perfectly with Proton I guess. No tweaks required. Fullscreen works, too.
Extremely brief gameplay test, but it works fine so far!
Incredibly brief test as I'm still playing through the first two games as a refresher, but from the little I played there were no visible issues! My Steam Controller connected and worked just fine too.
Game has no audio (even on Windows, according to the Steam reviews) and a flicker on the right hand side of the screen which also seems to be a game bug unrelated to Proton
Silly little game but works perfect with Proton
I was able to get all the achievements and play the "game" without any trouble
Game works out of the box
I believe this game was even whitelisted at one point. Regardless, it works perfectly with my Steam Controller and had no crashes so far. I also tested streaming the game to my phone using Remote Play Anywhere and it worked with no issues.
Works great with default Proton 7.0-3
Tested with a Steam Controller on KDE Plasma Wayland, no problems at all
Disable esync to find some minor, infrequent crashes
- You should use Proton as the Linux version of the game is not up to date. Performance has been spot on, better than the native game! And the issues I had with my controller (menus were extremely sensitive with the left stick using the native port) are fixed.
- Tested with a Steam Controller
- Used Valve's Mesa ACO Driver
- DLC for the game appears to have no issues
PROTON_NO_ESYNC=1- Disabling esync helps with some minor crashes
- Tested with Steam Controller
- ACO compiler was enforced with
RADV_PERFTEST=aco, not sure if it made a huge difference as the game ran fine anyway (I just enforce ACO for all titles)
Proton 9.0 or above (including Proton Experimental) required to fix slowdown, otherwise runs identical to Windows
Edited some registry settings to lower mouse sensitivity and game resolution according to this guide (https://steamcommunity.com/sharedfiles/filedetails/?id=3174952613), although the effect was rather minor.
Dungeon Keeper 2 works perfectly with Proton, with a couple of small gotchas:
- A Proton version based on Proton 9.0 or higher, such as Proton 9.0 (Beta), Proton Experimental (currenty based on Proton 9.0), GE-Proton9-1, etc. This is required to fix the game running at 11-14fps (tested with GameScope which shows the Steam Overlay, and the Steam Overlay reports this framerate). Once selected the game runs buttery smooth.
- This one seems not to be related directly to Proton, however, the game mouse sensitivity and scroll sensitivity, even with the lowest possible registry settings, are still way too fast for my tastes. I have not found a way to fix this, but I wanted to note it as issues like this are sometimes Proton-specific, but for Dungeon Keeper 2, it appears to not be Proton-specific.
- See this forum thread for the GOG version voicing a similar complaint (the Steam release is the same as the GOG release as far as I can tell): https://www.gog.com/forum/dungeon_keeper_series/dk2_mouse_key_movement_sensitivity_way_too_high
Overall works great once I changed the Proton version, although has a couple of small control QoL issues simply due to the game's age. Tested on KDE Plasma Wayland 6.0.1.
The game needs dotnet40 to run its launcher, and your WINE Windows version has to be set to Windows 7. If you're unfamiliar with the game like I was, it has its own launcher, more on that later. To fix the launcher:
- Run the game once and let it fail so Steam can generate the Proton prefix
- Then, set your
WINEPREFIXto the path to the Steam Library Folder that Elite Dangerous is installed in. If you've installed Elite Dangerous in the default install folder, the command would beWINEPREFIX="$HOME/.local/share/Steam/steamapps/compatdata/359320/pfx" winetricks dotnet40 win7
Initially, the game was set to a resolution of 1280x720. When I set it to 1920x1080, the game shrunk into a smaller window and I couldn't set it to fullscreen. I restarted the game and this was fixed
- Now about that launcher: you might get some issues after running this command about
rundll.exeand it not being able to find an application to launch, or something to that effect. Press OK each time these come up, and then use the launcher to go to the site and create an account. Link it with your Steam account, log in on the launcher, it'll tell you to buy the game so restart, and then open the game again. You should now have an orange play button in the corner. - I had the game running for nearly 2 hours, I completed the tutorial and all worked well. I haven't had any issues so far. I don't have the DLC for the game, so I can't comment too much on that (yet)
Use Gamescope and make sure to check your resolution is not blank in settings, and it's great native and with Proton with 1440p60 @ max
Game does not like multi-monitor setups on KDE Plasma Wayland, had to use Gamescope to fix this
- Did not have this issue when running under Proton
Game did not automatically detect a resolution so I had to manually select it in the settings (2560x1440). Not doing this will mess the game up when you try to save settings as it won't know the correct resolution to set to.
- This issue is also present with Proton
Tested the game natively and with Proton, I could not discern a performance difference though the native release used about 10% more CPU. Some notes:
- Tested on KDE Plasma Wayland with all settings at max except for vsync (off) and MSAA (High as opposed to Ultra, as this seemed to fix some aliasing issues)
- Save files do not carry over between native and Proton
- The Proton release has a bit less "pop in" it seems, but I did not extensively test so it could be just that one specific circumstance
- Tested both native and Proton with Feral GameMode enabled but it did not seem to make a noticeable difference
- Tested the native release briefly using Zink, this had worse performance (~55fps as opposed to solid 60fps) and some artifacting
- FYI for native release, the Music folder for custom music is not stored in the Documented folder stored in the relevant XDG spec folder (such as
~/.local/share/Euro Truck Simulator 2). Symlinks are supported
Both native and Proton are a great and pretty much equal experience. I would personally have stuck with the native release if save files carried over, but I am now further along running with Proton so I'll stick with that for now (or until I want to switch and find out if I can migrate save files).
DXVK_FRAME_RATE=60 %command%
Game detected my Steam Controller without any issues. I chose to cap the framerate using DXVK but that was my own preference and is not strictly necessary
Easy Anti-Cheat from lazy developers broke this game
The anti-cheat they added breaks the game for Linux players :(
Works out of the box at max settings
Everything worked out of the box, I had no issues at all and forgot it was even running under Proton!
- Afaik the game has no local multiplayer, so I didn't have anything to put down for that option
- Tested with a Steam Controller
- Tested with everything at max with absolutely no performance degredation
- Tabbed out frequently without any problems
Use launch options "WINEDLLOVERRIDES="xaudio2_7=n,b" PROTON_NO_ESYNC=1 %command%" to fix audio, navigate to "/steam/folder/path/steamapps/compatdata/377160/pfx/drive_c/users/steamuser/My Documents/My Games/Fallout4/Fallout4.ini" and just under the "[Controls]" section (for me it was at the bottom of the file) set "bBackgroundMouse=1" to fix mouse speed issues. Finally, open the winecfg for the Proton prefix (I recommend using Protontricks, though you can export the WINEPREFIX in a Terminal session and do that too: https://github.com/Sirmentio/protontricks), go to the "Graphics" tab, make sure "Automatically capture the mouse in full-screen windows" is checked, and check "Emulate a virtual desktop." Set it to the resolution of the monitor you intend to play Fallout 4 on - For me, 1920x1080. Click apply, exit winecfg and winetricks, and the game will launch! I get a pretty consistent 60fps with max settings (and no performance boosting mods) after the game finishes loading. Tested walking around a little bit and some brief combat. Game crashes more often than not if you try to exit to desktop from the pause menu - Instead, exit to the main menu and then exit the game from there. I have not tried any mods but intend to in the future. Someone else made a report talking about using the Vortex mod manager on Linux and said they had success with mods, so it seems to be possible. Overall, I'm very impressed with how the game runs after a couple of minor tweaks!
Didn't have to rename anything. No mouse issues. No lag issues. Game ran basically as though it were native.
In terms of performance, the game runs perfectly. I have it modded up to the eyeballs with anti-crash mods (NVAC for example) and the 4GB patched EXE (which everyone should use, as FONV is a trainwreak without mods). The only issue, and I stress, the ONLY issue, is that none of the radio stations work. If this was fixed, the game would have a Platinum rating.
As of Proton 3.16-5 Beta (which added an implementation of FAudio), the game runs 100% perfectly. Full 60fps, can alt+tab out of the game just fine, all my mods work, 4GB patched EXE works, and the radio stations now work as well. Excellently smooth and native experience.
Flawless. D9VK gives worse performance than stock DXVK, as a heads up in case you want to try it. Radio New Vegas is the only radio station that works as soon as you start up the game. The others take a little while to kick in (about 30 secs). Turn off the on-screen effects like Bloom and HDR to fix screen glitches and broken AA. Can't alt-tab out of the game if running in fullscreen - Works if running windowed. Tested with the 4GB patch, CASM, NVAC, MCM and Enhanced Camera. Game ran comparable to, if not better than, Windows. Solid Proton title.
Don't Alt+Tab if you play in fullscreen (if you play in Windowed then it doesn't matter) and disable HDR as it causes graphical flickering with dust. Both of these issues can be present on Windows though mostly on old hardware, so it's just a result of the game's engine being so old and not a fault of Proton necessarily. I installed a bunch of mods such as NVAC, 4GB patcher, NMC's texture pack (the 2048x2048 version), CASM, MCM, and the PipBoy 3000 reskin. These all worked. Radio stations work though they can be a little fiddly at times. Again, though, this can happen on Windows. It just seems to happen more consistently with Proton just like with the other issues.
As previous reports mentioned, adding various entries to the "Fallout_default.ini" file can fix issues. The only one I experienced was the mouse issue, which can be fixed via "fForegroundMouseAccelBase=0 fForegroundMouseAccelTop=0 fForegroundMouseBase=0 fForegroundMouseMult=0" as another report mentioned. Tabbing out in fullscreen doesn't work, and running in windowed mode breaks the Steam overlay (no Shift+Tab and no Steam Controller, big rip). It also causes the game to hang on exit and you have to manually kill the FalloutNV.exe process (I use KSysGuard but any System Monitor or equivalent Terminal command will work too). Performance is pretty much the same as Windows, just turn off HDR and Bloom (not even D9VK fixes this, and D9VK gives worse performance anyway in my tests). Trying to use galliumnine just borks the game for me so I couldn't test performance. The best part though: I was able to use the Vortex Mod Manager (previously known as Nexus Mod Manager) to install my Fallout mods. Enabling the script files sometimes doesn't work and I have to do that from the Fallout: New Vegas launcher, but I think setting load order works. I installed 0.17.X through Lutris (see here: https://www.youtube.com/watch?v=MDr7L-XRd54) but install Vortex on the same drive as your game or else you'll get a nasty error message about failed deployment. This is a result of EXDEV not being able to link files across drives/partitions. After you install Vortex on the correct drive, install the mods as you normally would for New Vegas, but without the glorious Mod Organizer 2. We can hope for WINE support someday. Profiles for New Vegas also work with Vortex, and you can switch between them with ease. NVSE and JIP NP NVSE both work, which are dependencies for many mods. The 4GB patcher works (I ran it using my system WINE installation of 4.11). On top of this, I tested NVAC, MCM, CASM, Enhanced Camera, Clarity, PipBoy 3000 Reskin, NMC's Texture Pack (2048x2048) and the Enhanced Loading Screens. Texture packs had no impact on performance, nor did any of the mods. The game seems to run much more stable through WINE/Proton, which is interesting. Either way, all the standard New Vegas mods will work when either installed manually or installed through Vortex. Excellent experience! Pity about the tabbing out, but alt+tab is kinda broken on Windows, too.
Game performance is solid, no need for D9VK (actually worsens performance). Audio will sometimes take a little bit to pop in from the PipBoy but this happens on Windows too. You can't tab out if you play the game in fullscreen as the game won't gain focus again. Bit of a pain, but oh well. Tested with a ton of mods (NMC's Texture Pack, CASM, MCM, NVAC, PipBoy 3000 Reskin, to name a few) and they didn't impact game stability from my tests. Use Vortex Mod Manager to apply these mods, or apply on Windows and boot the game using WINE. Disable HDR/Bloom to get rid of graphical effects. I didn't have any issue with VATs and never have, for what it's worth. Your mileage my vary though
Game works and mods do too, but trying to get LOOT to work on Linux to fix some load order stuff seems challenging. Just a heads up if you plan to play with mods! Vortex Mod Manager's load order sorting seems to do nothing.
Works out of the box with mods, however load order will get messed up. If you could theoretically get LOOT to run (which won't work under WINE or Proton for me, and I can't get the native Linux build to install) or had some other way of setting load order, you could play this game with mods using Vortex Mod Manager and it would be like native.
Game works out of the box
Not sure what the other reports were about, but the game may not work with DXVK on Intel iGPUs. However on my RX480 the game worked perfect out of the box
No issues with the latest version, using Mesa 20.0.0-devel with Valve's ACO fork
Not sure that the issues in the other reports were about in regards to drivers, but I haven't had any problems.
Classic, no issues. Fullscreen works, tabbing out works, all graphics and audio work, it's like native!
Everything works without any tweaks!
Haven't had any issues with alt+tab unlike other reports have mentioned
Works out of the box without any tweaks required
Worked without a problem on my laptop's iGPU. Some games have problems running on an iGPU but this game did not.
Needed to force the game to use the Steam Linux Runtime (used SteamTInkerLaunch, there are probably other ways too) in order to fix the game crashing at startup. This issue affects some native Linux games as of the last few months on my system
The problems I experienced could be specific to the libraries Arch uses, so if it works for you out of the box then you won't need this tweak.
Played at 900p, didn't get 60fps but it was more than playable
Set off a ton of fireworks on several occasions and the game did not crash once. Super stable experience even on this laptop. On a desktop the performance would probably be much bettter.
The game had some weird issues where the screen would not be cleared, so everything from the previous frame would overlay onto the new frames (akin to this effect in older versions of Windows. To fix this, I created a dxvk.conf file in the game's folder after browsing local files, with the single line dxgi.syncInterval = 1. This is my new favourite tweak for games to fix issues. Once this tweak is applied, the game will work just like it does on Windows.
I tested with a Steam Controller and it recognised it perfectly fine. No issues aside from the weird lagging effect I mentioned without the dxvk.conf file.
dxvk.conf- I created a customdxvk.conffile with the linedxgi.syncInterval = 1in order to fix the graphical issues I was having with the game. The framerate is now tied to your monitor's refresh rate e.g. 60fps
- Tested with and without the ACO backend
- Tested with a Steam Controller and a keyboard/mouse, both worked fine and the Steam Controller was detected without issue
Base Game and Hat DLC work out of the box
Had no issues running this game at all. Just press play and go ahead! The Hat DLC works too for those wondering.
DXVK_FRAME_RATE=60 %command%
The launch command adds a framerate limit. You can limit the FPS in other ways or go without the FPS limit if you want, I just didn't want the game running at 2000fps :-)
gamemoderun %command%
Ran with no issues for me at 1440p max settings, a solid stable 60fps with drops only down to about 40 for a couple of seconds during loading. No framedrops during matches.
- Played on KDE Plasma Wayland
- Game used about 65% of my GPU according to KDE System Monitor
- Played with some character mods, no problems (installed manually, did not try any mod managers)
- Played with a Steam Controller (Y button prompt missing but this is a game bug, not a Proton bug)
- Played some Arcade mode, training and tutorial missions without any problems. I haven't tested online play yet but I don't foresee any issues
- The
gamemodelaunch option may not be necessary
gamemoderun %command%
Absolutely no issues with framerate or latency while playing, other person I was playing with also said there were no issues
Older reports mention videos not working, framerate issues, mouse fullscreen weirdness and other bad things. This was the case when the game was out but is all fixed now and the game runs like native. Proton Experimental may be needed for the video fixes.
Latest patch works without any further tweaks needed, Proton Experimental needed for video fixes
Did not connect with my VPN turned on but was fine when I closed the game, turned the VPN off and opened it again.
The latest balance patch worked for me without any problems.
- Tested with a Steam Controller
- Tested on KDE Plasma Wayland
- Tested on 1440p max settings, Plasma System Monitor said my GPU usage was around 80% (vsync turned off)
Works out of the box, 1080p60
Played with Proton 6.3-3 and DXVK, didn't have any issues with graphics or sound. Played until the end of the tutorial.
- Tested with a Steam Controller
- Turned off vsync for better performance
Even though it's not on the store anymore, if you own it, it'll work perfectly fine with Proton
Worked perfect on the "Very High" settings preset
No complaints here. I haven't got a chance to test the Online Multiplayer yet but I played a dozen or so single player races.
- Steam Achievements work just fine
- Played on the "Very High" graphics preset (you can only choose graphics presets for this game, no granular control) and everything ran like a native game
- Tested with a Steam Controller
Game works great including local multiplayer
- Tested with a Steam Controller
- Tested a local multiplayer race using Remote Play Together with a friend, and we were both able to play just fine!
- Tested the game on the "Very High" graphics preset, didn't have any performance problems I still haven't gotten around to testing the Online Multiplayer, but there's no reason why it shouldn't work
Works flawless, even on integrated graphics. Tested my Steam Controller and it works too.
Works perfect with both default whitelisted Proton version and the 4.11-9 (the current version)
Tested the game with a keyboard and with a Steam Controller without any issues.
Works perfectly. Requires the same workarounds as Windows 10 to get it to run at 16:9 stretched and fullscreen (run in windowed mode, change settings, run in fullscreen usually works. You might have to try a few times. Again, this is present on Windows 10 too)
Perfect performance. Any graphical issues that need working around are also present on Windows and are not related to WINE. And as mentioned, they can be easily worked around.
Had to set the game to windowed, then set all the settings (including fullscreen) while the game was in windowed mode. This workaround is required on WIndows 10 as well and is not a Proton specific issue, hence the Platinum rating. Even on my specs with an iGPU it ran at full 60fps with no frame dips.
After extensively testing for several hours, the game works flawlessly under Proton.
Flawless. Works great, even on integrated graphics like my laptop.
Game has issues trying to fullscreen after changing certain values such as anti-aliasing. This issue is present on Windows too, it is not a Proton-specific issue however it is worth noting that you may have issues.
Works perfect
The bugs present in Windows when trying to fullscreen the game and set options such as anti-aliasing, are also present with Proton. It will work but it can take a while. This is not a Proton-specific issue however.
Works flawless through Proton, any issues present are also present on Windows
You may experience issues with certain menu settings, and they may be fiddly to get working. See previous reports on how to get around this, but it isn't an issue with Proton. It's just an issue with the game.
Runs perfectly on a variety of hardware and Proton versions
Tested on Manjaro and standard Arch across a bunch of different types of hardware and Proton versions. I've had no Proton-specific issues running this game. It has some bugs with setting certain display preferences but this happens on Windows too. Overall, the game works perfect. Tested with and without Valve ACO, a bunch of different Mesa versions, and tested with my Steam Controller and a keyboard/mouse. No problems whatsoever.
Works with keyboard/mouse and controller perfectly
The game works great! I haven't had any crashes, the fullscreen issue is a little annoying though but once you fix it the first time you won't need to mess with it again.
- The fullscreen issue is also present on Windows. Go out of fullscreen before you change any graphics settings, and apply fullscreen last. It's an old game ported from Xbox Live Arcade by a studio that has since been dissolved, what can you do?
- Tested with Remote Play Anywhere streaming to my phone and with my Steam Controller, I didn't have any problems at all
Works out of the box with Proton 6.3-7
Previously, this game had issues when configuring the video settings. These have since been resolved and the game runs out of the box with no tweaks. Some notes:
- Tested with a Steam Controller
- Tested with a Keyboard/Mouse
- Tested with a Nintendo Switch Pro Controller
- Tested under KDE Plasma with both X11 and Wayland sessions
- Additionally, there were no input or controller issues when running under Wayland
- Tested with with Steam Link Android app and did not have any issues using a Steam Controller or touch controls with this game
Overall this game is a pleasure to play on Linux and will be a great one for the Steam Deck!
Works out of the box at max with Proton 5.13-1 (DirectX 11 AND DirectX 12)
Unlocking the framerate didn't seem to work, could be a bug with the game though.
- I did a quick playthrough of the first level of the release version of the game as opposed to the demo other reports mention
- I tested the game at max settings using keyboard and mouse, and tested both DirectX 11 and DirectX 12 renderers. DX12 gave no noticeable performance boost or made any difference, but it worked with perfect, showing the maturity of the work on vkd3d-proton on games out of the box
- Not sure if it was related to Proton or just the game, but mouse sensitivity was incredibly low. The value it defaulted to was so low that I had to turn it up to 100. Other games don't seem to have this problem to such an extent which is why I mention it here
- I did test the game with Proton-5.9-GE-8-ST and it worked fine, but I only tested with DirectX 11. If you prefer using the GE builds of Proton those, the latest at the time of writing seems to work just as well!
No tweaks at all were needed to run the game, just booted up and went for it. Most of my playtime was spent with the DX12 backend as I was curious to see just how well it would work. Your mileage may vary based on GPU drivers (mesa-git and NVIDIA beta drivers are recommended generally) so if you have any problems you can switch to using DX11 and it should work just as well.
Runs perfect with Proton
Game has some issues (mainly around audio layering) but they aren't related to Proton
- Steam Leaderboard work
- Steam achievements work
- Tested with a Steam Controller
Launcher works and works well, crashes most probably due to WMV playback
There's a Lutris launcher for it, perhaps there's a way to link the Lutris WINE prefix to the Proton one? Although the Lutris prefix is 32bit and installs
wmp10, which is requried for playing the WMV files. Similar to Bubsy: The Woolies Strike Back, you can't installwmp10in the Proton prefix because it's 64bit. I've tried to find workarounds to use 32bit prefixes with Proton but haven't gotten anywhere.If you do want to play this game and are willing to use Lutris, there's an install script available and you can play the game through WineSteam (although with the new Chromium-based library view is glitchy and the friends menu doesn't work, and you have to close native Steam to use it). There's also a GoG install script available if you have the game from that platform.
Played through the game completely on Linux native a few years ago, still works great now
- The game detected all of my displays correctly (listed as XWAYLAND1 through XWAYLAND4), but it listed a lot more resolutions than I had available. It listed 3840x2160 as one option (the resolution of my scaled display), but when I selected this, the game was too big as if it was rendering part of a 4k display on a 1440p resolution (the scaled resolution for my primary display).
- To fix this I just chose 1440p. 1080p worked as well.
Tested on KDE Plasma Wayland
No problems with Proton 7.0-3
Fullscreen was not enabled by default, Alt+Enter allowed me to toggle it. Game works flawlessly as if it were native. Tested on KDE Plasma Wayland.
The game runs, all levels are playable as is the level editor. Unfortunately, the movement speed of everything is too fast. Exceptionally fast. This could be a general game bug as I have no tested on Windows 10, but in my previous tests of just using WINE and Steam it did not have this problem.
Game runs too fast again. D9VK causes the girls not to show up in the background. Couldn't get libstrangle to work with this game. If you could limit the FPS to 60, I imagine the game would work fine.
I used a custom dxvk.conf file in order to lock the game to 60fps. This is apparently an issue on Windows too if the monitor's refresh rate is more than 60hz, although the developer has stated otherwise on the Steam discussions. As the game was made in GameMaker, this seems to be an engine limitation.
To lock the game at 60fps:
- Open the install folder for the game (this can be done in the new UI by clicking the settings wheel button -> Manage -> Browse Local Files)
- Create an empty text file in this directory (the EXE should be located in this directory too) and name it "dxvk.conf"
- You can see a full
dxvk.conffile here, however only the following line is needed:dxgi.syncInterval = 1 - Profit!
Gothicc Breaker will now be locked at 60fps!
A few extra notes:
The patch for this game works! Go to this directory (
steamapps/compatdata/819230/pfx/drive_c/users/steamuser/Local Settings/Application Data/Gothicc_Breaker/) based on where your Steam library folder is, and modify the given file calledCENSORED.txtfrom sayingtruetofalse, just like you would on Windows. The reason I make reference to this here explicitly is to not only show that the patch works, but also to give you the directory to find and enable the patch!I can't verify if the controller is actually detected as a controller. The Steam API says that it is as I get the notification in the bottom right, however as there are no controller prompts it's hard to tell if it's detected as a controller or just mapped to my keyboard and mouse.
I can't use the analogue stick to navigate the menu with my Steam Controller, I have to use the D-Pad. However, I can use the analogue stick in game no problem! Perhaps the game is just mapped that way, as I never used a controller on Windows for this game. Either way, it is perfectly usable and I found no issues whatsoever.
Set dxvk.conf file in the game's EXE directory with the line dxgi.syncInterval=1. See this guide or previous reports for more detailed instructions: https://steamcommunity.com/sharedfiles/filedetails/?id=1907165410
Tested with Steam Controller and it worked great. Remote Play worked as well!
The game's logic is linked to the framerate. To limit this to 60fps, create a file called dxvk.conf in the directory with the game's EXE (browse local files, it's the default directory). Add the following line: dxgi.syncInterval = 1. For more information on DXVK configuration files, see here.
Tested with a Steam Controller. Works fine!
The game's logic is tied to its framerate which is always expected to be 60fps. On Windows, this is locked properly but it is not on Linux. To fix it, you need to do the following:
Custom dxvk.conf file - Create a file called dxvk.conf file in the directory with the game's EXE, which is the default directory when you browse the game files. Inside that file, add the following line to lock the game to 60fps: dxgi.syncInterval = 1
This tells DXVK to force vsync. If you don't know, DXVK is a layer of Proton that converts Windows graphics calls (Direct3D) into Vulkan. You can learn more about dxvk.conf and all of its parameters on the GitHub for DXVK.
As long as you have the file with the line specified, this game will work on every version of Proton that I have tested from at least 4.2-9 and up.
- Tested with a Steam Controller
- Tested with a third-party Nintendo Switch Pro Controller
- Played up to Level 6 and also tried out the Level Editor. No crashes or bugs so far
DXVK_FRAME_RATE=60 %command%
The framerate lock issue is a game bug that can be fixed by locking the game's framerate. There are a few different ways to do this, but using DXVK as described is one way. Forcing vsync using a DXVK config file is no longer required as DXVK now has the mentioned environment variable.
- Using Proton-5.21-GE-1 GloriousEggroll, which allows for DXVK async
- Using
DXVK_ASYNC=1launch option, not sure how much of a difference it makes but I have it enabled for most games now anyway - Using launch option
-RequireFocusToUpdate=falseas suggested by another report to save memory usage
You could leave out both of the launch options listed. If you want to use the Vulkan backend, you'll need Proton-GE
However, note that in my tests, the Vulkan backend wasn't quite as smooth as the DirectX backend. There was some microstutter, and vsync off caused some major hiss from my GPU fan, something not present in other games or with the DX11 backend which only had roughly 20fps of a difference. Your mileage may vary. The Vulkan backend caused the Steam overlay to flicker as well, which I've never seen from any game before. I can't say whether this is Proton or the game's relatively new Vulkan backend being a bit buggy, but personally I went back to DXVK. Some other notes:
- Tested with a Steam Controller and a keyboard/mouse. No issues
- Tested 3 levels of the game, didn't have any problems or slowdown
- Tested across multiple versions of Proton 5.0 and haven't had any issues
DX11 and Vulkan backend work out of the box with pretty much identical performance
Played at 1080p and mostly got 60fps with some slowdown when loading new rooms. Lowering the resolution would definitely help. Other notes:
- Tested with a Steam Controller
Forcing Steam Linux Runtime fixes the native game
You need to force the Steam Linux Runtime otherwise the game window will not show up. The game does not launch normally because it is looking for deprecated libraries.
Runs great aside from anti-cheat breaking online matchmaking
- Easy Anti Cheat breaks online matchmaking. However, you can play at least Firefight with friends lobbies. I tested this personally and it worked fine. I have not tested custom games or co-op (though I plan to test co-op soon)
- If you launch the anti-cheat version it will default to using the version that does not have anti-cheat, but for convenience it's best to select the non-anti cheat enabled version.
Anything with online multiplayer matchmaking won't work. I tested Firefight though and it worked fine. I haven't tested custom games or co-op, but I've heard mixed reports on how well they work. I intend to test soon though (once I have someone to test with). I don't see why they wouldn't work, considering Firefight worked. Performance was exceptional, worked great on my previous RX480 /i5-6500 and even better on my current specs
Unless you want to play co-op or play online competitive, you'll have a great time running under Linux
While it did not originally, MCC Singleplayer now works out of the box with Proton! Some notes:
- I experienced one crash in my 3 or so hours of playing. All of my playtime is under Linux, so I have no comparison for Windows, however it didn't seem to be related to Linux. It was a message box that said "Fatal Error" after excessive tabbing out
- Despite online competitive not working, Firefight on Reach does work
- Online co-op could work eventually, as far as I know it's being actively worked on. Check out the GitHub issue for MCC for more regular updates
- Tested with a Steam Controller and it was recognised fine
Works perfect so long as you aren't planning to play multiplayer
I had issues with Left Shift. Binding to a different key and rebinding back to Left Shift, then rebooting fixed the issue
I haven't had any of the stuttering or audio problems mention in the other reports and I've played around half of the Reach campaign so far. It works out of the box like a native game for me. If you're only planning on playing the campaigns like myself then you should be good to go just pressing the Play button!
Single player campaigns work perfectly fine
Online competitive multiplayer does not function due to Easy Anti-Cheat. However, Firefight and co-op should work fine! Co-op seems to be a bit hit and miss when playing with other Windows players at the moment, though it should work fine with other Linux players. Reach Firefight works completely fine, I played for about an hour or two with a friend on Windows. Investigation into the co-op issues with Windows players is being done, and you can keep up to date on the Proton MCC GitHub Issue Tracker thread.
- Steam Controller and Keyboard/Mouse work
- Had a slight issue with my left shift key not working a while back (it worked in chat) - To fix it, I unbound the suit ability key in settings, restarted the game, bound it to left shift, restarted the game again, and it has since worked perfectly fine. Previously, the shift key had worked too, but I only played for around 2 hours. Now that I've played for over 10 hours since rebinding, it seems the problem has been resolved by following those steps
- Played 8/12 missions in Reach and haven't had any problems
- Achievements do not work as they require EAC, but the campaigns function as normal
Runs at 1080p60 with original graphics, 1080p with enhanced graphics at lowest settings with mixed framerates
Game runs exceptionally well on this hardware. Hovers around 45-50fps on enhanced graphics with occasional drops down to 30, but is a smooth constant 60fps on the original graphics. Some notes:
- Tested Reach briefly and worked with reasonable framerates
- Tested Halo 1 extensively (3+ hours) and had a solid experience
- Tested with a keyboard and mouse, but my Steam Controller was detected and worked
A perfect native experience
Game works with keyboard/mouse and detected both my Steam Controller and Switch Pro Controller just fine.
Perfect experience out of the box
Unlike other PopCap games, I didn't need any -changdir launch option, all menu settings worked (fullscreen, hardware acceleration), and even the custom cursor worked without slowing the game down! Unlike Typer Shark Deluxe. Overall, out of the box experience.
Haven't played much but it runs and works fine with good performance at highest settings, 1080p60
Everything works
No slowdowns even with large amount of tiles, all achievements and puzzle autocomplete work
Changed name but still works like before
Game used to be called "Hentai Girl Betty", same game just renamed. Everything still works as expected
Spent over 2 hours playing this game to 100% completion just to confirm that it works flawlessly with Proton.
Think I got a cramp in my finger playing to write this report from all the clicking. Runs out of the box, no framedrops, everything works, no font glitches or anything. On first boot I got a crash after about 30 seconds of playing, but that hasn't happened again.
Lags a little if there are a lot of tiles and a lot of moving stars. Zooming in usually fixes this. Game can be 100% completed with Proton
Unlocked all achievements, Steam Controller can be set to use the WASD and Mouse config and it'll work with the game (though you probably won't want to do this). Framedrops when lots of tiles are on screen but that could just be an issue with the game. Doesn't take away from the experience. Perfect compatibility!
No issues to report
Sometimes gets a little sluggish when there are a lot of tiles, but this is probably a Unity issue. Tested with all settings at high, you might be able to mitigate this by turning the settings down (if it even does anything, which for these hentai games, I'm not sure it does)
Works flawlessly even at highest settings
Might slow down a little if there are a lot of tiles but that's just a game issue, nothing to do with Proton.
Works out of the box, just like the original Hentai Mosaique game. Runs identical in terms of performance and such. No issues so far, but haven't played for long. Achievements work too.
Runs exactly like Windows at max settings (turn down for improved, constant 60fps)
Works without tweaks at highest settings
Occasional slowdown when there are a lot of tiles, but it isn't noticeable for this type of game.
Runs perfectly out of the box
Tested with keyboard/mouse. Optionally, limit to 60fps to save GPU strain by creating a dxvk.conf file in the game's EXE directory with the following line: dxgi.syncInterval = 1
Game says I've played 17% of the puzzles, have not had any issues so far
Played the native release, haven't experieneced any problems with it.
Played the first level and I didn't have any problems with the native release
Just like the other games in this series, this one seems to work fine as well. It took a few seconds longer than most games to exit fully but that was a very negligable problem.
mangohud MANGOHUD_CONFIG="fps_limit=60;no_display" %command%
The native game (which uses Vulkan according to MangoHud, very awesome!) performs excellently at 1440p.I have not played much of the game but I have yet to encounter any problems.
- The game ran at about 400fps on my hardware, which is why I chose to cap the framerate
No issues, typing "666" applies patch as expected
Didn't complete all the puzzles, only a few. But I can't see the game having any further issues
Game needs xact to fix audio not playing. It also happens to fix a bug with the game resolutions list not displaying correctly. You can install it with Protontricks (a wrapper for winetricks) using the following command:
protontricks 1086900 -q xact_x64
Game works great out of the box! Sometimes it launches windowed, so you'll need to use alt+enter to fix that. Some extra notes:
- Tested briefly with a Steam Controller, it was detected fine. I mostly played with a keyboard
- Game defaulted to having sound and music at 0% volume after installing xact, so I needed to run those up manually in settings
- Tested local multiplayer against myself, no issues
- Did not test Remote Play Together, but there is no reason why it should not work
- Could not test online multiplayer as there were no rooms and I don't know anyone that owns the game to test with
- Without xact, the game does not show a list of displays to play on. After installing it though, it detected my monitor at 1920x1080 and 60hz
Game works out of the box now with Proton 7.0-3
The previously mentioned tweaks are no longer necessary :-) Game works out of the box
Native works better than Proton
Should work perfectly for most users, just keep in mind to install pipewire-alsa if it's not on your system already and the game is missing audio.
Works out of the box
Game is CPU bound, as it only uses a single thread. However this impacts the gameplay very little and the game is overall an out of the box experience. Tested with a Steam Controller
Works out of the box
I had no issues at all with this game. My Steam Controller and 3rd Party Nintendo Switch Pro Controller worked fine. I even tried a few different controller profiles for my Steam Controller. Overall, a very pleasant experience!
Game runs basically perfectly. About 56fps at 1080p fullscreen. Without the Steam FPS counter though, I wouldn't have been able to tell. This game runs as though it's got native support. Absolutely flawless. I had the game crash once during the first boss fight, and if the Steam Controller turns off while the game is minimised then you'll have to restart the game. This could have a general bug with the game, as I have not at all tested this game under Windows 10. Perfect rating.
Game runs perfect
Most likely due to video codecs (like Catherine Classic), the game is borked. I believe it's meant to have a movie opening, but it gets stuck before it can play it. The game will just not load anything, kind of like if you were to leave Catherine Classic on the initial startup screen. I attempted to use install-mf, but I had no luck. That actually caused the game to freeze and crash at that screen. Shame.
Opt into the beta, as other reports said. This allows you to skip the intro cutscene by clicking, so you can load the game. I played for about 2-3 minutes and didn't encounter any issues. Unlike other reports, though, using mf-install caused the game to crash for me. However I have not tried it on a fresh prefix with the beta
Opt into the beta by right clicking on the game -> Properties -> Go to the "betas" tab and, as of the time of writing, click on qa_v1.0.1 - which should be the only option listed. It might take a while for the game to start to the main menu so you might hang on a white screen for about 5 seconds, but be patient and the game will load and you can now date Colonel Sanders on Linux like you've always dreamed of
Seems to work with my Steam Controller as well, for those interested in playing with a controller
Works with no issues, including typing "666" for the patch
Attempted a few of the puzzles, then used the autocomplete the for the rest. Everything works without any issues!
gamemoderun %command%
Was able to send and receive kind words :-)
GameMode is only needed as the game can be a little heavy, but otherwise it's a perfect native experience
Played the native relese and it's worked fine for about a year
No problems to report. My Steam Controller worked fine as well.
gamemoderun %command%
Worked great on Linux! Notes:
- Tested on KDE Plasma Wayland with a Steam Controller
- GameMode helped with some stutters but worked fine without it
- Tested Remote Play Together, the other person said the network problems got in the way but I don't think this was specific to Proton
Disable esync to fix audio looping issue, which is the only out-of-box issue with the game. Now, your launch option string should look like: PROTON_NO_ESYNC=1 %command%
I didn't experience any slowdowns, and had an extremely nice experience with the game after disabling esync. I forgot it was running under Proton! Some extra notes:
- Tested with Valve ACO driver
- Tested with Steam Controller
- Tested with "Enhanced Graphics" and then tested with "FSAA x8", as the two can't be used together (engine limitation, nothing to do with Proton, see here). No performance degradation when using either of these and they both worked as expected. All other settings were at max
Disable esync to fix audio looping issues
- Runs at a solid 60fps with everything at max except FSAA. I turned that off, but you could probably keep it at about 2x on this kind of hardware. Note that this is purely a hardware limitation
- The Enhanced Graphics also works fine
- Tested with a keyboard/mouse and a Steam Controller
- Remote Play Anywhere works, I tried streaming this game from my PC to my phone and encountered no issues
Game runs perfect native, no tweaks needed
Native version works no problems, and has since the game came out at launch
The launch options PROTON_USE_D9VK and PROTON_NO_D3D11 are needed to fix a problem with the game's intro transition, where 1/3 of the screen fades in before the other 2/3. This fade effect doesn't seem to work properly without these launch options. Your final launch option string should look like: PROTON_USE_D9VK=1 PROTON_NO_D3D11=1 %command%
During some cutscenes, performance tanks. But this is really only in a small handful of cutscenes and not during gameplay. It doesn't impact the game but it happens. Note that this doesn't strain hardware, the game just tanks in framerate.
Steam Overlay does not work. I don't know if this happens on Windows but it didn't work for me in this game.
Works great under Proton
Can't properly alt+tab out of fullscreen, you'll need to press F4 to toggle fullscreen to do this. If you tab out, the game window still tries to take control of your input. While none registers, you can't move your mouse cursor outside of your current monitor. When you want to tab out, just press F4
The game runs at a solid 60fps. I mean, it's a cheap, low-effort game but it runs perfectly fine with Proton. In that respect, compatibility is perfect.
Got a couple of very minor frame dips (most probably my hardware) but it wouldn't have been noticeable if I wasn't looking at the Steam FPS counter. It's an asset flip title, but it has perfect compatibility.
Force Steam Linux Runtime using either the Steam compatibility tools dropdown or a third party tool such as SteamTinkerLaunch.
- Note that you may need to download the Steam Linux Runtime. To do this, search "Steam Linux Runtime" in your library and download the one without a suffix.
Native port is great but works just as well under Proton
Native is capped to 60, so there may be framedrops if you're burning a lot of items (same thing happens on macOS and Android). The game can't be locked to 60fps with DXVK as it doesn't seem to use Vulkan, libstrangle might work but I haven't tried it. The game runs at an excess of 500fps for me so no framedrops encountered, but I didn't test very long. Stutters a little when you tab out of Steam, but no real issues preventing you from playing comfortably with Proton.
The native port is probably better, though.
As of May 10th update you need to rename/remove some libraries in the game files to fix some bugs, works perfectly afterwards
Older release of the game worked perfectly, they messed it up a little with the latest patch but it works perfectly after those two tweaks mentioned. Forcing the Steam Linux Runtime using a tool like Steam TInker Launch could also fix it
Native works perfectly
Did not try Proton. Played natively and tested again recently, it still works fine.
Native works flawlessly
Played native at launch and it still works great. No problems to report.
- This is not Linux specific but I used MGROverride which overwrites the 800x600 resolution for the game to be a custom resolution (in my case 3840x2160). I was able to run this with my system's wine without any tweaks.
- By default, this game is limited to a fixed list of output resolutions and will not go higher than 1080p. If you want to play at resolutions above 1080p you'll need this mod even on Windows
After a 6 hour play session the game dropped to 56fps and I had to restart to fix the performance. This is a game bug even on Windows and is not specific to Linux.
Played the full story to completion on Linux without any major issues. MGROverride has some issues as noted on the PCGamingWiki page where the UI might flicker (primarily after a mission on the results screen) but this is not a Linux-specific problem.
- Played on KDE Plasma Wayland
- Played with a Steam Controller
- Played with Feral GameMode on and off and it made no noticeable difference
- Game resolution had to be changed each time the game was launched, from 1080p to the 800x600 resolution that MGROverride set to actually be 4k
- All cutscenes and audio worked perfectly
The main takeaway is that the game performs identically to Windows! "All we're saying is: Give Wine a chance!"
To fix the game showing a black screen with sound, I had to replace d3dcompiler_46.dll. Open a Terminal in the folder where the game is installed (you can find it by right clicking on the game > Manage > Browse local files, and take note of the path) and running the following command:
cd /path/to/game/ && wget https://wikidll.com/download/5374/d3dcompiler_46.zip && unzip d3dcompiler_46.zip && rm d3dcompiler_46.zip
This moves into the folder where the game is installed, fetches the DLL, unzips it and then removes the downloaded zip. You can also do these steps manually if you wish. Thanks to other reporters on ProtonDB for these steps, I did not find this fix myself. Just noting that it worked for me
There were some slowdowns which I was able to mitigate slightly by turning off the smoothing in the game's menu. This is a game bug on Windows too.
Adding the DLL using the steps mentioned fixed the game for me. It has some slowdowns but these are present on Windows too. Tested on KDE Plasma Wayland with a Steam Controller.
Had to use mfinstall to install Media Foundation codecs (https://github.com/z0z0z/mf-install). This fixes some tutorial videos on how to use weapons. If you've played the game, you'll know where these are and what this tweak fixes.
Game runs no higher than 45fps for me at max settings - Windows would give me around 90fps. Locking the game at 30fps mitigates this.
The game runs absolutely horribly on my old but still decent specs. Disable vsync, lock the game at 30fps and you should be good to go if you can tolerate the 30fps.
Used mf-install to fix the weapon tutorial videos
Cannot alt+tab when the game is set to fullscreen. Setting to borderless fullscreen fixes this, and I can successfully tab out of the game. I have tested this significantly with no issues.
Game is significantly slower on my hardware, however Proton 4.11-8 gives a significant performance bump. Setting the game to low settings and then increasing the "Advanced Graphics Options", I can get the game to run at a consistent 45fps. This might not sound very good, but the game looks extremely smooth to me personally and this is more than playable. However, on Windows, I would probably get over twice this performance. Looking at KSysGuard, my CPU usage is at about 80% while the game is running. I am aware that Monster Hunter World spawns a lot of threads, and the mix of my exceptionally poor CPU and Proton using a lot of CPU to begin with, that's probably the culprit for my high CPU usage.
Tested the game with a Steam Controller, and my desktop environment is KDE Plasma 5.16
Works great at 1440p max, had to use GameMode to fix some performance drops at 1440p with the ALOT graphics mod
gamemoderun %command%
Played with the ALOT graphics mod and got some frame drops, but enabling Feral GameMode fixed this. Played through the first mission of Mass Effect 1 without any problems
Click play and it works, no tweaks required
Absolutely flawless!
- Played with a Steam Controller
- Played on KDE Plasma Wayland
Previously, the "corefonts" package was required. With Proton 3.16-4, this is not the case and the game will work perfectly out-of-the-box.
I think it was Proton 3.16.X that added the corefonts and since then the game has worked out of the box for me. No Unity errors or anything.
Brief test of a new game and native didn't have any problems
All settings appeared to be correct and I did not see any issues with the fonts, which can sometimes happen with visual novels. Overall a good experience
Game is no longer available, but it *does* run through Proton
- If you know anything about this game, you'll know it's no longer support. The online no longer works and due to some unfortunate events the game can no longer be played. But it runs the exact same as the native game did and currently still does if you had it in your library - yes, this game had native Linux support!
- Through no fault of Proton, when you try to load up the game it says that it's no longer available to play. That's why I've listed the multiplayer as not working. This isn't to do with Proton, however. The game is just simply no longer available to play
Everything works out of the box, lowering some settings will get you a better framerate
Optionally, you can lock the game to 60fps by creating a dxvk.conf file in the directory that has the game's EXE file, and add the line dxgi.syncInterval = 1. This isn't needed, though. Game works great out of the box
Flawless performance
Played up until after the crab mission, game runs great - Never dips below 60fps at max settings on my hardware
Aside from missing Steam Overlay the game works well
No Steam Overlay but this could be a game bug
- This means controller support may be impacted
Did not test a controller but your mileage may vary as there is no Steam Overlay. Unsure of whether this is a game bug or not.
Didn't experience any issues at all, controller worked out of the box and performance is exceptional
- Tested with Valve ACO driver, may have helped performance slightly?
- Tested with Steam Controller, it was detected out of the box
- Ran the game on an SSD and with a dGPU, perhaps running on lower-end Vulkan drivers or with an Intel iGPU adversely affects performance
Worked out of the box with no tweaks, tested keyboard/mouse and Steam Controller
I'm using Valve's ACO Mesa driver, not sure if that's made any performance difference. I tested the game at max settings with vsync off and got a pretty stable 55-60fps
Great performance out of the box with no tweaks
- Tested with Valve ACO enabled (
RADV_PERFTEST=acoin the launch options, only works with support GPUs) - Tested with Steam Controller
Works like a native game, patch included (both Steam and third party)
Your system will need the Japanese locale set for Japanese text it seems, but other than that everything works including patch both from Steam and from a third party site like Denpasoft if you bought the patch that way.
Proton-5.8-GE-2-MF GloriousEggroll
Proton-5.8-GE-2-MF is needed to fix the tutorial and opening video.
The video progress bar for the tutorial video didn't move, but you could click and move it around just fine. Aside from that I didn't have any issues. Tested all settings on max and didn't have any slowdowns, later on I turned vsync off for my own personal preference. I kept the game locked at 60fps, which you can change in the settings if you want.
Runs flawlessly with no issues. The Steam FPS counter says the game runs at 57-58fps, so it doesn't quite hit 60fps (unless I set my CPU governor to Performance, which drains laptop battery). However it really isn't noticeable and it doesn't impact audio. Native experience.
Native experience with this game out of the box
Did not require any launch options. Tested with Steam Controller.
Can't recommend because of the crash, but the game runs on this laptop hardware @ 720p30
Have not personally gotten far enough to experience it but the game will crash not too far in when trying to play a cutscene. This is a Media Foundation related issue, potentially relating to 32bit MF libraries. The issue has been reported and is well known by Valve and other Wine/Proton devs. Although updates can be found on GitHub, there may be spoilers for the game on there as it is necessary for debugging the issue. Investigation (and potential contribution) is good, but read at your own risk!
The main purpose of this report is to document that the game runs on this laptop hardware. The Media Foundation issue will hopefully be fixed eventually.
- This laptop is an Inspiron 5505. With the base configuration (8GB RAM single channel) the game crashed when trying to load beyond the main menu. When upgrading to 16GB dual channel, the game loads and plays beautifully. Played just beyond the initial quest from Popola at the very beginning of the game and encountered no issues.
- It is likely you will need at least 12GB RAM to run this game, based on monitoring the usage while playing.
- Game runs at a stable 720p30, which you can force with MangoHUD (
mangohud MANGOHUD_CONFIG=fps_limit=30). If you wish not to, it doesn't seem to fluctuate much and is still very playable. You can turn on performance mode in the settings which essentially seems to set a variable resolution, so the game may look blurry at times while playing with this setting enabled.- Despite the game running at a stable 720p30, it has to be played windowed. I am unsure if this is a bug with the game as I have yet to encounter this issue with other games, but playing the game at 720p30 fullscreen degrades the performance to an unacceptable degree. Playing in windowed is fine, however.
Though once again, this game will not work beyond the first cutscene which is a little ways into the game, if you wish you play on the laptop or use a patch to skip the cutscenes it will work on this hardware (and likely on your hardware too if you're using a halfway modern desktop PC).
Proton-GE-6.8-1 fixes the previously reported cutscene crash, which is also noted in the GE-6.8 changelog. Awesome!
I have not gotten far enough into the game to test the other cutscenes, but the main menu cutscene that plays after you idle for a while works now! GStreamer Dirty packages are no longer required for it either as far as I know (as I think GE bundles them). Some other notes:
- Proton-GE-6.8 gives a slight performance boost, but on this laptop it does not run at 720p60 (as it does not even meet the minimum requirements)
- Tested with a Steam Controller
- Completed the first quest involving killing sheep, so from my test light combat works okay without impacting framerate
Set CPU Governor to "Performance" (if using Plasma, see this Plasmoid:https://github.com/jsalatas/plasma-pstate) and disable anti-aliasing for a consistent 60fps. I played everything at max with blur and vsync off as personal preference. FAR mod doesn't work as DXVK doesn't support DLL injection, but as DXVK was made originally for this game, true 1080p fullscreen works out of the box meaning the only thing you're really missing from the FAR mod is possible performance boosts. Steam Controller works, however if you tab out then the button prompts will sometimes get a little messed up and flash between controller and keyboard - Tabbing out can sometimes fix this but it's inconsistent. This could be present on Windows though, as the PC port of this game is poor. But overall, Proton performance is excellent!
Played 16 hours, game runs at a pretty consistent 60fps with everything at max except anti-aliasing unless a lot is happening on-screen. Play with the FPS counter off and you won't even notice it. Aside from the FAR mod not working, you get a better out-of-box experience on Linux. On Windows, the game runs at 720p upscaled. On Linux with DXVK, you get true 1080p.
Note: DXVK makes this game run at native 1080p out of the box, so FAR is not required (it doesn't work with WINE anyway). Turn off AA for best performance (barely noticeable graphical difference), only had a few instances of the FPS dipping to an unplayable standard (only really in this sandstorm thing). Haven't tried setting the Windows version to Windows 7 using winecfg but I'll try it out. Completed Route A with no crashes at all. Everything works, shame about the FAR mod not working. I'd love to see this game running with a HD texture pack! All the usual stuff works: Controllers (tested with Steam Controller), achievements, and so on. Excellent experience, played for 33 hours so far.
Played for 50 hours, completed Route A and Route B with only one crash during a quest in the desert with Route B. Though framerate can fluctuate at some times, if the FPS counter was off I wouldn't notice most of the time. Also, be sure to set CPU Governor to Performance. I also hear that Valve's new Mesa driver gives better performance on AMD and Intel GPUs, but I haven't gotten around to trying it yet. Something to keep in mind if you're up for a bit of tinkering for slightly better performance, but overall the experience has been really solid for me and I forgot it was running under Proton a few times
Played for over 90 hours now and only played on Linux. I had one crash, and I've got pretty much a full 100% save file now minus the Fish Encyclopedia and Archives - That is to say, all weapons are obtainable and all quests are able to be completed. All I can say is, it's a whitelisted title for a reason! Great out of the box experience, and as always the resolution is always true 1080p but the FAR mod does not work.
tl;dr full controller support and flawless performance, enable esync for even better performance and ability to use up to 2x AA - Over 100 hours tested, game gets great performance with all settings at max (vsync had no real impact on performance, but the game is capped at 60fps anyway) and AA turned off. Unless you enable esync (PROTON_NO_ESYNC=1 %commad%), the game is unplayable with even the lowest 2x AA enabled. 4x AA is playable but has more stuttering. Better hardware - GPU and CPU - could really help with this. Set your CPU governor to Performance (search for a Plasmoid on KDE Plasma, otherwise do a Google search for how to enable it on your distro) as the game is quite CPU bound like other games such as the Hyperdimension Neptunia Re;Birth games. I highly recommend enabling esync for a more consistent 60fps HOWEVER you will have a really nice experience regardless hence why I gave the game a Platinum as opposed to a Gold. Keep in mind that this game is a very poor port, so from what I can tell the inconsistent framerate is a problem with the game in general. If a lot is happening on screen, the game can drop down. With esync on and 2x AA, I get 56-60fps consistently, with drops down to 44fps during intense fights. It isn't all that noticeable to me though, so if you don't have your FPS counter on you probably won't notice. If your compositor (e.g. KWin) has vsync already, you can disable it in game. But having it on didn't do anything to the performance for me, unlike in games such as Yakuza 0. Enabling blur didn't really have any impact on performance, unlike other games. A very minor thing to keep in mind: The "Select Monitor" setting does not work. Other games recognise the two WINE displays, but this game does not. You can move it to another window using a keyboard shortcut or special window menu, but you cannot do it from the in-game settings panel. Finally, I played the game with the Steam Controller, so there is full controller support. If you Alt+Tab out (which works, unlike in games such as Fallout: New Vegas), it can be a bit fiddly to get the game to show exclusively controller prompts again. You have to click to focus the window, then move your mouse to wherever you want it to be e.g. the screen edge, since the game doesn't hide the mouse cursor, and this usually has to be done from the likes of a character dialogue or a game menu (like the pause menu), and press the LEFT Alt key. No other key worked for me, surprisingly. Not even right Alt. When you move the camera, this may mess up again. Repeat the process and eventually it'll stick. Or just don't tab out, haha. Great experience, "Glory to Mankind!"
Great out of the box performance. Set CPU Governor to "Performance" (can be done with Intel P-State Plasmoid on KDE Plasma, not sure about other distros) to improve performance. Disable esync and turn AA off (or at most set it to x2 with esync disabled) for better performance, and use Feral Interactive's Feral GameMode tool for another very slight improvement in performance (this can also be used to set CPU Governor if you set the gamemode.ini file settings correctly, which you can find on the GitHub page for the project). All of these combined give the game Windows-level performance, which honestly doesn't say much considering this is a terrible port. But you'll get around 57-60fps consistently, and 45fps if there's a lot happening on screen. Cutscenes run fine, too. Played through the entire game and then some exclusively with Proton, and have not played myself on Windows. Performance is still great with 4.11-3.
Played 110 hours under Linux with different Proton versions. With 4.11-7 and Valve's ACO driver, I can comfortably run the game at max apart from anti-aliasing, which I have to leave at 2x. With no AA, I get a consistent 60. With 2x AA, I get a consistent 58fps. I could probably turn blur off to improve performance, but this is more than playable. Oh, and unlike Windows, this game runs at native 1080p out of the box! IIt's a shame that the FAR mod doesn't work, that could help even more with performance and also allow for custom textures.
Works out of the box with great performance; DXVK automatically sets native 1080p
Some things to keep in mind for this game if you want to make the most of it with Proton:
- Like with Windows, the game does not run on Intel iGPUs
- Ran with the default Proton version and newer versions - The newer versions greatly improve performance and I recommend switching to using those (Properties -> Force Steam Play Compatibility Tool -> Proton [latest_version_here]
- NieR:Automata on PC runs at 720p upscaled on Windows and requires a mod to fix this (called Fix Automata Resolution, or FAR). This is not required with Proton, as DXVK was made for NieR:Automata originally and runs the game at true 1080p as a result. Therefore, FAR is not required (it also doesn't work, see below)
- This game runs poorly on PC usually; FAR mod does not work as DXVK does not support the method in which the mod works (also impacts mods such as BetterSADX for Sonic Adventure). The performance, however, seems pretty on par with Windows
- Set CPU Governor to performance (on KDE Plasma, you can use this plasmoid). This will greatly improve performance and all but eliminate stutter. Pro tip: This works in a number of games and is generally a good way to boost your system's speed
- Tested initially with everything at max (including vsync and motion blur) except for AA. With standard Mesa 19.2.X drivers, I can barely run the game with 2x AA
- Tested later on with Valve's ACO driver (based on Mesa 19.3 currently). It gives a MASSIVE performance boost, running the game acceptably at 2x AA and even at 4x AA. You could set a custom DXVK config file to cap the game at 30fps and run the game like that with full AA and it would be playable as well, if you really wanted to. However, running the game with 2x AA and Valve's ACO driver is more than enough to make this game an even better experience
Game is broken with 4.11-10 for me, use 3.7-8
The game crashes when trying to load a save file or exit the settings screen. I got an error in 4.11-10 about a page fault and not being able to write to a memory address in the Proton log, this is not present with previous versions including 3.7-8. I have not tested a custom Proton version such as GloriousEggroll.
I completed the game using a mix of Proton 4.2-9 and upwards up to 4.11-8. I got all the achievements, tested with ACO on/off (it made a huge difference) and tested the game on max settings. Solid 60fps on my hardware even with x8 AA. Shame we can't use the newer DXVK builds though. Steam Controller works perfect too.
Now works out of the box with Proton 5.13-1
Stopped working out of the box with some versions of Proton 4.11 until the latest Proton 5.13-1, where a patch submitted to fix this was implemented into Proton. Some additional notes:
- Tested with a Steam Controller
- Sometimes I needed to press the Alt button if I had used keyboard input (e.g. alt+tab or taking a screenshot) to get rid of keyboard input prompts, or to stop the game from switching between both
- Have not tested FAR mod with this release of Proton, but you should be able to install it as I was able to with Proton-GE
- Note that you don't need FAR for the resolution fix, but you can use texture packs and freecam with it and it should work under Proton
Played through the entire game twice on Linux with no issues
All of my 170+ hours on this game are under Proton. The only issue I had was a regression in Wine a while ago, which has since been fixed in Proton 5.13. You can 100% complete the game, and all of the games little gameplay "quirks" work perfectly fine with Proton as well. Some notes:
- Played mainly with a Steam Controller
- If you switch between keyboard/mouse and controller, the game will get confused and flash between keyboard and controller prompts. To fix this, press the "alt" key on your keyboard a couple of times
- Played the games at max settings including full AA
- At one point I did have FAR installed for this game, but I haven't tried to install it recently so as of right now I can't comment on whether or not it works
- I only had one performance dip, during the Simone boss fight very early into the game. There was a lot happening on screen and the game dropped down to 45fps. This could very well be down to the questionable quality of this port. Outside of this, the game ran consistently at a perfectly smooth and consistent 60fps
Glory to Mankind!
Runs @ 720p30 Low Settings on this laptop, only stutters for 1-2 seconds after cutscenes and unpausing
- Using a Dell Inspiron 5505. Did not run with base laptop configuration: Upgrading to 16GB dual channel RAM allowed the game to run with acceptable performance @ 720p30 with all the lowest settings.
- Locked the game to 30fps using MangoHUD (
mangohud MANGOHUD_CONFIG=fps_limit=30) out of personal preference for a consistent framerate. Will run slightly higher than 30 but fluctuate a lot, so I chose to cap it. - Tested up to reaching the Bunker (~1 hour of gameplay) and only encountered framedrops when leaving cutscenes/main menu.
- Tested with a Steam Controller
Overall, given this is a laptop, this is exceptional performance.
Couldn't get this one to run
No luck with this one for now. It might be a DLL related issue. Game runs in the background but doesn't start, no music either. Notes:
- Tried a few things; disabling esync, various versions of Direct3D, using the Open-GL D3D renderer, even running in a virtual desktop.
- I attempted to add a DLL Override "native,builtin" for the d3dcompiler_47.dll, as this DLL is present in the game's install folder, but had no luck. I also attempted to install the verb via winetricks with the command
WINEPREFIX=/your/path/is/different winetricks d3dcompiler_47.dllbut had no success. - The game has several other DLLs present in its install folder which could possibly need overrides, but I'm not experienced enough on how to properly do this.
- If you don't run in a virtual desktop (set via
winecfg) then the game will keep running. You can kill the processespython3,SteamChildMonitorand a ton ofwineserverprocesses, but if you run in a virtual desktop the game will properly stop when you close the virtual desktop window - Not that the game works in the first place.
Let's hope the game stays on Steam long enough for people to find fixes :)
No tweaks needed, the game runs native perfectly
No need for any of my usual native Linux game tweaks, this one works out of the box with impressively good native Linux support
Did a full playthrough of this game on Linux native a while back, still runs fine
Some native games have given me trouble lately but this one still works like a charm :-)
Through Proton the game worked fine for about 5 hours, then had really bad slowdowns in certain areas (behind Lumbridge castle, around the Grand Exchange, and a couple of other areas). To fix this, I used RuneLite (a popular open-source third party Old School RuneScape client) to play the native release. I launched this through Steam using SteamTinkerLaunch in a slightly unorthodox way:
- Download and install the RuneLite Linux AppImage (Flatpak may also work but at the time of writing it looked slightly out of date).
- Download SteamTinkerLaunch (recommended installation through package manager or Flatpak but only if using Flatpak Steam)
- From Steam, right click on Old School RuneScape, click Properties, and in the "Launch Options" box, enter
steamtinkerlaunch %command%.
- This is slightly unorthodox as usually you'd use SteamTinkerLaunch as a compatability tool, however this way allows us to launch the RuneLite client natively without Proton, as I believe using SteamTInkerLaunch as a compatibility tool would attempt to launch the AppImage with Wine and that would not work
- Launch Old School RuneScape, and when the SteamTinkerLaunch window appears, click the "Main Menu" button (or press space)
- Click on the Game Menu button along the bottom
- Under the "Misc options" heading:
- Check the "Use custom command" checkbox
- Click on the box beside "Custom command" and a file picker will open. From here, select the RuneLite AppImage. This is normally in
~/Applicationsif using AppImageLauncher, otherwise it'll be wherever you downloaded the AppImage. Now the Box should showRuneLite_abunchofnumbersandletters.AppImage - Check the "Only custom command" checkbox
- Click "Save and Play"
- RuneLite should launch and you should be able to play the game. For future launches, you can just wait for SteamTinkerLaunch to time out and launch the game, it should only add a few seconds to launch time.
Game works fantastic with this tweak!
Native didn't require any tweaks from me, just click play and go!
Didn't have any trouble with this game, despite some of its more unique gameplay mechanics they all worked great for me on Linux
Native worked great
Native has worked great for me without tweaks for the last few years, have not tried Proton. Just click play and go!
Anti-cheat prevents the game from running. If not for this, the game would probably work.
Works well with Proton
Pretty standard Unity game so I did not expect many problems :-) Game felt a little stutery but I didn't enable Game Mode so that could be why. It felt a little bit heavy on my system but nothing too bad. Totally playable overall with a solid 60fps
- The game fails to load beyond the ATLUS and P.Studio splashes, but you can fix it using Protontricks with the following command (make sure you run the game at least once):
protontricks 1113000 wmp9 quartz devenum. After this, you'll be ready to go!
Big thanks to the guy on the ProtonDB server who helped me out with this!
- Tested with a Steam Controller
- Tested with a few different graphics settings, and they all worked great
- The game didn't see my second monitor, it thinks I'm running on one monitor. However, this is not an issue at all, it's just something I thought to make note of since most games running under Proton see all my monitors now
- Enabling the online functionality didn't have any issues, but the game says this isn't used until later on. I haven't been able to test at all yet, but I can't see this being an issue in any way
Overall, a great experience so far! I'll report more once I've tested a good chunk of the game.
Delete prefix in steamapps/compatdata, it's the folder 1113000. Then run:
protontricks 1113000 wmp9 quartz devenum
Download "LAV Filters" from here (choose installer) and install:
protontricks 1113000 --gui- "Select the default WINE prefix", click Ok
- Run winecfg and go to Libraries tab
- Select devenum and click Remove
- Apply and Ok
- "Run explorer" and click "Ok"
- Navigate to folder with LAV Filters (Go to top bar and type
Z:\and type the full path using backslashes) - Double click EXE and follow installer with all defaults
- Navigate to folder with LAV Filters (Go to top bar and type
- Run winecfg again
- New override > type "devenum", click add
- Apply and Ok
- Close window
After the most recent patch, LAV Filters is now needed. It's tricky to install as you have to remove the Devenum first (disabling didn't work for me) and then re-add it. This was causing me headaches as I kept getting errors trying to register the DLLs during the install.
- Steam Controller still works great
- No graphical errors of note unlike other reports
- No audio issues unlike other reports Happy gaming!
Proton-6.19-2-GE was used as it runs the protonfixes to enable the game's cutscenes to work. This is why it can take a long time to run, as another user has mentioned.
- Delete pre-existing prefix (folder
1113000) in/steamapps/compatdata/. - On first boot with this version of Proton selected, the game said it was running for a few minutes (while running the protonfixes) and then crashed. On subsequent boots the game launched without issues and cutscenes worked without problems.
Proton-6.20-GE-1 does not work. It will give an error when trying to install LAVFilters. The game works with at newest Proton-6.19-GE-2. Older versions back to a certain point may work also. Once installed and set, the game will work flawlessly. Some notes:
- Tested with a Steam Controller
- Tested with a keyboard/mouse
- Tested with Plasma Wayland and Plasma X11
Game works out of the box with Proton 7.0-2, cutscenes and audio work as standard now
No custom Proton version is needed, no Proton Experimental. Delete your prefix if you're having trouble with cutscenes still. Finally!
Runs out of the box smoothly
All of my playtime with this game is on Linux, and I think I might have had one or two crashes randomly while playing. But for the most part the game ran perfectly.
- Tested with Steam Controller
- DXVK now works fine with later versions of Proton
No issues to report here.
Played for 147 hours with Proton across various Proton versions and hardware, did not have any issues
Completed the entire game with Proton, previously had issues with DXVK but these have since been resolved. I think I experienced one crash but that was likely more of a one-off. Tested with a Steam Controller.
PROTON_USE_WINED3D: For some reason, the game doesn't work when it uses what I'd guess is the standard DXVK. It doesn't even show the "CapCom" splash. To fix this, set Proton to use WINED3D
Your final launch string for the game should now be PROTON_USE_WINED3D=1 %command%
I played for about 35 minutes and completed the first case. I didn't encounter any issues once I properly set my launch options.
- Tested the game windowed and fullscreen with no issues. I'm running on KDE Plasma 5.17.5, your mileage may vary with other desktops/compositors/window managers.
- Had no problems tabbing out
- Tested with Steam Controller and keyboard with no issue. Game recognises my Steam Controller as a standard Xbox One controller
- Controller hotplugging (turning a controller on/off after the game has started) worked almost without issue - This is probably a game bug, but some parts of the game dialogue still show keyboard prompts instead of controller prompts. The UI displays correctly, but sometimes when characters are speaking it'll say to press "Tab" instead of "RB"
- Tested with vsync on and off, didn't impact performance for me
Unlike other reports, I did not experience any slowdowns, animation errors, graphical glitches, or anything that would impact the experience. The first bootup of the game took about 10 seconds after the CapCom splash faded out, but then the game booted up to the main menu. This is probably just how the game works, but I can't verify as I've only played through Proton.
Overall, an essentially native experience with Proton - For me at least!
Works out of the box as of Proton 5.0 - Played up to "Justice for All: Episode 4"
With Proton 4.11, I had to force WINED3D to get the game to run. However now, it all works fine. I experienced two crashes in my 60+ hours of testing as of writing. One was just a simple game crash, and the other crashed my entire system and I had to reboot by pressing the power button on my PC. Whether this was to do with my system as I run a lot of updates, or whether it was an issue with the game or WINE or something else, I'm not sure. Overall though, an extremely pleasant experience under Proton. Some notes about my setup:
- Tested with a Steam Controller
- Tested with a 3rd Party Nintendo Switch Pro Controller
- I have ACO enabled on my system, though it more than likely makes 0 difference with this game
- I tested the game windowed and fullscreen, they both worked
- I have the game on "high" settings, whatever that means for this type of game
Played through the entire game without issue
I played through the entire game, testing both a Steam Controller and a 3rd Party Switch Pro Controller. I had no issues at all. No special launch options needed, just install, hit play and enjoy!
Worked ootb
Fullscreening from windowed mode using Alt+Enter caused the game to look a bit blurry and have some very very tiny black bars (maybe 10 pixels) along the sides. Using the game's Fullscreen and Windowed toggles from the game settings resolved this.
You can rest easy knowing your pickles work on Linux :-)
Requires "-changedir" parameter in the Launch Options (right click -> Properties -> Set Launch Options). I did not need to disable 3D acceleration. The game ran fine for me with only the above parameter.
Adding the "-changedir" launch option (Right click -> Set Launch Options -> "-changedir", no need for "%command%") makes the game fully playable. There are occasional framedrops, and there's a significantly low framerate in the screen where you choose what plants you want to use in the level. However, gameplay itself is a solid 60fps. Played a handful of minigames, completed Adventure Mode and even tried out the Zombinator avatar creator (which exports to "/path/to/library_folder/steamapps/compatdata/3590/pfx/drive_c/users/steamuser/Desktop/"). The ending cutscene works fine too.
Add "-changedir" in the game's launch options and it'll run perfectly. The FPS drop in the plant picking menu seems to happen sometimes and other times it doesn't. Odd, but it doesn't impact gameplay much. Full 60fps on this laptop, which is mega cool considering it's running under Proton!
Fully completed the game on Linux, follow the tinker steps to fix the performance drop on the Plant Selection screen
Replaced the game's exe with the one in stemapps/compatdata/3590/pfx/drive_c/ProgramData/PopCap Games/PlantsVsZombies/, named popcapgame1.exe. You will need to run the game at least once to see this file. Copy this and paste it into the game's folder ("Browse local files" from Steam will bring you there), rename the original PlantsVsZombies.exe file to something else and rename popcapgame1.exe to "PlantsVsZombies.exe`.
- You may be able to use a third party tool to make Steam start the executable in the Wine prefix, but I didn't test this.
Move the executable in steamapps/compatdata/3590/pfx/drive_c/ProgramData/PopCap Games/PlantsVsZombies/ to the game's folder ("Browse local files" option), rename the original executable to something else and rename the new executable to PlantsVsZombies.exe. Fixes the slowdowns during the Plant Selection screen
Game is fully playable without the tinker steps but it will resolve the last remaining issue with this game.
- Tested with a Steam Controller and a keyboard/mouse, works fine
- Tested with KDE Plasma X11 and Wayland, works great on both
- Previously the game needed the launch option
-changedir, but this is no longer required
Added launch option "-changedir" to fix the game and make it run.
At certain times when selecting plants to use for the level, there will be a bit of slowdown and the game will chug around 5fps. This happens most of the time, but sometimes it will not happen.
Add launch option -changedir (no need for %command% to follow it), or else the game won't start
Sometimes slows down to about 3fps during the plant picking screen. It mostly consistent but doesn't happen sometimes. Tried a few tweaks to fix it, including PROTON_NO_ESYNC and PROTON_USE_D9VK. The ACO driver doesn't fix it. Not sure what causes it but it's not that big of a deal, it's only on that one screen, too.
Requires -changedir launch option or else the game will complain that it's not set with an error box and won't start. Once this is set, the game will work perfect
Runs with some slight lag in the menu where you pick plants
Use -changedir launch option in order for the game to launch
On the plant choosing screen, the game slows down most of the time (but not all of the time, strangely) to about 3-5fps. This is the only point in the game where this happens
-changedir- Add this launch flag to the game's launch options in order for it to run. You don't need to add%command%after it
The game slows down most of the time (but not all of the time) on the plant picking screen and when Crazy Dave talks to you. All other parts of the game seem to play fine, including the startup loading screen which used to previously slow the game down to around 20fps
Tested with many different version of Proton and the slowdown problem occurs in all of them (3.7-8, 3.16-9, 4.2-9, 4.11-11, 4.21-GE-2, Proton-tkg 5). Aside from this, though, and having to add the launch option, the game works flawlessly with Proton!
A near-perfect experience!
Plant selection screen causes framerate to drop to about 5fps. However, the actual game (other menus, gameplay, zen garden, survival modes, etc) all run perfectly fine. It does not impact the gameplay experience, it's just slightly annoying.
Works out of the box without needing the old launch option, and if it weren't for the slowdown on the plant selection screen I would say this game runs 100% perfect! So I'll have to settle for 99% perfect ;D
gamemoderun %command%
A perfect native Linux experience, though Proton works too if you are so inclined.
- You can add
-gamepaduito the end of your launch options (it would go after%command%) to use the Steam Deck UI and I believe this also uses DXVK to render the game if MangoHUD is to be believed. - Feral GameMode gives a very slight performance boost
gamemoderun %command%
Works perfectly
- Full game is playable on Linux with keyboard/mouse or controller, tested with a Steam Controller
- Multiplayer works no problem, played the entire campaign and some workshop maps
- Feral GameMode gives a noticeable but still fairly minor performance bump No real tweaking is required for this game, it just works!
Gets about 4-5hrs battery life with about 40% screen brightness and:
- Half rate shading
- 6w TDP
When waking from a 10-12hr sleep there is minor audio crackling, but this is a common issue with almost every game on Steam Deck
Cloud save is very annoying, usually it will fail to sync with the cloud and you have to retry until it fails instantly, then launch the game and the saves will sync. This is true on Steam Deck and a regular PC
Stuttering every 5 seconds or so during cleaning, disabling Auto-Save fixes this
There are a few minor issues like stuttering which can be fixed by disabling auto-save in the Genreal settings, the audio crackling which affects almost every game on Steam Deck when in sleep mode for several hours, and the cloud save annoyance which is probably a game bug. But to say those are minor would be an understatement, this game is flawless and I've played almost exclusively for about 45 hours on Steam Deck
Didn't play much but what I did play worked perfectly
Native Linux port worked perfect for me, no tweaks required.
Game music was present by default, but all other sounds (voice acting, sound effects, etc) were not present. To fix this, I used Protontricks (a winetricks wrapper for Proton prefixes) to open winecfg and set the xaudio2_7 override. Open winecfg and go to the "Libraries" tab, and from the top dropdown select xaudio2_7 specifically. Add it, and it will automatically be set to "native,builtin". Now the game will work perfectly under Proton!
- Tested with a Steam Controller
- Tested with vsync on, unlike most games where I turn it off. It had no issues in this game
- Tested Remote Play Together with no issues
You'll need to run winecfg on the Proton prefix for the game:
- Without Protontricks, you can do
WINEPREFIX="/path/to/libraryfolder/compatdata/971620/pfx" winecfg - With Protontricks installed,
protontricks 971620 winecfg
Once you have winecfg open, go to the Libraries tab, and in the override dropdown you can either type or search for xaudio2_7. Select this and apply your changes. It should be set (by default) to "native,builtin". This is what you want.
This workaround fixes the game's sound effects.
- Did not test any multiplayer
- Played with a Steam Controller
Did not need any tweaks, ran out of the box
- Did not test online
- Played with a Steam Controller
Endless Tetris on Linux!
Tested local multiplayer with Remote Play Together and it worked great
The game works great, including Local Multiplayer. Played with a friend using Remote Play Together. The game runs with no tweaks and if you want to invite a friend or four along for a game of Puyo Puyo and/or Tetris, you can fulfil your dream on your Linux box!
Unplayable due to black textures for walls and floors. Runs at a relatively stable 60fps, has some framedrops when switching between dimensions initially (dropped to about 53fps from 60fps for me), but this issue could be present on Windows. Subsequent dimension switches were fine. Steam Controller works. If the texture issues ever get fixed, this game would be perfectly playable.
Had to install vcrun2008 to fix the black textures problem. I recommend using Protontricks to do this, or following the method others have mentioned. Other than that, everything worked great. A full 60fps except on loading screens where it dipped to 12fps. Perfectly playable.
- I used a tool called protontricks which is a wrapper for running wintricks on Proton prefixes. You could also use standard winetricks by setting your WINE prefix and running winetricks on it.
- If using protontricks, select Quantum Conundrum from the dropdown if using
protontricks --gui, otherwise open winetricks for the game using it's AppID - Use winetricks to install
vcrun2008by going to "Install a Windows DLL or Component" and scrolling down until you find the appropriate winetrick.
Doing this will fix the issue with missing textures for the game.
- Tested with Steam Controller
- Tested with Valve ACO driver
- Tested with CPU governor set to "Performance", you can do this by using Feral GameMode
Native game and works great
Game opened on the correct monitor with the correct resolution, framerate locked to 60fps as well. Very nice native port! No complaints :-)
"Resident Evil" requires the WMP11 winetrick verb to work.
- Make sure you start up the game at least once, it'll load to a black screen after the "Capcom" splash. You need to run at least once to generate the Wine prefix for the game
- Make sure you have Protontricks installed, as it makes installing winetricks verbs much easier
- Run the command
protontricks 304240 -q wmp11- This command is a wrapper for winetricks, used to configure a wine prefix and, more often than not, install "tricks" or "verbs" to get applications to run/run better.
304240is the AppID for Resident Evil, it tells Protontricks where to find the game's prefix-q wmp11installs the WMP11 verb quietly, meaning you won't see any dialogue boxes or have to click through any install wizards, you can leave the command to run in the background and once it's done you can launch the game and play like normal
- Proton-5.21-GE-1 was used, did not test native Proton but I imagine Proton-GE improves DX12 compatibility
Only played about 90 minutes of the game until after meeting Carlos. There was minor stutter at first but it went away.
- Tested with a Steam Controller
- Tested with all settings at max
- Tested with DX12 backend and DX11 backend, both worked fine
- Mods installed with the Fluffy mod manager work just fine
Proton-6.19-GE-2 (GloriousEggroll) was used as cutscenes did not play with Proton 6.3-6 at the time. Did not try Proton 6.3-7 or Proton Experimental.
After using Proton-6.19-GE-2 I have yet to encounter any major problems. The only slowdown I have encountered is at the very beginning, when Ethan is about to get out of the car. I have only played 3 hours of the game but haven't had any slowdowns since then. Some additional notes:
- Primarily played with a keyboard/mouse
- Tested with a Steam Controller, no issues
- Tested with an official Nintendo Switch Pro Controller, no issues
- Tested with all settings at max, had no issues
- Resolution scale can be increased up to 1.5 while keeping a solid 60fps on my hardware. I increased this to test but didn't really need to have it on at all
- Tested streaming the game to my laptop and this worked fine
- I streamed the game to my laptop connected to a TV in another room and didn't have any problems. I was able to connect my Steam Controller and Nintendo Switch Pro Controller (on separate occasions) without problems and the game recognised them.
- Also streamed to my phone using the Steam Link app and didn't have any issues there either
- These tests were brief but there were no crashing issues
- Had issues trying to run upscaled at 4k using AMD FSR, but this is not a massive problem. The game didn't look like it was being upscaled, so perhaps there were some configuration issues I needed to iron out to ensure the game wasn't actually running at 4k. Keep it in mind if you plan to run the game with FSR though
This game is native though the store page doesn't list it as being native and as such neither does ProtonDB. However the game downloads a native Linux release and runs it, verified by checking the game files and running processes. Bit of an odd thing but the game works great native!
- Did not try Proton
Won't run in fullscreen but this seems to be a general issue with the game and not with Proton - The game just closes out of fullscreen and goes back to it's small window
Didn't experience any issues, worked out of the box
Worked with DXVK on my laptop's iGPU and did not require any special launch options, unlike other PopCap games. It only seems to be their newer games which require that
Doesn't work at all with Proton - Loads to black screen
Native version doesn't work when games are fullscreened so I decided to try Proton. However, after trying a multitude of options including disabling esync, using D9VK, and using WINE's OpenGL-based Direct3D renderer, the game seems to be borked under Proton completely. It loads to a blank screen.
TL;DR - Game runs perfect (haven't tried any DLCs but they should work too). Read on for details: The game itself runs perfectly fine - Full 60fps, though I only tried mini-reflexology and the posing mode. Steam Controller worked and button prompts even displayed correctly. However, the game doesn't have any settings menu. There is no way to set the game to fullscreen, and by default the game (for me, anyway) renders at 1920x1080 with a bordered, non-fullscreen window. To get around this, I used some Plasma KWin window features to disable the window border and set the game to fullscreen: Alt+F3, or right clock on the window titlebar -> More Actions -> Special Application Settings -> [Fullscreen: Size & Position tab, enable "Fullscreen" and set to "Force" from the dropdown and select the "Yes" radio button to the right of this dropdown] -> [No titlebar and frame: Appearance & Fixes tab, enable "No titlebar and frame" and set to "Force" from the dropdown, and select the "Yes" radio button to the right of this dropdown] - I only know how to do this with KDE Plasma 5/KWin, your mileage may vary with other desktop environments - Mainly look into disabling window borders and forcing an application to go fullscreen. Also note that the fullscreen won't be perfect, I have a very small bar at the bottom there the game isn't perfectly fullscreen that shows any windows underneath. It's no big deal and can probably be fixed by changing the "Size" parameter in KWin settings. But this is really minor, the game itself runs flawlessly and this just seems to be an issue with the port!
Game runs perfectly. It does actually have a settings menu, and you can set fullscreen. It's set to windowed by default. This works, and the rest of the game runs perfect from my tests.
Great compatibility, works out of the box. Just remember to set the game to run in fullscreen as it will open in a window that is the size of your display (minus the size of any panels, so in my case it rendered at 1920x1050), however this is an issue with the game in general and not with Proton. It'll remember that you set it to fullscreen with subsequent boots, too, so it's really a non-issue but something I wanted to make reference to.
Flawless out of the box experience, outside of the game's default graphical options which can be modified in-game.
Runs flawlessly
Game may start in a 1920x1080 Window with a border. Simply use the game's settings menu to set the game to fullscreen.
No issues
You may need to set fullscreen manually in the setting when you first load up the game, but that's more of an issue with the PC port than with Proton. Tested with a Steam Controller and had no issues
Works like native without any tweaks
Seems to be a game bug, but activating the Steam Overlay and modifying a controller configuration softlocks the game and requires a restart
Didn't have any issues when playing. Tested on KDE Plasma Wayland with a Steam Controller
PROTON_NO_ESYNC=1: This fixes a strange audio stutter glitch, similar to those you'd find in the likes of Sonic Generations or LEGO Star Wars without this parameter. When you set it, the game's audio will work normally
Replace $LIB with the path to your Steam library folder where is saved. For example /home/gaben/.steam/steam/steamapps
winetricks
- msxml3: Microsoft XML Parser
- vcrun2010: A set of runtime libraries the game requires
- d3dx9: DirectX DLL that some games need
To install, run WINEPREFIX="$LIB/compatdata/202530/pfx" winetricks msxml3 vcrun2010 d3dx9
Not Listed
- JRE 1.6.0: Unsupported version of Java, so you need an Oracle account for an official download. You could find a mirror, or try
wget. On Oracle's downloads page, look forjre-6u45-windows-i586.exe. To install this into your Proton prefix, run this in the same folder as the installer:WINEPREFIX="$LIB/compatdata/202530/pfx" wine jre-6u45-windows-i586.exe
You may need to restart for everything to work properly
If you put in the effort, this game will work nearly perfectly. A few extra notes:
- Launcher works, even launching the game from the launcher still works
- Game actually detected my second monitor and could be launched directly to it, unlike other games I've tried via Proton. Very minor thing overall though
- Tested with a Steam Controller. Remember to set your input type to "Gamepad" from the launcher, otherwise it won't work. Also ensure that the game is not set to use a keyboard binding for your controller, as it defaulted to this for me and it caused quite a headache
- If you don't close the game from the menu, it will run in the background even if the window closes. The process (
Sonic_vis.exe) can be killed manually however
- Proton-5.21-GE-1 GloriousEggroll allows the game to work out of the box with no tweaks needed - Fixes Media Foundation issues and removes the seccomp argument.
- I used
DXVK_ASYNC=1to give a small speedup and reduce some stutter with the game, though it's really not that much of a difference and you could leave it out if you want
During loading screens the framerate drops to around 30fps briefly. I'm running the game on an m.2 SSD so this shouldn't happen, but it's only during the loading screen and it could even be a problem in the main game
- Tested with a Steam Controller
- Ran the game with everything at max settings
- Only tested the 2B DLC
- Played with some
.pakfile mods, had no issues
Crackled occasionally with my headphones but almost every game on my Steam Deck does this. Does not happen with other headphones, bluetooth speakers/headphones, or TV audio output
Steam Controller only when connected to the TV would sometimes "Drop Out". Did not happen when connected to the Steam Controller undocked, and this only affected my Steam Controller. Switch Pro Controllers were unaffected.
The game works flawlessly out of the box. However it is recommended to use a patch for the game which has various improvements. This is called the Committee of Zero patch, and you can install it by manually running the installer with the Wine executable that comes with Proton. SteamTinkerLaunch should also work using One-Time run.
Did not play much of the game but what I did play worked great with Proton 7.0-3
Tested with a Steam Controller on KDE Plasma Wayland
Works at max settings out of the box
On first boot, my space and escape keys didn't work properly. After restarting the game, everything was fine.
Didn't try the experimental multiplayer, but I was able to play the game and even make an account for the upcoming multiplayer. Will report back if I find any other oddities or when the game gets more features!
Native works flawlessly
I was able to 100% complete the game on Linux native without problems
Native works great
Could not test the 18+ patch as I could not find it online (a common problem for older Sakura series games), but the native game ran out of the box for me.
Intel Integrated Graphics seem to have Vulkan drivers that don't play nice with Proton/DXVK, as the game crashes with DXVK. However, the game runs perfectly fine when disabling Wine D3D: PROTON_USE_WINED3D=1 %command%. The Steam FPS counter doesn't go above 30fps for me so I suspect that it's framelocked. Either way, it's a perfectly playable experience after forcing Proton to use WINE's OpenGL based Direct3D renderer.
Runs out of the box
- Game is capped to 30fps, for those wondering
- Game works fine with DXVK on my PC with an AMD GPU, not on my laptop with an Intel iGPU
Requires "PROTON_USE_WINED3D11=1 %command%" to be set in the game's launch options. Defaulted to medium settings for me, ran at 70fps. At all max settings it runs at about 55-60fps. About the same level of performance as Windows 10
Solid 60fps out of the box with all settings at max. Generating a new world took quite a long time (~2 minutes) and my CPU was maxed out for the duration. Performance is identical to Windows otherwise. I should note that I had my CPU governor set to Performance, and I'm using Valve's Mesa ACO driver.
Works at 60fps+ on max settings out of the box
The game runs at about 70fps for me on max settings, however to save GPU strain I created a dxvk.conf file. Put it in the folder with the game's EXE, which is Scrap Mechanic/Release. In the file, add dxgi.syncInterval = 1 to lock the game to 60fps - It may be tied to your monitor's refresh rate, I'm not 100% sure, but it locks the game at 60fps for me and that's all I needed it to do. For more information about what you can put in a dxvk.conf file, see here for a sample file.
Did not have any issues with performance and I ran the game at max settings. The latest release of Proton fixes the game. No frame drops, no lag, everything worked great for me. I haven't tried any multiplayer.
PROTON_USE_D9VK=1: Game runs better with D9VK as opposed to DXVK. For some reason, even with Proton 4.11-11, you still need to set this flag. If you're using a custom version of Proton, such as Proton-4.21-GE-2, then you may not need to set this (and in fact, it may use WINED3D, so if you are using a custom Proton flavour I'd recommend removing this option)
- I'm using the ACO shader compiler as I have it forced on in my
/etc/environment, but I'm not sure it makes a huge difference in a game like this - My Steam Controller was detected and the official configuration for this game was set out of the box. Although I opted to play with a keyboard and mouse, it's worth mentioning that it was still detected
- Played with max settings, AA was set to 8x as opposed to the default 4x
Your final launch option string should look like: PROTON_USE_D9VK=1 %command%
Launcher doesn't work. It might work if you install some dotnet library with winetricks/protontricks. I used this C program (https://github.com/ValveSoftware/Proton/issues/1981#issuecomment-450759700) to set the game to launch. You can compile it by going to the directory where the game is installed and running "winegcc whatever_you_called_the_file.c -o SteamLauncher.exe" and launching the game through Steam, which launches Shenmue I by default. Add anything to the launch options to launch Shenmue II. Run winecfg (either through winetricks/protontricks/directly by setting your WINEPREFIX or however you wish) and go to the Libraries tab. Add an override for "xaudio2_7", and make sure it's set to "native,builtin". If not, you can edit it and set it as such. This ensures that audio such as background music and voice lines play properly. After this, the game works perfectly. It's capped at 30fps, so this isn't a Proton issue.
Previously this game needed a lot of tinkering to get working but now it works out of the box with the latest GEProton release
This game is clearly why Valve developed Proton. Can't tab out of the game but otherwise works perfect.
All issues have been fixed, game works perfectly
Tabbing out now works, fancy puddles work, different screen sizes work, the game is a lot more stable than when I first tried it 8 months ago. You can shower with your dad on Linux now without any issues.
Native didn't recognise my Steam Controller, but running under Proton it did
Run under Proton if you're experiencing controller issues
The game itself runs perfectly with very few frame drops. I have yet to experience a crash. Note that the configuration tool does NOT work. However if you install WINE and run the configuration tool via your own WINE prefix you can configure files, or you can edit them manually.
The Launcher doesn't work for me even with Proton 4.2-3, but the base game does. This, however, does mean that the configuration in steamapps/compatdata/212480/pfx/drive_c/users/steamuser/My Documents/SART/My Documents" is not generated. The game runs perfectly fine but with very low graphical fidelity. If you install dotnet40 with protontricks then the launcher runs. Highly recommend disabling vsync, which is a given for games in general (even outside of Linux). With everything else at max, the game runs perfect.
Flawless! With Proton 4.11-8, configuration tool now works out of the box too!
Previously you would have needed to install at minimum dotnet40 yourself using winetricks/protontricks, however now this works out of the box! You will get a warning saying something about an unhandled crash exception when you open and exit the configuration tool, however if you just click "Continue" the launcher will work open and properly, and all your settings will be saved. Remember to select "Quit" when closing the launcher, or it will continue to run in the background and you'll need to terminate the process manually!
Launcher works with later versions of Proton that include updated dotnet40
- The launcher now works, you might get an error about an unhandled crash exception, but if you click "continue" then you can proceed to configure the game and increase the graphics settings. When you quit the launcher, you'll get this error again. Select "Quit" and the launcher will close. You can launch the game proper now
- Tested with Valve ACO using
RADV_PERFTEST=acoas a launch option, it slightly improved performance but not that much (only works for Mesa 19.3 and up on supported AMD GPUs) - Tested with a Steam Controller, no issues to report
You need to rename the Launcher EXE and the sonic2app.exe files, so that Steam thinks that the sonic2app.exe (the actual game) is the launcher and will launch that, as the launcher does not work. Also note, the game works with a controller, but it emulates the keyboard and mouse. It shows keyboard prompts, and does not have typical controller input. You cannot walk more slowly by only gently nudging the left stick for example; it acts as a button press.
The Launcher and Game EXE need swapped around, so rename Launcher.exe to anything, and sonic2app.exe to Launcher.exe. This makes Steam think you're launching the game. Also, for controller input to work, you need to copy some configuration files into the game folder as others have mentioned. Outside of this, the game runs flawlessly with no crashes or slowdowns.
Performance is perfect, basically native. But getting the game to run requires some effort. Rename "Launcher.exe" to anything else, and rename "sonic2app.exe" to "Launcher.exe". This is because, like other games such as Borderlands GOTY Enhanced, the launcher doesn't work with Proton (probably a .NET incompatibility or something). As a result of the launcher not running, you'll need to import configurations to get controls working. Other people have linked to this. Once you've followed these steps, the game will work perfectly.
Must rename "Launcher.exe" to anything else, and "sonic2app.exe" to "Launcher.exe," as due to issues present in standard WINE as well as Proton, the game's launcher doesn't work. You also have to manually import game config files which are meant to be generated by the launcher, but of course are not because "Launcher.exe" does not run. After this, the game will work like native! Played about 20 hours with Proton, tested out cutscenes, all levels, Chao Garden, Sound Test (clearly the best part of the game) and encountered no issues. Played with the Steam Controller.
Game and launcher work fine out of the box with Proton 7.0-2
Played the game entirely vanilla and didn't have any problems with this game whatsoever. The launcher worked perfectly and I was able to select my controller. In the past I had trouble with this, and if the game won't let you select a Gamepad option for controls, right click the game > Manage > Browse local files and delete the two files in the game's "Config" folder, then relaunch the game.
- Played with a Steam Controller and an Official Nintendo Switch Pro Controller
- Played without mods, though likely SteamTinkerLaunch could be used to make using mods easier by setting the Mod Manager to launch as the game's executable (meaning you may not need Bottles for it separately)
- Game has a bug (not Linux specific) where on high refresh rate monitors it may run too fast. Using your preferred framerate limiter can fix this, for example:
- MangoHUD:
mangohud MANGOHUD_CONFIG="fps_limit=60;no_display" %command% - DXVK:
DXVK_FRAME_RATE=60 %command% - Gamescope:
gamescope -r 60 -o 60 -- %command%
- MangoHUD:
BetterSADX will not work for reasons similar to why FAR for NieR:Automata and the Performance/HDR fixes for Monster Hunter World do not work: DDL injection through unimplemented parts of the DXGI API for DXVK.
Game and launcher work out of the box
Have not tried D9VK to see if it makes a performance impact
Works great on my laptop
At 1080p with FXAA the game starts to run at about 30fps, bringing it down to 720p fixes performance. Keep in mind that I'm running on a laptop with a low end iGPU, on a desktop the game will run fine at max settings.
Works with DXVK and also D9VK, but BetterSADX does not work
Vanilla game works perfect, tested with a Steam Controller too. However, BetterSADX does not work so far. Further testing needed though.
Vanilla game works perfectly, the below is information for those using BetterSADX and Sonic Adventure DX Mod Installer
Proton-5.8-GE-2-MF GloriousEggroll
This is only for "BetterSADX" or "Sonic Adventure DX Mod Installer", as the vanilla game works out of the box with Proton.
winetricks- Installed thedotnet40verb withWINEPREFIX=/path/to/protonprefix winetricks dotnet40. Fixes UI problems in MainMemory's SADX Mod Manager that needs .NET 4.0- Custom Proton Fork - Used Proton-5.8-GE-2-MF which has fixes for Media Foundation playback & allows intro videos for the modded versions of Sonic Adventure DX based on the 2004 US PC release to play videos without the Quartz winetrick
- Not Listed - The Lantern Engine used for both BetterSADX & Sonic Adventure DX Mod Installer requires a DLL override. Set this in "Libraries" in
winecfgford3d8as "native,builtin". This should be the default. Omitting will likely cause crashes
When using PROTON_USE_WINED3D=1 I had around 45fps the initial Chaos 0 bossfight with Sonic. However the next set of levels I tested and Station Square didn't have any performance issues. Omitting this flag fixes the issue, and the flag is only required for the Mod Manager with BetterSADX or Sonic Adventure DX Mod Installer.
As mentioned, the vanilla game works out of the box. Below are notes for those using mod packs that significantly improve the experience:
- You'll likely get .NET warnings consistently saying something along the lines of "Could not find a version of the runtime for this application". It's fine to ignore this and just press OK. It hasn't had any impact on the game so far and could probably be fixed by installing a newer .NET version. This can be risky though, so I haven't opted to try it
- The Sonic Adventure DX Mod Installer installation process can be a little touch-and-go. In WINE 5.8 I had no issues aside from missing images. In the currently latest WINE 5.9, some images display properly but checking for updates fails with a page fault - this is a WINE bug. Select the option to not check for updates and the modpack will install correctly
- I haven't had any issues installing BetterSADX for those of you using that, just remember to use
dotnet40and use either thequartzwinetricks verb or use one of the latest builds of Proton-GE, and use the DLL override ford3d8so that the Lantern Engine (used by both packs) will work - The Mod Manager fails to check for updates, saying the connection to the repositories for the mods gets closed. I haven't found a workaround for this yet and seems to mainly be an issue with Sonic Adventure DX Mod Installer. You may not have this issue with BetterSADX
Full 1080p60 even with FXAA enabled
Same as Windows, the text for hints in Mission Mode (when you view them in the menu that lists all the missions) is borked. It's scaled completely wrong. Not sure how to fix it, but worth mentioning.
- Tested with a Steam Controller
- Completed the main game with Proton, didn't encounter any issues or crashes
- Game benefits massively from dual-channel RAM, goes from mostly stable 60fps to consistently stable 60fps
Install dotnet20 to get the game's launcher to work, you can do this by setting your WINE prefix to the location of the game's Proton prefix which is in a compatdata folder inside the library folder where the game is installed; i.e. for the default library folder the command would be something like WINEPREFIX=$HOME/.local/Steam/steamapps/compatdata/213610/pfx winetricks -q dotnet20. The -q option means everything should just install automatically without needing to go through any installer. After this, the game should run!
Connect controller before starting up the game and/or the launcher if you used the dotnet20 winetricks command. Otherwise the game won't see it, and if you connect while the game is running it'll ask you to restart the game just like on Windows.
- Tested with Steam Controller and MadCatz Turbo controller for local multiplayer
- ACO driver makes no difference for this game
- CPU governor makes no difference for this game
- Local multiplayer works fine
- Launcher can be fixed by installing
dotnet20meaning you don't need to copy game controller configuration files or rename the game files - If you don't have winetricks installed or don't want to run any tweaks, open the game files where the EXE's are stored and rename
Launcher.exeto anything else, andsonic2app.exetoLauncher.exe. This tricks Steam into launching the game instead of the launcher, as it's hardcoded to look for the launcher file. As the launcher never runs, the game doesn't have a chance to setup controller profiles. To do this, use the instructions found on this GitHub issue for Proton
Launcher is broken out of the box and requires dotnet20. This is needed so that the game can generate some configuration files it needs. You could download/generate these yourself and put them in the Config folder within the SA2 install folder. Otherwise, install dotnet20 using winetricks.
- Identify what library folder you've installed SA2 on. By default, this is
$HOME/.local/Steam. Then, you need to find the Proton prefix. This is your library folder path +steamapps/compatdata/213610/pfxfor SA2 specifically UseWINEPREFIX="/path/to/sa2/prefix" winetricks dotnet20"to installdotnet20and fix the launcher. Follow any prompts. You can try usingWINEPREFIX="/path/to/sa2/prefix" winetricks -q dotnet20to install quietly without the prompts.
- My laptop worked perfectly fine with very infrequent framedrops down to 55fps. This is the best experience I've had with a 3D game on my integrated graphics laptop running with DXVK, I was shocked. This is a very pleasant experience on my hardware and is more than playable
- Tested with Steam Controller on my laptop and with the Steam Link app on my phone
- Game works fine streaming to my phone from my laptop using the Steam Link app and my Steam Controller
- Note for Remote Play Together: Connecting with Remote Play Together whenever both people want to use a controller changes that player's control scheme from keyboard to controller, as the control scheme for each player is set in the launcher. Connecting via Remote Play Together while the game is still in the launcher doesn't work as the controller is "connected" after the game is started. Both controllers technically need to be plugged in before the launcher even starts. This is a limitation with Sonic Adventure 2 and not Proton, but something I want to make a big note of. Trying to set a controller configuration in the files and bypassing the launcher didn't work. I haven't found a workaround.
Wine D3D fixes some strange stuttering when on loading screens. Not needed but I prefer running the game this way, and haven't noticed any performance degradation
- Use Protontricks to install the
dotnet20winetrick, as this is needed for the game's launcher. You can do this withprotontricks 213610 -q dotnet20, with the-qflag meaning you won't have to follow the install prompt- Optionally, use Protontricks to install
dotnet40to enable support for MainMemory's SA2 Mod Loader. You can do this withprotontricks 213610 -q dotnet40. The launcher will complain when you first run and try to install it that it can't find a complete path, it's fine to ignore this and click "Continue". The launcher won't update itself and likely won't update mods automatically, but you can install and use mods just fine like you would on Windows. I tested the Cutscene Overhaul mod and No Model Tinting mod without issue
- Optionally, use Protontricks to install
- Game had some extremely minor graphical degradation in City Escape and only in City Escape when using Proton 5.0-7 and DXVK. Using Wine D3D fixed these.
- The Local Multiplayer issues mentioned are because for Remote Play Together I can't seem to get the controller for Player 2 to work. If you're playing on the same machine though, you're fine
- If you can't or don't want to install
dotnet20, you can swap the names ofLauncher.exeandsonic2app.exein the game's files to skip the Launcher. You'll need to find preset configurations for keyboard/controller files though and put these in the games files. I highly recommend installingdotnet20as it's the simplest way, and you can rename the Launcher later to skip it - Mods seem to work fine. I've only tested a handful but the Mod Manager works provided you have
dotnet40. You can launch it from Terminal while inside the SA2 game files folder withWINEPREFIX=/path/to/protonprefix wine SA2ModManager.exe
No controller support. Runs at about 30-50fps at max settings, with stuttering while loading parts of the level. Can be played, keyboard controls aren't that bad for the game, but definitely not preferable.
Turn vsync off and set framerate to unlimited for best performance. Runs fine with frame dips every so often. Not a bad experience, most certainly playable. Played with a Steam Controller.
Can help with stutter when loading character interaction dialogue, however it is not required and the game will run okay without this
Using Valve's ACO driver helps a lot with game performance and reducing stuttering, and esync is the final tweak to make this game work basically like native
PROTON_NO_ESYNC=1: Disabling esync helps fix some stutter when loading character dialogue
RADV_PERFEST=aco: With Valve's custom Mesa fork (based on Mesa 20.0.0-devel) or Mesa 19.3 and up, a new shader compiler backend called ACO is available for AMD GPUs. This gives a significant performance boost for the game. Add it to your launch options for the game
Final thoughts:
- Tested with a Steam Controller
- Uncapped, the FPS was at around 280fps for me pretty consistently
- Tested Modern Sonic, Classic Sonic, Custom Avatar and Shadow levels (from Episode Shadow) and didn't encounter any issues
- When I first tested this game a long time ago, I ran it on my NTFS drive and had massive performance issues. As is recommended with all Proton games, run it on an ext4 drive. I can personally say that for Sonic Forces it made a HUGE difference
Your final launch option string for the game should look like, PROTON_NO_ESYNC=1 RADV_PERFTEST=aco %command%
- Esync fixes out of sync/crackling audio
- D9VK vastly improves performance, allowing the game to run at a consistent 60fps at max settings (any dips present also occur on Windows too)
So far, everything seems to work once the launch options are applied; cutscenes, every Classic/Modern level up to Seaside Hill, the extras room, side missions, I have yet to experience any issues. A few notes:
- Configuration tool works, if you experience any errors after opening the configuration tool, go to Steam and select Sonic Generations settings icon -> Manage -> Browse Local Files, and delete "GraphicsConfig.ini", then open the launcher and set everything again
- Tested using Valve's ACO driver, which does have a slight benefit in reducing stutter
- Tested with a Steam Controller
- CPU Governor was set to "Performance", to do this use Feral Gamemode or this plasmoid for KDE
The performance for this game has improved dramatically over the months, very pleased!
Audio in game is borked with esync enabled. Use the following launch option to fix the audio: PROTON_NO_ESYNC=1 %command%. Other, older reports mention D9VK, however the official documention on the GitHub README for Proton list this as being obsolete since it's been merged into the wider DXVK. In my tests there's no degration without this launch option in Proton 5.0+ compared to Proton <= 4.11 with D9VK. In fact, I'd say the game runs better on the whole.
At first load of the main hub world, there was a slight drop to 40fps for about 10 seconds. After this, I didn't experience a single framedrop.
Note: You may need to disable fsync if you have installed the kernel patch. If you have no idea what that means, you most likely don't have fsync and don't need to worry!
- Tested with a Steam Controller
- Tested Green Hill, Chemical Plant, and City Escape. Worked great!
Tried disabling esync (PROTON_NO_ESYNC=1 %command%) and had no success. Tried Proton 3.16-8 and 4.2.2, no difference at all. This means the sound is stuttery and gets in the way. But if you can live with that, the game performs pretty well both with vsync on and off. Though I'd recommend turning it off, as the game has some strange frame dips. This doesn't seem to be affected by levels (tested a couple and always dipped to about 50fps at some point), just seems to happen. The launcher for the game also works, except the fonts look very strange and broken almost. Still readable but just ugly. Overall, it's playable.
Disabling esync and using D9VK ("PROTON_NO_ESYNC=1 PROTON_USE_D9VK=1 %command%") allows the game to run pretty much like it would on Windows, aside from some severe stutter on the animation on the INITIAL loading screen - That is, the first time the game loads the main hub. For about 10 seconds while here, the game will stutter a little and hover around the 45-55fps mark. After that though, it'll run at a near consistent 60fps. I played with everything at max and vsync off, and got WAY better performance than I did with Proton 4.2-9 a while back; D9VK makes all the difference in the world. Played through Green Hill, City Escape and Crisis City. All of these stages special events (i.e. the G.U.N. Truck chase sequence) worked with basically no noticeable frame drops, though I did see a few drops to 53-55fps at times (just before the truck crashes, for instance). However without the FPS counter, I'd have thought it just ran like native. Excellent experience!
Game is playable at any resolution below 1080p. Setting it to 1920x1080 causes the game to drop from a solid 60fps to 40fps, and the game logic must run even slower because it's basically unplayable. D9VK causes the game to load to a black screen. Controller works, menus work, map works, achievements work. Tried disabling esync and it made no difference.
- Disable Esync to reduce stuttering
- Use D9VK to vastly improve performance
Your final launch option string for the game should look like: PROTON_NO_ESYNC=1 PROTON_USE_D9VK=1 %command%
Set CPU governor to "Performance", using something like Feral GameMode. For me, the game stayed around 50fps before I set this, then it was at a consistent 60fps.
- Tested with Valve ACO driver
- Tested with Steam Controller
Runs exceptionally well, even the leaderboards. Using Sonic Mania and the Sonic Mania Plus DLC. Steam Controller is fully supported.
When using the latest Sonic Mania "community_beta" channel (as of March 8th 2019) the game runs flawlessly. Denuvo DRM was removed in this update. Previously, the game only worked on one of my drives. Then, it worked, but the shaders for the game didn't work. Then, the game gave me Denuvo DRM issues. Then it just went back to not working. However, as of today, the game runs perfectly on all 4 of my drives, shaders and all. Steam Controller works perfect. It runs as though the game were native.
Denuvo DRM is gone! No tweaks required. No graphical glitches. Fullscreen, windowed, borderless, all work fine. Shaders such as the "CRT-Sharp" now work properly. Hope Valve set this as a whitelisted Proton title soon!
Testing here on my laptop, game ran out of the box (now that Denuvo is gone, which also brought the game down to a little over 200mb!). Full 60, no slowdowns, 1080p fullscreen, vsync makes basically no difference. Didn't test with a controller but my Steam Controller works on my PC so there's no reason it wouldn't work here on my laptop too. Runs buttery smooth without any tweaks!
Tested a bunch of levels with Sonic, Tails and Sonic & Tails, tested my Steam Controller, the game worked very well. Full 60fps, used the CRT-Sharp filter and even with vsync on there was no performance hit (though like with every game I play, I turn vsync off even on Windows). My laptop hit about 80 degrees and I played with my processor PState set to performance, though it didn't add much in the way of performance. Great experience though, just like native!
Everything works out of the box now, haven't had any fullscreen issues. The removal of Denuvo fixed any intermittent launch issues I had, and a game patch a number of months ago fixed the screen filters! I can now play with my CRT-Sharp filter on Linux. Awesome and flawless out of the box experience!
Tested on a fresh (~2hr old) installation of Arch. Game runs perfect, no framedrops even on my hardware with vsync and triple buffering enabled (not that it's needed since Plasma has it's own vsync and I don't let applications block compositing). However, the game crashes for me if I tab out too often - It seems random. Sometimes I can tab out about 5 times and it's fine, other times if I tab out twice it'll crash. This does NOT happen on my PC (i5-6500 / RX480 / Proton 4.11-2) as the game runs perfectly fine there. I imagine it's something to do with the Intel Mesa drivers. Steam Controller works. Framerate only occasionally dropped to 59fps during gameplay and about 44 for half a second on menus - This is normal behaviour for any game, and nothing to be concerned about.
Full game works, including fullscreen, tabbing out works fine, screen filters, triple buffering/vsync, and the Encore DLC works too!
Runs out of the box, even on low-end hardware. Shaders work too, and there are no longer any DRM issues now that Denuvo has been removed
Works out of the box
Did not experience any issues with shaders, graphics or triple-buffering. Alt+Tab worked fine too. Tested with Steam Controller. I had and have had an out of the box experience ever since the removal of Denuvo DRM a lot of months back, which coincided with the patch that fixed shaders being set incorrectly (and coincidentally fixed the shader issues on Linux)
Flawless with everything at max, did not dip below 60fps once
Works fantastic even on my iGPU
Base game and DLC work perfect
- Local multiplayer works
- Local multiplayer through Remote Play Together works
- Works perfect through Remote Play, streaming to my phone and my laptop (also works great running on my laptop, see previous reports)
- Tested with Steam Controller & Keyboard/Mouse, both work great
- Tested with and without the Valve ACO driver, no difference was really made and the game still works fine with Valve's driver
Native-like experience
It just works. Tested with DLC and with just base game, no issues. Also tested with a Steam Controller
Works out of the box with all versions of Proton that I've tried, including 5.0-8
- Tested primarily with a Steam Controller
- Since the removal of Denuvo quite a while ago this game has had absolutely no issues running
Tested specifically with 5.0-9, works out of the box
Had no issues running this game with any version of Proton since the removal of Denuvo quite a while ago, and still with 5.0-9 the game works perfectly. Tested with a Steam Controller
Works flawlessly out of the box
Did not encounter any crashes or audio issues, worked out of the box with Proton 6.3 (latest at the time of writing) and has worked flawlessly for many iterations of Proton on a variety of tested hardware.
Flawless experience, no tweaks necessary
There used to be some issues with this game around Denuvo Anti-Tamper DRM, and some minor windowing/filter issues, but these have all since been fixed. Works like a native game!
Worked great out of the box
Game works perfectly in all my tests, both with the latest stable Proton 7.0-3 release and with GE-Proton7-20, as well as working perfectly when using Gamescope to run the game at 2160p. Game held a solid 60fps the whole time and ran like native
I have a panel on the top of my monitor, with KDE Plasma. The game fullscreens and cuts off at the panel, but it does not go under the panel.
To fix this, I used Alt+F3 to open the window settings -> Special Application Settings -> Enabled Fullscreen, selected "Force" from the dropdown and selected "Yes" which was the default coincidentally. Now the game always starts in fullscreen.
The Steam Overlay does not work with this game meaning the Steam Controller does not work, however as far as I can ascertain this is an issue on Windows as well. Other controllers may work fine, but the Steam Controller requires the Steam Overlay to work. Launching in Big Picture mode did not help.
Steam Overlay does not work, this means no screenshots, no Steam Controller, no music, none of the features at all from the Steam Overlay will work. As of right now, I have been unable to get the Steam Overlay to work. Forcing PROTON_USE_WINED3D=1 did not work, neither did using a WINE virtual desktop, and neither did using SC-Controller. PROTON_USE_D9VK=1 causes the game to crash. Tried installing vc2015 with winetricks, didn't fix the problem. It is quite possible that this issue exists on Windows, too.
Unsure if other controllers work, but my Steam Controller does not
If you don't mind playing with a keyboard and doing some fullscreen tweaks, it's a great Linux experience
- Game will start to a black screen unless you set
PROTON_USE_WINED3D=1 %command%
-Selecting the "x3" or "Full" options in the resolution settings did not set the game to fullscreen. I don't recall the game having good fullscreen support on Windows either
- I was able to set Plasma to make the game fullscreen by pressing Alt+F3 and going to Window Options -> Fullscreen. You can also set a Special Application Rule to force fullscreen for the game, that way you won't have to set this each time the game starts up
- The game has no Steam Overlay support, so I couldn't use my Steam Controller. At the time of writing, SC-Controller is not working for me either so I wasn't able to test properly. I don't have a wired controller to hand at present either
- This game has some issues even on Windows, so I don't think too many of these problems are solely to blame on Proton
- The game gives a warning at startup about that D-Input. Setting overrides for this, unsurprisingly, did nothing, but just in case you had the same idea as me I have to report that it didn't work. Even though it makes no difference to the game itself from what I can tell, it might cause issues with controllers.
Overall, performance and experience is fine on Linux but it needs a couple of small tweaks to get working.
Proton-6.8-GE fixes the Steam Overlay for the game and controller support
Game only supports 16:9 resolutions. When fullscreen on my 16:10 display, there was a black bar along the bottom. This is an issue with the game on Windows too, but worth pointing out all the same
- When using DXVK, the main menu background is little stuttery, but overall it is perfectly acceptable and the game is smooth.
- You can fix this stutter with
PROTON_USE_WINED3D=1 %command%in your launch options, however this breaks the Steam Overlay which means some controllers may not work!
Previously this game required tweaking and various workarounds to be a good experience. Now with the latest version of Proton-GE at the time of writing, the game is a near-perfect experience out of the box. Tested the first level with a Steam Controller.
- Note that this game only supports a handful of controller buttons - Basically SNES controller buttons. This means no trigger support, but you could bind triggers to be the same as bumpers using the Steam Controller Configuration which will allow you to use more buttons on your controller. This is a game design decision, not a bug with Proton
Only a brief test, but the native game worked flawlessly
Tested the native game my trusty Steam Controller and didn't have any issues
Proton-5.9-GE-2-MF GloriousEggroll
- As of writing (less than 2 hours after launch), the game will launch with SteamVR if you have that installed. To fix this, add the launch flag
-nohmd - Proton-5.9-GE-2-MF is the latest GloriousEggroll release of Proton at the time of writing, which has Media Foundation patches. These are needed to fix the intro splashes, but the game should mostly work fine without them. Audio at the very least will play and I didn't have any crashes without Proton-GE, but I highly recommend using it. Eventually the Media Foundation patches should be part of Proton and we won't need this build, but as of writing it is required.
- This is likely a result of the game's new release, as a few DirectX graphical patches were pushed out about 30 minutes after the game's release to fix missing textures and crashes, but sometimes the game's textures and lighting are missing for half a second after a new scene appears in a cutscene. This is not present in gameplay from what I have played so far
- Cutscene audio is completely out of sync, but this is a game bug as well. It should be fixed once the devs push out a patch, and once I play more I'll make an updated report to comment on whether or not this is fixed
When I first launched the game, my controller wasn't detected. I needed to reboot my computer to fix the issue. Since then I've had no problems.
- I have tested very little of the game but the initial testing hasn't shown any problems
- Tested with a Steam Controller
- Tested with vsync on and off, made no noticeable difference
- Tested with fullscreen and windowed mode, both worked fine
- I'm playing just hours after the release, so my issues may get fixed as both Proton and the game gets updated
Proton-6.5-GE is needed for the Media Foundation fixes in the main menu only. The rest of the game works fine. There'll still be a black screen on the "Are ya ready kids"? part of the menu but it will eventually show the bubbles and then transition to the main menu.
Cutscene audio was out of sync on the first load of a new save game. I simply restarted the game and loaded a new save. The issue disappeared after that.
The game runs at about 45fps most of the time, with occasional spikes to 60fps and drops as low as 35fps in my playtesting. Perfectly playable for me and acceptable for this laptop hardware. I would recommend capping the framerate at 30fps with MangoHud though.
- Tested with a Steam Controller
- Played through the first level, roughly an hour of gameplay. It was perfectly playable with no crashes
Works perfectly out of the box
Had no issues playing this game. I just simply clicked on the play button and everything worked as expected! Though the game is still in early access, and at the time of writing is only about a day old. The only glaring thing "issue" I noticed is that the game lists resolutions up to 8k, while I only have a 1080p monitor. Most games limit your upper resolution to that if your current display. It's not anything that impacts gameplay, and could be an issue with the game itself, but I thought I'd make mention of it anyway. All other aspects of the game I tested in my brief session worked - Cutscenes and audio were mainly what I was looking out for.
Did not experience any issues
I didn't have any texture issues, and I ran the game at max settings. It is capped to 30fps but this has nothing to do with Proton. As other reports mentioned, the online services don't work but that is also not something related to Proton. As it stands, the game seems to work exactly as it would under Windows.
Great native Linux port
This game works great, however it falls victim to a semi-common quirk I have seen with native Linux Unity games: The game displays too many resolutions, more than any of my displays have. Therefore you have to select the right resolution, otherwise the game will display too large on your selected display, as if it is rendering offscreen. This could be a KDE Wayland multi-monitor only issue but worth mentioning. As long as you select the right resolution you will be fine. The game correctly detected all my monitors and listed them as XWAYLAND1-4, and the game opened on my primary display. Overall a great native experience!
Works fantastic
- Tested with Steam Controller and with keyboard/mouse
- Tested with ACO on, though I doubt it made a difference with this kind of game
- Tested 32bit and 64bit builds, both worked fine
Not entirely sure how this differs from regular Starbound in terms of features and the like, though I did notice this version has no Steam Workshop support. So I can't test if mods work with it. Everything I did test (which was the brief into mission for the game and tweaking the resolution) worked without issue.
Works out of the box with no tinkering needed
Played an online casual match and experienced no issues at all. Issues mentiioned in other reports may have been resolved now.
Played the game at 1440p with max settings and had absolutely no issues online or offline. The opening cutscene worked fine and I was able to play the tutorial, a training match and a casual online match without any problems. The version of Proton used at the time of writing is Proton 7.0-2.
Works OOTB on AMD/Intel, needs a launch option for Nvidia though - Leaderboards cause a game crash
- Tested with a Steam Controller
- On my 5700XT and Intel HD620 the game worked out of the box! If you use Nvidia (tested with 980Ti), you'll need
PROTON_USE_WINED3D=1. - Tested local co-op using Remote Play Together (Both Linux hosts), worked seamlessly
- Trying to select the leaderboard option causes the game to crash. There's likely a fix for this, but I haven't looked. I highly doubt this is to do with any form of anti-cheat, as some other games have issues with leaderboards and need workarounds (e.g. Bayonetta at one point needed this I believe)
- Tested with Proton 5.0-9 and Proton 5.13-1, both worked perfectly fine
Can run at about medium settings with between 40-80fps. Slowdowns during opening cutscene occur. There is a strange mouse bug that increases sensitivity, which requires a game restart. It's playable though.
Tried running the game in and out of fullscreen, and adding the "-popupwindow" launch option. I still have the mouse issue. The game performs fine, normally stays above 60fps on medium settings (AA off, vsync off, reflections and water quality at medium, bloom and dithering on, and everything else at high). If not for the mouse issue, this game would have a Platinum rating.
Experimental branch fixes the mouse issue. I used the launch options "-window-width 1920 -window-height 1080 -popupwindow". I played with everything at max except Screen Space Reflections (kept at low), motion blur off and vsync off. I got about 70fps in my 30 minutes of playing on the experimental branch. Great to see this working well now!!
Use the experimental branch to fix the mouse problem. Then the game will run perfect. I ran the game with everything at max (including motion blur) and vsync off and got a consistent 50fps, with drops to 40fps when loading new areas. Turning some settings down (mainly screen-space reflections to "Off" and water quality to "Medium") gets the game to run at 60fps+ for me, but honestly if I didn't have the Steam FPS counter then I wouldn't have noticed that the game wasn't running at 60fps with everything at max. Great experience, now I actually want to play the game!
No problems to report
Only played about half of the game but it was a native-like experience. No issues at all.
Aside from a minor fullscreen issue, the native release works well
I am running on KDE Plasma Wayland. Your experience may be different on other desktops.
- Alt+Enter made the window bigger but it did not fullscreen. It fullscreened to the resolution of my monitor without my panel, and it went underneath my panel. I was able to move it down using Alt+Enter.
- Optionally if you are on KDE you can use Alt+F3 to open the window options menu, choose More Actions and select Fullscreen to force the window into fullscreen
- You can force this permanently for this game by enabling the fullscreen flag in the Special Application Settings menu
Native game worked without any major issues to report apart from the mentioned fullscreen problem. Did not test a controller. Overall a good experience on Linux.
Fullscreen works, dialogue speed changing works, all settings I tested work. No font rendering issues and no need to use any tweaks from my tests.
Great out of box experience, did not need WineD3D personally but it may be requried on dGPUs
Despite the store page listing, this game has native support! However it has no controller support - at least when I tested it with my Steam Controller. The game runs slightly better with Proton in my brief tests, and playing with Proton adds controller support! No flaws, played a couple of levels and all was right in the world.
On Intel Integrated graphics, this game requires WINE's OpenGL based Direct3D renderer to run as the Vulkan drivers don't seem to play nicely with DXVK sometimes. This does not impact performance at all.
Game will run at full, consistent 60fps with this as well. However, the game has native Linux support. The store page doesn't list it, but the game has a native Linux build. You can run it out of the box natively, or use Proton. In my experience, my Steam Controller did not work when running the native version. I would recommend Proton regardless though
Works with Proton out of the box with my dGPU, but game has a native port as well
The store page does not list it, but the game has a native port that works fine! Proton makes the game run slightly better and adds controller support. The native game did not recognise my Steam Controller.
Works perfectly, including fullscreen and custom cursor (unlike some other PopCap titles that have issues with fullscreen)
Game runs with some minor slowdowns (even with vsync off). I get about 90fps most of the time. My CPU is maxed out (with the game using about 60%) and is two generations behind the recommended CPU anyway, although the game runs without these issues on Windows. This aside, the game is fine and it is of course fully playable!
Solid performance, online works, only issue is no intro video - However this seems to happen sometimes on Windows too. I think this specifically is an issue with Proton. There's probably a fix but it's really no big deal as it doesn't cause any game lockups (unlike Catherine Classic).
Game runs with near-native performance with all settings at max. Intro video doesn't play by default, but use "mf-install" to fix this (https://github.com/z0z0z/mf-install), note that you DON'T need mf-installcab, the standard mf-install is enough to fix the intro cutscene. Follow the instructions on the README to install but it's essentially [WINEPREFIX="/path/to/library/folder/compatdata/78520/pfx" ./install-mf]. After that, you'll have your intro cutscene.
Game works perfect with on-par performance to Windows, optionally requires mf-install for opening cutscene
Used mf-install to fix the opening cutscene not playing. This has no bearing on any other aspect of the game, as far as I am aware, but I have not played much of the game in general, let alone through Proton.
Game itself works perfect, including multiplayer, but needs mf-install to fix missing intro video
- Tested with Steam Controller
- Tested on highest settings
- Tested both single player and multiplayer, no issues to report
- Tested streaming to my phone with Remote Play Anywhere, no issues
- Set CPU governor to "Performance", through the likes of Feral GameMode, to improve performance further
- Did not test local multiplayer or Remote Play Together
- Game requires you to use
mf-installto fix intro video, which isn't required by any stretch but it's a nice touch for perfect Proton compatibility - No one really plays online anymore, but if you do manage to get on, you won't be impacted by any kind of anti-cheat. The online racing worked perfect
- Intro video doesn't work, use mf-install to fix this
- Limited framerate to 60fps with a custom
dxvk.conffile in the directory with the game's EXE (browse local files, it's the default directory) with this single line:dxgi.syncInterval = 1- This is not required and is personal preference, but I like my games limited to 60fps
- Tested with Steam Controller
- Tested with Valve ACO
Proton-5.9-GE fixed all the annoying windowing issues I was having before, making the experience flawless now!
Proton-5.9-GE-5-ST
Couldn't easily escape fullscreen. On KDE Plasma, Alt+F3 brought up the window menu. From here, I could go to "More Options" and de-select the "Keep Above All" option. After this I had no issues.
Didn't try a controller. Completed the tutorial and had no problems. Using the Unofficial Oblivion Patch (installed with Vortex Mod Manager using Lutris) and I didn't have any problems installing or using it.
Game requires mods for best stability and framerate (1080p60 @ Ultra High), but this is true for Windows as well
- Forcing the game to only use Direct3D 9 massively boosted performance to a mostly consistent 50fps. Use
PROTON_NO_D3D11=1 PROTON_NO_D3D10=1 %command%
- As with Windows the game runs best if you install some mods, at the very least the Unofficial Oblivion Patch. I installed several which boosted my framerate up to 60fps at Ultra High settings. There are a variety of ways to install mods for Oblivion but the most common is to use Vortex Mod Manager. I installed it through Lutris and it worked out of the box.
- Full list of mods installed:
Oblivion runs extremely well on this hardware. Out of the box it gives 1080p50 @ Med (with slight tick stutter due to a game bug present on Windows too), with the mods listed it runs at 1080p60 @ Ultra High.
- Played primarily with a keyboard/mouse, but my Steam Controller worked too
- On this laptop I had to disable AA completely. The framerate dips to about 50fps regardless of whether you choose 2, 4 or 8 samples. The framerate will not go lower with more samples, or higher with less. On a Desktop PC this is not an issue, but on this laptop it is.
- Sometimes upon alt+tab the game's intro splash credits would be scaled down but this is corrected once the game fully loads. Alt+Tab does not have any further issues.
- Previously, Oblivion would crash or otherwise become unplayable when using Alt+Tab and the game required you to enable a Virtual Desktop, however this seems to have been resolved as of Proton 6.
- Beginning "Bethesda" Splash is visually bugged after installing mods, but is likely an issue on Windows too. Audio plays and the splash ends as normal, it is purely a visual bug - Nothing to worry about unless you really wanna see that splash animation :)
Overall a buttery smooth experience on Linux, with no more effort than Windows! The optional installation of Vortex might take longer but it requires no more effort than it does on Windows.
Works out of the box @ 1080p30 max settings using Proton 6.3-7 (w/ KDE Plasma Wayland)
Recently moved over to Wayland on my laptop, game runs flawlessly with slightly better performance under Wayland (approx 10fps boost) compared to Xorg.
- Had some greyed out menu options issues with Proton-tkg but not with vanilla Proton or Proton-GE. Not Wayland-specific though
- Did not try out a controller.
- 30fps was around the lowest I experienced under normal gameplay, but it did fluctuate between 30fps and 45fps depending on the world. 30fps was the minimum.
Very pleased with the performance on this laptop with Wayland.
Works great vanilla and with mods!
Game worked great out of the box with Proton 7.0-2. Optionally you can install mods using MO2, Vortex or manually, I used SteamTinkerLaunch for this but it's entirely optional. Played with a few different mods but mainly the Oblivion patches.
- Tested on KDE Plasma Wayland
- Didn't test a controller
The NPC guy at the start has a bugged out face and no eyes, audio is non-existent for me and performance on lowest settings is pretty low (however I'm running on pretty low-end hardware, I have yet to try on my PC). I tried with both D9VK and DXVK, with D9VK giving just a 2-3 frame boost. No crashes though, and if the game had audio then this would instantly jump to platinum I suspect.
On my laptop, faces are borked. Here on my desktop, everything except NPC audio works. There's substantial stutter if playing with esync enabled, so turn that off in the game's launch options with "PROTON_NO_ESYNC=1 %command%". I tried the game with both DXVK and the Proton 4.11-1 bundled version of D9VK, and performance was the same (interestingly, since SE still uses Direct3D 9). Played with settings set to Ultra and at 1080p. Tabbing out works, and you can quit the game from the main menu. However there is no NPC audio. There is background audio and sound effects and such, but not NPC works. Their lips flap but no words come out. If this is fixed I'm sure the game would jump to Platinum. I haven't tried compiling FAudio myself and trying to install the latest version with Protontricks/winetricks gives me an error. I haven't tested with mods, but they should work if you either have mods already installed (i.e. you're using a shared Windows/Linux drive and you currently have mods installed from playing on Windows) or if you use Vortex Mod Manager and install mods that way (like with Fallout: New Vegas and Fallout 4). This can be run through Lutris, or you can install it yourself (though just make sure the prefix you install Vortex on is on the same drive as the game you're modding). I haven't played Skyrim before so I'm haven't extensively tested the game, but once NPC audio works and I have a bit more free time I intend to delve into the game more.
Still no NPC audio out of the box with 4.11-2. Disable esync to remove stutter, game runs around 50-56fps. Haven't tried any fixes for the audio as I don't really intend to delve into the game too much yet, I'm waiting until audio works OOB before I consider it. Once it goes, I imagine the game will jump to Gold (as the esync tweak is needed).
Followed the instructions listed in this guide (https://www.reddit.com/r/wine_gaming/comments/q0uh4p/the_great_ace_attorney_chronicles_cutscenes_fix/), except for downloading the EXE manually. The script was able to do this itself without issue. The rest of the guide is required, however, especially the part about downloading the required DLLs!!
This the first title in a long time to require mf-installcab, and it requires extra DLLs too. The guide linked above can get the game working, though you don't need to manually download the EXE as the script is able to do it. Getting the game to work essentially boils down to using mf-installcab and moving the DLLs mentioned in the guide to the game's folder. Some notes:
- Tested VERY briefly, basically to check if the cutscenes worked
- Tested with a Steam controller
Force Steam Linux Runtime using either the Compatibility Tool menu (the same menu where you would force a specific Proton version) or using a third party tool such as Steam Tinker Launch
Once the Steam Linux Runtime is forced the game works great, forcing this is a common fix for native Linux games and isn't a big deal. Enjoy :-)
- Used Proton-6.19-GE-2. May not be required, but I used it regardless to ensure any issues with Origin would be stomped out.
I did not test regular Proton. Game takes a while to start up and install Origin, especially on less powerful hardware and connections.
- A lot of "ghost" Origin windows appear, likely related to the Origin overlay. It creates about five of these ghost windows, they show up in the task switcher and the like, but focusing them seemingly does nothing. It does not impact gameplay, but is something I wanted to note.
Perfect native Linux experience
Only played a few hours but it works without problems for me
Needs a launch option to disable fullscreen to fix a crash, other than that works flawless at 4k60 almost max settings
mangohud %command% +fullscreen 0
Tiny stutters that were unnoticeable most of the time, I think I only actually noticed once, but the rest I could only detect because I saw a frametime spike with MangoHud (which I only had on to test for this specific part of the report). In other words, the issues were undetectable in my play session.
Trying to initialise fullscreen from the settings with either the "Fullscreen" or "Borderless" option causes a crash. Trying to use GameScope also causes a crash.
Disabling vsync caused a crash most of the time, but not all of the time. Toggling graphics settings very quickly may cause a crash as well, I encountered this once when unreasonably changing settings, applying them, then discarding them and repeating this quickly. Under normal usage, most settings adjustments will not cause a crash,
I tested the "Short Demo" and had an excellent experience. Apart from minor stutters that, in all but one instance I could not visually detect, and the required launch option, this game works flawlessly at 4k60. I turned almost all of the settings up to the max, with vsync + framerate cap (works fine without vsync as well). Some other notes:
- This game uses Vulkan, so ensure you have Vulkan-compatible GPU drivers. Zink is not required and will degrade performance.
- Game needs the launch option
+fullscreen 0in order to launch, and cannot be fullscreened without causing a crash. Trying to use GameScope to circumvent this also causes a crash. This crash appears to be as a result of an issue with the Vulkan backend (https://steamcommunity.com/app/257510/discussions/0/135509472110661811/). To get around this issue, I used the KDE Plasma window menu options (Alt+F3) to force the game to run in fullscreen. - The only setting I couldn't max out was setting the "Max 3D Rendering MPIX" to unlimited, as this resulted in 100% GPU usage and 40fps. I maxed out all of the extra custom CPU and GPU settings though. GPU usage was averaging around 80%.
- The stutter was not reduced by lowering the game settings, so it is more than likely just an issue with the game rather than a result of the graphics settings.
- Given that I only tested the short demo, graphics settings may have to be adjusted to have a comfortable experience at different points in the game.
- Game does not require the Steam Linux Runtime, but works with 1.0 (Scout). I did not see any benefit to using it, it did not resolve any issues, and this game comes with a script to prompt you to install any missing packages that it requires. Should these become unavailable/outdated/incompatible in future, the Steam Linux Runtime (1.0, or much in the future 3.0 which currently has to be forced from
config.vdf) should resolve any compatibility issues with these libraries. It will not, however, solve driver-related issues.
Game was tested on KDE Plasma Wayland 5.27.10 with a keyboard and mouse.
Works great, just don't alt+tab
Alt+Tab breaks game with latest Valve ACO driver - Happens with Proton 4.11-8 and default 3.7-8
Steam Controller seems to work fine too
Alt+Tab breaks the game. You can't get back in if you Alt+Tab, the window is black and isn't fullscreen anymore.
You can also play GZDoom - a GoldSrc recreation of DOOM - that runs natively via Luxtorpeda. But if you stick with this standard DOSBox version you'll have no issues aside from not being able to Alt+Tab when fullscreen.
Works out of the box, no tweaks needed
The native game ran without any tweaks. Some native games need extra tweaks but this did not. Had no issues with windowing either. A solid native Linux port!
Runs perfectly smooth. For even better performance, set CPU Governor to Performance. For even extra better performance, install D9VK.
Add -changedir launch option as required by several games including Plants vz. Zombies
My GPU has official Vulkan support. My laptop's Intel iGPU most probably won't have compatible Vulkan drivers. Keep this in mind if you're playing on integrated graphics or older hardware with poor/no Vulkan support. If you experience issues, try using PROTON_USE_WINED3D=1 %command% in the launch options. This will force the game to use a WINE OpenGL-based Direct3D renderer as opposed to DXVK which uses Vulkan.
The game requires a custom launch option, -changedir. Set this and the game will run. Some other PopCap games require this, such as Plants vz. Zombies
Great native Linux port
"Problem" might be a stretch. The game by default opens in windowed move but moving it to a different display and then enabling fullscreen again will make the game fullscreen on the window it originally opened on. Not a big problem but worth remembering!
- Most desktop environments give you some way to move the window between displays
- This is my experience on KDE Plasma Wayland, your experience on other desktops may be different!
Another great ebi-hime game that works great native :-)
Used SteamTinkerLaunch to force the game to use the Steam Linux Runtime, otherwise it would crash on load
Force the Steam Linux Runtime using a tool like SteamTinkerLaunch to fix native release crashing on load
Works FAR better than the native port, though cutscenes are a little jittery at the start; Proton recommended regardless!
Game doesn't quit properly, had to kill with task manager. Game window closes but audio still plays and process still runs in the background
- I get a full 60fps with everything at max except AA which had to be ran at FXAA instead of SSAA. On my specs I got about 45-50fps with SSAA x2 and about 40fps with SSAA x4, so if that's acceptable to you, go for it! You could have a really good experience at max settings if that's the case
- Valve's ACO driver was used, it may have had an impact to improve shader performance but I can't say for sure
- Make a file called
dxvk.confin the game's main folder where the EXE is located to cap the game to 60fps. Add the linedxgi.syncInterval = 1and save it. Now the game will go no higher than 60, helping GPU load, avoiding the nasty stutter most games give with vsync, and making the game look smoother
Works out of the box
The game didn't open properly the first time I tried to run it on my new hardware, but it worked fine the next time. I turned all the settings up to the max and I got around 80fps on average, although the benchmarking tool said I got an average of 103fps. Runs far better than the native version!
LD_PRELOAD=/usr/lib/libfreetype.so.6 %command%
Unfortuantely it now needs the launch option mentioned for libfreetype, otherwise it works perfectly. Played entirely on native Linux and did not have any problems.
Perfect. Any issues with the game are *not* specific to Proton (e.g. Steam Controller showing generic xinput prompts).
Works just like Windows
Using D9VK, the game stays on top of all other windows. This makes it difficult to alt+tab out. You can change this by either not running the game with D9VK as it is not required, or setting some special application windowing rules if your compositor allows for it (e.g. KWin)
You can't use your controller until you either tell the game to use a controller in the settings, or until you select your profile that you've previously selected to use a controller in. This is a limitation of the PC port and nothing to do with Proton, after further investigation.
Game also displays generic Xinput prompts (button1, button2, button3, etc) for my Steam Controller. This seems to be an issue in general with the game after doing some research, and I can't find any way to change this. It's not a Proton issue by the looks of it but still something that will impact your experience.
I should note that, for anyone wondering, the game does not need a controller. It's perfectly playable with a keyboard and mouse. But if you do decide to use a controller, you should keep this in mind.
Works like Windows, but that doesn't mean it's perfect. Here are some notes:
- Tested with Steam Controller, works fine
- Remote Play Together is supported!
- Game is capped at 50fps
- D9VK works but makes no noticeable difference (aside from making it difficult to alt+tab, as mentioned earlier)
- As mentioned, controller prompts show numbers instead of A/B/X/Y, etc. Luckily, you can view your controls from the game's pause screen once you've loaded up a level (e.g. the Toy Box)
- Controller cannot be used until a profile is selected, as the control scheme used is dependent on what you set in your profile (massive PC port limitation, but nothing to do with Proton thankfully)
- Game cannot be ran at a resolution higher than 1600x900, as there is no option to select anything higher. Again, this is an issue with the game and happens on Windows too. I'm including this in case you've only played the game through Proton, so you know it isn't to blame.
Overall, runs perfect through Proton.
Game does not work, period.
This seems like it could be an all around issue with the game even on Windows. I'll keep trying periodically to see if I can fix it, but I have my doubts.
Still doesn't work with latest version of Proton
Audio works, you can sort of click around sometimes, but you can't see the game. Absolutely unplayable.
Works, no Steam Overlay support but that isn't a Proton-specific issue
Everything worked out of the box, great experience with Proton. Trap waifus on Linux :D
Works with no issues
No Steam overlay and audio crackles sometimes but I highly suspect these are issues with the game itself and not Proton.
Runs perfectly. No Steam overlay but that's not a Proton issue. 18+ patch works as well.
Game crashes with .NET error
Game shows a .NET error dialog. You can press continue but the game just hangs. Did not try any tinkering such as attempting to install removing wine-mono and installing dotnet48.
Like with many of these old titles, the fullscreen doesn't seem to work with Proton or on Windows. So not a Proton issue. Outside of this, works perfect.
Played about 2 hours under Proton, fullscreen seems to work but it lags a fair bit. Not sure why. Aside from this, flawless experience.
Ran in fullscreen on my laptop by default, it didn't on my PC. If you use a custom cursor, the game will start to lag if the game is in fullscreen (it's fine in windowed mode). I'm not sure why, but don't use a custom cursor and you'll be fine! The game isn't really focused on the mouse anyway :-) This issue could be present on Windows too, but I haven't tested. There is also no issue with quitting the game as noted in the Steam reviews, so I'd say perhaps the game runs even better on Linux than on Windows! On this laptop hardware, while it got a little hot, CPU usage was never too high and the game ran at a consistent framerate. Fun little time killer!
If you use a custom cursor and set the game to fullscreen, there will be lag in menus. Simply disable custom cursor and you won't have any issues.
Works without any tweaks
Don't set a custom cursor when the game is set to fullscreen or else you'll get some nasty lag. This might even be present on Windows, I haven't checked
Works perfectly
Problem: Custom mouse cursor causes the game cursor to lag when fullscreened Solution: Disable custom mouse cursor
No issues running on my laptop, unlike some games that require WINE D3D this game worked fine
Works great out of the box
Turn off custom cursor if you're running the game in fullscreen to prevent stutter. It's not needed anyway, it doesn't affect gameplay in the slightest
Disable/don't set custom cursor and the game will work fine!
When using fullscreen and a custom cursor, the game slows down when you open dialog boxes (e.g. settings or any of the menus to start a new game mode). To fix this, disable custom cursor. I couldn't find a way to fix this, and I tried several launch options including PROTON_NO_ESYNC=1. I tried setting some custom Proton versions based on WINE 4.21 and WINE 5.0, but no luck. It's not a big deal though, as custom cursors are not needed (and the game is primarily keyboard focused, anyway)
Played the entire story mode of the game with no issues. Hardware Acceleration works fine as well on my hardware
- Proton-5.9-GE-2-MF or any newer version with Media Foundation patches (as of right now this is the latest) is required to get the game to load beyond a black screen.
- Alt+Tab breaks the game, even in windowed mode the game just freezes. Setting a virtual WINE desktop did not fix the problem either
- Using a virtual WINE desktop does not set the game to the correct resolution
- The "downscaling" option did not work, it resulted in the level turning completely black
I only tested the first two levels but I didn't have any performance issues, no crashes, everything worked great!
Game ran out of the box with no issues. Didn't test VR but sound, mic, and so on all worked fine. Didn't have any issues loading worlds.
Didn't have any issues with the game
Everything worked fine for me, but I didn't test the game in VR as I don't own a VR headset
Need to force Proton (any version) or else it tries to load a native game for some reason
Game works perfectly fine but you can't just click play. You need to force the game to use Proton in the Steam settings.
Works flawlessly without tweaks
- Going from the Main Screen with the "Start" text took about 7 seconds, which scared me for a second. But the game did eventually load without any issues!
- Tested with all the DLC, including the patch, and it applied as expected
Native game works perfectly
- This game is designed to be played by two players I assume sharing a keyboard (one player uses WASD, the other uses arrow keys, the pause menu lists the controls).
- I tested this by using a clever trick to simulate having a second player: controlling both characters myself. This worked fine, so there is no reason it shouldn't work if you have another person playing as well
- I did not try Remote Play Together but I don't see any reason why this wouldn't work
Some Unity games' launchers list resolutions higher than I can use but this game did not, it correctly listed 2560x1440 as the maximum resolution (the scaled resolution of my display). It also detected and listed all of my monitors correctly, labelling them as XWAYLAND1-4 displays followed by their size in inches. Overall a flawless native experience.
Played 1600x900@60fps with medium settings preset (vsync off), fantastic for this hardware!
- Proton-6.12-GE-1 was used. I did not try with native and had no strong reason for using it.
- Feral GameMode was used to attempt to boost performance.
Given my hardware the performance was exceptional. I could potentially turn the settings a little higher but I was happy with the performance I got. Played for around 2 hours up to the beginning of Chapter 2 and had buttery smooth performance. Ran like native!
No tweaks needed, game works out of the box
A visual novel style game so there wasn't really anything to go wrong. Game was capped to my monitor's refresh rate so no need for any tweaks here!
2K Launcher is broken, use AML and SteamTinkerLaunch to make the game launch using the AML executable
The game itself works great, max settings 1440p@60! However, the 2K Launcher is buggy and requires several relaunches of the game before it seems to maybe work. For this reason I gave up on it and used the community mod manager AML, which did require using the Windows build of the game through Proton but I encountered no errors. I used SteamTinkerLaunch to manually edit the game's executable. Instructions to do this are below:
- Close Steam
- Download and extract the XCOM Community launcher to a location on your computer. I chose the game's installation directory (Right click game in Steam > Manage > Browse Local Files). It doesn't matter if it's in a subfolder or not, but I chose to put it in one to keep the installation folder clean.
- Install SteamTinkerLaunch (Compatible with Steam Deck!), either from source or if its in your distros repositories you can install it with your package manager. NOTE: May or may not be incompatible with Flatpak Steam. Once STL is installed run
steamtinkerlaunch compat addto add it as a compatibility tool to Steam - Re-open Steam and force SteamTinkerLaunch as a compatibility tool for the game (this will force it to use the Windows version of the game if it's not already in use)
- Launch XCOM 2, press the "Main Menu" button for SteamTinkerLaunch, then click the "Game Menu" button at the bottom of the main menu, tick the "Use custom command" checkbox, and finally click the "Custom command" box and select the AML executable.
- Click "Save and Play" and enjoy XCOM 2. The launcher may say it cannot find any mods but you can manually set the mod path using the mod manager's settings. Click AML's button to start the game and it'll play without issues.
No Steam Controller support. As with Windows 10, requires vsync or there is incredible amounts of tearing. Must be played on lowest settings to get any kind of playable framerates (14fps average).
Ran on an NTFS Samsung 850 EVO SSD. Full Steam Controller support since Kernel 4.19.4. Game needs a while to "warm up," runs at 80+ FPS on high settings with vsync off after you've loaded into a save for about 30 seconds. A similar kind of treatment is needed on Windows 10. With vsync on, performance takes a decent hit, only running at around 45fps. The only issue I encountered was no sound effect at the "SEGA" splash screen.
Performance is absolutely perfect. Has some performance issues if Plasma dies. You need a small path (ideally with no spaces or special characters) for the arcade games to work. Audio does not work in arcade games. Do not set the game to Borderless Fullscreen, as you will not be able to change that setting without the game crashing. I recommend playing without vsync for best performance.
Game works extremely well. Played on max settings. Some framedrops in certain areas and dialogue scenes. Arcade games have no audio, even with Proton 3.16.6's FAudio implementation. Very minor graphical glitches with texture clipping in very select areas, which isn't noticeable unless you're trying to find them. An overall very nice experience.
Arcade minigame audio (i.e. Out Run) doesn't work, there's no "bah" sound at the start for the SEGA splash, but everything else works. Played at Ultra with 2x SSAO and no vsync for 160+ hours at a fairly consistent 90fps+. Did a full 100+ hour Legend playthrough on Linux, the game only crashed once - it crashed more on Windows. Climax battles work, arcade games work (aside from audio as mentioned), 60fps cutscenes work, Steam Controller works perfect out of the box, basically the game runs perfect!
I've played a few hundred hours with Proton with no issues. Full controller support, but in terms of graphics I'm a tad limited by hardware. Everything except full AA can be turned on and will run at a smooth 90fps+!
Played for a few hundred hours with a Steam Controller and it runs perfectly. Just disabled vsync. Performance is identical to Windows. I recommend locking the game at 60 in the configuration file located in the game's Proton prefix, similar to how you would do it with Windows.
Flawless performance, no audio in arcade games sadly (but the games themselves all work fine). Everything else works perfectly. Played through the normal game and a Legend difficulty save both under Proton with no issues, and have played over 300 hours with Proton.
No arcade audio in minigames or for startup sound. All other audio works.
Recommended to lock at 60fps for a more stable experience, particularly to avoid any kind of stuttering in cutscenes if you don't have them locked to 60fps.
Works almost perfectly, arcade audio missing but that's it
Arcade game audio does not work. I have yet to find a fix. Perhaps playing with FAudio and winetricks could fix it?
A few notes about my setup and experience:
- Tested with everything at max except for vsync and AA; vsync causes stutter so I'd advise removing it
- Tested with Steam Controller
- Valve ACO driver makes a slight but noticeable difference
- Limit to 60fps either with DXVK or set the
MaxFPSthe game's configuration file: - DXVK: Make a file called
dxvk.confin the game's directory with the EXE and add the linedxgi.syncInterval=1 - Configuration File: Go to
steamapps/compatdata/638970/pfx/drive_c/users/steamuser/Application Data/Sega/Yakuza0/, opengraphics.iniand set/add the lineMaxFPS=60 - Set CPU Governor to Performance (use Feral GameMode or this plasmoid for KDE Plasma, this will help with stuttering
- A minor aside not directly related to Proton, but worth mentioning for Proton gamers: I played with Steam Remote Play, and it worked flawlessly! No issues streaming even though it was running under Proton
Aside from no arcade game audio, the game runs without issue
A previous report mentioned the save file bug. I experienced this on both Windows and Linux equally, it seems to come and go. Just go to a telephone box and save, and the bug will resolve itself. This is a game issue though and completely unrelated to Proton.
- Did a full legend playthrough with Proton and didn't have any problems
- Played for a significant chunk of my time (300+ hours) on Linux, and a fair bit on Windows too. The game runs identical in my experience on both. The higher AA values have a bug that affects AMD hardware on Windows and Linux (this is present in Yakuza Kiwami and Yakuza Kiwami 2 as well)
- The game ran at a consistent 60fps for me (after I locked it in the game's configuration file, see previous reports on how to do this)
- No arcade game audio sadly, and I haven't found a fix for this yet. However it doesn't impact gameplay, so if you're reading this and you haven't played the game - don't worry, it isn't going to impact game performance. Out Run with no music is a little lonely though...
- Tested basically everything in the single player and the multiplayer very briefly on Linux. I did all the Climax Battles without issue, all the gambling minigames, darts, pool, Out Run, Super Hang On, Space Harrier, Fantasy Zone, Mahjong, and I didn't have any problems aside from the audio issue mentioned
Yakuza 0 works fantastically well on Linux! There is nothing stopping you gameplay-wise from getting 100% completion if you wanted to with Proton
Works perfectly
Arcade minigame audio is missing but this isn't game-breaking by any means, the games themselves still work.
- Tested with a Steam Controller
- Tested with ACO enabled
- Did a full playthrough on Hard and Legend, and played all Climax Battles without issue
Works out of the box
- SEGA logo is missing the "bah" sound effect at startup
- Arcade games are missing audio (though this does not impact gameplay)
For me, this game has worked perfectly with Proton for the last almost two years! Some are reporting issues with save files and crashes but I haven't personally experienced that.
- Tested with a Steam Controller
- Tested the entire game on Proton, including a Legend playthrough
- Tested all Climax Battles
- Tested all minigames, aside from arcade games missing audio everything else worked as on Windows
- All achievements are unlockable with no issues
- Enabling vsync can help with cutscene jitter, the same way it helps on Windows too
Runs at a stable 45fps on this laptop (Inspiron 5505)
- Played with a Steam Controller on this laptop, I get a stable 45fps pretty consistently. You could lock the game to 30fps with something like MangoHUD if you want a more consistent framerate.
- This game used to have an issue where the arcade games (Out Run, Super Hang On, Space Harrier and Fantasy Zone) didn't have audio. This issue has now been fixed. Arcade games have audio now. This means the game runs exactly like native, including pretty much 1:1 performance.
Disclaimer: I upgraded this laptop to have 16GB dual channel ram and it gives a noticeable boost to this game. However, it can run at a stable 30-35fps without this upgrade.
Runs better than it does on Windows, all cutscenes, audio, minigames (and minigame audio) work perfectly
I have played a lot of this game on Linux, and originally almost 4 years ago there was missing audio for the SEGA "bah" sound when you launch the game, and no minigame audio. There was also a weird bug when saving that would activate some kind of "debug mode". In some specific locations there were odd textures too. This has all been fixed for a very long time and since then the game has worked perfectly.
- Played with a Steam Controller and official Nintendo Switch Pro Controller without any issues
- Played with some mods such as the HD character mod and HD UI mod, no issues with them
- Played with everything at max settings except SSAA which I kept at 2x (vsync was off too)
- Played on KDE Plasma Wayland but the game works fine on X11 as well
However, some notes for those wanting to play at higher resolutions:
- Playing at 4k (the game barely ran at 1080p on Windows) required me to use Feral GameMode to fix some frame drops in Kamurocho, but if you're on better hardware or not playing at 4k you won't have any problems
- You can set an FPS limit for the game in the system settings or use an FPS limiter (such as one built into Gamescope) or you can use MangoHUD with
mangohud MANGOHUD_CONFIG="fps_limit=60;no_display"to cap the framerate. Either works fine and may be preferrable to take some strain off your GPU
A fantastic experience on Linux that outperforms the native experience.
gamemoderun DXVK_FRAME_RATE=60 %command%
I saw some reports saying this game is crashing now, so I tested for myself and it all worked fine on my end for some reason (not to discredit the other reporters, just documenting my own experience).
- Tested in-game cutscenes as some of the Steam Deck reports mentioned freezing but it was fine on my PC (will test on my Deck when I finally get it)
gamemoderunoption helps boost performance at 4kDXVK_FRAME_RATE=60is an easier way to cap the game's framerate, though this can also be done from the game's config file and also through MangoHud- All of the launch options I use are entirely optional, game works fine without them :-)
Controller support specifically for Yakuza Kiwami was implemented with WINE 4.7. As of writing, Proton is currently based on WINE 4.2. However, follow this guide on GitHub based on a Steam forums post (https://github.com/ValveSoftware/Proton/issues/2403#issuecomment-489368485) to build a custom version of Proton and controllers will work. Tested with the Steam Controller and it's flawless. Just be sure to build in your home directory. Played about 15 hours so far, on Chapter 4. No crashes, a couple slowdowns, performance is identical to Yakuza 0 - about 70-90fps with everything at ultra, SSAO at 2x, vsync off and 1080p borderless fullscreen. This is expected as they use the same engine. Puddles don't have any splashing effect, they just act as though they were part of the terrain. Tested the karaoke, MesuKing and UFO catcher, all work fine. UFO is a little jittery but this could be a Windows issue too. Sometimes pavement/wood textures render too stretched, though this happened in Yakuza 0 as well. Never played game on Windows so I have no reference but it's been a perfect experience so far outside of controller support, hence the Gold rating.
As of Proton 4.2-4, controllers work out of the box. Tested with the Steam Controller. I completed the main story. Performance is great (solid 70fps+) with everything set to Ultra, SSAO at 2x, 1080p borderless fullscreen and vsync off. I recommend borderless fullscreen, vsync off and capping the framerate at 60fps by going to "(/path/to/steam library folder/)steamapps/compatdata/834530/pfx/drive_c/users/steamuser/Application Data/Sega/YakuzaKiwami" and setting "MaxFPS=60". This makes the game feel much smoother. The UFO catcher is a little jittery but all minigames work fine - Mahjong, MesuKing, the Cabaret Clubs, etc. Perfect experience.
Played the game fully and exclusively on Linux, no crashes or freezes. With Proton updates, controller support was implemented. Way back, this was the biggest problem I faced and had to use a custom version of Proton-tkg. Now, though, the game works out of the box! Not a single crash, freeze or any issue. Everything except AA can be played at max, just like the game's predecessor, Yakuza 0.
Exclusively played under Proton. Encountered absolutely no issues. Runs like native. Played with Steam Controller.
No audio issues unlike other reports. Worked out of the box!
Works perfectly including controller
Many many moons ago this game did not work with a controller, but this issue has long since been fixed (in case you're wondering about the older reports). Ran with everything at max except SSAA, which I kept at 2x (though it will probably run with with 4x). This is the same as Windows for me. Vsync was also turned off as usual. Great performance! Played this game exclusively on Linux, so all my hours are from Proton
Played the entire game on Proton and I haven't had any problems
- Tested game with a Steam Controller
- Tested with and without ACO, and the new backend didn't make a whole lot of difference. As Proton and Mesa have matured, performance has definitely increased through!
- This game runs slightly heavier than it's younger brother, Yakuza 0, but both run fantastically well on my hardware. On my old RX480, Kiwami chugged a little bit, so I'd just keep that in mind (especially if you use a slightly older version of Proton)!
Crashes with Proton 4.2-3. Goes to a black screen with my custom version of Proton based on WINE 4.7
Game launches consistently. All settings at max except AA at SMAA and motion blur off - almost identical to how I play it on Windows with nearly identical performance except Render Scale should be reduced to 75% as opposed to 100%. There are slowdowns when performing the spam-Y/Triangle attacks in Extreme Heat Mode , and when loading new parts of the map. As with Windows, Sotenbori has better performance than Kamurocho. Cabaret Club Grand Prix, Majima Construction, Karaoke, Virtua-On, Virtua-Fighter 2.1 and Toylets work perfectly well. The game generally stays around 60fps in my tests. No crashes yet. Cutscenes can be a little choppy because of the varying framerate. It's perfectly playable though, and I'm sure with the right hardware it runs great!
Game launches every time for me. Render scale had to be set to 75%, and AA had to be set to FXAA (this is due a bug, also present on Windows). Everything else can be played at max, so long as the CPU Governor is set to performance. These settings, for me, are the exact same as how I played on Windows with near 1:1 performance. I capped the FPS at 60 as added in the latest patch just for preference and to take some load off the GPU. Heat Actions have frame drops to 10fps, but setting the blood to mild fixed this. Played through the whole game, including the Majima saga - 70 hours on Linux, not a single crash.
Runs pretty much as well as it does on Windows, except the render scale has to be set to at least 75% (though I got a stable 60 with up to 85% render scale). Game will be a bit slow to start up as on Windows, meaning for the first 30-45 seconds in game you may have a bit of stutter and framerate fluctuation. Let your GPU warm up and you should be good. I recommend capping the framerate at 60fps in the settings (added with a semi-recent patch). Also, there'll be frame drops in battles if you have the "Blood Level" in the game settings set to "Normal" - Turn it down to "Mild" (the only other option) and that'll fix it. Haven't had a crash or boot issue ever since about Proton 4.2-9, and I can run the game directly through Steam. No minigame issues to report either.
Game runs at 60fps (capped) with everything at max except SMAA and Render Scale at 75% (SSAO doesn't work because it sets the render scale to 100%). This is to be expected on my hardware, which is about two years behind what is recommended. It's a miracle the game runs at all. With Valve's ACO Mesa driver, the frame dipping during heat actions has been fixed! Now the game runs buttery smooth on my hardware. If you had something more recent such as a 5700XT or a Radeon VII, you'd probably get a solid 60fps at max settings.
Performance more than acceptable given my specs. With render scale at 75%, everything max bar AA at MSAA, fps locked @ 60, game runs perfect
Use Valve's ACO driver to fix stuttering during heat actions. Otherwise, if you do not use a compatible GPU, set "Gore Level" to "Mild" instead of "Normal" in the game's settings.
Performance is the same as Windows
- I am running FAR below the recommended specs for this game and I can run it at a consistent 50+ fps with everything set to max except for Anti-Aliasing. On AMD cards, there are major issues with the highest AA option. However I can run with SMAA just fine.
- Even the render scale set to 100% works now! Using Valve's ACO Mesa driver fixes the slowdown during heat actions, if you are not using a compatible AMD GPU then turn the gore setting down in the game's settings (Essentially turns off the blood during heat actions)
- If you want a perfectly smooth experience, you can cap the game at 30fps and you won't notice any stuttering or hangs (game has an option for framelocking builtin, no need to use
dxvk.conf) - Set CPU performance governor to "Performance" as the game can be quite CPU-bound with Proton (like some other games). You can do this with Feral Gamemode or this plasmoid
- Tested game with a Steam Controller and did a full playthrough with Proton
- Everything works just like Windows, if I met the recommended specs I could probably run this game at a solid 60fps (say with an RX 5700 XT and a Ryzen processor of some description)
Runs like a dream with the correct hardware
On my 5700XT, the game runs at a consistent 60fps+ with everything at max except AA. The higher values still have a bug that affects AMD hardware, so I keep it at SMAA. Tested out a few bouncer missions and had a few drops to 55fps ish, but without the FPS counter I wouldn't have noticed. Tested with a Steam Controller. Valve's ACO fork should no longer be needed to fix the gore, as it should be part of Mesa 19.3 onward.
Mesa ACO Shader Compiler- On compatible AMD hardware using Mesa 19.3 and up (or Valve's custom Mesa fork based on Mesa 20.0.0-devel), you can now use a new shader compiler developed by Valve called "ACO". To enable it on Mesa 19.3, set the launch optionRADV_PERFTEST=aco. This gives big performance boosts and fixes a bug where the game would slow down during heat actions. Huge quality of life improvement, for those who haven't played the game and are unaware of what heat actions are, so I highly recommend enabling it if you can! Chances are, if you're running an AMD GPU capable of playing this game, you can probably use ACO. If you're using Valve's custom fork, ACO is already enabled for you!
- Tested the game with a Steam Controller
- Tested various minigames, karaoke, played the entirety of the Majima story on Proton too - No issues to report
- Played the last half of the game on Proton and didn't encounter any issues
Works out of the box with great performance
This game is unoptimised as heck on PC but now I seem to get near native performance - and this has continued to improve overtime.
On AMD hardware with Mesa 19.3 and up I highly recommend enabling ACO as this fixes a slowdown during heat actions. You can do this by adding the launch option RADV_PERFTEST=aco. As on Windows, the highest form of AA causes severe lag on AMD hardware (this affects all Yakuza games) and this is still present when running under Proton. However, ignoring that, you can run the games with all settings at max. I personally lock my game to 60fps and I can hold a solid framerate without issues. The entire main story + Majima Saga is fully playable under Proton!
Game does not start
The game crashes with an illegal instruction error (wine: Unhandled illegal instruction at address 000000014442DC0E). Based on other, similar errors in other games, this is likely a DRM issue or an unimplemented feature of WINE. It may work in the future, but as of right now it does not. It's also worth mentioning that this game has not had a very smooth launch on PC, so that may also be contributing and/or may delay progress on a patch. You can keep track on potential updates on this issue on the Proton Issue Tracker
- Proton-5.9-GE-8-ST with the launch option
PROTON_USE_SECCOMP=1allowed the game to boot up! - The GitHub issue tracker for the game has a custom build of Proton 5.13-next that can be installed and used to run the game without the launch option mentioned above, and is a more "vanilla" version of Proton so to speak. Some users may prefer that!
If the game is set to "Fullscreen" (the default), alt+tab does not function correctly and you'll get some flickering. Setting the game to Borderless Fullscreen fixed this entirely
- Some infrequent and extremely minor but noticeable dips of 1-2fps during cutscenes when the camera angle changes.
- Dips for half a second while roaming around Kamurocho initially, lowest was one dip to 45fps but most were only down to 56-58fps
- These dips disappeared after roaming around for about 10 minutes
- A small hang before playing the cutscene after the game's opening gameplay chase sequence
I personally mostly tested with the custom build of Proton 5.13-next that I mentioned. However, I accidentally left my PROTON_LOG=1 launch option on and this usually gives me a pretty big hit with game performance. Overall, I got a very solid 60fps. It's a great experience!
- Tested very briefly with a Steam Controller
- If you have issues with your controller, it's likely the game! It has some bugs at the moment with controllers
- Played with all settings at max, vsync off and framerate locked at 60fps
- With framerate unlocked it's a consistent 75-85fps
- Played at 1080p
- Played up until after the tutorial fight and roamed around Kamurocho briefly. Had no crashes or problems or anything aside from the occasional framedrops I mentioned.
Native ran without problems
Tried tweaking various graphics settings and everything worked as expected. Have not tried a controller. Great native port!
No issues. Played with all default settings (including leaving 3D acceleration on). Unlike, say, Plants vs. Zombies, I didn't need to set any launch options. Game works out of the box. Alt+Tab also worked fine for me.
Worked without any tweaks on my laptop
No issues with fullscreen, alt+tab, game ran at full 60fps, no issues to report!
Add -changedir to the game's launch options, similar to what is required for "Plants vs. Zombies". The game will display an error saying that the -changedir launch option was expected, and will not start.
- Enabling 3D acceleration does not work, the game just reboots after accepting the changes in the settings. This could be a general bug with the game as it is quite old, however I have not tested on Windows
- Enabling "hi-res mode" causes the game to restart in the same way, as it requires and automatically enables 3D acceleration, meaning you cannot enable this option. The game will restart in the same way.
The good news is, these features aren't required, and every other setting works (custom cursor, custom radical, etc). Having these options off does not take away from the game whatsoever.
Works beautifully with "-changedir" applied, everything works on my desktop PC except for "hi res mode"
Use -changedir launch option for the game, or else it will give you an error saying that you need to apply it.
Trying to enable "Hi Res Mode" does not do anything. The game will restart when you click "Ok", like it says it's going to need to do, and then when the game loads back up again, the option is still disabled. On my PC, "3D acceleration" works and is enabled by default. It is not on my laptop (see my previous report).
Launcher doesn't work but game itself runs fine
- I suspect the launcher could be fixed by installing some dotnet winetricks and otherwise doing some fiddling, but the launcher isn't necessary as the game recognised my Steam Controller and graphics settings out of the box
- I didn't experience any crashes in my time playing so far, and I played through the first level (Last Resort) just fine. Didn't experience any issues with Alt+Tab either which I did quite frequently
- I tried with standard Proton 5.0.7 and Proton 5.8-GE, both versions worked fine with no noticeable difference
- I see no reason why this wouldn't be an enjoyable experience with Proton
Runs at about 45fps, so it's a bit sluggish. However that framerate is consistent. The biggest issue is that sometimes objects and people in the game (including Leon and Ashley) lose all lighting effects and become black. There is also some lighting problems outdoors. But, there's nothing game breaking that I encountered which could stop you from playing the game start to finish.
Textures frequently disappear, framerates are inconsistent, the Steam Controller and possibly other controllers have issues where moving will be jittery, as if the analogue stick is rapidly being pushed upwards rather than held upwards. Could be played, but isn't as nice of an experience as Windows.
It works now with D9VK! Either install it yourself manually into your Resident Evil 4 Proton prefix (https://github.com/Joshua-Ashton/d9vk/) or use the version that comes with Proton 4.11+ by: Right Click on Resident Evil 4 -> Properties -> Set Launch Options -> PROTON_USE_D9VK=1 %command% - This will give a full 60fps. I only encountered some very light stutter and it was only maybe two or three times. Pretty much a native experience!
Set "PROTON_USE_D9VK=1 %command" for flawless performance and no graphical issues. Fixes the black texture and stuttering of the game. Also, my Steam Controller now works fine with the game. No noticeable issues, no crashes experienced so far, runs basically like native.
D9VK gives better performance and fixes graphical glitches.
Game was tested and played with my Steam Controller and worked exactly how it does on Windows.
Using D9VK fixes performance and missing textures. Your launch option string should now be PROTON_USE_D9VK=1 %command%
Works out of the box with 4.11-11, now that DXVK and D9VK have merged
No need to set PROTON_USE_D9VK=1 anymore. If you've set this previously, remove it as it is no longer needed. Steam Controller works and the game works fine with RADV_PERFTEST=aco, though I haven't seen any major noticeable difference...
