pal1000

Results 288 comments of pal1000

> I’m not really sure what to do from here, but I’m hoping you will forward this to those who might be able to solve it? [Done](https://gitlab.freedesktop.org/mesa/mesa/-/issues/6801).

Unfortunately no, but I'll re-test to see if anything changed soon.

Post upstream directly : https://gitlab.freedesktop.org/mesa/mesa/-/issues Make sure you specify driver used. Also GLonD3D12 from MSVC package can use GPU.

When using MSVC package GLonD3D12 is used by default if you are on Windows 10 v19041.488 or newer and you have a D3D12 capable GPU. You can try it with...

Note that RADV isn't very useful on Windows yet as WSI isn't in place yet, You can look at #83. The short gist is to set `VK_ICD_FILENAMES` environment variable value...

Note that VK_ICD_FILENAMES only accepts absolute paths. Also @jpark37 may be able to answer to this as he's the one making the port to Windows.

I actually have logic [fixing the JSON for both RADV and lavapipe post build](https://github.com/pal1000/mesa-dist-win/blob/master/buildscript/modules/fixvulkanjsons.cmd) as I know they were both kinda broken from day 1. Lavapipe has absolute path in...

> Just to experiment, I renamed OpenCL.dll to OpenCL.dll.bak and MesaOpenCL.dll to OpenCL.dll. That's a bad idea because MesaOpenCL.dll is an ICD that needs to be loaded by official Khronos...

Copy `libgallium_wgl.dll` and `libglapi.dll` in `C:\Program Files\MESA` and then remove those 4 files from Dvinci Resolve folder. If this still doesn't work we are kind of screwed.

> So it must mean Resolve 15 is coded in such a way as to need to see a physical GPU card. Precisely, it demands a CL GPU type device,...