


inital readme needs to be closed in desktop mode but runs fine after

Mandatory first startup in desktop mode
Activation of gamepad in game settings required
When you start the game from Steam the first time, it will show you a readme text file. To solve this, restart your Steam Deck and go into desktop mode. In desktop mode, start the game and then you can simply close the viewer with the text file. The game launches afterwards. Then close the game and go back to Steam Deck mode. Now the game will launch without any issues anymore.
When you launch first time in desktop mode, the gamepad controls do not work. Use the right track pad to move the mouse and you can select menu items with Steam + RT (to simulate left mouse click). Go into the settings and the to controls. There you can activate the Xbox control layout (gamepad), which enables all the controls you expect.

I have tried many different ways to get this started in desktop and game mode. Nothing works. Just says updating executable and then nothing.

PROTON_USE_WINED3D=1 %command%
Audio stopped working after tabbing out of fullscreen
The game runs, Was able to play each campaign a bit and experienced only the one audio bug, otherwise it was very much enjoyable

The game needs to be launched once in desktop mode first, so the readme popup window can be closed.
You need to toggle the relevant in-game oprion to enable native gamepad support.

No tweak, I have tried with Proton Experimental only and played more than 1 hour on Predator campain. I'm running on Nvidia RTX 2080 and on Wayland too! Stable 400 FPS without vsync.

Overall, while encountering significant difficulties to get it to work, I've been able to get it to become playable.
__NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia PROTON_USE_WINED3D=1 %command%
At different times under different circumstances, I've had it lag really bad, graphics become low detail or otherwise weird looking, fullscreen issues, audio breaking if game exited and re-entered, movement input getting stuck (keeps on walking after input stops), and a crash during the tutorial. Most of these issues I've been able to correct.
Online gameplay was okay, I think I had a slow internet connection, otherwise it would have been better.
Most of the bugs seemed to be somewhat random and related to Fedora updates and graphics driver issues. Install the NVIDIA drivers before playing if using an NVIDIA card: https://rpmfusion.org/Howto/NVIDIA
In my case, it was the 4700xx driver and the cuda drivers as well. Installed via command line, and had success at getting game to run with minimal problems. Game was very sensitive to changes in graphics, changing screen resolution, detail levels, switching between DirectX9 and DirectX11, all had a major effect on the playability of the game. For some reason, later versions of Fedora seem to make the game unplayable, at least in my case. Runtime game options shown were important as well to getting the game to run correctly.

game would crash after few minutes of the campaign
gamemoderun %command%

Played well.
Skip into videos: SteamApps/Common/Alien Isolation/DATA/UI/MOVIES then find AMD_IDENT.USM, CA_IDENT.USM, and FOX_IDENT.USM - Delete or rename them.

Plays at 60fps and looks great

I am only saying no because many will see the multiplayer crashing as a major issue. The team deathmatch is still rather popular online.
Playing Multiplayer causes a crash that closes the game. As soon as it initialized connection to the multiplayer menu / lobby area the game just closes everytime on all versions of proton I've tried.
I must add that the game is still playable in single player mode. I am currently working through the predator on nightmare again. Still havent finished that mode.
So I wish I could give it a good rating. I know there are many out there like me though, those who lived on the multiplayer team deathmatch, so I have to say thumbs down.
Install game. Switch to desktop mode. Browser game files. rename read me to whatever. Switch back to game mode. Launch game, a pop up window will appear, use mouse (hold steam button & use left track pad) to click cancel. Game will load, use mouse in options to enable controller in game or use community profile.
Runs great!
Set refesh & fps to 40, Set TDP 5-7Watts
The game does not have good UI to play but it is not a problem with Linux (but the game being "old").
Worked essentially flawlessly
Tabbing out and in made the sound go away
I was able to find some matches with the help of https://avp2010.avpunknown.com/
As the summary says.
On launch, it opens a .txt. Use desktop mode, to start there the first time, close the txt, head back to gaming mode and enjoy. :) Switch the layout to one of the community made ones to save you some hassle. Keep in mind the game does not support cloud save. Other than that, the game runs and looks fantastic.

-subwindow
Sound is disabled when fullscreen mode is enabled
Fullscreen disables sound in both modes DX9 or DX11
All worked as intended on my OS and hardware setup. I was able to play in both modes DX9 and Dx11, the latter has more graphic features activated like texelation an better shadows. The sound issues were gone after setting -subwindow as launch option but you gotta play in windowed mode setting up desired resolution and maximizing the window on the OS.

Works ootb.
Mind no cloud saves.
work out of the box
alt-tabbing can cause you to loose the game sound
work out of the box just don't alt-tab if you like hear the game sound
You have to enable gamepad/controller in the menu yourself, it doesn't auto enable
a read me pops up on first time launch, use desktop mode to negate this
Looks phenominal and is essentially flawless on the deck
-subwindow -winsize 3440x1080
Games locks up at Start/loading in Fullscreen. Maybe ultrawide limitation?
Needs -subwindow in launch options to get past initial loading screen. Otherwire runs flawlessly
Drops to about 50 FPS during busy or demanding scenes at max, set AA to 2x for a pretty locked 60 FPS
First time launch in desktop mode
To left mouse button control
First time launch/setup loads readme file
Game supports controller, but doesn't automatically connect to it; using the right track pad as mouse with left click and going to controls options gives controller compatibility
Very minor framerate stutter during scene transitions
Opens a readme.txt instead of launching.
Has to be run in desktop mode the first launch. There is a popup that can only be closed in desktop mode.
Once this popup is closed in desktop mode the game will run in both desktop and gaming mode.
Just launch in desktop mode for the first time you play it so you can close the popup window.
It won't work on steam deck unless you go to desktop mode (just for the first time you run it).
Now works (with Proton 6.3-8)
Stops after alt-tab
Played with Proton 6.3-8
Works great
I works only with Proton 6.3-8 for me.
sometimes after alt+tab sound doesnt work
As of Proton 6.3-8, game now launches and runs identically to that on Windows.

Este juego corre muy estable con proton 6.3-8 y con direct x11.
Laptop con gráficos integrados, mi procesador i3-1005G1 va muy bien a 45 fps estables con "gamemoderun strangle 45 %command%" sin sombras y gráficos en normal a una resolución de 1280x720 16:9, en ajustes se puede activar la opción de mando, yo lo jugué con un mando de ps4 y va muy bien.

The game runs really great on proton, and according to the game original release date, i'm surprised (in a good way).

You lose your sound when you alt-tab.
DX9 mode will have a large amount of missing textures in some levels. DX11 mode can be played with sound by using the -subwindow launch option.
You lose your sound when you alt-tab.

Only has audio when loaded in Direct X 9 mode.
Works with the new Proton Experimental. Minor graphical and audio bugs but outside of that it runs 100%.
If Alt-tabbing the sound stops working until you relaunch the game

Audio breaks if you alt-tab from fullscreen mode. Use launch option -subwindow to use windowed mode and run the window fullscreen, alt-tab works fine then
Ultrawide supported in gameplay. Menus and cutscenes are locked 16:9 aspect ratio.
Game is a bit slow to launch and starts in a tiny black window in the upper left corner, just wait for a little while (less than 30 seconds) and it'll open in a proper window.
As of 29/10/2021 CEG DRM is working with Proton experimental on the Beta client of Steam.
Installed and played first mission without any issues.
Initial launch is in a tiny window. Just need to maximise it to view the menu and then you can change graphical options.
As of 29/10/2021 CEG DRM is working with Proton experimental on the Beta client of Steam.
With CEG starting to be supported in the latest Steam Client beta and Proton experimental (6.3-20211027) the game works now out of the box.
I played through some known trigger points, where the game tends to crash when there is an issue with CEG (you could get the game working with Proton before, but it was tricky) and these all worked, no issues.

Does not launch due to CEG DRM
Neither the DX11 or DX9 modes launch properly due to the usage of Valve's CEG DRM, which is still currently an open issue on their GitHub tracker for Proton.
Has no Windows Steam - can not generate exe with DRM. Now game exit silently.

Runs in dx9 mode after copying from a wine/windows installation of the game, but only on even days of the month.
Most of the steps I took to get this game to run have been taken from Corben78's findings here: https://github.com/ValveSoftware/Proton/issues/530
There seems to be some kind of issue with this game's DRM that makes it crash when killing an enemy during odd days of the month. Either playing the game on an even day of the month or setting the system time to an even day lets the game work. I've tried to run the game with faketime, but to no avail. In addition, I could not run the game in dx11 (HUD would display but the rest of the screen was black) or windowed mode (crash after splash screen), and alt-tabbing would cause a heap of issues, generally ending in the game crashing. To remedy this, I had to use winecfg in the game's prefix ($protontricks 10680 winecfg), enabled wine's virtual desktop at the resolution I intended to play the game at, and unchecked both "Allow window manager to ..." options. I also installed xact ($protontricks 10680 xact).
After all of that, start the game in dx9 mode with proton 4.11-13 and after waiting about 30 seconds, the game should hopefully be running. So far, I've played through the entire marine campaign with no major issues. Be sure to not verify integrity of game cache, as doing so will make the game unplayable, and you will have to copy it from a wine/windows install again.