


The game is pretty heavy on the battery. Limiting fps to 30 saves on some much needed battery life.
This game is an unoptimized mess, even on consoles. Can maintain 40fps lock about 75% of the time, expect dips here and there. No dips below 30fps though.
Recommend locking to 30fps and lowering TDP slightly for stability and battery life.
gamemoderun %command%

it's not a good port, it struggles to keep stable fps above 30. Set in-game fps to 30 do the same with the deck's fps limiter that way it runs just fine. You would have to lower the fps to 30 at some point to avoid some game breaking issues that happen with higher fps anyway. Set R1 button to "toggle" in Steams controller menu for a better stealth experience
R1 to toggle
11 tdp
Not an optimized port - set to 30 fps

perfomance can drop in certain huge enviroments
works great at almost 60 FPS, can drop to 40 in certain scenarios but otherwise an good experience on the Steam Deck.

I dont really like seeing missng textures, black windows or walls in an old game, makes no sence
textures not loading from the first cutscene forward

Worked out of the box
Absolutely no issues encountered specific to Proton, I ran the game at 60 FPS from start to end without issues. I did have to swap to 30 FPS for some of the chase scenes due to bugs, but those are also a thing on Windows.

Had to play at 900p for Smoove gameplay

Works perfectly out of the box
Had no stuttering or anything, even without any launch options. If the mouse cursor stays after closing a menu just rightclick and it will disapear. Don't know if this is a Proton related "issue".

%command% +com_skipIntroVideo 1 +r_swapinterval 2
textures load slowly on this game, even when it's using 90% of my gpu
mouse is laggy on the menu, but in game works ok
The game uses alot of gpu somehow even when you have shadows and everything else on low, forcing the gpu too much even when you have locked at 60fps
This is a pretty bad port but it's playable.

collectable text can be small
you can try for 40FPS but some locations will drop frames
Works well with a few minor graphical problems that seem to be on the regular PC version.
Tecture pop in
There was some pretty noticable texcture pop in during cutscenes, but they seem to be present on windows as well. I switched to GE to see if it solved the issue, but it didn't. Otherwise, the game ran fine, so no need to switch to it.
Im not 100% sure as my experience reguarding the texture pop is was inconsistent but my setup worked just fine for me.
__GL_THREADED_OPTIMIZATIONS=1 __GL_YIELD=NOTHING __GL_MaxFramesAllowed=1 STAGING_WRITECOPY=1 STAGING_SHARED_MEMORY=1 %command% +image_useCache 1 +com_skipIntroVideo 1 +com_allowConsole 1 +mt_genVmtrCompression none +vt_pageImageSizeVmtr 16384 +vt_pageImageSizeUniqueDiffuseOnly 16384 +vt_pageImageSizeUniqueDiffuseOnly2 16384 +vt_pageImageSizeUnique 16384 +fc_maxCacheMemoryMB 2048 +mem_phyMemBlockSizeM 2048 +r_WSFilePrecacheinit 1 +r_WSFilePrecache 1 +exec j.cfg
r_swapinterval 0 and capped the fps to 60 to prevent game logic and texture streaming issues.
The options and main menu feature heavy deadzones for mouse movment due to software input.
+com_skipIntroVideo +r_swapinterval 0 also added these. The second one being uncapping the frame rate.
I added the proper folders as stated on the pc gaming wiki to return texture caching.
I had textures not loading in and staying as low poly models a decent amount during the gameplay. This is a known issue with the Id tech 5 engine the game uses and I don't believe it has anything to do with proton. It did not take away to much from my gameplay experience and the texture caching fix helped.
Pretty good experience all around just wish the game's use of virtual texture streaming didn't weight it down so much.
Works out of the box

Minor, and very infrequent audio choppyness.
Texture streaming issues. Late loading (sometimes never loading) of all textures (models, objects, environment). Pausing the game seems to force loading of all textures in camera view.
Vsync doesn't work. Game always runs uncapped. Didn't affect gamplay nor graphics (didn't notice any tearing), but this taxes GPU fans more than it should for such an old game.
I haven't tried the fixes mentioned in other reviews. Perhaps they do help. I don't recommend playing the game as is. Breaks immersion, and some puzzles requires pausing/unpausing to solve. In some cases it did affect gameplay (couldn't tell beige blob of an untextured Haunted from the beige sea of the untextured environment.
Some slight performance issues, but this is down to bad optimisation, as it played the same in windows.

Works fine with Proton 7.0-4 and "+r_swapinterval 2" launch option. Sometimes still shows textures with a slight delay.
%command% +r_swapinterval 2 +image_useCache 1 +fs_cachepath "C:\Cache"

Either turn off V Sync manually to get a probable locked 60 FPS or decrease resfresh rate to get stable 45 FPS at max settings
Only if you want to disable V Sync
Capped refresh rate to 45
Unproblematic pop/load in issues during cutscenes
Can't seem to keep a stable 60 FPS even at low due to V Sync always being enabled

+com_skipIntroVideo 1 +com_allowconsole 1 +r_swapinterval -1 +image_useCache 1 +fs_cachepath "C:\Cache"
High res texturres loading late on 60 fps vsync
With 30 fps and +r_swapinterval -1 launch options works very well

Just set in-game settings the right resolution
Works fine but it seems the game isn't well optimized. It doesn't matter if I set all low.
Works great out of the box
r_swapinterval 2
r_swapinterval 2 (60fps) or 3 (30fps) is needed or else textures fail to load in properly. (-2 or -3 for swap tare)
Put a text file called dxvk.conf in the directory and add dxgi.syncInterval = 0 dxgi.tearFree = False to disable vsync while allowing the frame rate cap. External frame rate limiters do not fix the texture bug.

Runs just like in Windows, complete with stutter and texture pop-in. Check PCGamingWiki entry for fixes.
strangle 60 %command% +com_skipIntroVideo 1 +r_swapinterval 0
Libstrangle can be used to cap the frame rate at 60fps: www.gitlab.com/torkel104/libstrangle
PCGW page: www.pcgamingwiki.com/wiki/The_Evil_Within
Runs perfect
Small texture pop-ins. Nothing major.
This plays on Linux better than windows. Windows has game breaking bugs and pop-ins on textures but linux only has the texture pop-ins. Linux 1 / Windows 0

Proton-7.0rc6-GE-1 GloriousEggroll
Textures would refuse to load in, sometimes for 3+ seconds, sometimes indefinitely, unless the game was paused and unpaused. Nothing I tried fixed it.
Tested with Proton-6.9-GE-2 and it run amazingly. Performance pretty much the same with windows.
A bit of stuttering and texture pop-in doesn't stop this being an enjoyable game on Proton.
Alongside the game stuttering, there's a LOT of audio stuttering during cutscenes, but not during gameplay.
There's a lot of texture pop-in in this game, but from what I've read it may just be an issue with the game itself rather than anything to do with Proton.
A lot of stuttering during cutscenes, and sometimes during gameplay, mainly when certain enemies appear, like Laura and the Keeper.
I had three freezes during my playthrough, two of them in the same chapter in the same area.

All good with proton 5.0-10
I tried proton 5.13-4 but the games gets stuck at start-up (black screen forever)
I experienced some random in-game crashes. I added these options "+com_skipIntroVideo 1 R_forceaspectratio 2" just to be on the safe side. Enjoying this game a lot since I missed out on it during its release. Runs about 60 fps on my rig.
For me this game actually runs better on Linux with Proton than on Windows.

To get a better perfomance I used gamemoderun %command%
on the launch parameter.
Game runs well, minus the annoyance with texture loading
Whenever loading a new area, the textures will not load initially. If you pause the game, then unpause, the textures will be available for that area. If the textures do not load, they may eventually load them when moving around. Setting a cache path via +fs_cachepath command didn't help either.
I did not experience controller issues with the standard Proton 5.13, but if I used Proton-5.9-GE-8-ST, it would not detect my Playstation 4 or Xbox One controller. Will have to test GE when a newer version based on Proton 5.13 is released.
Other guides say to use +r_swapinterval 0
as a launch option, but I didn't notice a difference when setting 60 FPS + Vsync in the game options.
Works flawlessly
I'm not sure how performance is when compared with Windows but on a 2060 I can get a stable 60 with like no drops whatsoever