TacoDeBoss
Published
This game starts and runs to the main menu OOTB, but both wined3d and DXVK will run out of memory and the game will crash during loading.
dxvk's d3d9.evictManagedOnUnlock = True option gets the game running with severe graphical issues making the game completely unplayable.
WINEDLLOVERRIDES="opengl32.dll=n,b" %command% +gl_twopassdyn 1
By default, lighting issues are observed, such as the flashlight not lighting many surfaces ingame. However, after some experiments, I found the command gl_twopassdyn 1 ingame which fixes all the lighting issues ingame without any performance hit or cumbersome DLL hacks, which weren't working for me anyway. The black screen issue has been fixed in Proton Experimental too, so all you need to do is force Proton Experimental and use the launch commands listed here to enjoy the game on your AMD GPU system. It has, of course, been working on Nvidia GPUs for some time without any commands or tweaks (aside from WINEDLLOVERRIDES launch command to load the custom renderer).
Performance seems slightly sluggish compared to Windows, expecially when using the radeonsi OpenGL driver, but research is ongoing. Performance may be improved with zink (add to launch command: MESA_LOADER_DRIVER_OVERRIDE=zink), but introduces new subtle graphical issues such as the player's hand model flickering while dual wielding. Personally, it's an acceptable compromise.
Works quite well. The Source engine utilizes d3d9 but runs well enough to keep even a consistent 144fps at 1080p at maximum settings. The only issue is the font kerning which is a known issue with Source games run under Wine. There is no known workaround. The font will be slightly less readable, but still legible.
Works only roughly initially. Must disable HDR and water reflections to avoid some graphical issues. There is, however, a black V.A.T.S error that persists even with those settings and I have not found a solution to this issue online or by myself. Restarting the game will solve the issue for 15 minutes or so.
Far Cry 2 is a game with many issues - even on Windows. You'll be stuck with running this game in d3d9 which means pretty dreadful performance. You'll have to drop some settings down to medium to get the framerate high enough to be playable. On the topic of framerate, this game has countless issues when going over 60 FPS. Add "-RenderProfile_MaxFps 60" to your launch options to force a 60 FPS lock. Ingame anti-aliasing results in broken alpha textures. Not usable. D3D10 does not appear to work in any way. Not usable. The game also crashes quite frequently. You'll almost never be able to use the buses due to crashing, and sometimes you'll crash out in the game world. Use the quick save, and use it often. Once you've done all this, the game should be playable enough. You can follow the Steam guide to get the Predecessor Tapes in the game if you want more content, too.
As close to perfect as currently possible. Very rarely are stutters and sound issues (music cutting out due to FAudio) - otherwise seemingly flawless. Framerate is just as good as in Windows.
This game runs perfectly on my system after updating DXVK by dragging updated DLLs into the game directory, and obtaining mfplat.dll from Windows 7 and placing that in the game directory too. I used the utility python-installcab on my proton prefix but some have reported this is not necessary. I have played for 34 hours with only 2 crashes as of writing. These crashes are not proton/linux exclusive, I've seen other people experience rare crashes on Windows as well.
Performance is great, but I have no comparison as I've never played it on Windows. The only issue I have discovered is that the mouse controls do not work properly by default. You could probably fix this, but it's abundantly clear this game is not made to be played on a keyboard and mouse either way, and I highly recommend against doing so.
Bad stutters on RDNA1, force amdgpu power_dpm_state for smooth performance
Tested on the specs listed. Was getting horrible stutters until I ran a few commands to force my card's clocks up.
echo performance > /sys/class/drm/card0/device/power_dpm_state
echo manual > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo 1 > /sys/class/drm/card0/device/pp_power_profile_mode
Just as other reporters said: Setting the prefix to ALSA sound, disabling the Real Tone cable, and disabling d3d11 are all necessary, along with the INI tweaks. I couldn't get the game to launch unless I installed it in ~/.steam/steam/steamapps and set the Z: drive to /home/user/.steam/steam/ If you prefer your games on a seperate drive, you're kinda screwed. Even moving the game and then symlinking to it results in a crash on startup on my end. The minor sound lag is still an issue. It depends on how you play - personally I can adjust to the lag after a few minutes if I have noise cancelling headphones.
