Dzmitry Malyshau

I haven't investigated this myself in depth yet. What I see is that a lot of time is spent between in `indirect()` itself, outside of the payload (the library code)...

For everybody having `ERROR_INITIALIZATION_FAILED` or `NotSupportedError`, could you please: - make sure Vulkan is installed. If you can run `vkcube` from vulkan-tools, there is a high chance you'll be able...

@AA1999 looks like you are getting a build error, which is something entirely different from the Vulkan (runtime) error in the subject. Let's discuss/resolve it in a different issue, please.

@aohanhongzhi @K0IN this sounds like our old issue https://github.com/kvark/blade/issues/88 Could you provide the contents of "/etc/prime-discrete" on your system if you have it?

@aohanhongzhi could you also do the following please: - post/attach `nvidia-smi` output - run `vkcube-wayland` and see if it works @flukejones what do you make of this case?

Interesting. The only relevant bits of the change are related to raw-window-handle update.

Discussed this [on discord](https://discordapp.com/channels/869392257814519848/1204679850208657418/1210840532381728808) and got a better understanding about how `calloop` fits in. I think it's a good direction, thanks @tadeokondrak for explanation. Please rebase the PR and address...

Just needs a driver update to pick up "VK_KHR_dynamic_rendering". Your 470 driver is 3 year old.

> doesn't that mean that my GPU is not supported? Technically, no. This extension is not about GPU capabilities. It's about driver capabilities. > I just checked compatibility and it...

I tested this when integrating Blade. The Send/Sync story is solvable on Zed side: OpenGL doesn't like us talking to it from different threads. The bigger issue is the use...