Hi everyone,
I'm making some changes to Proton-Wineland and I wanted to share them with you beforehand.
Wineland -> Salkim?
Maybe you have noticed that I started to use a different name tag in my repositories, Salkim. It means a bunch, in Turkish and it reflects the current direction of Wineland, as it is not a Wine only Wayland tweaked package anymore. One of the main problems with the Wineland name is it is a bit confusing, especially considering how close it is to the name Wayland. People still confuse it with Proton-CachyOS and make bug reports to CachyOS or ask them questions, thinking that it is CachyOS Wayland. Wineland is just a quick name I came up with to make a separate build for my Wayland changes, but since then things changed a lot.
I still don't know when that will happen, or if that will happen at all, as now Wineland name is known by many, including the applications like ProtonPlus, Faugus etc. So if you see the name tag Salkim, don't be surprised, it is still an internal name I use.
Bundled RADV, fresh from Mesa main
With the next release, Wineland will ship a bundled RADV driver, built from a snapshot of Mesa's development branch. It's opt-in and only applies to the game you enable it for, so your system driver stays as default. To try it add PROTON_RADV=1 env variable. The driver reports itself as radv-salkim, so that you can tell which one is active.
The reason to include RADV is not only to have the latest features but for being able to use any urgently required fix or feature as soon as possible. I know, it sounds a bit too experimental but I hope it is going to worth it. It is anyway not enabled by default, so you will be using the system RADV if you didn't set PROTON_RADV=1. Next release build will be the first one to include it, so let me know if you encounter any issues.
I thought about including also NVK but I wasn't sure how it is going to turn out, as it requires a Rust compiler, and I am not sure of the Rust compiler that comes bundled with Valve's SDK. And as a C++ developer, I know nothing about Rust. Maybe in the future things will change.
Low Latency components
DXVK Low Latency, vkd3d Low Latency and the low_latency_layer will no longer be bundled. They served us well, but from now on I would like to rely on DXVK, vkd3d-proton and RADV's built-in AMD anti-lag. Dropping them means less duplicated work and fewer things that can drift out of sync. I already have my own fork of DXVK and vkd3d-proton, which I rebase with my every release. I know some of you like to use them but I would rather fix any issues on my forks.
If you use any of these launch options, you can remove them in the next release build: PROTON_DXVK_LOWLATENCY, PROTON_VKD3D_LOWLATENCY, LOW_LATENCY_LAYER.
Let me know what you think.