d9vk VS wine

Use https://github.com/doitsujin/dxvk

It will be easier to understand if you show me an example of terminal commands under GNU/Linux. I tried to follow his instructions but I don't know one method is good

If you know the directory structure and where the versions of Proton live that Heroic uses, you can also go to the dxvk github page and select the 1.10.3 tar ball, download it and extract it, then manually move the appropriate files to their desired location in the Proton file structure. As with all things like this, .old is your friend if you stuff something up. And yes this does work, I compile my own vkd3d versions and use this approach as a lazy way to test them in Steam.

You can try dkvx Github dkvx , which is a mod that supposedly translates the DX11 stuff to Vulkan but I am not an IT guy so no clue how that works but as I said somewhere else on this thread it helped some people.

Worry not, if you want to play Windows games on Linux, you will use Wine, and Wine has codepaths for very old DirectX versions, it translates it to OpenGL. Alternatively if you really insist there is D8VK although it shouldn't be necessary. For DirectX games that use DirectX 9, 10, or 11 you are covered with DXVK which translates those APIs into Vulkan. And for DirectX 12 games you're back to Wine with WineD3D which will do translation to Vulkan. Technically WineD3D supports every DirectX version, but DirectX 9, 10, and 11 codepaths are half finished, buggy, and less performant, that's why DXVK exists.

You can give DXVK a try.

If you are going to download DXVK, you can download from GitHub.

No, it does not. Check the readme - https://github.com/doitsujin/dxvk DX12 goes through this - https://github.com/HansKristian-Work/vkd3d-proton

Much like it did before this commit.

Both Proton and Wine are open-source, there's not much to be gained by trapping any possible development to only folks working at Valve when there are thousands would happily help for free, on top of those Valve already pays.

Valve doesn't use upstream Wine. They use their own fork: https://github.com/ValveSoftware/wine

The 'No GPU Found' error is caused by https://github.com/ValveSoftware/wine/commit/51ce414a1f41fcaa415c4d3b4edd6b96ba711a35

Here is a github issue that describe it better https://github.com/ValveSoftware/wine/issues/177

Looks like Proton Experimental just fixed it. https://github.com/ValveSoftware/wine/commit/ae2fad7338cc2f914536469656448ecb5fdcf294

I'm pretty sure Eggroll is reffering to this Gnome 43 specific ALT+TAB fix which was merged in Proton Experimental last week: https://github.com/ValveSoftware/wine/pull/169

A solution is in progress. Give it a few weeks, or build Proton yourself. https://github.com/ValveSoftware/wine/issues/172

Then, if you managed to attach gdb, source this script and run lsf. After that let the game continue until you hit the crash and you should be able to get a backtrace with symbols (don't forget to use a radv build with debug symbols left in.