dxvk-native VS protondb-evalute

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!)

Here are some numbers I've extracted from ProtonDB:

About a year ago I've written a custom set of scripts to parse the public data from ProtonDB locally generating visual graphs to see how relative progress is moving. Today I updated the graphs again which I didn't since February and the launch of the Steam Deck made quite an impact in the ratings.

Here is the source for the numbers: https://gitlab.com/TheJackiMonster/protondb-evalute (I wrote a little Python script some time ago. ^^)

From statistics we can actually expect to have similar compatibility across all the Linux distributions. ProtonDB states that from all reported/tested games, about 66% is recommended by at least one to be playable. The amount of playable and verified games (the sum of both) by Valve is also about 66% of their tested games. When you rank all reports on ProtonDB with a sensible metric, you will also get about 66% reported as playable (I have actually written a Python script to do just that).

You can check it out here: https://gitlab.com/TheJackiMonster/protondb-evalute

The number is definitely accurate. I have written a script in the past to evaluate the protondb-data which is publicly available at Github. The script will categorize newer reports into the old categories and provides an overall category from the most given one by all reports to a specific game.

Wine/Proton will definitely improve. We are currently at about 62% (I checked via this tool) compatibility overall. So guessing it will increase to about 70% (even without working anti-cheat) is a good estimate.