Shadowfly
Published
gamemoderun %command% -nologo
DS4v2 Controller was not detected. Fixed by Mod
Game was fixed at 90FPS. I eddited the config for 120.
- Game crashes every 30-50 minutes, even if you just sit with the game paused.
- Sometimes (About 20% of the time) the game did not close. I had to kill it by finding it's id in top and killing it with kill .
Really good game, can be played mostly hitch-free thanks to shader pre-compilation.
Unfortunately the game crashes too often to be enjoyed by te average gamer, but if you are ok with crashes every 30 minutes, it's a great game.
gamemoderun %command% -nostartupmovies
- Hitching (propably shader compilation) when entering a new level: Fixed by looking in all directions
- Enabling PhysX reduced the framerate from 100FPS to 20FPS.
In the first 5 hours of the game, crashes happened about every 45 minutes. After about 5 hours in game, there was not even one more crash.
After playing a few hours i thought i would rate this not enjoyable, as there were somewhat frequent crashes. But after that, the game ran great.
My modifications:
- (DualShock 4 Button promts)[https://www.nexusmods.com/batmanarkhamorigins/mods/164/] (highly recommended)
- Downsampling (only for high-end GPUs): xrandr --output DisplayPort-0 --scale 2 && gamemoderun %command% -nostartupmovies && xrandr --output DisplayPort-0 --scale 1
gamemoderun mangohud %command% -oldgameui
I downloaded the native version, and started playing. The first levels worked great, but more and more artifacts showed up over time. First my lamp glitched, then transparent objects, and in 'The Office' level, the lighting failed completely and i was stuck in the dark.
So i uninstalled the game, Right click on game -> Settings -> Compatibility -> Force -> Proton 7.0-3.
I installed the game again, and even the save files were carried over.
Unfortunately the main menu was gone. Fixed by assing -oldui to launch arguments.
Played until the end in Proton. No more Glitches.
Tldr: Force proton with -oldui
Worked right out of the box. Played for only 15min, as i already played trough it on Windows
When i clicked "New Game", the screen turned white. After a few seconds i pressed "X" on my DS4-Controller, and the game began to load the first level. I don't know if this is the way it should be.
Just like native
Had two crashes during my playtrough, which is not more (or less than) on Windows. Performance is pretty bad (in relation to the graphics), just like on Windows.
Crashes while game is trying to switch backgrounds in main menu.
Works using Proton 5.13-6. Good performance and awesome gameplay. Videos not playing ruin the immersion in some scenes.
Many in-game videos and video-textures showed just a white screen and the according audio. This ruins some epic moments.
Heavy stuttering during first attacks and in some scenes due to shader-compilation.
If the videos would play, it could be recommended to the average gamer. Modern versions of Proton did not work for me.
Broken since last update
Memory leak: RAM fills within seconds of launching the game. Game is playable with only minor freezes until swap is full, then the system freezes.
I played this game for a few hours already, and everything worked fine. Then a new update came, and now there is a memory leak that fills the RAM within seconds and allows for maybe 20 minutes of gameplay until my oversized 128GB swap is filled.
I tried default Proton, Experimental and Proton GE. Nothing worked so far.
- I did not notice any artefacts in the main game until I saw the credits. They were flickering, and sometimes vanished for a few seconds. This persisted until the credits were over.
- Just like in DS1, the game created tear-lines. Here they were frozen in place, not moving like in DS1. I fixed this by enabling triple buffering in xrandr.
When starting the game, sometimes the controller would not be detected. Pressing any key on the keyboard as soon as the Dark Souls title was shown in game made the screen freeze for a few seconds. After the freeze the controller was fine and usable.
Dark Souls II itself ran smooth (4K@60) all the time (DS1 had a few stutters here and there). I did never notice any slowness or dropped frames, but the DLCs were not that smooth. They make use of quite some alpha-effects (snow/fog) which sometimes lower the framerate in the 45fps area. Luckily this was no issue during boss fights.
I made a full play-trough including the DLCs, not including optional bosses. After about half of my play-trough the servers were shut down due to a remote code execution vulnerability being found in the client. So I did not get the full multiplayer experience. The servers have not come back as of today.
gamemoderun %command%
After i first started the game, locking onto enemies filled my screen with images of swords and eastern letters (might have been japanese). This made fighting a bit more difficult. After i made it into the first major city and rebooted my PC, the issue never returned.
On rare instances my controller would not be detected after starting the game. Clicking my mouse in the main menu once made my screen freeze for a second. After that my controler was detected.
- In some areas in later parts of the game there is a lot of transparency effects going on, and in these areas the performance is not as great as one could expect (4K@~50fps for my setup).
- Every time the game was saving, the game had about a 30% chance of freezing for ~0.5s. This was especially bothering when i took a item from the ground, and the game just froze. This issue was not present for me with Proton 6.3-8, but the performance in the areas mentioned above was so much better with Proton 7, that i did not downgrade again.
- For users with AMD GPU: My GPU switched constantly between power saving (500MHz) and performance (2500MHz). This causes inconsistent performance in all areas of the game. I used CoreCtrl with the global GPU-profile set to Fixed->High to eliminate this issue.
During my entire playtrough i could not connect to the servers once, as the servers were shut down by the developers after a remote code execution vulnerability was found in all Dark Souls games. This is not Linux specific. It also affects Windows.
I do not think the average gamer would enjoy this game on linux, because it shocks the player right in the beginning with a screen filled with swords and strange writing. After that, it runs great for a while, until you reach some areas where the performance is far worse than what you would expect given the hardware. If you can accept to lower the resolution in some areas (or accept lower fps), you should have no further issues.
Despite having Vsync on in the settings, the game created tear-lines that crawled slowly over the screen. I fixed this by enabling tripple buffering in xrandr.
In some areas the game felt a little bit stuttery despite having 60fps. The frametimes were uneven in these areas. Nothing that bothered me to much.
The game was sometimes stuck in a few seconds of black screen while starting. Waiting resolved the issue.
Laggy and Crashy
After Alt-Tabing out, the game blackscreened
- Low FPS when moving mouse over escape-menu
- Somewhat high input lag in game
Crashing while loading a new level about every 30mins (Vulkan)
Runs out of the box but has problems that distract from the experience
Crackling occurred every few seconds and 'PULSE_LATENCY_MSEC=60' did not help.
The game ran at only 4K@80fps, despite having nearly nothing in view except the ground and a few stones.
Every few seconds there was a stutter.
At one point framerate fell to 45fps. Disabling Vsync got it to 80fps.
Runs out of the box
The game ran at only 4K@80fps, despite having nearly nothing in view except the ground and a few stones.
At one point framerate fell to 45fps. Disabling Vsync got it to 80fps.
I had stuttering and audio crackling trough my playtrough, but as the stutters and crackling persisted in another game, i realized that my PC was the problem. After a reboot there is no more audio crackling or stuttering.
DXVK_ASYNC=1 gamemoderun %command%
Minor artifacts caused by DXVK_ASYNC
I started the game with Proton selected by Steam and got severe stuttering right from the start. Therefore i followed the advice of others here, and enabled DXVK_ASYNC. Unfortunately i did not know that this only works with Proton-GE. As it had no effect for me , i "disabled" DXVK_ASYNC again and played (almost) the entire game with default Proton and no DXVK_ASYNC.
The severe stuttering (mostly) subsides after you have driven for half an hour or so through one area, but as soon as you enter a new area (or update Mesa), the stuttering returns. Also large settlements (camps) were prone to stuttering.
I had already decided to give a "not recommended" rating here, but then i learned that DXVK_ASYNC only works with Proton-GE. :(
When i used Proton-GE and DXVK_ASYNC=1, suddenly (almost) all stuttering was eliminated. Rides on the countryside were now (almost) fully smoth, and the camps had only minor and infrequent hitches. This way, the game plays incredibly.
I also tested the game on windows, and learned that windows suffers from the same stuttering the default Proton suffers from, even though to a lesser extend.
ProtonGE with DXVK_ASYNC >> Windows > Proton
CPU-Limited scene: Linux 62fps, Windows 51fps (+21%)
Mixed scene: Linux 77 fps, Windows 65fps (+18%)
GPU-Limited scene 1: Linux 79 fps (CPU limited), Windows 90 fps (-12%)
GPU-Limited scene 2: Linux 78 fps (CPU limited), Windows 88 fps (-11%)
TL;DR Use Proton-GE and enable DXVK_ASYNC to get a smooth and consistent experience better than Windows. Use Windows for raw performance with severe hitching.
- The game was limited to 60FPS, even when i disabled VSync.
- I experienced high input-lag.
Dead Space runs really well on modern hardware. I had 0 issues during my playtrough, but installing Origin was definitely not as easy as installing games on Steam.
My modifications:
- Mouse fix to get rid of mouse acceleration
- Downsampling (5120x2880 -> 2560x1440) by running 'xrandr --output DisplayPort-0 --scale 2' in the console
Works out of the box with noticable stutters
I played the complete game and experienced some stuttering, but nothing that bothered me too much. If you want to eliminate stuttering, you should set DXVK_ASYNC=1 in the Steam launch options with Proton_GE as Proton version.
Mission Accomplished (>80h)
Played until the official ending (and beyond). Default Proton. No glitches or crashes.
gamemoderun mangohud %command%
A few times my controller was not detected.
Sometimes when the game saves, the game freezes for ~100ms. This happened to me on Dark Souls 3 too, but in Elden Ring the freeze seems shorter.
- About 20% of the time i tried to launch the game, the Easy Anti Chat window would show, but the game would not start. Restarting Steam did not work. Logging in and out of Linux did not work. Only rebooting worked.
- The game crashed once in my 101h playtrough
The game runs almost without issues, while the frametimes seem more stable than on Windows. Unfortunately the game runs still poorly when comapred to other games. You will need a high-end Ryzen 2000 for 4K60. Not to speak of 120+FPS. For me (1440p) it was mostly 50FPS, but there were dips into the 35FPS range.
DXVK_ASYNC=1 gamemoderun %command% -d3d11
- Frequent hitches (Presumably shader compilation): I swiched the game to dx11 mode and installed ProtonGE in combination with activating DXVK-Async to get much fewer hitches.
- Bad framepacing (rare): I had really bad framepacing like once every 10h of gameplay. Restarting the game fixed this.
The game is out of the box in a acceptable state, but by spending like 20 more minutes installing ProtonGE, activating DXVK-Async and forcing dx11, the experience can be greatly improved.
If you have a fast GPU, and you dislike the blurry image and heavy ghosting TAA produces in this game, you should really downgrade the game to v1.001 and deactivate TAA, then replace it with downsampling. The game is >50h long, so it's worth the hassle.
gamemoderun %command%
Running the game at max settings 2560x1440@~120fps.
gamemoderun mangohud %command%
Sometimes when switching between rooms the entire screen shows only fog. No other 3d objects. Happens on Windows too. After like 3 Seconds the level returns.
I got a decent FPS boost (110 -> 160) by switching VSync on and off, and by adjusting the in game FPS limit.
I had 0 crashes so far. Played only on Linux.
gamemoderun mangohud %command%
I started playing the game using the Proton version selected by Steam, and there were no artifacts.
After about 15h of playtime, some update lead to objects flickering for a few seconds after they were loaded or switched LOD. I manually selected Proton 7.0_1, and it worked for a few hours until the flickering returned.
Then i switched to Proton-GE, and played through the remaining game without issues or artifacts.
Initially the game ran great with automatically selected Proton, but issues occurred over time. I recommend Proton-GE.
Degraded but enjoyable
Videos displayed the test screen and did not play
I did not try ProtonGE, so a few videos did not play for me. I recommend using ProtonGE because the videos are quite atmospheric, and may contain story.
But even without them the game was great to play.
If you have a fast GPU, you can use downsampling to get rid of more Aliasing. Set the following launch options:
xrandr --output DisplayPort-0 --scale 2 && %command% && xrandr --output DisplayPort-0 --scale 1
Then select the highest resolution In-Game (5120x2880@~80FPS for my PC).
gamemoderun mangohud %command%
Horrific frametimes: Frametimes spike by ~4x every 1-2 seconds. Especially during traversal.
The game runs perfectly fine - except for the horrific frametimes that get triggered as soon as you move. Especially inside Hogwards Castle. I don't know if it's that broken on Windows, but if you enjoy smooth framerates: Stay away.
gamemoderun %command%
The frametime graph looked like a saw blade when i loaded into the first level. Switching VSync on in the game menu fixed this.
Sometimes the game would not close properly. Steam would still detect it as running and i would need to press 'Stop' in Steam to end the game.
I played the Enhanced Edition. I did not test Ray Tracing. As long as you play with VSync, you should be fine. For my hardware the performance was about 4K80fps at max settings (GPU limited).
Awesome game with poor performance. While the performance is far from enjoyable, it is still better than on Windows (at least for me)
6.10-GE-1 GloriousEggroll
I used Proton 6.10-GE-1
I also used PlayStation Button Replacer
I had poor performance (about 44fps on Linux, 32fps on Windows) in almost all levels of the game. Small levels consisting out of one simple room and my characters ran at about 50fps. Only when all walking animations of my character and all NPCs were complete, i got solid 60fps until i moved my character again. GPU usage was low at all times.
Nice game with poor performance and a problematic save system
Missing cut-scene at beginning and at the end of the game.
Game is separated into Levels which contain multiple checkpoints at certain points in space. Checkpoints are activated by passing trough them. Loading these checkpoints worked, but i could not move around, just look around. Fixed by reverting progress to beginning of chapter in the ''Esc'-menu. Lost like 1h of progress this way.
Some levels had poor performance (about 45fps). I don't know how it would run on Windows.
Please exit the game only after you have reached the FIRST CHECKPOINT within the next LEVEL (new level is indicated by loading screen, checkpoint is indicated by symbol in right corner of screen), otherwise you will loose your progress.
(Almost) perfect
Adaptive Triggers did not work during 2 play sessions. Restarting the game/PC would have most likely fixed the problem.
One time the game refused to close. I force closed it with Steam and some progress (~5mins) was lost.
Low FPS (~30) in Levels with water/transparency effects (Manaan,...)
The game likes to crash. Especially when loading new levels.
I played trough the game with the following mods installed:
- Kotor Community Patch
- UniWS
- Bodies Stray
- Security Spikes Fix
- KotOR 1 Remastered
- Selphadur's Kotor Texture Redux
- Complete Character Overhaul -REDUX- (Ultimate HD Pack)
- Better Skyboxes
Whenever a new Level is loaded (which is often), there is something like a 20% chance of the game crashing. Therefore saving before each door is necessary.
I kept a modded and a unmodded version of the game, beacause sometimes (about once per hour) the modded version of the game was unable to load a level, so i deleted the modded version (except the saves), and replaced the files with the vanilla version. This trick got me trough all doors.
Sometimes it was the other way around: The unmodded version would crash, but the modded version would not.
TL;DR: The game is fully playable but only with mods, crashes and a lot of patience. So the average gamer would propably be really annoyed, even though most of the crashes are presumably the games fault.
gamemoderun mangohud %command% -dx11
- Starting problems: The game did not want to start on many occasions. Killing the process and restarting the game usually fixed the problem.
- Memory Problems: One time the game did not start. Insted it filled my RAM with countless epiconlineservice.exe processes, until i stopped it at 27GB RAM used.
- Crashes: During several boss battles the game crashed. Retrying did not help. Downgrading to Proton 7 did help.
gamemoderun %command%
The main menu had about 30FPS and horrible frametimes. Did not affect the game itself.
Runs incredible
Runs without tweaks, without hitches and at amazing performance.
If you have a high-end GPU and a 1440p (or lower) display, you can enable downsampling by setting
'xrandr --output DisplayPort-0 --scale 2 && gamemoderun mangohud %command% && xrandr --output DisplayPort-0 --scale 1'
as launch arguments.
This assumes you use DisplayPort and do not have a second monitor switched on.
For me it ran at 2560x1440x2@60 (5120x2880) and with less than 40% GPU load.
I installed the game using GE-Proton8-16, then switched to normal Proton.
- FPS: Initially there were no performance issues, but after some mining and ship-building the performance got worse and worse. In the end i had less than 1/7th the performance of what i should have had.
- Loading times: The loading takes like 5 times longer on Linux. The larger the alterations of the level, the longer it takes.
- Streaming problems: Structures, Spaceships and altered terrain load much slower on Linux. When running a server on my Linux PC, bombing the ground only created holes for some time. Then (i presume some buffer was full) and destruiction was no longer possible. So running a multiplayer server on Linux is basically impossible.
I played online. Initially, as the server was fresh, i could join the server without issues. But the more altered the landscape became, the more often the game would crash while loading. In the end i had a 25% chance of joining the server, and a 75% chance of crashing while loading. I then alleviated this somewhat by getting the savegame of the server, and loading this savegame locally before joining the server (Start game -> Load server savegame in singleplayer -> Exit to main menu -> Join server). This increased my likeliehood of sucess to like 80%.
Tldr: Do not run a multiplayer server on Linux. Even as a client expect low performance <20FPS with High-End CPU and crashes while loading.
Sadly it seems that Steam does not pre-compile the shaders of this game, so i experienced shader compilation stutters while walking around. Fixed by telling the game to compile shaders while loading
I played with a DS4v2 controller. Occasionally the game was really slow in detecting changes in my controller sticks orientation when i tried to pan the camera around.
With the shader compilation fixed (and a really fast GPU), the game runs soft as a kitten. Unfortunately the controller input was laggy for me, but the gameplay is really slow so i barely noticed it.
gamemoderun %command%
You can start the game just the way it is, and get a native-like experience already. But because the game is so long (>40h) i recommend switching to dx11 in-game for ~+10% more FPS and less stuttering.
gamemoderun mangohud %command%
In the cementary the bushes were glowing strangely. Looked a bit distracting, but could also be intended by the developers of the game.
Directly after loading a level the game hitched sometimes for a quarter of a second. Not really a problem but slightly distracting.
The performance of this game is awsome on linux. Therefore you might want to use downsampling if you have a high-end GPU:
- run 'xrandr' in the console and note how xrandr calls your display. For me it is 'DisplayPort-0'
- use the following arguments for steam: 'xrandr --output DisplayPort-0 --scale 2 && gamemoderun mangohud %command% && xrandr --output DisplayPort-0 --scale 1'. Replace DisplayPort-0 by what you noted before and adjust --scale 2 to your hardware. You can do 1.25, 1.5, 1.75 or 2.
6.12-GE-1 GloriousEggroll
I used Proton 6.12-GE-1.
I used mf-install and fixed the cutscenes as recommended by AwesamLinux.
Please note you need the program xxd to run the script to fix the cutscenes. For this i needed to install the vim package.
Could not get my DS4 working with the game. I tried disabling Steam Input and using ds4drv --hidraw, but it did not work for me.
I followed the instructions of AwesamLinux, and once it was all done, it ran flawlessly. Unfortunately i think that is too much work to do for the average gamer. Also the Quick Time Events are brutal when played with the keyboard (Controller did not work for me).
Broken.
Tried Proton Experimental and Proton GE.
The game installs. After launching, it opens a small message:
Title: Themedia
An Error has occurred while loading imports. Wrong DLL present.
I tried default Proton, Proton Experimental and Proton GE.
The developers/publishers logo did not show the first few launches. After a few launches it was shown. Does not impact gameplay in any way.
Slow but playable
In some scenes CPU limited to 1440p@40fps or 720p@45fps at max settings for no apparent reason.
Reproducable crashes with dx12. No crashes with dx11.
While the game itself runs flawless, there are severe performance problems. If the game were something different than a really slow walking simulator, i would have considered it unplayable.
Sometimes just having a mirror in view cuts the framerate in half. Only play if you have extreme single core performance (Ryzen 3000 or better), and are ok with <50FPS.
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command%
After installation, the game did not want to launch, so i set the launch options to launch the game directly:
bash -c 'exec "${@/2KLauncher\/LauncherPatcher.exe/TheQuarry.exe}"' -- %command%
The game worked for a few days, then it refused to start. So i removed all launch options and started the game trough the launcher.
Apart from the startup issues everything else ran well.
Cute game running flawlessly
I played the main story, and started the DLC, but i have not completed the DLC yet. So far i had zero issues with the game. There was no tinkering needed in any way.
As the game is highly minimalistic, it uses almost no resources. If you want to improve the image quality a little bit, you can enable downsamplig by adding the arguments "xrandr --output DisplayPort-0 --scale 2 && gamemoderun %command% && xrandr --output DisplayPort-0 --scale 1" in steam.
If you don't have your display connected via DisplayPort, run xrandr in the console to find out how your display is named.
Example output:
Screen 0: minimum 320 x 200, current 2560 x 1440, maximum 16384 x 16384
DisplayPort-0 connected primary 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
2560x1440 59.95+ 29.94*
gamemoderun mangohud %command%
Artifacts were common: Small black boxes flickered around objects, lines shot across the screen and sometimes mostly transparent artifacts filled almost the entire screen. Distracting but not game breaking.
- When my DS4 (Bluetooth) controller ran out of battery, the game froze.
- Sometimes there was a high ~200ms input lag.
- Sometimes a small amount of movement on the stick would jank the camera around.
- The deadzones were too large. My steam-settings were ignored. I resorted to Gyro-Aim over Steam.
Sometimes the game was CPU limited ( low GPU usage) to 2560x1440@~100FPS, wich is strange considering how fast my CPU is and how little happens in the game.
- Unchared 4: The game crashed 3 times. Everytime in a cut scene. Luckily there are a lot of checkpoints, and no progress was lost here.
- Lost Legacy: The game crashed in about 4 locations, in gameplay and in cut scenes. Reloading lead to a immediate crash. Water was always involved. Fixed by either toggeling on the in-game 30FPS lock or by temporarily locking the game to 45FPS until the water shader was out of sight.
- Switching between Uncharted 4 and Lost Legacy crashed the game.
The game in it self is really good and worth playing. Even on Windows there are occasional crashes, but if the average player were to play this on Linux, they would put all the blame on Linux and switch back to windows.
If you are a experienced Linux gamer, know how to set FPS limits in MangoHUD and are OK with occasional artifacts, you can play both games on Linux and have fun. I recommend using the Gyro for aiming, as the deadzones are unreasonably large in this game.
As a Linux newcomer, you should stay away from this game. It requires manual intervention and a lot of restarting of the game.
6.14-GE-2 GloriousEggroll
Flickering of glowing particle 'snow' on Deimos
Game may crash when using Alt-Tab while game is loading
Controller (DS4) input was registered twice per input. Fix by disabling Steam Input and using 'ds4drv --hidraw' to emulate controller
Stuttering in first minutes of gameplay due to shader compilation
Crashes frequently when using Alt+Tab while loading. Otherwise i had only 2 crashes in 230h of gameplay.
Lutris-ge-6.21-1x86_64 GloriousEggroll
I tried the following versions of Proton:
- Proton 6.21-GE-2: Stuttering despite having high FPS, High input lag, Controller (DS4) was registered as a mouse. Adjusting controller sensitivity in game settings did not work for me. Adjusting mouse sensitivity in game settings worked for mouse and controller sticks.
- Proton 6.3-8, Proton Experimental: Controller registered as mouse (as above).
I tried the following versions of Wine:
- Lutris-ge-6.21-1x86_64 (Esync + Fsync): Much more stuttering while compiling shaders. Input lag and controller issues resolved.
Using ‘ds4drv --hidraw’ to emulate controller
Crash reporter may show up. Just ignore it.
Since my last report, the New War update was published. Since this update Proton 6.14-GE-2 no longer worked for me.
For mouse + keyboard players: Try Steam with Proton 6.3-8 or Proton Experimental. They both run great for me.
For controller players: Proton did not work for me. The controller had a crazy high sensitivity, and turning it down in the settings did nothing for me. Turning down mouse sensitivity in the game settings worked, but created other issues (unable to switch back to mouse, as sensitivity is too low. Railjack did not work with controller.). If you play with controller, switch to Lutris with Lutris-ge-6.21-1x86_64. Use ds4drv --hidraw for emulating DXInput. This will fix all the controller issues, but lead to a bit more stuttering for shader compilation.
I can still recommend this game to the average gamer if he uses mouse and keyboard.
Duviri Paradox: Plays out of the box, but slowly corrupts itself.
After playing the game for some time, the game started to show the crash reporter at startup. It seems the game is corrupting itself very slowly. Therefore i recommend regular cleaning and reinstalling.
