pal1000

> Not sure if that means that Windows will not support OpenCL at all for the future Windows has CLonD3D12 driver but it may have stopped working with switch to...

Using CLonD3D12 works the same way it worked with clover ICD (`MesaOpenCL.dll`). CLonD3D12 ICD name is `openclon12.dll`.

Registering OpenCL or Vulkan drivers in general doesn't involve copying files over to program folder at all, instead it works by writing to registry or setting environment variables that point...

I recommend you to just extract mesa-dist-win release package somewhere and then the paths to CLonD3D12 driver would be `\bin\x64\openclon12.dll` and `\bin\x86\openclon12.dll` respectively. For Vulkan and OpenCL drivers you don't...

[Vulkan runtime](https://vulkan.lunarg.com/sdk/home#windows) is packaged an excusable installer. Just run it as it's unpacked in Windows\System32.

I got crash with Luxmark 3.1 and CLonD3D12 as well so it's not just you. Try collecting a call stack (MSVC) or backtrace (MinGW). Help yourself with debug packages. Report...

Try 24.0.3. I updated CLonD3D12 ICD to include fix for microsoft/OpenCLOn12#58

If you mean the compatibility profile that's used by default by most Windows programs, it got further. lllvmpipe supports OpenGL 4.5. zink and d3d12 might still be around OpenGL 3.1.

How to proceed depends on your AV so I can't give precise instructions about that. Also the build script usage document has seriously bitrotted. I didn't have time to update...

Well you try. First deploy Mesa3D with per application deployment tool, then set environment variable `GALLLIUM_DRIVER` to `zink`.