Hi, I’m working on upgrading our kit app that streams Omniverse content to Apple Vision Pro from kit 106 to kit 109 and have some issues getting the CloudXR / OpenXR runtime working.
Idk if there is any recent guide available on what exactly we’re supposed to do, in kit 106.5 the runtime was integrated to the Omniverse extensions but apparently not anymore.
I found the just today released 6.0.2 version of the CloudXR runtime on NGC and downloaded it, and I’m trying to put the openxr_cloudxr.json there as the custom OpenXR runtime in Omniverse XR Experience or whatever the extension is called in the latest version, just appears as “XR” tab.
On attempting to “Start XR” I get the following error:
2026-01-14T14:28:27Z [604,605ms] [Error] [omni.kit.xr.ui.window.viewport.xr_components.xr_viewport_layer_component] Failed to activate OpenXR: XR_ERROR_RUNTIME_FAILURE
ERROR [ipc_connect_pipe] Connect to \.\pipe/tmp/ipc_cloudxr failed: 2 The system cannot find the file specified.
ERROR [ipc_client_connection_init] Failed to connect to monado service process
Please make sure that the service process is running
It is called “monado-service”
In build trees, it is located “build-dir/src/xrt/targets/service/monado-service”
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : LoaderInstance::CreateInstance chained CreateInstance call failed
Error [GENERAL | xrCreateInstance | OpenXR-Loader] : xrCreateInstance failed
I’ve also got some old (kit 105 maybs or 106.0) version of the runtime which does have a “cloudxr-service.exe” inside it that Iirc had to be running in the background. However the 6.0.2 zip just has the DLLs and stuff inside, no executable. Also no README to explain anything…
Any guidance or pointers to up-to-date documentation on how to run XR in kit 109 would be much appreciated.
Okay, I think I got it running now by tinkering with the CloudXR Stream Manager also available in NGC, but my AVP app doesn’t connect. I probably need to update the client library to matching version and do some refactoring in the app to get it to work.
Is there plans to integrate the runtime to the XR experience again somehow or into the avp bundle extension or something? Setting up the runtime is way too much hassle for our users who just want to hit Start XR and be able to use the app.
@juho.kostet How were you able to get it working? I set the value of the StreamManager pipe to what OV is expecting. When I click “Start XR”, OV just hangs.
Curious about this too, @Richard3D do you know if there’s been changes to how you’re supposed to connect to this headset in Kit 109? I can’t find any updated instructions for Apple Vision Pro.
As far as I know there should be no difference in how we do streaming to AVP. It’s the same set of extensions. But for my help you need to be posting in the correct forum area. In Omniverse > Core Platform
@eisen.montalvo I’ve not got the client to connect yet but at least OV doesn’t hang to throw OPENXR_RUNTIME_FAILURE anymore. Apparently there are some a bit simpler StreamManager instructions here: Stream Manager — NVIDIA CloudXR SDK.
@michael.easter1 I guess this should be up to date for 6.0.2 (and presumably work with kit109): Your First CloudXR Client for visionOS — NVIDIA CloudXR SDK
@Richard3D I don’t really see why the core omniverse category would be more appropriate when this has to do with the XR category and the cloudxr specifically..
I built the “generic cloudxr viewer” for AVP from GitHub - NVIDIA/cloudxr-apple-generic-viewer: Sample app using CloudXR Framework for Apple clients. to rule out any old code in our own app, but even this fails to connect to the USD Composer built from the kit109 template.
Looks like it does get somekind of connection on port 443 first and starts setting up the streaming, but then fails the “RTSP handshake (error code: 0X800B1004, NVST_R_ERROR_UNEXPECTED_DISCONNECTION_INITIAL) on port 48010.
I do have inbound TCP on the port (+ the required UDP ones) allowed on the PC running the server, and I’ve got it working with the past versions: cloudxr package 1.0.0 (or 1.0.1) and kit 106.5, so it shouldn’t be an issue with the firewall…
@michael.easter1 @eisen.montalvo Okay, so it appears that there is still indeed an Omniverse extension that has the integrated runtime and one doesn’t have to setup the external one and have it fail for no apparent reason like.
Idk why but for kit 109.0.2 I was getting incompatible versions:
```
[Error] [omni.ext.plugin] Failed to resolve extension dependencies. Failure hints:
- No versions of omni.kit.xr.cloudxr that satisfies: foo.bar-0.1.0 depends on omni.kit.xr.cloudxr version *
- Available packages for omni.kit.xr.cloudxr version *:
(none found)
Platform incompatible packages:
- omni.kit.xr.cloudxr-6.0.4+109.0.2.lx64.d.cp312 (registry)
- omni.kit.xr.cloudxr-6.0.4+109.0.2.wx64.d.cp312 (registry)
- omni.kit.xr.cloudxr-6.0.4+109.0.2.wx64.r.cp312 (registry)
- omni.kit.xr.cloudxr-6.0.4+109.0.2.lx64.r.cp312 (registry)
Synced registries:
- kit/default : found 0 packages (couldn’t connect or empty)
- kit/sdk : found 0 packages (couldn’t connect or empty)
- kit/prod/default : found 640 packages
- kit/prod/sdk : found 376 packages
```
Then rebuilding the app with 109.0.3 finally worked and the external runtime setup was not required.
@Richard3D maybe you can pass some greetings to the Omniverse side that it would be much appreciated if Nvidia would:
-
Publish any actually useful documentation for the XR modules to explain how the systems are built (e.g. to get an understanding on how to build a custom XR tool and assign it to a controller button or other event without doing weird hacks).
-
Included XR changes in the kit SDK changelogs or any other relevant places, maybe even included deprecation warnings between version before actually removing stuff or moving it around to different modules. There is rarely ever anything in the changelogs or migration guides even though even minor versions of the SDK (like 106.0 → 106.5) include breaking changes..
Same scenario for me with Kit 110.0, Available packages for omni.kit.xr.cloudxr version *:
(none found)
I have to build with Kit 109.0.3
I succeeded with doing Meta Quest 2 VR with Omniverse USD composer template running on a cloud VM, I am yet to figure out how to implement the XR+Streaming on OKAS,