Describe the bug
I am reporting two bugs here but one of them I was able to find a workaround for. For some strange reason, on my Arch Linux, Wayland setup, SteamVR decides to set the RADV_FORCE_FAMILY env, causing the mesa drivers to see the gpu as null, and thus, DXVK and other graphics related programs all fail catastrophically. Through the help of some very talented individuals on discord, I was able to compile custom drivers to ignore this environment variable.

After finally getting SteamVR to run after many hours, I was unfortunately greeted by something that I do not believe I am capable of fixing. The game audio streams to my headset and the SteamVR lobby runs great, but the game never starts. The game runs on my desktop just fine, but where the game is supposed to show, there is just a pixelated mess!
The video of this strange behavior is here

To Reproduce
Steps to reproduce the behavior:

1. Get a clean install of Arch Linux, with KDE Plasma and set the compositor to wayland.
2. Add the enableVukanAsync flag to false as indicated by other issues on this github.
3. Try to launch a game as a baseline.
4. Launch SteamVR (In my case ALVR was used as an intermediate to connect the headset to SteamVR, but does not explain this behavior)
5. Attempt to launch a game either from Steam itself or from the menu in the SteamVR lobby.
6. Witness very strange graphical artifacting and a failure of the SteamVR lobby to transition to the game itself.

Expected behavior
SteamVR is expected to not set the flag RADV_FORCE_FAMILY on a system with an AMD gpu.
SteamVR is also expected to show the game in high resolution while it is loading, and to transition into the game once it is finished loading.

System Information (please complete the following information):

• Distribution: Arch
• SteamVR version: 1.24.6
• Steam client version: Nov 17, 2022 at 02:45:32.
• Opted into Steam client beta?: No
• Graphics driver version: [run nvidia-settings or vulkaninfo | grep driverInfo:

[drew@archlinux ~]$ vulkaninfo | grep driverInfo
        driverInfo      = Mesa 22.2.3
        driverInfo                                           = Mesa 22.2.3
[drew@archlinux ~]$ 

DISCLAIMER: As mentioned before, I am running a custom driver to circumvent the RADV_FORCE_FAMILY environment variable. This mesa driver is identical to the upstream 22.2.3, with only a single line change to bypass the fatal errors.

https://gist.github.com/DrewRidley/e76b8120de2f2db3833ce12e9e1e8fbf