Innoactive Spatial Lessons Learnt

This article summarizes common setup issues observed when working with Innoactive Spatial ecosystem. Use these lessons to avoid typical runtime and initialization conflicts.

Installation Blocked by Windows Policy (OpenXR Service)

Context
During installation, installer may fail when attempting to install OpenXR service. This typically occurs in restricted corporate environments with Windows group policies blocking system service installation.

Symptoms
Installer gets stuck during OpenXR service installation step.

Root Cause

• Windows policy prevents installation of system services.

Resolution

1. In installer, untick feature “OpenXR Service.”

2. Continue installation.

3. Runtime and VRED plugins will install without service component.

4. If OpenXR runtime is not active, Spatial Runtime will prompt user on startup.

Important
OpenXR service is only required to set active OpenXR runtime without admin privileges. Runtime itself installs independently and works without service.

Conflicting OpenXR Layers and Duplicate Plugins

Context
Connection instability and runtime conflicts were observed during startup.

Root Cause

• VIVE OpenXR API layers installed (unsupported by CloudXR).

• Legacy CloudXR script plugin present.

• Multiple Innoactive plugins loaded from different directories.

Resolution

1. Uninstall unused VIVE OpenXR API layers.

2. Remove legacy CloudXR script plugins.

3. Ensure only one Innoactive plugin is installed.

4. Delete duplicate plugin folders from user ScriptPlugins directory.

Avoid multiple OpenXR runtimes, legacy CloudXR integrations, and duplicate plugins. Only one active runtime and one Innoactive plugin installation should exist.

Varjo Native Foveated Rendering Causing Visual Artifacts

Context
A visible square or different display area appeared in Apple Vision Pro while connected to VRED.

Root Cause
In VRED under Preferences → Extended Reality → XR Options → Varjo, option Native Foveated Rendering was enabled.

Resolution

1. Open VRED.

2. Go to Preferences → Extended Reality → XR Options → Varjo.

3. Disable Native Foveated Rendering.

4. Restart session.

Disable Varjo-specific rendering features (e.g., Native Foveated Rendering) when using CloudXR to avoid visual artifacts.

CloudXR Not Starting – Varjo Base Blocking Vulkan

Context
Varjo Base can reserve Vulkan resources on GPU, preventing CloudXR from initializing.

Symptoms
Streaming session fails or CloudXR does not start.

Resolution

1. Check if Varjo Base is running on workstation.

2. Fully close Varjo Base (including background processes).

3. Restart Innoactive Spatial Runtime.

4. Start streaming session again.

CloudXR should initialize correctly.

Unreal Engine – “VR Preview” Greyed Out

Context
Unreal Engine requires active XR runtime before enabling VR Preview.

Symptoms
“VR Preview” option is disabled.

Resolution

1. Exit Unreal Engine.

2. Start streaming session on Apple Vision Pro.

3. Verify Innoactive Spatial Runtime shows runtime as started.

4. Launch Unreal Engine.

5. Open project and select VR Preview.

VR Preview should now be available.

TestFlight UI Delay After Update

Context
After triggering update in TestFlight, UI may take 10–20 seconds to refresh.

Symptoms
Update button appears unresponsive.

Resolution

1. Click update in TestFlight.

2. Wait up to 20 seconds.

3. Do not close or force-quit app during update.

This delay is expected and not related to Spatial Runtime.

Outdated GPU Drivers Causing Runtime Issues

Context
CloudXR and Vulkan-based workflows depend on up-to-date GPU drivers.

Symptoms
Runtime crashes, streaming instability, initialization errors, or degraded performance.

Resolution

1. Check installed GPU driver version (NVIDIA Control Panel or Device Manager).

2. Download latest recommended production driver from GPU vendor.

3. Perform clean driver installation.

4. Reboot workstation.

5. Restart Innoactive Spatial Runtime and test session again.