HansKristian-Work / vkd3d-proton

Fork of VKD3D. Development branches for Proton's Direct3D 12 implementation.
GNU Lesser General Public License v2.1
1.89k stars 198 forks source link

The Finals fails to launch on Intel Arc with DX12 #1832

Closed Vinjul1704 closed 9 months ago

Vinjul1704 commented 9 months ago

The Finals fails to launch on Intel Arc with DX12 (default). After the initial EAC splash screen, the main game window opens and stays as a black screen for a few seconds, before simply closing. During that black screen, the CPU usage spikes and after a handful attempts of launching the game, it doesn't even get to the black screen anymore and simply crashes right after the EAC splash screen.

Using the -dx11 launch argument works to get the game running, however there is no graphics API selection offered by the game itself and it's unclear if that option is intended to be enabled and might go away at some point.

According to other Proton reports, it seems to work fine with DX12 on other GPUs.

Software information

The Finals (2073850), default settings

System information

Log files

Proton Log with DX12: https://gist.github.com/Vinjul1704/032f920f99c11103bf4a7e015d757308

mbriar commented 9 months ago

If it works on AMD/Nvidia, you should probably rather report this issue on the Mesa bugtracker and not here. However, this is probably just another case of any game supporting XeSS upscaling crashing on Intel on linux if you don't report a non-Intel vulkan verdor. Try force_vk_vendor="-1" as environment variable.

Vinjul1704 commented 9 months ago

If it works on AMD/Nvidia, you should probably rather report this issue on the Mesa bugtracker and not here. However, this is probably just another case of any game supporting XeSS upscaling crashing on Intel on linux if you don't report a non-Intel vulkan verdor. Try force_vk_vendor="-1" as environment variable.

Thanks, looks like force_vk_vendor="-1" does indeed work. I'll make a Mesa report as well then, as you suggested.

mbriar commented 9 months ago

You can close this one, there is nothing that vkd3d-proton can do about it.