Compatibility Report

• Name of the game with compatibility issues: DEATH STRANDING DIRECTOR'S CUT (Epic Version)
• Steam AppID of the game: (The pure Steam one is) 1850570

System Information

• GPU: AMD Radeon 780M Graphics (RADV PHOENIX)
• Video driver version: mesa 25.2.5-1
• Kernel version: 6.17.4-gentoo-dist
• Link to full system information report as Gist: this
• Proton version: Proton Experimental

I use the Heroic Launcher. I also paste the log of a good version here.

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

Symptoms

Sorry if a non-Steam report is not welcome.

With Proton Experimental the game launch takes too long time. It is ok with Proton-10.0 (Or for Proton-GE, 10-15 is good and 10-17 is bad, probably meaning 10-16 is bad, too.)

When you choose "continue" at the title screen, a loading gauge (progress bar) appears. In the bad version, it gets stuck at 11% and won't progress further. (So I manually stop the game there.) The process is not hung; a loading icon continues to rotate.

There's at least one more difference. When you start the process, first the screen is black, then brand logos appear. the time to reach logos is (seconds) longer in the bad version.

Number differences in log.

I noticed one thing in the log, which is a noticeable difference for Proton-GE-10-21, in parts where vkd3d reports "it took xxx ms."

The first chunk looks like this (L 609-):

9672.123:00cc:01c8:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Merging pipeline libraries took 3.742 ms.
19672.123:00cc:01c8:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Mapping read-only cache took 0.228 ms.
19672.123:00cc:01c8:info:vkd3d-proton:d3d12_pipeline_library_read_blob_stream_format: Device teardown request received, stopping parse early.
19672.123:00cc:01c8:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Parsing stream archive took 0.010 ms.

We ignore this for now and go to the second one (L 641-)

19672.211:00cc:01d0:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Merging pipeline libraries took 0.283 ms.
19672.238:00cc:01d0:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Mapping read-only cache took 27.086 ms.
00d0:fixme:wbemprox:client_security_QueryBlanket semi-stub.
00d0:fixme:wbemprox:client_security_Release 00006FFFF9231EC0
00d0:fixme:wbemprox:client_security_SetBlanket 00006FFFF9231EC0, 00000000066080A0, 0, 0, (null), 0, 3, 0000000000000000, 0
00d0:fixme:wbemprox:client_security_Release 00006FFFF9231EC0
19672.254:00cc:01d0:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Parsing stream archive took 16.614 ms.

Compare it with the second chunk of the good log (L 650-):

16108.613:0154:01d4:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Merging pipeline libraries took 0.482 ms.
16108.613:0154:01d4:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Mapping read-only cache took 0.403 ms.
16108.613:0154:01d4:info:vkd3d-proton:vkd3d_pipeline_library_disk_cache_initial_setup: Parsing stream archive took 0.011 ms.

The second and the third numbers are absurdly big for the bad log, by two or three digits, (27ms, 17ms) vs (0.5ms, .01ms).

This does not happen for Proton Experimental, so perhaps I'm in fact mixing two different reports. For Proton Experimental and GE-10-21 however the first number of the first chunk is 2x or 3x of the good one, typically 1.5ms.

Thanks a lot for developing Proton.

Reproduction