GPU Interop Sample Issue?

[dbriard]

Hi everyone,

I wanted to have a look at Vulkan in .NET and remember you had a GPU Interop Sample, but unfortunatly it doesn't work as expected.

Here what I see when I run the sample :

It seems to be a refresh issue. If I move a slider to refresh, or if I run the animation, I got the correct display:

Hovewer, if I resize the windows, I got the problem again.

The problem is only with Vulkan, I tried the D3D11 version of the sample and no glitches.

1. Anyone know how to fix the Vulkan sample? or if there is another sample around with Vulkan or D3D12 integration?

2. This sample require both SharpDX and Silk.NET, are both really needed for Vulkan?

Thanks in advance.

[llfab]

The sample works on my Windows 11 both with Intel and Nvidia. For Windows the SharpDX is needed because the GPU interop uses texture sharing. This works through OpenGL/angle with a shared DX texture provided to the vulkan renderer.

The sample uses Silk.net for the Vulkan bindings but you can use any vulkan bindings also your own. We use our own bindings for our Vulkan 3D renderer and use the GPU Interop for texture sharing.

For Linux I don't know. It is supposed to work for Linux but we found a blocker some time ago which is not fixed yet.

[llfab]

Try setting Rendering Mode to OpenGL:

instead of vulkan

[dbriard]

Hi @llfab ,
Thanks a lot for the tips, there is no issue with AngleEgl!

May I ask two more things?
Is there a trade-off compared to the Vulkan backend?
Is this parameter only for AvaloniaUI, independently of the Vulkan surface?

[llfab]

There is a bit of trade-off. 1st from a complexity perspective: it needs some available extensions from vk (which are available on all kind-of-recent machines also on Intel) and the wiring for sharing the angle texture needs all three on Windows Vk, Dx, angle. There may also be a performance thing but we never saw problems below 60 fps.

We actually financed the development to be able to run Avalonia on Vulkan. However, we found no drawbacks for using Gpu Interop on OpenGL ES/angle basis and can rely on Avalonia on OpenGL which is proven and tested for much longer.

The above parameter really is for Avalonia only. Again, our 3D renderer is completely independent of Avalonia in its internals and all wiring for the 3D is under our control. Only, were our 3D renders into the shared texture including synchronization, there is interaction.