The Innoactive Spatial Runtime

What the Spatial Runtime is, the processes it installs on your RTX workstation, and how it streams Autodesk VRED to Apple Vision Pro.

The Innoactive Spatial Runtime is the Windows service stack that streams your Autodesk VRED scene from an RTX workstation to an Apple Vision Pro. Immersive for Autodesk VRED and the full Innoactive Spatial edition use the same runtime — install once and both editions of the Vision Pro app can connect to the workstation.

This article gives you the operational picture: what gets installed, which processes run, and how they talk to each other and to the headset. For pure firewall configuration see Ports to whitelist on the workstation firewall.

Download

Always pull the latest installer from spatial-runtime.innoactive.io. The page redirects to the current signed .msi.

Compatibility (Immersive 1.0.x)

  • Innoactive Spatial Runtime 2.0.x or newer
  • Autodesk VRED Pro 2026 / 2027
  • Apple Vision Pro on visionOS 26 or newer
  • NVIDIA RTX GPU with current production driver

What the installer puts on the workstation

ComponentDefault pathRole
Innoactive Spatial Runtime (tray app)C:\ProgramData\Innoactive\Spatial Runtime\Coordinator. Discovers headsets, starts CloudXR, exposes the REST API used by the VRED plugin.
CloudXR binaries (NVIDIA)C:\ProgramData\Innoactive\Spatial Runtime\CloudXR\NvStreamManager.exe, CloudXR Runtime Host.exe, CloudXrService.exe — handle the actual video / audio / control streams.
OpenXR Runtime ServiceC:\Program Files\Innoactive\OpenXR Runtime Service\Windows service running as LocalSystem that lets standard users switch the active OpenXR runtime without admin rights.
VRED pluginVRED's script plugin directoryAdds the Innoactive XR button to the VRED toolbar and exposes variant sets, render mode, and quality controls.

The OpenXR Runtime Service is optional — you can untick it during installation if Windows group policy blocks system services. The runtime will then prompt for an OpenXR runtime switch on startup instead.

Process map

Apple Vision Pro                       Workstation
─────────────────                      ─────────────────────────────────
Immersive for                          ┌──────────────────────────────┐
Autodesk VRED        ◀────────────────▶│ Innoactive Spatial Runtime    │
  (visionOS)         REST + WSS +      │   (tray app, REST API,        │
                     mDNS + CloudXR    │    Bonjour, signaling)        │
                                       └──────┬─────────────┬──────────┘
                                              │ named pipe  │ named pipe
                                              ▼             ▼
                                       ┌──────────────┐ ┌──────────────┐
                                       │ NvStream     │ │ Innoactive   │
                                       │ Manager.exe  │ │ OpenXR       │
                                       │ (NVIDIA)     │ │ Runtime Svc  │
                                       └──────┬───────┘ └──────────────┘
                                              │ named pipe
                                              ▼
                                       ┌──────────────────────────────┐
                                       │ CloudXR Runtime Host.exe OR  │
                                       │ CloudXrService.exe (NVIDIA)  │
                                       │  — only one is active        │
                                       └──────────────────────────────┘
                                              ▲
                                              │ TCP 42084 (Python-API-style REST)
                                       ┌──────┴───────────────────────┐
                                       │ VRED Plugin (inside VRED Pro)│
                                       └──────────────────────────────┘

Only one of CloudXR Runtime Host.exe or CloudXrService.exe owns the CloudXR media ports at a time:

  • CloudXrService.exe when streaming uses Apple's Foveated Streaming Sessions framework (dynamic foveation).
  • CloudXR Runtime Host.exe when streaming uses static foveation.

How a session starts

  1. You click Innoactive XR in the VRED toolbar. The plugin opens a TCP connection to the Spatial Runtime tray app on 127.0.0.1:42084.
  2. The runtime advertises the workstation on the local subnet via Bonjour / mDNS (service type _innoactive._tcp, multicast 224.0.0.251:5353).
  3. The Apple Vision Pro app discovers the workstation and lists it.
  4. You pick the workstation on the headset and approve the session.
  5. The runtime hands off to NvStreamManager, which starts the right CloudXR host. Video, audio, and tracking flow over UDP to the headset.
  6. Variant sets, render mode (ModelOnly vs FullScene), graphics API (OpenGL / Vulkan / GPU Raytracing), super sampling, and DLSS (VRED 18.2+) are controlled live through VRED's Python remote API at https://<workstation>:8888/pythonapi.

If the runtime tray icon shows the workstation as stopped, no Bonjour record is published and no headset will see it.

Operational notes

  • Local network only. All streaming traffic stays on the local subnet. No internet egress is needed for the session itself (sign-in and update checks aside).
  • mDNS / multicast must be allowed. Enterprise switches that block UDP multicast to 224.0.0.251:5353 will break discovery — the headset will simply see no workstations.
  • Driver freshness matters. CloudXR is sensitive to GPU driver versions; install the latest NVIDIA production driver after a clean uninstall of older drivers.
  • Varjo Base conflicts. If Varjo Base is running it can reserve Vulkan resources and prevent CloudXR from starting. Quit it fully before launching a session.
  • Only one OpenXR runtime. Multiple OpenXR runtimes or stale VIVE / legacy CloudXR layers will cause instability. Keep one runtime active.

When something doesn't connect

Check, in order:

  1. Runtime tray app is running and shows "Started". If not, restart it; if the OpenXR runtime is not active it will prompt you.
  2. Firewall rules. See Ports to whitelist on the workstation firewall and confirm Innoactive Spatial Runtime.exe, CloudXR Runtime Host.exe, and CloudXrService.exe are allowed.
  3. Headset and workstation on the same subnet. Guest Wi-Fi networks and client isolation will break discovery.
  4. VRED Python API reachable on https://<workstation>:8888/pythonapi. If not, variant sets will be empty even when streaming works — look for httpsPortUnreachable errors in the headset logs.
  5. Logs. Capture them with the steps in How to obtain debug logs from Innoactive Spatial app before contacting support.