Proposal: DisplayXR for SideFX Houdini (HDK adapter on the shared host core, dedicated 3D window; Leia SR tested) #2432
joehillthunder
started this conversation in
Ideas
Replies: 1 comment
Readiness on the released runtime: Pass (2026-10-28)Plain
Not tested: Send to Omniverse (needs an Indie or commercial licence; Apprentice writes |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Houdini has no OpenXR mode, so it can't run as a hosted legacy app. It runs as a thin in-process HDK adapter in the dedicated-3D-window class, on the same app-neutral host core as the MotionBuilder (#2423) and Nuke adapters.
Code:
joehillthunder/displayxr-houdini@553494d(private, Apache-2.0 + NOTICE; internals insrc/core/coupling.h). Tested on Houdini 22.0.466 (Apprentice), Windows 11, Leia SR as the tested display.What it does
XR_DXR_win32_window_binding. It weaves there next to other 3D apps by construction; F11 gives the full panel. Status text reads "3D active" / "3D off".XR_DXR_display_info.DXR_HostedDepthRel./WorlddefaultPrim, remapped paths, relative textures. It passes 28/28 tests andusdchecker. Under the Apprentice licence, Houdini's USD ROP writes.usdnc, so the tool refuses with a clear message rather than working around the licence.Measured
Renderer caveat
The eyes are rendered with Karma (XPU when the GPU is free, otherwise CPU), because Houdini VK's
HUSD_Imaging::render()fails offscreen. So the 3D updates only about 1–2 times per second while the camera moves. It's fine for review, but not yet viewport speed.What the shared host library needs (from this adapter)
VK_KHR_external_memory_win32. An offscreen Vulkan render path in Houdini would remove the Karma limit.Platforms
Pending
🤖 Generated with Claude Code
All reactions