10:04 <chloekek> Hi, I’m wondering if Zink is suitable for packaging with an application (both libGL.so and libzink_dri.so), and having it use the OS-provided Vulkan loader. The reason I’d like this is twofold: having a only one OpenGL implementation to worry about, and being able to use GL_ARB_sparse_{buffer,texture} on Intel and with RenderDoc. Is this supported at all, and will {glX,wgl}CreateContext create a Vulkan device

10:04 <chloekek> and surface?

10:51 <chloekek> It would be great if GLX could be bypassed entirely and directly supplying a VkSurfaceKHR

12:29 <kusma> You could always set $LIBGL_DRIVERS_PATH to point to where you have libzink_dri.so, I think...

12:31 <kusma> On Windows, this is a bit worse. The WGL implementation in mesa is kinda lacking, so some applications needs proper WGL (for stuff like font outlines etc). But using the proper WGL implementation requires the driver to be registered, which is a windows registry thing, and... uh, that'll interfere with other applications...

12:32 <kusma> If you can live without full WGL, just stuff build OpenGL32.dll and put it in the right library search path ;)

12:51 <zmike> sparse binding isn't supported in any way on ANV

13:33 <zmike> can I get a couple quick acks on https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20867 and https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20791

14:17 <kusma> zmike: Done!

14:17 <zmike> thx!

15:36 <chloekek> zmike: I thought sparse binding was a required feature of Vulkan, but now I see VkPhysicalDeviceFeatures::sparseBinding exists and it can be false lmao. Thanks.