Name of the game with compatibility issues: Conan Enhanced
Steam AppID of the game: 440900
System Information
GPU: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q]
Video driver version: NVIDIA 595-Open
Kernel version: Linux 6.17.0-23-generic
Link to full system information report as Gist: N/A
Proton version: Experimental (Also tried 11-Beta)
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
The Launcher shows fine, and I've disabled BattleEye to play offline, however, when hitting Play, a window pops up, saying that DirectX12 is required, and to remove the DX11 launch options (I don't have any launch options set). When manually setting the launch options for DX11 and hitting Play in the launcher, a new popup says "This project doesn't support DX11.", and the game fails yet again. Keep in mind, this is after Vulkan has finished processing Shaders.
It is my understanding the DXVK isn't supported for DX12, only 11 and older, and I've never used it before. I checked Reddit, and some people are able to play Conan Enhanced on Steam Deck perfectly fine, so I'm unsure why Linux users are having such a hard time, but as of now, noone has found a work-around.
Contacted Steam Support, and they didn't have any advice for me, just to leave a bug report here. If anyone knows what's going on, please reply to my report.
Reproduction
Clear all Conan Enhanced Launch Options, Set Compatibility to any Proton Version, Launch, let Vulkan Process, Disable BattleEye and hit Play in the Launcher.
Get met with a popup complaining about needing DirectX12, and to remove your DX11 Launch options, even though you've got none of that set (Probably something Proton is doing in the background, idk).
Force DX11 in launch options, launch the game, and get another popup saying that the project doesn't support DX11.
Verify files, Clear everything again, set to Proton Experimental, launch. Hit Play in Launcher and be met with the same messagebox again, effectively locking you out of the game.
Only thing I havent tried yet is tinkering around with Protontricks/Wine to try to launch the executable directly, which according to others on reddit, is hit or miss for others on linux with the same issue.
Compatibility Report
System Information
I confirm:
Symptoms
The Launcher shows fine, and I've disabled BattleEye to play offline, however, when hitting Play, a window pops up, saying that DirectX12 is required, and to remove the DX11 launch options (I don't have any launch options set). When manually setting the launch options for DX11 and hitting Play in the launcher, a new popup says "This project doesn't support DX11.", and the game fails yet again. Keep in mind, this is after Vulkan has finished processing Shaders.
It is my understanding the DXVK isn't supported for DX12, only 11 and older, and I've never used it before. I checked Reddit, and some people are able to play Conan Enhanced on Steam Deck perfectly fine, so I'm unsure why Linux users are having such a hard time, but as of now, noone has found a work-around.
Contacted Steam Support, and they didn't have any advice for me, just to leave a bug report here. If anyone knows what's going on, please reply to my report.
Reproduction
Clear all Conan Enhanced Launch Options, Set Compatibility to any Proton Version, Launch, let Vulkan Process, Disable BattleEye and hit Play in the Launcher.
Get met with a popup complaining about needing DirectX12, and to remove your DX11 Launch options, even though you've got none of that set (Probably something Proton is doing in the background, idk).
Force DX11 in launch options, launch the game, and get another popup saying that the project doesn't support DX11.
Verify files, Clear everything again, set to Proton Experimental, launch. Hit Play in Launcher and be met with the same messagebox again, effectively locking you out of the game.
Only thing I havent tried yet is tinkering around with Protontricks/Wine to try to launch the executable directly, which according to others on reddit, is hit or miss for others on linux with the same issue.