UnsupportedShow Details
Unknown
Using the 'Laptop' graphics preset and ProtonGE-9.27, performance is very good, 50-60fps at almost all times
Contrast between text and background on some main menu and pause menu options makes it hard to read, otherwise with UI scaling at maximum all other text is readable, although still a little small
One early area had floor textures popping in and out, have not experienced it anywhere else
With the aforementioned settings, the game runs very well, at medium settings it was closer to 30fps and character movement looked a little jittery so would recommend just using the lower setting and ProtonGE to get the higher frame rates
TDP 11 FPS 30 (60 Hz)
Some dialogues are cropped in Spanish language. Text are small also.
15 FPS with recommended proton. With 8-25 works well but FPS pacing is not good (this occurs in Windows also. It's a game engine problem)
Graphical options to medium. It gives you 40-50 FPS most of time but with bad FPS pacing. I prefer to use forced 30FPS with 60Hz.
Game ran poorly on ge-proton7, much stuttering and eventual horrendous stuttering. Was using laptop graphics mode, 11-30fps
Changed to GE-Proton8-25 and game runs 50-60fps on high settings. Works awesome with this version.
Black Screen if in fullscreen mode.
The only problem was to set fullscreen with my external monitor, just stay with audio and no video, had to use bordeless windowed. In Deck's screen works fine. GE-Proton8-4
Tried to play on Steam Deck, but It's unplayable (I assume due to graphic reasons). Everything just freezes and turn into slow-motion.
Some of the text is pretty small, but mostly readable.
Game sometimes crashes on exit.
It is possible to get the game to run at acceptable framerate by the combination of following:
- Forced Proton 6.3-8,
- VRAM expanded to 4GB in BIOS,
- swapfile expanded to 16GB,
- swappiness set to 30,
- graphic options in-game set to laptop or low preset.
Game don't look amazing, but it works. Eats through battery like it was pancakes, GPU is at constant 100% utilization.
CryoByte33 have on his github a script that you can run from a desktop mode, that will set your swapfile and swappiness to selected values. I read the script, nothing suspicious there (Oct 29. 2022). You can also see his youtube channel for guide on how to access BIOS and set VRAM.
Do not limit FPS in the in-game menu! Your frametimes will go crazy, jumping between 2 and 70 ms resulting in very choppy gameplay.
I first tried it on Proton 7.0-4 but performance was quite terrible during some battles. Downgraded to 6.3-8 at the recommendation of some people and it worked flawlessly.
Starting with older Proton versions lead to strechted grass and bushes textures, making the game not enjoyable. After switching to the latest Proton Experimental these artifacts were gone.
There some areas where the game stutters but this seems unrelated to Proton since it happens to W*n users, too.
After refunding th game after launch due to the texture stretching I am now happy that the issue is resovled with the latest Experimental version.
Lowest graphical settings, tried limiting refresh rate and frames to 40 using the deck's game settings panel.
Like many other games on deck, menu screen options are often blurry. There is a larger text option in the game's settings for cutscene/dialog text that worked fine while playing the game handheld.
I only played three levels - starting a brand-new game.. The first level felt sluggish (performance, not gameplay-wise), but playable. The second level felt slightly worse, but was still playble overall. The third level was practically unplayable in most sections. I believe it was due to the amount of fog in the game world. With all the game settings at their lowest possible amount, I couldn't actually finish that third mission.
Lowest graphical settings, tried limiting refresh rate and frames to 40 using the deck's game settings panel.
Like many other games on deck, menu screen options are often blurry. There is a larger text option in the game's settings for cutscene/dialog text that worked fine while playing the game handheld.
I only played three levels - starting a brand-new game.. The first level felt sluggish (performance, not gameplay-wise), but playable. The second level felt slightly worse, but was still playble overall. The third level was practically unplayable in most sections. I believe it was due to the amount of fog in the game world. With all the game settings at their lowest possible amount, I couldn't actually finish that third mission.
Grass patches are stretched 2-3 times every now and them, leading to some odd looking articaftc. A bit annoying but nothing serious.
Slight slowdowns every now and then. Was worse initially, switchign to 6-3.8 helped to keep it at a minium to the point of being barely noticeable.
Had a couple of crashes, not sure if proton-related or expected for the game. There are seems to be reports of stability issues on the steam forum even by windows players.
A game itself is known for having issues so not sure to what extent proton makes it worse. It feels a bit rough but wouldn't say there are any deal breakers when playing on proton.
Proton 7 causes stuttering. Older 6.3.8 version runs fine playing on ultra settings.
"Precise GPU Shadows" setting can cause sever crashes that require a hardware reboot when enabled with some gpus, mostly AMD Vega series.
With default graphics settings the game is completely unplayable on my hardware due to crashes 9/10 times a battle starts or cutscene plays. Disableing Precise GPU Shadows resolves crashing
Tinkering may not be required depending on what gpu you have, but disableing precise gpu shadows may be required for the game to be able to progress through the first non-tutorial mission
As long as GPU shadows is disabled the game is playable, it is completely unplayable on my hardware with GPU shadows enabled
This game seems to have frequent severe crashing issues (doesn't just crash the game, it managed to crash my whole desktop environment and blocked accessing a terminal so I had to do a full reboot) especially during cutscenes with AMD gpus, particularly Vega 56/64. Disabling "Precise GPU Shadows" in graphics settings seems to resolve the crashes
"Precise GPU Shadows" setting in graphics seems to cause crashes during cutscenes on AMD GPUs, especially Vega GPUs
Completely unplayable past the tutorial if you have the wrong combination of settings and hardware, make sure precise gpu shadows is off if you experience crashing
I suppose with a decent graphic card, the game can run without issue. Will wait to upgrade to 6600XT to confirm.
My GPU is a 760GTX. I was not even expecting to start playing. And yet, at medium and Low, it runs. But performance is very slow.
Bug on making a choice, the game wasn't responding after. After reload no problem.
I wasn't expecting to be able to play it after reading so many comments about the performance. But to be able to run it on a 760gtx tells something I suppose.
I tried default proton, GE-Proton 7-15, Experimental as well as changing in-game graphic options and runtime parameters like PROTON_NO_FSYNC, PROTON_NO_ESYNC, PROTON_HEAP_DELAY_FREE.
Sometimes patches of grass are streched across the screen (texture tearing), obscuring the game.
Framerate take a strong dip when grass or fog are present in the scene. There is a lot of grass and fog in this game.
the graphical glitches are so big I switched to play it on Windows
really big artifacts basically like grass coming out to cover the entire screen in weird shapes
Open winecfg (tested with wine v6.2-1) go to libraries and add the following DLLS: "d3dcompiler_47", "d3dx11_43", "CRYPTSP"
minor missing textures
I used experimental_5.13
User RossBC describes quite well the requirements that are needed. But since the game is in an EA stage and requirements can drastically change from patch to patch, I decided to provide some additional help for people that may find other issues that prevent them from starting the game.
So after installing the game, from Steam open the game's properties and add the following launcher options:
LD_PRELOAD= PROTON_LOG=1 %command%
Run the game for the first time and let it create the wine prefix. Once that is done the game will exit with an error (unless future versions of protondb fix this).
Search for errors (seel below)
$> grep -i 'err' ~/steam-1157390.log
..:err:module:import_dll Library CRYPTSP.dll (...) not found
..:err:module:import_dll Library d3dcompiler_47.dll (...) not found
..:err:module:import_dll Loading library d3dx11_43.dll (...) failed (error c000007b).
..:err:module:import_dll Library CRYPTSP.dll (...) not found
..:err:module:import_dll Library D3DCOMPILER_47.dll (...) not found
From the above we see that we only have errors due to missing DLLs.
To install the missing DLLs you need to start winecfg that uses the prefix that the game is using.
The prefix does not change and will have the same number for almost all steam users (unless you have explicitly changed the paths that steam uses to install games and compatibility tools)
To start winecfg:
- First open winetricks:
WINEPREFIX=~/.steam/steam/steamapps/compatdata/1157390/pfx/ winetricks - From the winetricks window select
Select the default wineprefix - Next select Run winecfg
- From winecfg select the Libraries Tab
- In the New overried for library box type
CRYPTSPand select the ADD button - Install the remaining missing DLLs by following the step from above for each dll:
d3dcompiler_47,d3dx11_43
Finally you can close the winecfg window and switch back to steam and start the game.
(Reported experimental version: experimental_5.13)
Open winecfg (v6.2-1) go to libraries and add the following DLLS: "d3dcompiler_47", "d3dx11_43", "CRYPTSP"
The initial report made by RossBC works well. But since the game is in EA and many thigns can change and additional requriements can be added, I am adding this for people that may find other issues that prevent them from starting the game in order to help them find a solution easier rather than waiting for someone with the same issue to report a solution.
After installing the game
- Open properties and add the following launcher options: LD_PRELOAD= PROTON_LOG=1 %command%
- Run the game for the first and let it create the wine prefix. Once that is done the game will exit with an error
- Under home directory you will find the following log file: ~/steam-1157390.log
- Check for module errors (seel below)
$> grep -i 'err' ~/steam-1157390.log
315284.398:00d0:00d4:err:module:import_dll Library CRYPTSP.dll (...) not found
315284.398:00d0:00d4:err:module:import_dll Library d3dcompiler_47.dll (...) not found
315284.398:00d0:00d4:err:module:import_dll Loading library d3dx11_43.dll (...) failed (error c000007b).
315284.455:00d0:00d4:err:module:import_dll Library CRYPTSP.dll (...) not found
315284.455:00d0:00d4:err:module:import_dll Library D3DCOMPILER_47.dll (...) not found
From the above we see that we only have errors due to missing DLLs.
To install the DLLs you need to start winecfg first. To do that
- First open winetricks:
WINEPREFIX=~/.steam/steam/steamapps/compatdata/1157390/pfx/ winetricks - Next select "Select the default wineprefix"
- Next select "Run winecfg"
- From winecfg select "Libraries" Tab (follow the next section below)
To install the required DLLs:
- In the "New overried for library" first type "CRYPTSP" and select the "ADD" button
- Install the remaining missing DLLs by following the step from above for each dll: "d3dcompiler_47", "d3dx11_43"
Finally you can close the "winecfg" window and switch back to steam and start the game.
Installed D3Dcompiler_47 with winetricks Manually downloaded cryptsp.dll, then put it into the games executable folder. Used winecfg to dll override cryptsp.dll to native.
Some pixel tearing, it may have been a driver issue though, after upgrading to 460.39 barely happened anymore.
Given that it is early access, the game does have issues accross all platforms so it is hard to say what problems are proton related or EA related.
Game shows in log files that it is using dx11 not dx12.
added D3DCompiler_47 with winetricks. Manually added cryptsp.dll to the games executable folder. (manually Downloaded) Set cryptsp.dll to be used as native with winecfg
Strange tearing while rotating camera during the third fight.
logs show the game using dx11
(Reported experimental version: proton-experimental)
Installed D3DCompiler_47 with winetricks Manually downloaded cryptsp.dll and put it in the games executable folder Used winecfg to add cryptsp.dll and set to native.
In the 3rd fight it had some weird texture tearing, hard to describe. only happend while rotating the camera.
No work arounds were required to run video. logs said it was using dx11.
