protonscr

Dead Space: Poor performane

vkd3dclosed
HansKristian-Work/vkd3d-proton#1407 · opened 2023-01-30 by K0bin · updated 2025-07-07 · 5 comments · github
KK0bin 2023-01-30 github

This hallway (as an example, it's not limited to this particular spot):
20230131000058_1

runs at 54 FPS on Linux and 96 FPS on Windows.

Both at 4k, VRS enabled, ultra settings, RTAO, DLSS Balanced. Both are GPU bound.
It doesn't seem to scale that well with resolution either. I have to drop the output resolution all the way down to 1080p to achieve comparable performance on Linux (100fps).

Nvidia RTX 3090 with 525.60.11.
Using #1405

TTamsenSpelchak 2023-02-01 github

I am having trouble replicating this issue. I see roughly equivalent performance between native d3d12 on Windows 11 and VKD3D-Proton on Linux. This is with all settings maxed out, (including RTAO,) at 3440x1440 without upscaling. I'm using an RTX 4090 with 525.85.05, but I've seen similar performance on the previous 525 driver, and the vulkan developer beta driver.

Windows 11:
Screenshot_20230131_074938

VKD3D-Proton ae06b479a8402484c5e55deac6ac13b61487ccd1 on Arch Linux:
Screenshot from 2023-01-31 19-28-20

(I'm guessing the saturation difference between the two screenshots is Windows capturing an SDR screenshot of an HDR application)

KK0bin 2023-02-01 github

I did another test and I got for better results this time.

Screenshot_20230201_032733

74 fps on Linux vs 96 fps on Windows. 78% is still somewhat bad but not as catastrophic as before. (ignore the GPU util% in the screenshot, thats just because I made the screenshot)

The Vulkan beta seems to do slightly better, coming in at roughly 80 fps.

Rrurigk 2023-02-17 github

I noticed that after some time of playing fps start to drop when loading a new section
You can fix the fps drop by saving and loading

I dont have a windows machine to test if this happens on windows as well

KK0bin 2023-02-17 github

I did my comparison immediately after starting the game.

KK0bin 2025-07-07 github

I haven't really tested this but I'm replaying it right now and performance seems fine.
I'll just assume it's fixed by NV_raw_access_chains.

Nothing extracted yet.