Xeloses
Published
Works perfect out of the box.
Works perfect out of the box on the Proton 7.0-1
Works good out of the box.
Completed full game (native, no proton) on Linux, didn't encountered any issues.
Works good out of the box. Completed the game from chapter 1 to chapter 5 without any problems or crashes.
Works perfect out of the box.
Completed full game (no DLC) on Linux, didn't encountered any issues.
Video/cutscenes works well, no crashes, Alt+Tab worked ok.
Works good out of the box.
Completed full game on Linux, didn't encountered any issues.
Works good out of the box.
Alt-Tab works well, but the game continues to handle the mouse cursor even in background. It makes other apps/windows inaccessible while the game running. But apps/windows on the second desktop are still accessible, so desktop switching can be used instead of Alt-Tab
Completed full game on Linux, didn't encountered any issues.
Works good out of the box.
Completed whole game on Linux, didn't encountered any issues.
Works good out of the box.
Completed full game on linux.
Encountered only one issue: opening and ending videos played upside-down.
Works good out of the box.
Completed the game (single route) on Linux, didn't encountered any issues.
Works very good out of the box. Perfomance is much better than in Windows.
Important: use x64 version (x86 version crashes every 2-4h.)
Works good out of the box.
Make sure to enable the "Quicksave" option in game setting to prevent crashes after combat encounters.
Perfomance is much better than in Windows.
Completed whole game in Linux, encountered only 1 bug in the chapter 2, but according to game discussions in Steam it's not a Linux-related bug.
Works good out of the box.
Completed whole game on Linux, didn't encountered any issues.
Works good out of the box.
Completed full game (with 2 DLC) on Linux, didn't encountered any issues.
Works good out of the box.
Completed full game on Linux, didn't encountered any issues.
Played in window mode, Alt+Tab worked well. Didn't tried fullscreen mode.
PROTON_USE_D9VK=1 %command%
Edit "KidEngine.ini" as described here: pcgamingwiki.com (method 3)
Game crashes after 1 or 2 missions without an INI-file tweak.
~
The best config I've found for myself is D9VK + Proton Experimental, the game never crashes with this setup.
Works good out of the box.
Completed the game on Linux (single route), didn't encountered any issues.
Loading screens without textures (but loading is very fast, so it's not a big problem). No images in the tutorial, but text explanation in the tutorial is enough.
To play game add this string:eval $(echo "%command%" | sed "s|Launcher\/Mirror2.ProjectX.Launcher.exe|ProjectX\/Mirror2\/Binaries\/Win64\/Mirror2_X-Win64-Shipping.exe|")
to the game launch parameters in the game options dialogue.
Doesn't play MPEG video on the loading screens (but loading is fast even on SATA HDD, so it's not a big problem). Doesn't show images/video in the tutorial, but text explanation in the tutorial is enough.
To bypass game launcher and start the game directly - open game properties dialogue in Steam and add the string below to the launch options input box:
eval $(echo "%command%" | sed "s|Launcher\/Mirror2.ProjectX.Launcher.exe|ProjectX\/Mirror2\/Binaries\/Win64\/Mirror2_X-Win64-Shipping.exe|")
For better perfomance use Proton Experimental.
Use Proton GE to fix video playback in game.
Works good out of the box.
Completed full game (used DX10/11 version) and DLC on Linux, didn't encountered any issues.
gamemoderun WINE_FULLSCREEN_FSR=1 %command%
Very low FPS with game version installed by default (~15 fps in the Linux, while in the Windows game shows ~50fps).
By default Steam install the "Ray-tracing" version of the game. For the better perfomance (and FPS) install "non Ray-tracing" version: open game properties in the Steam → Beta-version → select "dx11_non-rt" in the dropdown list.
Works good out of the box.
May have FPS drop on the scripted encounters.
Works good out of the box.
Completed whole game and survival mode on Linux, didn't encountered any issues or crashes.
I didn't tried import save file from Banner Saga 1.
Works perfect out of the box.
Completed full game on Linux, didn't encountered any issues.
WINE_FULLSCREEN_FSR=1 gamemoderun %command%
Multiplayer in Warframe hosted on PC of the squad leader, so lags depends on his/her connection speed.
Important: on the first launch let Steam fully compile shaders (it may take a long time).
Ingame settings:
→ Window mode: borderless
→ VSync: disable
→ FPS limit: 30
→ Mouse/aim sensitivity: reduce (default is 50, I set it to 10 for comfortable playing, may depends on the mouse dpi).
Tried maximum session 6 hours in a row, has no issues.
Sometimes game can crash on leaving large areas (like Plains of Eidolon).
Overall perfomance is much better than in Windows!
Game works good out of the box.
- Vanilla game (without «War of the Chosen» DLC) works good with or without mods (native, no Proton; completed the full game on Linux, didn't encountered any issues).
- «War of the Chosen» DLC works well without mods (native, no Proton; I didn't tested it much because mods make the game much better; completed some missions, was no issues).
- To play «War of the Chosen» DLC with mods you should use a custom game launcher under Proton. I used «Alternative Mod Launcher» (AML): github.com/X2CommunityCore/xcom2-launcher. To run the game with this launcher:
- Force using Proton (in Steam open game properties dialogue, select "Compatibility" and click the checkbox, also you can select Proton version; for me Proton Experimental worked better than Proton 7.0).
- Open game installation directory (in Steam open game properties dialogue, select "Local files" and click "Explore" or "Open"). Create a new directory inside the game installation directory for the launcher (for example, create a subdirectory «AML», so fullpath to it will be
<steam-library-path>/steamapps/common/XCOM 2/AML/). - Download the archive with alt. launcher from GitHub and extract all files from it to the newly created directory (the «AML» directory in the example).
- In Steam open game properties dialogue and add this string to the launch options input box (if you used another name for the launcher installation directory - change «AML» to your directory name):
eval $(echo "%command%" | sed "s|2KLauncher\/LauncherPatcher.exe|AML\/XCOM2 Launcher.exe|") - If you encounter crashes on cutscenes in the Windows version of the game (under Proton) try one of the following methods (or a combination of them; I've used pulse latency customization + borderless mode, completed full game with this setup and 74 mods, all work perfectly):
- switch to the borderless or windowed mode (ingame options → Video);
- add launch parameter
PULSE_LATENCY_MSEC=50(adjust latency (50) according to your hardware); - switch to Proton Experimental;
- force use DirectX 9 (add launch option
PROTON_USE_D9VK=1).
PROTON_USE_WINED3D11=1 %command%
Use PROTON_USE_WINED3D11 to prevent screen flickering.
Completed whole game on Linux, didn't encountered any issues.
