Matoking
Published
Played for a few hours without any problems except shader compiling stutter, which only occurs once.
If your game is crashing, try disabling all mods first!
I had frequent crashing due to Workshop mods; one of the mods seems to have been responsible for the crashes, probably due to becoming broken by one of the game's updates. I started the game on Windows, so I initially thought Proton was to blame.
I tested Online Party briefly and didn't have any issues.
MANGOHUD_CONFIG=fps_limit=95 mangohud %command%
If the controller disconnected briefly the game would not re-detect it correctly. Using "Gamepad" in the launcher could fix this, but I didn't try.
The game has a bug where 100+ FPS will cause Somnium scenes to have graphical glitches. The bug also appears on Windows.
In either case, to fix it you'll have to cap the FPS below 100. In my case, I found MangoHUD to be the easiest option. Install it, then add the following under the launch options:
MANGOHUD_CONFIG=fps_limit=95 mangohud %command%
Completed all the episodes with no problems using the Vulkan renderer.
Completed the game without any issues using a DualShock 4 controller
Game launched with black screen, which was fixed with a single Protontricks command. Completed the game without any issues afterwards.
Black screen fixed using the following Protontricks command:
protontricks 674140 d3dcompiler_47
Completed the game and the two DLCs without any significant issues.
Adaptive sync was not always active when starting the game, requiring a restart
Completed the game without any problems aside from occasional stutter
Slight stutter when picking up weapons or killing enemies. Seems to be shader compilation stutter, although I'm not sure if it appears on Windows as well.
Gamepad didn't work out of the box and required a configuration change. As stated in another report: enter Big Picture mode, then Control Settings and disable all options except the one for generic controller support. After doing this and launching the game in normal mode (not Big Picture), my Dualshock 4 controller worked just fine.
After the controller tweak, the game worked perfectly from start to finish.
Proton-5.9-GE-3-ST
FMV cutscenes have a minor issue with a green line appearing at the bottom. No issues with in-game graphics.
Finished the game with no problems using GloriousEggroll's Proton build.
It's recommended to play using a controller instead of keyboard + mouse if possible; the game will randomly stop responding to KBD/M input for a few seconds randomly every half a hour or so. This is not a Linux-specific issue and occurs on Windows as well.
Audio in FMV cutscenes has crackling even with Experimental
FMV cutscene playback is still a mixed bag.
The first option is not to change anything, which results in crackling audio in cutscenes. It appears to be stable, though.
Another option is to transcode the WMV files to MP4, and then use a hex editor to change WMV and wmv strings to MP4 and mp4 respectively in dmc{1,2,3}.exe files (I used Bless for this, which appears to be available on Flathub as well). I used this FFmpeg command in the data/dmc{1,2,3} directories:
for FMV in *; do ffmpeg -i $FMV ${FMV:0:-4}.mp4; done
Note that this command does not flip the video vertically, unlike a different command someone posted before. This doesn't appear to be necessary anymore, though the WMV -> MP4 conversion is still necessary to solve crackling issues. However, while this makes the playback perfect when it works, it also introduced random crashes for several FMV cutscenes in DMC3, and caused a single mid-mission cutscene to crash consistently in Mission 15 in DMC3, making it necessary to revert this workaround in order to continue playing.
Other than that, I was able to complete both DMC and DMC3. I also played through a tiny bit of DMC2, though I didn't bother to play any more of that.
Completed the game without any major issues.
Minor lighting artifacts in some areas of the game. Fixed by disabling bloom.
Game has frame pacing issues when the game's FPS doesn't reach the monitor refresh rate, but those are related to the game engine and not Proton.
The game seems to run with no glitches compared to Windows, apart from decreased performance. On Linux the FPS usually hovers around 40-50 FPS, sometimes going as low as 30 FPS depending on the scene, while on Windows the game would stay around the capped frame rate of 60 FPS. The game is a walking simulator, so the lower performance may not be a deal breaker.
There's an optional mouse sensitivity fix on PC Gaming Wiki you can enable using Protontricks:
https://www.pcgamingwiki.com/wiki/F.E.A.R._2:_Project_Origin#Mouse_deadzone_and_sensitivity_problems
After you have launched the game at least once, download the fix and install it per instructions. After that, run the following Protontricks command:
$ protontricks 16450 winecfg
Select "Libraries", enter "x3daudio1_5" into the "New override for library" field and click "Add". Ensure the override is defined as "native, built-in". After this is done, launch the game and mouse sensitivity should now work properly.
The assault rifle's laser sight seems to disappear at random. I don't know if this is a Proton related issue or not.
Finished the game with 1440p + 144 Hz on keyboard and mouse with solid performance with no major issues.
Proton-GE is required for a background effect to render properly later in the game. It is subtle, so you may not notice it.
Up-to-date GPU drivers with stream output support required, otherwise the player character will be invisible. With that, the game worked perfectly and I was able to play the game all the way to the end.
Completed all three games without any major issues.
Aside from one cutscene playback issue in which the cutscene restarted once for some reason, I encountered no issues.
Playing without the Peacock Project server replacement caused the occasional "could not connect to server" error booting me back to main menu. This is probably due to Hitman's official servers having the occasional hiccup and was solved by running the aforementioned offline server replacement. They have Linux specific installation instructions which worked fine.
Completed the entire game without graphical glitches. Aside from the rare and minor issue of audio getting out of sync in cutscenes due to shader compilation stutter, there were no issues with the game.
The game is very demanding, and FPS usually hovered around 50-60 FPS with high settings with 1440p resolution. This seems to be similar to what you'd get on Windows, though.
Played the game using GE Proton. Other reports mentioned animated textures being missing or having placeholder textures; this is often due to missing video codec support in official Proton and is usually fixed by using GE Proton, which I configured from the get-go.
I didn't notice any missing textures or other issues when using GE Proton 7.25. I didn't test default Proton.
SteamDeck=1 %command%
Installed the custom Kingdom Hearts launcher mod by SandeMC which works without issues.
The game audio has slight background crackling at times. This is an issue with the game itself and occurs on Windows as well.
Alt+tabbing the game would sometimes result in the game remaining fullscreen but the game screen getting cropped slightly in the corners. Fixed by restarting. Unsure whether this is a Proton issue or a game issue.
Completed the Enhanced Edition without any problems with stable 144 FPS at 1440p.
Raytracing was not tested.
The game runs well on my Dualshock 4 controller (it even has correct button icons), the frame rate is good (stays at 60 FPS most of the time on 1440p and high settings) and there are no issues with graphics most of the time. The only issue is the occasional graphical bugs, where some of the characters' 3D models will start distorting, requiring the game to be restarted before stopping: https://steamuserimages-a.akamaihd.net/ugc/947341929947080143/6F0B48FB1B5942B65F2D059D547C46CDF7E45004/
I haven't seen this issue reported anywhere else, so it might be a regression in the latest upstream Mesa drivers, or an hardware issue (I hope not). Your mileage may vary.
Finished all five endings without any issues after applying the fixes. The game was stable at around 100 FPS at 1440p.
Proton-6.10-GE-1 GloriousEggroll
Used Proton-6.10-GE-1 to fix FMV playback.
Installed NieR Replicant High FPS fix from Nexus Mods: https://www.nexusmods.com/nierreplicant/mods/3
This allows the game to work properly above 60 FPS.
Does not work with the latest game version at the time of writing, so you'll need to downgrade. Until the mod is updated, you can use a Steam depot downloader to download the older game EXE and use it to replace the existing one.
Set Launch Options to WINEDLLOVERRIDES="dinput8=n,b" %command% to enable the high FPS mod.
If you're on AMD, you'll want to run echo "high" > /sys/class/drm/card0/device/power_dpm_force_performance_level as root (adjust card0 if necessary) to force the GPU to stay in performance mode. This nearly doubled my frame rate from around 50-60 to 100-110 FPS.
Run protontricks 1150690 winecfg. Select tab "Graphics" and uncheck "Allow the window manager to decorate the windows" and "Allow the window manager to control the windows".
This fixes the flickering taskbar when playing the game in full screen.
Taskbar would flicker in full screen mode unless window settings were disabled using winecfg.
Finished the game with a few minor issues.
The title sequence was not played after finishing the intro (about half an hour of gameplay). Fortunately, it's the only FMV in the game and you can look it up on YouTube.
Game seemed to stutter when controller was plugged in. I was playing using mouse + keyboard, so I solved the issue by simply unplugging the controller.
Completed the game without any issues aside from stutter, which mostly affected the first ~45 minutes of gameplay.
If you're running the game using an AMD GPU, I recommend installing a newer version of the Mesa driver with ACO if you don't have it.
If you have a recent version of Mesa with ACO support, change the launch options to "RADV_PERFTEST=aco %command%" to enable the ACO compiler, which will enable faster shader compilation and make the stuttering more bearable.
The game has occasional stutter due to shader compilation. This is especially noticeable during the prologue and its scene transitions, and the first half an hour or so of gameplay after the prologue. Thankfully, it happens only once and becomes a lot less severe afterwards, usually happening again when entering a new area or during cinematics.
Severity of the stutter may vary depending on the GPU vendor, driver version and the CPU.
The leaderboards for the Spirit Trial minigame don't display anything.
Having a fast CPU should also help by making shader compilation faster, regardless of the GPU vendor.
Played the game to completion with no problems using both DualShock 4 and mouse + keyboard.
Finished the game. After applying the configuration fix, the game played smoothly aside from infrequent stutter when traversing the map.
Per instructions in PC Gaming Wiki, open the file Pathologic_Data/boot.config in the game's installation directory and add/change these lines:
gfx-enable-native-gfx-jobs=1
gfx-enable-gfx-jobs=1
This increased FPS greatly and reduced the amount of stutter considerably. This change seems to help with performance regardless of the platform.
protontricks 1113000 wmp9 quartz devenum
Completed the entire game using a DualShock 4 controller. The game ran at a stable 144 FPS on a 1440p monitor.
Aside from the Protontricks command, no other adjustments were required.
Completed the first game without any issues and I don't expect the other two games will have any problems either.
Finished the game with 100% completion without major issues aside from the rare controller problem
Proton-GE seems necessary to run the game in D3D11 mode.
Controller disconnected twice during 20 hours of gameplay and wouldn't be recognized by the game again. This could only be fixed by restarting the game.
Add -force -dx11 to the game's Launch Options to enable D3D11 and improve performance. In one scenario I tested it improved FPS from 80-90 to 100-110 FPS.
Completed the entire game without any problems.
I used the default launch option (D3D11) instead of the secondary option to use D3D12. D3D12 also seems to work, although I only tested it very briefly.
Game runs well when using the 64-bit version; 32-bit version causes the game's environmental textures to go haywire. The only downside seems to be that achievements are no longer unlocked.
I played the game from start to end using the id5Tweaker mod to raise the game's FPS cap from 60 to 144. Aside from issues caused by the game's increased FPS cap, I didn't have any problems.
The id5Tweaker mod requires a DLL override to work. To enable the mod, open winecfg using the command protontricks 9200 winecfg, select the "Libraries" tab and add a DLL override for dinput8 (native, builtin). After this, the mod should work.
WINEDLLOVERRIDES="dstorage=d,dstoragecore=d" %command%
Noticed very infrequent (three times during my playthrough) and minor texture corruption issues. Unsure if these are related to the game, GPU drivers or Proton itself. They were not a problem, though.
Rift loading times were very short with a Samsung 980 Pro even without DirectStorage enabled.
Launch options were modified to ensure DirectStorage was disabled to enable higher graphics settings without crashing. This may not be necessary on an AMD GPU, however.
110+ hours of gameplay without any issues aside from an infrequent graphical glitch.
Ground would be covered in striped artifacts in certain places in the world. See the screenshot for an example:
I haven't found any other reports of this issue aside from the ones on ProtonDB, and I suspect it's a problem related to AMD's RADV drivers. Using AMDVLK drivers instead seemed to solve the issue, though I only tested them briefly.
-noprefetch -nointro
I had the occasional crash even after fixes, but this seems to be an issue with STALKER regardless of the platform.
Installed XpressTuning's Remaster mod pack. Since the game uses a 32-bit executable, the game - as well as some other games, especially when modded - will sometimes exceed the ~3.5 GB memory usage limitation for 32-bit applications when using HQ texture mods or when the game otherwise uses a lot of memory; this is exacerbated on Linux, since Proton has higher baseline memory usage than Windows. This results in frequent crashes or hangs, Fortunately, a workaround was recently implemented into DXVK and should be available in the official Proton release eventually.
For now, you can install the fix manually by downloading and installing a development DXVK build from the project's GitHub page here. Download the artifact, which should be a ZIP archive containing directories x32 and x64. Extract all files inside the x32 directory in the game's installation directory under bin; after you have done this, the directory should contain the existing game executable XR_3DA.exe as well as files such as d3d9.dll and dxgi.dll. Start the game and you should now be able to play the game with mods without frequent crashing.
Note that the DXVK fix I mentioned will probably be included in a newer version of Proton once that comes out, or another unofficial release such as GE-Proton. The newest official version at the time of writing is Proton 7.0 with DXVK 1.10, so if you have something newer, you might not need to do anything to use more memory hungry mods.
If you play vanilla without mods, you might not need to do any tweaking, though I didn't try.
Proton-6.16-GE-1 GloriousEggroll
Proton-6.16-GE-1 was required for an in-game video to play correctly.
Completed the game without any issues aside from the "white screen on startup" issue, which has an easy workaround.
Game starts in white screen. To fix this, switch between virtual desktops in your desktop environment twice; this should make the game visible in full screen. For example, with KDE Plasma you can enable two virtual desktops and then click the pager in the desktop menu bar to switch between them.
Enabling virtual desktop using Winetricks is not recommended. While it fixes the white screen issue, it causes lower performance and prevents FreeSync from working, making the game less enjoyable to play.
Finished the game without graphical glitches except for performance issues: the game would run most of the time at locked 60 FPS, but the performance would regularly drop dramatically. Steam's in-game FPS counter would still display 60 FPS, and the performance would switch from "stable 60 FPS" to "very low performance" seemingly at random without any middle ground.
Proton-GE is likely still required for FMV cutscenes; those appear later on in the game, though I didn't test the game using vanilla Proton.
Completed the first two games without any major issues, apart from two broken cutscenes in the second game.
Installed the mf-install fix ( https://github.com/z0z0z/mf-install ) to get the cutscenes working for the most part.
Most cutscenes worked flawlessly with the mf-install fix, but two cutscenes in the second game were skipped by the game: in those cases the game displayed a black screen for a moment before skipping to the gameplay.
To use Arise-SDK, set the following to the launch options in Steam after extracting the files as instructed:
WINEDLLOVERRIDES="xinput1_3,dsound=n,b" %command%
This should be all that's needed. Another guide also suggests using Protontricks to run a few commands and then deleting the prefix. That doesn't seem to make any sense, since deleting the prefix/compatdata directory should remove any changes aside from the launch options.
Completed the entire game with Proton from start to finish. Runs at stable 144 FPS at 1440p with all graphical options set to maximum except anti-aliasing.
No graphical issues as far as I can tell.
The game has a few minor issues: the game is finicky with the DualShock 4 controller: if you unplug it and plug it again during gameplay, it will act as if one of the buttons was stuck. There were also rare issues with audio playback (an ambient audio track seems to continue looping for longer when it shouldn't). These issues could also happen on Windows, but I haven't checked.
The game also has post-processing blur that looks ugly at times: the blur could be disabled with a 3rd party mod bundled with Special K. Unfortunately, that mod doesn't work with Proton.
Finished the game using Proton without any issues.
The native version had an issue with overlapping music, which wasn't present when running the Windows version using Proton.
Completed the game without any major issues.
Graphical settings do not persist after rebooting the system for some reason. In practice I had to dial down two settings after each launch to maintain a good frame rate; the game is very demanding graphically.
Installed the T2Fix patch. You'll want to do this even if you're not using Proton
Game would not always launch into full screen properly, causing the game to appear a bit stuttery, probably due to adaptive sync not working properly.
This was fixed by restarting the game after which there would be no issues for the remainder of the game session.
Installed the unofficial TFix patch
On rare occasions, fullscreen wouldn't work properly and cause stuttering until I restarted the game.
Performance is good and the game is rendered correctly without graphical glitches. The only problem seems to be the lack of audio in arcade games and the SEGA splash screen.
FMVs go gradually out of sync
FMVs have frequent artifacting
Installed "Yakuza 5 Licensed Music Video and Uncensor Restoration Patch". Finished the game mostly without issues, although prerendered cutscenes have annoying artifacting and audio sync issues. Haven't checked if the issues are related to the mod.
Completed the game without any problems using a DualShock 4 controller.
