If you wouldn't mind, it shouldn't be hard to wire up these in d3d via https://learn.microsoft.com/en-us/windows/win32/api/dxgi/ns-dxgi-dxgi_adapter_desc which has all this info.

If you're feeling extra crazy, you could also wire this up on GL via https://registry.khronos.org/OpenGL/extensions/EXT/EXT_external_objects.txt, but not touching that one is also understandable lol.

@tychedelia Can you clear up the CI failures? We generally don't start reviewing PRs until CI likes them.

@tychedelia Can you clear up the CI failures? We generally don't start reviewing PRs until CI likes them.

Yes, apologies was just (slowly) doing @cwfitzgerald's suggestion.

I've removed Uuid as there doesn't appear a way to do this in the Windows API. But the bus ID is sufficient for a stable identifier and probably more useful anyway.

Is the Luid in the adapter info not the same? I thought that was how you matched devices when doing cross api interop.

Is the Luid in the adapter info not the same? I thought that was how you matched devices when doing cross api interop.

I am not super familiar with these APIs but the docs here suggest it's not valid across restarts, which limits its usefullness relative to the Uuid provided by Vulkan.

https://learn.microsoft.com/en-us/windows/win32/api/d3d12/nf-d3d12-id3d12device-getadapterluid