Appelsin
Published
Doesn't work OOTB, but if one can get over doing the protontricks config, the game runs fine :)
Added the following launch commands:
PROTON_NO_ESYNC=1 PROTON_USE_D9VK=1 %command%
Instal Protontricks (flathub).
Add protontricks alias to .bashrc:
echo "alias protontricks='flatpak run com.github.Matoking.protontricks'" >> ~/.bashrc
Run the following commands for protontricks:
protontricks 35140 mdx d3dx9 d3dcompiler_43 win10
Dualshock4 works, but button prompts are for Xbox. I used this mod to get proper DS4 prompts.
Instal Protontricks (flathub).
Add protontricks alias to .bashrc:
echo "alias protontricks='flatpak run com.github.Matoking.protontricks'" >> ~/.bashrc
Run the following commands for protontricks:
protontricks 35140 mdx d3dx9 d3dcompiler_43 win10
I encountered a bug(?) that makes the process hang on the last command (win10?), where the terminal informed me that the "This will hang until all wine processes in prefix (path) terminates." I have no idea what to do about that, but I think this sovled it:
protontricks --no-background-wineserver 35140 mdx d3dx9 d3dcompiler_43 win10
At least the process finished when the --no-background-wineserver flag was invoked. YMMW.
I had to switch to Proton 6.3-8 to run it. Anything else will just get you the BM launcher, and pressing Play will crash the game. On Expermiental and Proton 7, I had 1-20 FPS. Glorious Eggroll was same, with 1-20 FPS. I.e. unplayable, as others have reported.
Using the abovementioned Protontricks, it runs smoothly, with no issues other than a periodical crash to desktop (ofc. when least convenient). But that problem was present in Arkham City and Origins too, so some extent. There's some screen tearing, but that may be on my end. I've also disabled Vsync due to significant input lag when enabled.
To conclude: Protontrick + Proton 6.3-8 will have the game running, provided you can get past the Protontricks eternal-hang-bug.
Dualshock4 works perfetcly, but will need a mod to get proper DS4 button promts.
Runs like a charm OOTB
Occasionally audio would crackle, but only during the transition from cut-screnes/scripted interactions to giving you control of the charater. This occured at the same time as the aforementioned stuttering in graphics would occur.
Sometimes there's a bit of stutter, but mostly during cut-scenes. Nothing that impacts gameplay.
Crashed with "fatal error" every few hours. Just press OK and restart the game.
Gamepad works perfect, though only with XBox button prompts (no DS4 buttons).
Additional settings can be tweaked using the guide below, e.g. remove intro ads and force-set 60 FPS minimum. Other reports here have good suggestions for which tweaks to set.
Runs perfectly OOTB, except for CTD after about 2-3 hours playtime.
CTD after about 2 hours ingame.
Runs like a charm ootb. Been playing mostly with a DS4. KB&M works as it should. No issues other than a CTD after playing beyond 2 hours. Annoying, especially if you're in a boss fight on harder difficulties (not me though), but usually it just means that I should get on to do something more usefull than playing video games.
Played through several levels (back to finish Achievements). Installs, launches and runs perfectly out of the box, at highest settings. No graphical or audio issues at all.
Installs and runs like a charm OOTB
Played through all the DLCs using Proton. It runs completely smooth without any issues. It's been some years since I played the main game on Windows, but I'd say it runs just as good under Proton as it did under Windows.
Add the following launch options to Turn off logging, and Enable D9VK rendering:
DXVK_LOG_LEVEL=none PROTON_USE_D9VK=1 %command%
At the time I was playing it, it was said you could get a bit better performance by setting the following launch option in Steam:
DXVK_LOG_LEVEL=none PROTON_USE_D9VK=1 %command%
This will turn off logging and Enable D9VK rendering.
Installs, but does not run/launch/start
Unable to start the game. According to other report you can get it to run by applying a crack to work around some DRM, but I've been unable to get this to work (I probably didn't find the right one?). Though tbh you should not be required to use potentially harmful executables to launch a game you've paid for.
Does not start/launch
Apparently because DRM. I tried applying some Skidrow HMA.exe, but that did not help. I've tried several versions of Proton, without success.
I'm very disappointed that the only socalled "fix" for a game I PAID FOR is to run around adding potentially harmful executables to my computer / games.
Also, Steam Support does not care. They sell a game that does not work, and doesn't take any responsibility for it. I was denied a refund, and I was told to contact the publisher/developer (which points you back to Steam Support).
So, in conclusion, Square Enix and IO Interactive have stolen this game from me, and everyone else that are unable to launch it, since I/we have paid for it but are denied from playing it because they don't give as flying donky about their DRM literally blocking you from launching and playing the game. Valve apparently does not care that they are enabling and profiting off a literal scam product (you paid for a game, but were given only a thumbnail image in your Steam Library) /rant
Given my (by now) fairly ancient hardware, I should think most recent PC builds would have no issue running it. Haven't played for long yet, so cannot attest to long-term stability, but the initial installing, launching and playing of the game showed no signs of issues.
Runs alsmot perfect OOTB. Only thing not working is in-game videos
In-game videos not playing (videos on ingame PC and TV in the ship).
Played with Dualshock 4 controller. Works like a charm through Steam, but in-game layout is locked to XBox. Everything works so far, except ingame video (ads on the TV and video messages from HQ). Runs pretty great on High, considering my ancient hardware.
Runs like a charm OOTB.
Runs OOTB. Audio works as it should, as far as I can tell. Audio-based game, so that's the important part. Haven't tried with gamepad yet, but keyboard input works as it should.
