


Played through the whole game with an Xbox 360 controller without any issues.
MANGOHUD_CONFIG="fps_limit=60,no_display" mangohud DXVK_FILTER_DEVICE_NAME="AMD Radeon RX 6800" DXVK_HDR=1 ENABLE_HDR_WSI=1 gamescope -w 2560 -h 1440 -f --force-grab-cursor -- gamemoderun %command%
If you are getting stutters try: Deactivate Motion Blur InGame, FPS Lock on 60, go to [...]/Steam/steamapps/compatdata/1693980/pfx/drive_c/users/steamuser/Documents/Dead Space (2023)/cache/ and delete all contents, let the game rebuild the shaders most stutters should be gone now
Game has shader compilation stuttering for the first while of the game, as well as each time you enter a new area. Sometimes these stutters will completely freeze the game for multiple seconds, but it never resulted in a crash. They go away after the shader compilation has happened the first time, but beware that a reinstall will delete the shader cache and you will be back to square 1.

Even tho it can not be easily modded, each and every Proton Version allows anyone to actually play the game smoothly, without major bugs.
DXVK_FRAME_RATE=144 %command%
tl;dr I made a post on Steam's Community https://steamcommunity.com/sharedfiles/filedetails/?id=3424834997
As MY Guide states, "Proton Experimental & Hotfix don't allow me to edit game settings, BUT allow the mod to work even if it was made to only work on Windows".
I REALLY advice you to read my Guide, I had to figure out a couple of things by myself, since they were not easy to find at all.

Can not progress past chapter 5 due to crashes

Performance wasn't great in the opening cutscene but ran great after that

PROTON_USE_WINED3D=1 %command%
When alt tabbing my regularly mouse stays visible and is rather annoying
Controller stopped working after awhile with no explainable reason
The game is fun to play, Just dont get scared

Runs fine out of the box.
Be sure to run this game using Steam Runtime, not Steam Native. Attempting to run via Steam Native will result in the game not launching at all.

WINEDLLOVERRIDES="dinput8=n,b" %command%
There is a strange "deadzone" to the mouse movement. This is not a Proton Thing, it's a bad console port from 2008 thing. A fix can be found here. You will also have to add my launch arguments to get it to work, the linked page doesn't mention that in it's instructions. This fix isn't perfect, in some situations the sensitivity will change wildly, but it's much more playable with the fix than without.
Also of note, this game handles mixed input really well if you wanted to do some Flick Stick or Gyro Aim after applying the mouse fix.

DXVK_FILTER_DEVICE_NAME="NAVI21" %command%
Might be an issue on my system, but I often have to specify the GPU, game ran without any issues. Had a crash once or twice, but that's on the game from what I've read.

40Hz
Set Anti Deadzone a little below th half slider
Installed ReShade and preset for improved graphics like SMAA or Ambient Occlusion. Also used film grain and sharpening.

RADV_DEBUG=nogpl %command%
Crackling audio appears when returning to the game from sleep mode after a certain amount of time (it was a few days in my case). Restarting the game fixed the problem.
Use the launch option RADV_DEBUG=nogpl %command%
to fix diagonally sliced menu elements. The issue is known and can be tracked here https://gitlab.freedesktop.org/mesa/mesa/-/issues/9126
Cloud save syncing is not supported.

PROTON_USE_WINED3D=1 %command%
Without that command, it won't open.

Changed back grip buttons to something I liked more: L4: Mission Log (J), L5: Database Log (L), R4: Stomp (RB), R5: Map (Select)
8W TDP limit
An issue I had with the default controller layout is that the right joystick felt very bad. The sensitivity was weird, and most importantly it only seemed to output up/down/left/right (no diagonal!). This was fixed by switching to the community layout I mentioned, which uses the "Joystick Mouse" setting. Luckily this game seems to support simulaneous gamepad and kb/m inputs so this worked great.

Played flawlessly from start to finish. kept 60fps the entire game at 1280x800. some people suggested turning off vsync to reduce input lag but I got to the last chapter before trying that and I dont think it made a difference. At some points the deck was reporting over 6 hours of remaining battery life which is impressive.

Runs great
Starts up and runs perfectly. Ran on big picture mode 3400x1440p ultrawide resolution locked at 60Hz no problem. Dualsense controller working fine. Using Wayland
Runs like a charm.
Runs great, looks great. Controller input is where the age of the game shows itself, but can be improved slightly by a mouse fix mod.
Did the mouse fix mod that many have recommend. Not needed for a good time, but improves the cluncy mouse / controller input a bit.
Played the game mostly docked and rendered in native 4K 60fps at max settings. Mostly locked fps, some minor dropps during heavy action scenes. For conpletely locked framerate, you may as well use gamescope fsr to render at 1440p and upscale to 4K, which still looks amazing.
Port itself seems to work just fine. Unfortunately the gamepad controls have some terrible acceleration and deadzones on controlling the camera when not aiming the gun, though that seems to be an issue on Windows as well.
I played through the entire game flawlessly, worked like a charm even in docked mode, in 1080p.
XVK_FRAME_RATE=60 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 %command%
Physics is broken if your game isn't capped at 60 fps.
Whenever I change a window, while playing in fullscreen, after I come back to the game it doesn't register any inputs + it gets resized to the point that it's unplayable.
I've completed the whole game on Steam Deck without any issues.
Turning off v-sync reduces input lag significantly.
Played on max settings using latest Proton GE. Game runs smooth with just a couple technical issues.
Mouse cursor would appear in game when switching windows and will not go away without restarting the game. Just don't switch windows while playing and you won't have to deal with it.
Download the mouse fix and disable vsync to rectify the issue.

Works flawlessly out of the box
Runs perfect
Amazing game, the whole series is in my top 3 Once I got it working it was smooth as butter, and worked 100x better then windows
-nointro DXVK_FRAME_RATE=60
nothing terible, just everyonce in a while it would over or under shoot
I only noticed a little over shoot or under shoot on my mouse/cursor when in really big render spaces, like a lot of dust particals or something silmilar. it was nothing that actually altered or changed my expirence, I was too busy crapping myself to really care or notice.
Got a new monitor, Game no longer starts
I recently upgraded from an old office monitor (acer 1080x1920, 75hz) to a new MSI monitor, it is a 1440x3440 165hz. Once everything was set up, I attempted to load Deadspace and it would instantly crash. I tried a few other versions of proton, and to no luck it is still not working.
Controller configuration sucks!
Tabbing out and back in makes cursor always visible on top
Input is what makes this game unplayable in my opinion, it's just horrible, needs a lot of tinkering to get it going and still then it is not good at all. RPCS3 version plays with less fps but better controls
not enjoyable

- The game was limited to 60FPS, even when i disabled VSync.
- I experienced high input-lag.
Dead Space runs really well on modern hardware. I had 0 issues during my playtrough, but installing Origin was definitely not as easy as installing games on Steam.
My modifications:
- Mouse fix to get rid of mouse acceleration
- Downsampling (5120x2880 -> 2560x1440) by running 'xrandr --output DisplayPort-0 --scale 2' in the console
Cannot stomp or punch - no bindings seem to work.
Any key binding for stomp and punch are inactive, even alternative keys. Other keys work fine.
Inactive keys as mentioned.
Unplayable without stomping and punching.

If you want to play with mouse and keyboard, apply the mouse fix. Controller support is fine.
WINEDLLOVERRIDES="dinput8=n,b" %command%
Tabbing out of the game unhides your mouse cursor until you restart the game.
The PC port of Dead Space has bad mouse controls, even on Windows. You can fix them with this https://community.pcgamingwiki.com/files/file/840-dead-space-mouse-fix/ You'll need to add a launch option to tell Proton to load this DLL instead of it's builtin one.
The physics system is tied to the frame rate, which can break some sections of the game. Enabling vsync in the in-game options should be good enough, my game runs at 144 fps and other than some weird ragdolls it has no problems.
Game did run at first launch. After restarting the computer run just fine! Form there afterwards, the game run without any problems.
One could limit TDP, but battery life is okay without tinkering
Disabling vsync in-game massively improved the input lag
Some fullscreen issues, lagging, and the occasional crash. Comparable to Windows though
The beginning sequences had something like a screen are on the top centimeter, stopped quite quickly though. This may be related to running in windowed mode due to the initial issues getting it fullscreen.
During the initial boot it loaded on the second monitor, it wasn't alligned properly so only a quarter of the menu was visable. Setting it to windowed mode moved it back to the primary screen as fullscreen. After a couple restarts i tried again and was able to turn on the fullscreen setting without issue.
During the asteroid scene the controller was going really slow and occasionally speeding up, I plugged in a mouse to get through the scene.
During demanding scenes the game would be laggy felt like 30-40 fps at times but the fps counter was always above 140 fps
The game did crash out a couple times during my playthrough, seemed random.
Game runs, you can play and everything is amazing. As it is an FPS you need 60 fps, the problem is you need to manually change proton versio
Cloud saves were not downloaded from pc running linux with same version of proton.
I have this game with EA Play, so i can report than even with that it is running. Sadly for me, cloud saves are not working.
No inputs were recognized, stuck at "Press Any Key".
Chaning compatibility from Proton 7.0-2 to 6.3-8 fixed the issue.