pal1000
pal1000
> Does your build using ORC JIT by default? No. It's still very experimental, has no upstream CI coverage and fails static linking. The last is fatal for MSVC build...
Do you something attached that uses your sound card? > does the store know about my mainboard and fetch a customized installer?). Realtek Audio console detects motherboard vendor from first...
Remove `RealtekHSA` folder from `Realtek-UAD-generic\Win64\Realtek` but if Realtek audio console fails to start afterwards you'll have to install the latest RealtekHSA and then update from [Windows store](https://www.microsoft.com/store/productId/9P2B8MCSVPLN) or offline package...
You should try collecting a call stack with MSVC, Windbg or x64dbg. Debug info package will help.
- Deploy Mesa via per app deployment tool; - set environment variable `GALLIUM_DRIVER` value to `zink`; - Make sure Nvidia Vulkan driver is used instead of integrated graphics'.
> Deploy Mesa via per app deployment tool Somehow you are failing this step. Check if there is a file named `libgallium_wgl.dll` in same folder as `gpu_caps_viewer.exe`. If it's there...
You need to run per app deployment tool. You just copied `libgallium_wgl.dll` over. Here is how folder content should look. See symbolic links with shortcut icon arrow. 
Mind reporting [upstream](https://gitlab.freedesktop.org/mesa/mesa/-/issues).
You probably need to register Mesa3D OpenGL ICD to Microsoft Remote Display Adapter. Unfortunately I don't know the howto or even if it's doable in the first place.
1. Deploy dzn or lvp drivers, see Vulkan drivers deployment section [here](https://github.com/pal1000/mesa-dist-win?tab=readme-ov-file#usage-notes); 2. Deploy Mesa OpenGL driver for program you want to use zink driver with; 3. Select zink driver...