
Used 2009 Honda Civic LX
Published
Works out of the box
A couple crashes, but I remember it also doing that on Windows, I think it's just because it's an older game rather than due to Proton
I played start to finish with no problems and no tinkering required. The DLC episodes also work fine. Great if you're looking for a good story.
Game runs great - if you have the bravery to play it
I've played 4 hours and haven't had a single problem so far. Wonderful game.
No issues, performance has been fixed.
Game used to have major issues on Linux with models not loading and various instabilities. These have been patched out. It works flawlessly now, loads very fast and performs very well. Never had a crash in about 40 hours of testing.
Large warning, playing with Proton Experimental (or Linux in general) can get you banned
I've played for a few months with Linux. Flawless experience, no issues. Proton-GE, Proton Experimental and a couple other versions, but mostly Experimental. I log in last night to discover my account was suspended with no explanation. I sent an email to EA support appealing the ban and was declined, saying they have confirmation I was using cheating software and it will not be overturned. I (obviously) do not cheat, have no idea how you even would on Linux and have a low K/D regardless. The only explanation I can think of is Proton Experimental had an early change of some sort and flagged the anti-cheat. I would stick to Windows if you take the game seriously.
Be heavily warned that this game hands out bans like candy for playing on Linux
I was falsely banned for nearly a month due to playing on Linux, and after multiple threads finally got it overturned. I can now play the game again.
I made a report a few weeks ago saying I was falsely banned for playing on Proton and EA support refused to overturn it. I was I believe the first one this happened to due to the fact I was using bleeding-edge but more cases started pouring in and now there's multiple reports of bans here. They seem to be overturning the bans now, I just had mine overturned, but I would be very wary about playing this game in the future on Linux. They mass-banned Linux users 2 years ago as well and I suspect this will happen again.
Anti-cheat blocks Linux now
Not much else to add. You just can't play the game. Big shame considering it having Linux support was a huge win for a while.
Ubisoft Connect install script
Game's default input set is wrong on an Xinput controller, you'll have to rebind them yourself in the controls menu
Playing from Ubisoft Connect on Lutris it just works without any issue. No stuttering like AC1, and no performance issues whatsoever. 180 FPS, physics are a little buggy unless you enable VSync.
I would recommend downloading EaglePatch and installing it to unlock the content you can't get anymore because of the servers being shut down (Altaïr's robes and some weapons). You will need to add a dinput8.dll override in your respective game launcher to get the mod to work.
Ubisoft Connect install script from Lutris
You have to manually enable the controller in the game's options menu. Was also an issue on my Windows machine, so not Proton related, but would be a hassle on the Steam Deck
Stutters every 60-120 seconds, explained below
Leap of Faith causes death when framerate was greater than 60, can be solved by locking the FPS or just enabling VSync
Played on Ubisoft Connect through Lutris, didn't own it on Steam
The game has a stutter every 60-120 seconds that lasts for around 1-2 seconds. This isn't a Proton issue, it's caused by the game trying to reach a server that doesn't exist anymore to upload your stats. The fix for this in Windows is to just block the IP from your "hosts" text file, but this didn't work for me. The only way other way to fix it is to unplug your ethernet cable/wifi adapter. This worked, but I didn't want to disable my internet for this game, so I just dealt with the stutter.
It's not a Proton-specific issue, but you can't fix it on Proton without disabling your internet.
*Mostly* free of issues, launched and played as normal, but would suggest buying on Ubi Connect over Steam
In certain missions, notably the castle attack at the beginning, the game will bug out when above 60 FPS and the missions will be nearly impossible to complete. AC1 also has this issue, but turning V-Sync on fixed it. It does not in Brotherhood. To fix it, you have to use Mangohud to limit the FPS or manually change your refresh rate in your display settings. In most of the game 180fps works fine, so you can keep it on until you encounter issues.
This is not a Proton issue, just an old game issue.
Ubisoft seemed to have replaced the UPlay launcher with Ubisoft Connect, so the steps from older ProtonDB reports about replacing UPlay are not necessary anymore. You can install the game and Ubisoft Connect will appear, no tinkering/installing required.
However, perhaps due to being "contained" in the Wine prefix, it seems Ubisoft connect will forget your login info everytime you close the game and you'll have to input it on the next boot. You can add a "note" to Steam and save your login info to just paste it in, but it is annoying. Using say, Ubisoft Connect from Lutris does not have this issue.
It should also be noted this game doesn't have cloud saves (not a Proton issue, but I didn't know and lost my saves).
Unless you really want it for collection purposes, I would suggest buying it on Ubisoft Connect instead so you do not have to deal with the login annoyance. Other than that, flawless performance and controller support out of the box. Works the same as native.
Works out of the box
One crash in a loading screen, in about 9 hours of play.
No issues on my end. A friend of mine couldn't get the game to run even close to 60 FPS without editing an engine.ini file in the prefix for the game in the compatdata folder (something about setting disablevsync to true), but for me it ran at 120 fps out of the box. No problems. Only one crash when I was alt tabbed.
Dead by Daylight is a generally buggy game, so if you have issues it's unlikely it's tied to specifically Linux, lol
Runs well after changing to Vulkan rendering
Midway through rounds the FPS halves, then eventually slowly drops to 10-11, making it unplayable. Fixed by using Vulkan in the graphics settings.
Major lag during heavy team fights, but this might be the game's servers due to it being an alpha release rather than being a Proton problem.
The game boots with Direct3D rendering which runs fine at first, but midway through rounds I went from 180 fps to 60, then to 30, then to eventually <10. Extremely problematic for any game but especially this one. After changing to Vulkan rendering I have not seen this happen again in over 10 hours of play.
Played from start to finish and both DLCs, no crashes
Game doesn't automatically detect save files from Dragon Age: Origins to be imported - easily fixed by moving the save files from DA:O's steamapps/compatdata folder to Dragon Age II's. You can get the game IDs from SteamDB to find the right folder.
Finished without any problems
Save games importing to the DLC work fine. I didn't have any trouble with the game. From what I understand Proton automatically applies the 4gb patch for 32bit games to the exe so you don't need to go install it yourself. The game does slow down during long sessions but that's not a Proton issue, it's a known error the game has.
Works great, although I heavily recommend modding it
I couldn't get Frosty Mod Manager to work under Wine or Protontricks, but this modified build of it: https://www.nexusmods.com/masseffectandromeda/mods/1190?tab=description works great in Bottles. I heavily recommend modding the game for some QOL features that it sorely needed (faster movement speed, no looting animations, faster war table missions etc). Out of the box it was a fine experience though.
Modded a HUD scaling fix into the game for readable subtitles
When in a firefight and activating the slow motion ability, a "dust cloud" flickers on screen rapidly. Doesn't always happen. Seems to be tied to outdoor areas? I can't seem to reliably reproduce it, it just decides to happen. Other people reported this and also had a NVIDIA GPU. Might be an issue with Proton + NVIDIA drivers. It's absolutely still playable, just odd.
(EXTRACTION POINT REVIEW) Runs great! However, lock your FPS to 60 (for both EXP and FEAR)
It works fine, no issues noted after a full playthrough. A HUGE note about this and the original FEAR though, LOCK YOUR FPS TO 60. The game has no in-game framerate limit, so you either have to do this via Mangohud (which I could not get working on this game), or putting your refresh rate to 60, as the game seems to force V-Sync in my experience. if you don't do this, the game will "flash" colors and stretched textures in slow-mo and the ragdoll physics are a total mess. This is not Linux-specific, but I couldn't find any info about this on the internet, so I'll leave it here.
In the games control settings, you have to rebind the right mouse button.
You have to rebind the right mouse button, or else you (for some reason) cannot throw objects, and right clicking (blocking) will get you "stuck" in blocking and you can't interact with anything. Rebinding the "block" key (right mouse) to anything, including just right mouse again, will fix this. You have to do this everytime the game starts.
Flawless otherwise. Audio, saved games, fullscreening and no graphical errors or control issues aside from the one listed above.
Game is broken as of 1896 update, patch needed ASAP
Worked fine prior to the newest update released today, but now the game simply boots to a black screen for about 45 seconds with the cursor visible, then closes itself. Disappointing as I played dozens of hours on Linux with better performance than my Windows partition.
On some Linux systems, you cannot play multiplayer unless you join someone who's matchmaking IS working.
The game initally does not boot no matter what you do, and only gets to the main menu with bleeding-edge Proton Experimental. That works, I can modify and purchase characters, look at the battle pass, so on, but when I try to queue it tells me "region is not available". Then, it takes me to the settings to select a new region, and every server is listed as "N/Ams" under its latency. There is no way to connect to them.
However, if you join a friend who is able to play, you can queue. My friend (also on Linux, weirdly) is able to queue solo, and if I join him with him as the lobby leader, he can queue and I can connect and play.
So, you cannot play solo. You have to have a friend who's matchmaking is working. Hunt worked for me for the past 4 months before this, so I think this is an issue brought by the new update?
On night maps you'll get weird green/blue orbs at the top unless you put post-processing to low.
Game will play russian roulette and just randomly boot you back to the login screen sometimes after a round
Could not play without use of a script, details below
Forced Proton Experimental bleeding-edge will get the game past the boot screen and into the main menu, but I personally could not get a round. All regions said N/Ams. If I played with a friend, it worked, but I almost exclusively play this game solo, so that was a dealbreaker. I almost quit the game after 330 hours until someone linked me this Github script: https://github.com/V0LD3M0R7/HS-allow-ping
If you run into either all servers say 0 or N/A in place of your regular ping, this should solve it. All in all, I personally would not recommend picking the game up right now if you've never played it and wait until they patch the issues, but if you're a regular/veteran, it's not too hard to get working.
On the games default D3D9 renderer it stutters every couple seconds on a 3070. Using OpenGL from the settings makes it run flawlessly, but it breaks lighting on some maps. Pick your poison.
Native version wouldn't boot
Works fine, aside from EA's launcher
The game sometimes just doesn't open and you'll need to restart Steam. Seems to be related to EA launcher.
I've played to the end of Mass Effect 1 without any problems, but sometimes the game doesn't boot and I have to restart Steam in order for it to open. It says I'm in-game on Steam but nothing appears on my desktop and the EA launcher never shows up. Other than that I didn't have any problems. I will add additional reports for 2 and 3 once I play them.
Mass Effect 1 and 2 work flawlessly OOTB, no tinkering needed.
I've played both games, 1 to the end and 2 halfway through, no problems at all on either. The EA app sometimes doesn't start and you'll have to shut down the game from Steam, then re-open it, but that only happens rarely. Save games also work fine with the cloud, I had to uninstall the game temporarily for something else and I didn't even have to log back into the app when I reinstalled the game. Perfectly seamless.
Added a widescreen patch and a hex edit to make the game run on a modern Ryzen CPU, but these aren't Linux-specific tinkers, you'd have to do them on Windows
I saw other people post commands to lock the game to 60fps but these don't work for me. I've verified that Mangohud works fine on any other game on my system but it doesn't open with Max Payne, perhaps because it uses a launcher. In any case the game's physics work fine anyway even though it's running at 180fps. I didn't notice Max's jump distance being shorter. You can manually change your desktop refresh rate to 60 if you run into issues because this game forces V-Sync but it should be fine.
Flawless performance.
Runs well in multiplayer with someone who was on Linux and other users from cross-platform. No bugs, no crashes, runs well, ultra settings at 1080p, locked to 80 fps to keep temps cool. Very fun game, saved data from 3 years ago on Windows ran without issue as well.
Native and Proton both run fine, but to get the game working with Reshade requires some work
This game will run without issue on both the native port and under Proton - you do not need to do anything, the rest of this information is for if you want to use this Reshade script with this game: https://github.com/kevinlekiller/reshade-steam-proton, then you'll need to downgrade to Proton GE 8-7, boot the game once, exit and install Reshade 4.9.1 as it's the last version that works with Penumbra (there's a comment on how to in the documentation in that Github page), otherwise the game is completely broken. After installing you can switch back to new Proton versions without issue, but for me it broke without doing it in that order, for some reason. The start with the ship is fine, but outside in the snow is completely broken - the entire screen turns yellow, for some reason.
In Act 2 Part 3, the initial cutscene didn't have any dialog audio at first. Bizarrely, the rest of it (footsteps and SFX) was still there. When I restarted the mission, the dialog played correctly. Not sure if this was a Proton issue or just with the game.
The entire game functions fine. Some reports say the streamed cutscenes are awful quality but they ran fine at 1080p for me, but you do need good internet. You'll have to watch them on Youtube if you have a slow connection, because due to a 5head move from Remedy only the Windows Store version locally stores the cutscenes. From what I understand the live cutscenes only play with GE, so I just played the game with that. The in-game video player is awful and if you try to forward or reverse it bugs out, but I don't think that's a Proton issue. Overall it performs the same as native.
For modding, enable Proton to play the Windows version of the game
Most mods for this game will not run on Linux because they make use of Windows code/shaders(?). Not exactly sure why, but even though the Linux native port works without issue, you will probably want to use the Steam workshop. To do so, just enable Proton under the game settings and you'll be using the Windows version. All mods should now run fine. RavenM also works under Proton.
Totally messed up out of the box for me, likely due to having an 8gb NVIDIA card, but works fine after a bit of tinkering
SteamDeck=1 %command%
Shadows are totally borked and messed up on the default "high" settings, also listed a fix below
Game drops to 1 FPS on high settings upon loading into a level, I noted a fix below
Game warns that the Playstation SDK isn't installed at each launch, but boots anyway. Not sure how to fix it.
The shadows are completely broken out of the box on "high" settings - everything is super blocky. You have to disable ambient shadows under "shadow quality" (it's a drop-down menu and you can mess with each setting on its own, I did not realize this at first) if you have the same problem. I've only seen NVIDIA users report this. The game doesn't crash, but drops to 1fps and never goes back up on "high" settings to me once I load into a larger level as well. Setting texture quality to "medium" fixed this. I'm assuming it's a VRAM problem. A bit of a disappointing release for the devs saying that Steam Deck verified was a huge priority, but better than others nonetheless
Works well, just install TFix and optionally OpenAL binaries
If you enable Hardware Accelration without OpenAL, directional sound ceases to work
You need to install TFix to get the game to run well on modern hardware. I did this by giving Bottles permission to Steam's directory via Flatseal, then running TFix's installer inside of Bottles and pointing it to the game's directory in steamapps/common. Worked like a charm. I would recommend disabling all of the mods in the installer except for the candles and body carry if it's your first time through. Install the OpenAL binaries if you want EAX, but if you don't care about that then just turn hardware accelration off and the audio and directional audio will function as normal.
In the thief_2 folder, open the cam.ext file and scroll to "force windowed" and remove the ; behind it.
If you don't do the above configuration tinker, the game will launch to a black blank screen in the corner of your monitor
The game seems to be broken on startup and in order to get it to open you have to remove the comma behind force_windowed to get the game to boot in windowed mode. It will boot into 640x480 but if you install T2Fix via Bottles (give Bottles permission to the Steam directory via Flatseal) you'll have widescreen/modern resolutions available as an option in the video settings. Disable most of the mods when installing T2Fix if it's your first playthrough.
WINEDLLOVERRIDES="d3d9=n,b" %command%
Installed the widescreen patch
Using Shader Model 3.0 in the settings causes the game to take at least 10 seconds to tab back into if you tab out. Shader 1.0 doesn't have this issue and I don't really see a visual difference, so I just use 1.0.
If you force close the game via task manger or just the "stop" button on Steam, it reverts your settings back to 800x600. Only way to "save" your settings is by using the in-game exit button. Kinda annoying, but not gamebreaking.
Works wonderfully as long as you select Vulkan in the settings
If you run the game through DirectX (the default setting, at least for me) it will stutter massively and hitch on hordes. Frames will also drop. Switching to Vulkan fixes both of these problems and it ran at 120fps for me on high without dropping.
Native build doesn't open
Trying to start the game straight from the native version, it did not open on Mint 22. Steam says it's starting, then the launch button just reverts to "PLAY" and nothing appears. Forcing Proton on the game (which downloads the Windows version instead) allows it to open and play flawlessly.