dxvk-native VS ToGL

DXVK 2.0 has upstreamed the dxvk-native code, meaning the game runs using native Linux libraries but uses DX11 with DXVK. This is mostly done because the ancient OpenGL linux-native renderer was rather bad.

what works best is games supporting dxvk-native: https://github.com/Joshua-Ashton/dxvk-native

There is DXVK native which doesn't require wine.

https://github.com/Joshua-Ashton/dxvk-native

There are also Dxvk native for porting game to Linux. Which is used by valve to port it's game to Linux.(replacing togl)

I disagree, but I get the frustration. It's just that I've been playing CS:GO for almost a decade, and while I think the game is neglected by Valve in general, it's way a worse scenario on Linux. For instance, Vulkan support (via dxvk-native) was added back in December last year, and it's not been updated ever since, so you get way worse stuttering when compared to OpenGL (which is actually a DirectX 9 to OpenGL translation layer, called toGL, which has its own set of bugs and issues); Plus, you can't change screen resolution when using Vulkan. I get some occasional little stutters on Windows as well, but the whole CS:GO experience is honestly just way worse on Linux, unfortunately.

DXVK-Native and the game Perimeter. Perimeter is the one game I know of that's opensource and that uses DXVK-Native. I got it to run, but there was no support for any audio, making this pretty unexciting. This is still being worked on upstream, so maybe a DXVK-native port later and a port of perimeter will happen then...

You never mentioned that requirement, but here you go: https://github.com/Joshua-Ashton/dxvk-native

DirectX isn't an option on linux/mac anyway, it's just launch or safe mode. (Note to any SCS developers if they're lurking around here... please implement the DX pipeline into the linux build so we can use DXVK-Native, it's much faster than OGL!)

I think the Vulkan flag uses DXVK. Before that, the game used ToGL. With CS2 I think they're going Vulkan native.

Yes and no. Most of the code is, but the graphical part itself isn't native since source only supports directx, so Valve developed ToGL. ToGL, however, is nowhere near as performant as DXVK. https://github.com/ValveSoftware/ToGL

The Source engine originally used a translation layer called [ToGL](https://github.com/ValveSoftware/ToGL) (D3D9 -> OpenGL). VALVE has been introducing DXVK natively into the engine, among other reasons, to enable the use of Vulkan and improve overall performance.

Not if you have an NVIDIA card.

I disagree, but I get the frustration. It's just that I've been playing CS:GO for almost a decade, and while I think the game is neglected by Valve in general, it's way a worse scenario on Linux. For instance, Vulkan support (via dxvk-native) was added back in December last year, and it's not been updated ever since, so you get way worse stuttering when compared to OpenGL (which is actually a DirectX 9 to OpenGL translation layer, called toGL, which has its own set of bugs and issues); Plus, you can't change screen resolution when using Vulkan. I get some occasional little stutters on Windows as well, but the whole CS:GO experience is honestly just way worse on Linux, unfortunately.

Yes, Linux native CSGO uses OpenGL as default via ToGL.

Ah, I think you are right, this one yes? https://github.com/ValveSoftware/ToGL

"native" in Valve games (maybe aside from source 2, not sure) just means they compiled the existing game code to Linux (probably with some minor changes) and put their own DirectX shim on top. Lately, they have been giving us the option to replace that shim with DXVK.

Current implementation is ToGL, will be replaced with DXVK. Source 1 is designed around old versions of DirectX (8).

There's a decent chance Valve will replace their ToGL layer in CS:GO with DXVK Native as well, if the trend (Portal 2, L4D2, HL2) continues.