Which InteropType is best

[jodysowald]

I noticed that externalObject interop types are preferred automatically over NV_DX. Is this purposeful?
As I try the various interop types, i see significantly better performance from WGLDXInterop and Blit compared to ExternalObjectsD3D, nearly double the FPS. Is this unique to my project or is there a purpose to selecting for the ExternalObject approach over others?

[jodysowald]

Actually on further usage, I'm occasionally seeing tearing issues with NVDX_INTEROP when my canvas is big and my render is fast. I don't see this issue with Blit or external object. So maybe its not reliable or maybe its a concurrency concern?

[husker-dev]

Blit uses "downloading" of each frame to RAM, and "sending" it back to the GPU. This is very inefficient, because both CPU and RAM are used.

In the case of WGLDXInterop (NV_DX), this can be avoided, because there is a regular copy from one GPU buffer to another, without CPU and RAM.
But this is an NVidia extension, and other vendors may not implement it, or do it with problems (hello AMD).

externalObject is almost an alternative to NV_DX, but it works through Vulkan, and is a standard. It also does not use CPU and GPU, and according to my tests it showed greater efficiency than NV_DX.

[husker-dev]

For Windows and Linux the best interop type is externalObjects. For MacOS - IOSurface.
WGLDXInterop and Blit are used as fallback.

[jodysowald]

Interesting. I suppose I'll need to to test why external object isn't as performant for me. Thank you.

…

On Thu, Sep 4, 2025, 5:05 PM Nikita Shtengauer ***@***.***> wrote: *husker-dev* left a comment (husker-dev/openglfx#114) <#114 (comment)> For Windows and Linux the best interop type is externalObjects. For MacOS - IOSurface. WGLDXInterop and Blit are used as fallback. — Reply to this email directly, view it on GitHub <#114 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BEUFYG6A7NHBCE43W4LKH6L3RCSRXAVCNFSM6AAAAACFVB6KVOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENJVGY3TAMBRGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Visit LaserLinc at any of these upcoming events <https://laserlinc.com/events/>