Innoactive Spatial Runtime Lessons Learnt
This article summarizes common setup issues observed when working with Innoactive Spatial Runtime. Use these lessons to avoid typical runtime and initialization conflicts.
1. 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
Check if Varjo Base is running on workstation.
Fully close Varjo Base (including background processes).
Restart Innoactive Spatial Runtime.
Start streaming session again.
CloudXR should initialize correctly.
2. Unreal Engine – “VR Preview” Greyed Out
Context
Unreal Engine requires active XR runtime before enabling VR Preview.
Symptoms
“VR Preview” option is disabled.
Resolution
Exit Unreal Engine.
Start streaming session on Apple Vision Pro.
Verify Innoactive Spatial Runtime shows runtime as started.
Launch Unreal Engine.
Open project and select VR Preview.
VR Preview should now be available.
3. 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
Click update in TestFlight.
Wait up to 20 seconds.
Do not close or force-quit app during update.
This delay is expected and not related to Spatial Runtime.