@q-tan0x while the workaround you mentioned allows you to at least launch the game and start a run, neither the player's nor the enemies' bullets have collision, making the game unplayable still.
There's a workaround according to [protonDB](https://www.protondb.com/app/3138090), replacing d3d DLLs using winetricks/protontricks. Dunno why but this works for many games. See also the above winehq bug report. **EDIT*...
I believe it's technically already been reported as [Bug 37676](https://bugs.winehq.org/show_bug.cgi?id=37676). Per your advice, I'll refer to my findings here in a comment for that bug report soon.
@yoshiweegee Thank you for this information. Our plan is (and has been for a while) to regularly update the vkd3d submodule, but we do not yet have it automatically updating from the master branch on winehq as you've not...
I attempted to cherry-pick the relevant changes to get a successful run. My changes and findings in order: - For Wine, [d01ae151](https://gitlab.winehq.org/wine/wine/-/commit/d01ae1512fe0f0b4288a97b38cf888095159b919#7e59...
> It seems that because the Wine repository is using vkd3d 1.10 where `VKD3D_SHADER_TARGET_FX` didn't exist yet, there's a mismatch between what Proton's Wine and vkd3d expect for compiling D3D effects, resulting in `com...
Dug through vkd3d and found that the other error is a bug in its HLSL lexer. ___This bug has already been fixed in [Wine's GitLab repository](https://gitlab.winehq.org/wine/vkd3d/-/commit/5ea946aa90e0de4a4851c98bfeb4e5bc...
Tested with the only changes being vkd3d being version 1.10 and [commit e527d7c](https://github.com/ValveSoftware/vkd3d/tree/e527d7c1e7cf78bfa42b573ef8d2571003f6a1a5) (the commit right before adding `VKD3D_SHADER_TARGET_...