Cy
Published
Works okay out of the box. Can be tinkered with to work better.
In orbital camera wings movement momentarily leaves artifacts on water effects shader.
Either play controller or disconnect it entirely and play with kb+mouse. Switching between them is buggy. The game's at fault, not Linux.
When loading dusk/dawn resources there's a stutter. Sometimes there's a frame drop that can't be explained but I suspect it'd happen on Windows as well because I play in 4K on high settings.
I played Primitive Plus which (for whatever reason) loads all of the vanilla content just to replace about half of it with what comes in DLC. It consistently took about 40 minutes to start the game and connect to the server on ext4 HDD. It took about 30 minutes on ext4 SSD. When I switched to btrfs it took about 20 minutes. It's still a very, very long wait on the loading screen. But again, it's the game's fault - works the same on Windows.
Game installs Battleye Proton runtime and runs with it perfectly on official servers.
Freezes on creating new player.
It freezes about 5 seconds into character customization screen. I found in the discussions it used to freeze for people in online mode but switching to offline mode doesn't help.
Works flawlessly out of the box.
No tinkering. If you play on Steam Controller, beware:
- the button glyphs are incorrectly from PS controller in the menus, but it doesn't happen in-game,
- switch the right touchpad in Steam overlay from "Aim Joystick" to just "Aim", because that 1st one is relative and feels weird.
Assuming the launcher crash gets fixed or if you've agreed to EULA in the past, you can enjoy the game no issues. Otherwise it won't start.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 PROTON_NO_ESYNC=1 DXVK_FRAME_RATE=90 gamemoderun %command% -world=empty -noLogs -enableHT -hugepages -noLauncher
The game is old and can't utilize modern hardware properly. FPS drop to low values on both Linux and Windows. This can be mended some with mods (e.g. one that automatically lowers view distance to keep constant FPS).
I was lucky. When I installed the game 1st time the launcher complained about Steam not being online and refused to update or run the game, however, after changing Proton to GE it worked okay and I was able to accept the EULA. I think accepting the license is required and the game won't start without it. The day after, there was a small update and now launcher crashes after few seconds (however, it's possible it only happens on AMD) - I wouldn't be able to accept EULA again. Assuming you've accepted EULA in the past and it's saved in your Arma 3 profile somewhere, you'll be able to skip the launcher entirely using -noLauncher flag.
I wasn't banned yet so I assume BattleEye works fine on Linux now.
Launcher issues are the only ones I've encountered but if you find a way to set EULA as accepted by e.g. modifying some files, then it's redundant - everything you set up in the launcher can be set up either in-game or with flags. There are 2 downfalls of starting Arma without the launcher, though:
- after enabling mods in extensions menu the game will restart itself (takes some time)
- when connecting to servers using mods that you're missing, the launcher has an option to subscribe to all dependencies, however, the in-game server browser doesn't (at least I didn't find one) so you have to figure out all the dependencies and manually subscribe to each of them in the Steam Workshop
Some tips to get better performance:
- to avoid loading of the animated background in the game menu use
-world=emptyflag (quicker start) - disable in-game vertical sync and instead use
DXVK_FRAME_RATEenvironmet variable (less stutter) - if you have a slow drive, disable logs with
-noLogsflag (less stutter) - if you have 16+ GB of RAM use
-hugepagesflag (less frequent memory allocation, less stutter) - some people swear by
-malloc=system(default?) or-malloc=tbb4malloc_bi(for Intel but there are AMD CPU users claiming it helps), I fail to see the difference - try with and without
-enableHT, it might improve or damage your fps depending on CPU and driver (more max fps) - mods that automatically restrict view distance but keep vehicles visible at all times (less fps drops)
In my case the mod didn't show its variables in game settings. To get it configured I had to run the game editor, start empty VR level, then open the debug console (~ tilde) and set up variables with the following commands:
profileNameSpace setVariable ["AVDVAR_fpsTarget", 60];
profileNameSpace setVariable ["AVDVAR_minViewDist", 600];
profileNameSpace setVariable ["AVDVAR_maxViewDist", 6000];
Your multiplayer name will be `steamuser` by default (because this is the default user account name in Proton environment). You can click on the torso icon in the upper right screen corner and add a new profile there - change your name, appearance, voice, etc. The game runs last selected profile by default. You can also use `-name=yourNameHere` flag to pre-select an existing profile or create one on start if it doesn't exist.
You need to set up the prefix and run wine cmd.exe /C gencfg.bat "%CD%" in game directory to generate the missing BADMOJO.INI file but even after that it crashes immediately after a split second of black screen and there's a segfault printed to STDERR when run from the terminal. Tried BADMOJO.EXE, launcher.exe and launcher2.bat - none start the game but STDERR outputs differ slightly.
Installs but doesn't start.
Some Black windows flicker, one with message "Troubles? Look at comments in launcher.bat", then crash. Comments in launcher2.bat are irrelevant. Error:
wine: Unhandled page fault on read access to 00000000 at address 00000000 (thread 0110), starting debugger...
That memory addres looks incorrect. I tried several versions of Proton: default, experimental and GE-7.33, as well as usual environment variables, nothing works.
xrandr --output DP-1 --mode 640x480; %command%; xrandr --output DP-1 --mode 3840x2160
The game runs in a small 640x480 area of the screen.
Opening the save/load dialogue takes the game out of full-screen. I didn't find a way to focus it back. So even though the game loads the saved state properly, you cannot continue playing.
Unfortunately, BadMojo doesn't support modern resolutions - even though it claims to be "Redux". The only way to stretch it to full-screen is to match the system resolution. The above launch option does it automatically.
You might need to replace DP-1 with your output name. Check xrandr in terminal. Typical outputs are HDMI-0, DP-1, DisplayPort-2, etc.
If you prefer the game to run in a small area in the centre of your screen instead, you can achieve that by omitting launcher.exe and calling BADMOJO.EXE directly:
eval $(echo "%command%" | sed 's#launcher.exe#BADMOJO.EXE#')
The fact the game runs at all is a testament to Wine development. A year ago, it wouldn't even start - nowadays, it can be actually beaten. If you find a way to scale the game up instead of changing the system resolution, or to continue playing after loading a save, please, report back here.
Install the game, try to run it once (it'll install some stuff) then stop it, open the terminal and run the following line:
protontricks 35140 d3dx9 d3dx9_43 d3dcompiler_43
Wait for it to finish and that's it - run the game again and this tme it'll work, the launcher will start after a few seconds.
If you want FSR, special DXVK behaviours or GameMode daemon to govern your CPU, you'll need to force those in launch options but none of this is really necessary to run the game:
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 DXVK_ASYNC=1 gamemoderun %command%
Nvidia users can add physx at the end of that protontricks line, just beware, after installing all DirectX dependencies Protontricks will download and run PhysX installation which can't be automated so if it takes a long time and you don't see the installer window, try to alt+tab or look for it on another screen.
For some reason the official Steam Play run script installs wrong version of DirectX dependencies. If someone at Valve could fix that it'd work out of the box.
eval gamemoderun $(echo "%command%" | sed 's/Chivalry2Launcher.exe/TBL\/Binaries\/Win64\/Chivalry2-Win64-Shipping.exe/')
The result of the command that you need to paste into the launch options is just a path to the game executable instead of the game launcher. That's it. No magic. Explanations of every part of that command below:
eval- everything after this is evaluated before running the command, it has to be for $() to workgamemoderun- if you don't have Gamemoded installed, remove this, if you do, leave it, also any environment variables you'd want to use, e.g. to enable FSR or trigger DXVK async, goes betweenevalandgamemoderun$(command)- runs command in a subshell and outputs the resultecho- everything between this and | is being outputed as a string%command%- Steam replaces this on runtime with a path to Chivalry2Launcher.exe, however, for some reason the launcher doesn't run with Wine (or Proton) so we substitute that part of the path to skip the launcher entirely and point directly to the game executable instead|- a pipe connecting output streams between programs, it passes the output of echo "%command%" to sedsed- a stream editor, it takes output of another program and modifies its#foo#bar#- a sed command to substitute foo with bar, I'm using # as separator to avoid escaping every / in the path
Ignore older reports, including mine. Launcher is required now and works fine with current Proton - doing the old workaround will trigger Easy Anti Cheat, preventing you from playing and possibly getting you banned.
Game doesn't start at all. Neither native version nor Proton.
It seems to be borked since 2017.
Works flawlessly out of the box.
So a chameleon, an imp, and a penguin walk into a bar...
When I tried it on default Proton version cinematics didn't play. They played fine when I force-used Glorious Eggroll's spin-off of Proton (I had the newest one already installed, I'm guessing using Valve's experimental Proton would work as well).
gamemoderun %command%
Fullscreen renders game with 0fps (1 frame per ~20 seconds)
I worked around the fullscreen issue by forcing windowed mode, i.e. I'm on i3wm so this helped:
# windowed 4K minus 1 pixel on every border (otherwise i3wm redners full-screen any way)
for_window [class="steam_app_803330"] floating enable, border none, resize set 3838 2158, move position 1 1
The game still starts in fullscreen so after running it I have to press a system shortcut to switch it to windowed, then switch to a different desktop, then switch back to the game.
Final note is that since the game runs in windowed mode there's no way to utilise FSR.
DXVK_FRAME_RATE=120 obs-gamecapture gamemoderun %command%
Must do:
Deus Ex: GOTY must be installed (or you get a “Core” package error).
Select Direct3D 9 (it actually runs Vulkan thanks to DXVK; OpenGL was never finished)
Select ALAudioSubsystem (Galaxy crashes on certain sounds)
Optional stuff:
“Settings > HDTP Options” - character models are vanilla by default, can enable HD
“Settings > Sound > Soundtrack” can be set to “Deus Ex” for vanilla
“Settings > Display > UI Scaling” is set to “HiDPI” in 4K, but “Relaxed” or “Dynamic” are bigger
“Settings > Sound > Hardware 3D Support” and “Dolby Surround Sound” can't be enabled (it's not OpenAL, it's ALAudio v2.4.7 — fake EAX for Windows; but you can overwrite
Deus Ex/Revision/Systemwith newer v2.4.8 for better reverb)FPS drops on old hardware? Use GPU scaling: for desktop in 1080p set the game to 720p full-screen and:
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 %command%
Works flawlessly out of the box.
Would a typical gamer enjoy it, though...? I didn't. Played with Steam Controllerset to mimic keyboard (WSAD).
Works flawlessly out of the box.
Played in on-line multiplayer on Steam Controller, no issues.
Game stops at 0% of the "Preparing Planet Generation System" step
I tried different Proton versions and command line arguments but nothing worked so far. It used to play without issues on Nvidia 1070 and 16GB of ram in 2021. I'm very unhappy it doesn't run now.
If any of you encountered something like "This account doesn't own Elite Dangerous" it's because you have old cache files from before the launcher update. You need to completely uninstall the game, close Steam, remove all files and directories containing 359320 in their name under ~/.steam (you will loose your configs, I think) and then start Steam again and install the game. It'll start the launcher with "Login with Steam" button this time.
I've encountered 2 issues that most people won't unless they're coming back to game after some time or tinker with their GPU drivers.
if you don't see "Login with Steam" button, remove the prefix and restart Steam:
rm -rf ~/.local/share/Steam/steamapps/compatdata/359320if the game freezes on 0% of "PREPARING PLANET GENERATION SYSTEM", uninstall AMD proprietary drivers:
yay -Rs vulkan-amdgpu-pro lib32-vulkan-amdgpu-pro # on arch or sudo apt remove vulkan-amdgpu-pro vulkan-amdgpu-pro:i386 # on debian
After this it should work fine.
Works flawlessly out of the box.
It does work great out of the box, however, it is a very old game (sorry to people in their 30s). It was rushed to the shelves and it shows. To improve it, either install the community patch called Fallout Fixt, or even better, install Fallout 2 and a community patch letting you play Fallout in Fallout 2 engine - you can do it in 3 easy steps:
How to install Fallout Et Tu
I. Put everything in correct paths:
- install both games (Fallout & Fallout 2) via Steam
- download Fallout Et Tu, extract somewhere, cut the
Fallout1in2directory - Steam: right-click Fallout 2 > "Manage" > "Browse local files" and paste-in the
Fallout1in2directory
II. Extract data from Fallout 1:
- Steam: right-click Fallout > "Properties" and paste the following in launch options:
cd "../Fallout 2/Fallout1in2"; eval $(echo "%command%" | sed 's#Fallout/FalloutLauncher.exe#Fallout 2/Fallout1in2/undat.exe#') - Steam: run Fallout 1 (it'll open
undat.exewindow instead) - paste the following path into the 1st input field (replace
deckwith your username if you aren't on Steam Deck):Z:\home\deck\.local\share\Steam\steamapps\common\Fallout\MASTER.DAT - click the EXPORT button, wait until done, close window
III. Make Steam run Fallout Et Tu instead of Fallout 1:
- Steam: right-click Fallout > "Properties" and paste the following in launch options:
cd "../Fallout 2/Fallout1in2"; eval WINEDLLOVERRIDES="ddraw=n,b" $(echo "%command%" | sed 's#Fallout/FalloutLauncher.exe#Fallout 2/Fallout1in2/Fallout2.exe#') - Steam: start Fallout 1 (it'll run Fallout Et Tu)
Enjoy!
3 initial crushes, then runs fine
During the first run there are some shaders compiling so it takes longer (maybe a minute), subsequent launches are quick.
Game crashes 3 times:
- after run
- after logging in to GOG launcher and starting Gwent
- after in-game login
Then it starts right away, goes straight to game (no GOG launcher showing) and works flawlessly without any further crashes.
Works almost flawlessly out of the box.
One crash during a whole walkthrough.
On-line multiplayer with a friend, we both used gamepads (Steam Controller and Xbox's one), finished the game. One random crash on my side mid-way through (I was the host). No other issues.
Doesn't go pass the splash screen
From Proton logs: Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x00c0426f). 003d:fixme:dbghelp:elf_search_auxv can't find symbol in module
Needs both d3dcompiler*.dll files linked or copied from Win64Shared to Win64 in game directory, other than that runs perfectly well, 1080p on very high usually keeps around 60-70 fps but sometimes visibly stutters and drops to 30-ish for a second while loading stuff.
After game update 2018-10-31 you need to link all DLL files from Win64Shared to Win64. Other than that, works perfectly fine. GTX1070 runs 1080p high between 40-60 fps v-synced.
PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_USE_WINED3D=1 gamemoderun %command%
The game needs all 3 environment variables (to launch, and for cutscenes to work). No other issues. Finished it with Steam Controller. Man, Larry's nephew's head is huge!
Works flawlessly out of the box.
Beware it uses ScummVM underneath, so read other comments for key binds to handle full-screen, scaling, etc. You can also install Luxtorpeda (alternative to Proton for specific old games) and set up those things beforehand.
Works flawlessly out of the box.
It uses ScummVM under the hood, so read other reports for key bindings regarding full-screen, scaling, etc. Either that, or use Luxtorpeda (Proton alternative for some old games) and set those things up beforehand.
Works flawlessly out of the box.
Finished the game with no issues.
If you mess up Steam settings preventing it from using the preferred version of Proton (i.e. the one provided by the per-game install script), then you'll have to force an older version of Proton in game properties. If you didn't mess with Steam settings, the game will run without any tinkering.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 gamemoderun %command%
The game runs after tweaks but freezes in the menu (freezing might be specific to my system).
Run the game once to create the wineprefix (it'll fail), then remove 42910_install.vdf in the game directory (otherwise it'll try to install some of the dependencies and fail each time). Run protontricks 42910 dotnet35sp1 xna31 to install all dependencies manually (when the installer asks about XNA select "repair"). It'll run afterwards. For me it freezes after about 2 minutes in the menu but it might be due to my custom browser not handling some privacy notice I'm not able to read or skip.
Loading the level and exiting game takes about 3-5 minutes without any progressbar.
Works out of the box
It works either way, natively or with Proton. I haven't noticed any benefit of running it with Proton, though, it actually runs a bit better natively. You can expect slowdowns when there are many thorn shooting larva enemies in the room but it's unrelated to Linux or Proton.
Works flawlessly out of the box.
By default, Steam installs the preferred version of Proton for any given game, especially old ones (it has a per-game install script). If you went to Steam > Settings > Compatibility and overloaded the default Proton version for unsupported titles with e.g. newest GE, it will use that instead. Meaning, you'll sometimes have to force an older version of Proton in game properties. Don't tinker with it, and most old games will continue to run out of the box for years to come.
Works flawlessly out of the box
Do not tinker with it. When Steam installs a well known Windows game on Linux, it usually has a script that selects the preferred version of Proton. You can override it in game properties, sure, but in this case - just don't. If you do, and it's too new, there will be issues. Steam comes with Proton builds as old as 3.7, and that's for a reason. Don't be blindly switching to a newer one and then complaining something doesn't work.
Game doesn't support Xinput on Linux. To play with controller set walking as X in game settings and use my Steam Controller config (other community mappings are Windows only): steam://controllerconfig/35000/1613175559
Works out of the box except videos (black screen, no codec, just skip them)
There are no players online but if you have a friend you can race just fine.
Controllers with analogue triggers highly recommended (for breaks and throttle).
The game works out of the box and it's fully playable. The only issue is a black screen that shows from time to time instead of a video but you can just skip them with Enter (or A on the controller). I tried Proton GE and Experimental but videos still don't play - must be a proprietary codec.
Works out of the box, and it's one of my fav games to date!
Fully playable single- and multiplayer. VR works fine. HOTAS works great.
If you don't have friends but want a multiplayer adventure, search for Pulsar server on Discord and post in #looking-for-game or #schedule-play in advance. You'll have someone to play with in 10–20 minutes.
Native version is a 1-click plug-and-play experience. I pulled in at least 8 other Linux users, and the only issue we found was a minor weirdness with mouse scrolling speed on 1 machine. We fixed it by editing settings.xml in the game's directory and bumping the <ScrollwheelSensitivity/> value to 10 (the in-game GUI lets you go up to 5).
We even got mods working. It's as simple as switching to Mono branch (right click on game in Steam > Properties… > Betas > Mono branch) and running the Pulsar Mod Loader downloaded off Discord (it supports Linux, it's open source, what's not to love).
Not a Linux thing (happens on Windows as well), but the in-game voice comm servers are finicky. On a bad day, your game just won't connect no matter what, even when other players hear each other. Discord is a fine alternative. If you really want to use the in-game VC, there's a mod called “Advanced VC settings” that usually mends the issue.
In Proton, it works as well as native, but beware switching from native to Proton (or vice versa) will remove your local saves.
Steam Controller won't work no matter what - no proper xinput support. You need to set it up as keyboard (effectively loosing all comfort of the analogue input so you might just play with the keyboard as well) and disable controller for all players in game settings. Other than that it seems to work flawlessly. No issues 6 hours in.
No way to play, EAC or not.
You can find no-EAC servers in Steam client by going to "View -> Servers" and selecting "Anti-cheat: Not secure" in filters. One try takes about 30 minutes including starting the game. However, even then after connecting, "warming up" all the assets, railing monuments and so on the game crashes to desktop. There are 4-6 players online almost all the time on Deadlock server but they play on Windows.
WINE_FULLSCREEN_FSR=1 WINE_FULLSCREEN_FSR_STRENGTH=1 %command%
The only non-EAC server I found is Deadlock Dweebs.
With GE-Proton8-3 and game intsalled:
- run the game
- wait ~5 min to load menu
- press F1, type "
connect play.deadlock.com:1333", press Enter - wait ~20m to preload stuff
- enjoy!
I use FSR upscaling for higher FPS but it's not necessary if you have a good GPU.
Played with Steam Controller, no issues, great performance.
Works out of the box. Supports only Xbox controller.
Setting 1440p in-game resolution rendered a window that covered 3/4 of a 4K screen. No way to scale it up. Therefore no way to configure FSR. I think it has something to do with how the game is runned in Proton (some kind of virtual desktop, maybe).
Steam Input isn't supported, only plain Xbox controller signals are recognised properly - it means you can't have Xbox controller support enabled in Steam settings or use any other controller (e.g. Steam Controller).
Works exactly the same as on Windows.
It's categorized as game but it's Valve's video streaming service.
Runs perfectly fine, full support for Steam Controller. Had to reboot after system update otherwise Proton wouldn't start.
PROTON_USE_D9VK=1 %command% in launch options gives performance boost.
There are minor slowdowns on high@1440p when there's a lot of particle effects.
Native version crashes frequently, in proton it doesn't render.
Native version runs fine until about 2-3 minutes into the game when it'll crash randomly on interaction with object or person.
When run under proton it starts fine but when new game is started or Continue is selected in the menu the game doesn't render and the screen goes black. You can hear the game sounds when running around and shooting or bring up the game menu and quit but you can't see anything.
Game renders only in actual screen resolution (i.e. same in game and nvidia-settiongs). Otherwise you can hear sounds, shoot, walk, etc., but the screen is black.
Change Steam Controller's right pad to joystick (it's joystick-like mouse by default).
Native version crashes randomly on object or person interaction about 2-3 minutes into a game. In Proton it's stable.
Works flawlessly out of the box.
Finished the game with zero issues. Played with Steam Controller.
Installed 2 patches:
- TFix
- HDmod (optional)
Stereo issues. Go to Options > Audio in game and set:
- Hardware Acceleration to OpenAL
- EAX to On
Low res and 4:3 aspect ratio lock. Solved by TFix.
Go to Options -> Controls -> Customize Controls in game and Load one of the prepared bindings.
Low FPS. Solved by TFix.
Solved by TFix.
For optimal experience:
- install and launch the game with Steam once
- exit the game and Steam (significant)
- download TFix v1.27 and HDmod v1.2
- install TFix in terminal:
protontricks -c 'wine ~/Downloads/TFix_1.27.28.exe' 211600
- when asked for a path paste this (but replace
$USER):
z:\home\$USER\.steam\steam\steamapps\common\thief_gold\
- install HDmod in terminal (paste same path as before):
protontricks -c 'wine ~/Downloads/Thief_1_HDMod_1.2.exe' 211600
- run the game, go to Options:
- Audio -> Hardware Acceleration: set to OpenAL (for proper stereo)
- Audio -> EAX setting: set to On (for echo in caves, etc.)
- Game -> Auto-equip: set to On (to see your loot)
- Controls -> Customize Controls -> Load: select a sane preset
Final thoughts:
If you don't know your username run this in terminal:
echo $USER
If you don't exit Steam before applying **TFix** there will be glitches in game, e.g. items upside down, animation issues, dialogues not triggering.
If you don't see **OpenAL** in **Hardware Acceleration** you're missing OpenAL library, just install it from your distribution's repository.
**HD mod** is entirely optional but highly recommended. There are several different ones but I find this one easy to install.
As always, you should be aware installing anything from a 3rd party (like **TFix** and **HDmod**) is a security risk, however, here we're talking about a very reputable website (ModDB) and files downloaded by thousands of users.
Works flawlessly out of the box.
The game and it's community suck balls, but there are no technical issues whatsoever.
Pretty landscapes, full moon, mist and more. Still runs perfectly fine. Unfortunately the murican hunting culture makes it boring as hell.
On first run after download (creating Steam Play prefix) it seemed to freeze but it turned out the game spawned a Mono installation window that was under the Steam client window so I didn't notice there's one extra "Install" button to click. If that happens just minimize Steam for a sec.
