Innoactive Spatial Runtime – Processes and Networking Overview

Innoactive Spatial Runtime

Process
C:\ProgramData\Innoactive\Spatial Runtime\Innoactive Spatial Runtime.exe

Networking

• TCP (Inbound): 42084

Explanation

• Coordinates connections from:

  • Application plugins

  • Client applications

• Listens on TCP port 42084

• Starts and stops CloudXR runtime via NvStreamManager.exe

• IPC communication with NvStreamManager via named pipe

2. NvStreamManager

Process
C:\ProgramData\Innoactive\Spatial Runtime\CloudXR\NvStreamManager.exe

Networking

• None

Explanation

• Provided by NVIDIA

• Manages CloudXR lifecycle and coordination

• IPC communication:

  • With CloudXrService (named pipe)

  • With Innoactive Spatial Runtime (named pipe)

3. CloudXrService

Process
C:\ProgramData\Innoactive\Spatial Runtime\CloudXR\CloudXrService.exe

Networking

TCP (Inbound):

• 48010

• 48322

UDP (Inbound):

• 47998

• 47999

• 48000

• 48002

• 48005

• 48008

• 48012

Explanation

• Provided by NVIDIA

• Core CloudXR runtime service

• IPC communication with NvStreamManager via named pipe

• Official NVIDIA network documentation:
  https://docs.nvidia.com/cloudxr-sdk/latest/requirement/network_setup.html

4. VRED Plugin (or Other Application Plugin)

Process
Plugin running inside VRED (or other supported applications)

Networking

• TCP (Outbound): 42084

Explanation

• Connects to Innoactive Spatial Runtime via TCP port 42084

• Enables:

  • Application registration with Spatial Runtime

  • Client discovery

  • XR mode activation when triggered by runtime

VRED Web Interface

Protocol: TCP
Port: 8888

Purpose:
Used to access VRED Web Interface.