Hello @nhkode, these look like some lines of interest from the log:
err: DxvkMemoryAllocator: Mapping memory failed with VK_ERROR_MEMORY_MAP_FAILED
[line repeated many times]
err: DxvkMemoryAllocator: Memory allocation failed
err: Size: 1048576
err: Alignment: 16
err: Mem flags: 0xe
err: Mem types: 0xff
err: Heap 0: 1767 MB allocated, 1767 MB used, 1801 MB allocated (driver), 3323 MB budget (driver), 3050 MB total
err: Heap 1: 2160 MB allocated, 2007 MB used, 2183 MB allocated (driver), 5229 MB budget (driver), 6101 MB total
If the game executable is 32 bit, this could be another example of https://github.com/doitsujin/dxvk/issues/1318.
It might be interesting to test how the game behaves with the launch options set to PROTON_USE_WINED3D=1 %command%. This tells Proton to use wine's DirectX to OpenGL render path instead of DXVK, which tends to have lower vram requirements compared to DXVK. It should also be noted that this runtime option is also expected to come with a significant performance penalty and is not considered supported.
With wined3d the game behaves somewhat randomly. First time it just showed a black screen instead of the main menu. Pressing up/down I was able to here the menu interaction though.
The second time I rendered the main menu just fine and I was able to load a save game. But after loading the level the game just showed a black screen at incredible 20-30 fps. According to the sound the game itself was running properly though. Exiting it via the deck steam menu also crashed steam itself that time.
The third time I started the game the menu rendered fine until I switched to the options menu, where the screen turned black again.
proton log for black screen main menu with wined3d steam-251110.log
PROTON_USE_WINED3D=1x1 2022-04PROTON_USE_WINED3D=1 %command%x1 2022-04
Compatibility Report
System Information
It also happend on a second desktop system the last time I tried it there but that was one or two weeks ago, no clue if it would be reproducible right now
I confirm:
proton log contains the proton log for a run with "Memory Available" set to Medium and a run where it was set to High.
Symptoms
The game reproducible hangs when loading certain levels if the in-game video option "Memory Available" is set to Medium or High. I believe one of those is the default setting. When set to Low the game seems playable just fine.
Reproduction
First map where it's reproducible I believe was the third area right after entering the elevator down the dam. It also happens when loading most of the later maps.