Optimize the network for local streaming

Router placement, Wi-Fi channel choice, firewall configuration, and Vision Pro settings that keep a local Innoactive Spatial session stable.

These recommendations apply to local streaming setups between a CloudXR server workstation and one or more Apple Vision Pro headsets.

Start with a wired workstation

Connect the workstation by Ethernet to the local network and the headset by Wi-Fi to its access point. Keep them on the same local subnet for the standard discovery setup, with client isolation disabled for the intended devices. The workstation does not need to join the headset's Wi-Fi. This follows NVIDIA's wired-server recommendation.

Router recommendations

Position of the routers

  • Position the routers at 2 meter level (to avoid body water-bag effect) and 2 to 3 meters distance from the main play space
  • Position the router at least 30 cm from a wall or any reflective surface, avoid corners (to avoid multi-path interference)
  • Never put the router on the floor (the antenna radiation pattern is horizontal + downwards)
  • Never put the router on the workstation
  • When using several routers, position them at opposite sides of the space, not next to each other
  • Try to have 3 meters plus between two Apple Vision Pros (for MIMO spatial diversity to work)

Type of router(s)

For a single Apple Vision Pro
  • Wi-Fi 5 is sufficient as long as there is no other device connected to the router and no interference on the channel
  • Classic 1 × 5 GHz band capable is sufficient
For two or more Apple Vision Pros
  • Wi-Fi 6 router is strongly recommended
  • 2 × 5 GHz channels capable

Router key settings

5 GHz channel selection

For a controlled local-streaming setup, test a locally permitted non-DFS channel to avoid radar-triggered channel changes. Ask IT to check access-point logs if a channel change coincides with a freeze. Available channels and transmit-power limits depend on the country, equipment, and deployment; use the access point's correct regulatory region and manufacturer guidance rather than a universal channel/power table.

NVIDIA suggests testing channels 44 or 149, where available, for periodic latency spikes associated with Apple Wireless Direct Link (AWDL). This is a targeted troubleshooting option, not evidence that every freeze is caused by channel hopping. See NVIDIA's troubleshooting guidance.

For several access points, have IT plan non-overlapping channel blocks for the chosen channel width. Different primary-channel numbers can still occupy the same wider channel block.

Band and channel width

  • Select a band supported by the actual headset model and deployment. For the 5 GHz setup covered here, verify that the headset actually connects on 5 GHz.
  • Treat 80 MHz as a setting to evaluate in a controlled streaming setup, not a universal requirement. Compare stability and throughput in the actual radio environment with IT.
  • Do not disable 2.4 GHz or 6 GHz throughout the network as a blanket fix. If needed, IT can configure a dedicated test network to control the headset's band without disrupting other devices.

Apple's router and access-point recommendations provide general configuration guidance. Record any departure made for a controlled test and compare the result before keeping it.

Suggested routers

  • Netgear Nighthawk RS600
  • Netgear Nighthawk RS700

Workstation firewall configuration

Ensure your firewall allows communication between the CloudXR server and connected devices. You may need to open dedicated ports and/or whitelist IP addresses — see Ports to whitelist on the workstation firewall for the full list.

Review network and Wi-Fi configuration

Verify the workstation's wired connection and the headset's access point are on the intended local network. Ask IT to check that firewall rules apply to the active Windows network profile. Only classify a network as Private when it is trusted and consistent with your organization's policy.

Retest if performance drops

If streaming performance suddenly degrades, your router may have switched channels. Re-evaluate your setup and manually select another clear channel.

Check for security software interference

Some corporate security or endpoint protection tools can block Innoactive executables or network traffic, preventing local streaming. Common causes include:

  • Standard antivirus or endpoint protection rules.
  • Windows Defender Advanced (Enterprise layer), which can block local UDP traffic even when the standard Defender allows it.

If you notice that executables stop shortly after starting or connections fail to establish, contact your IT administrator to:

  • Whitelist or exclude:

    • In C:\ProgramData\Innoactive\Spatial Runtime\

      • Innoactive Spatial Runtime.exe
    • In C:\ProgramData\Innoactive\Spatial Runtime\CloudXR\

      • NvStreamManager.exe
      • CloudXrService.exe
  • Verify that no network-level policies (such as Defender Advanced) are restricting local connections.

Apple Vision Pro settings

For measured periodic latency spikes, NVIDIA lists disabling Location Services among possible AWDL-related troubleshooting steps. Treat this as a temporary comparison with IT or support: record the original setting, repeat the same workload, and restore it if there is no improvement. Changing it can affect other headset features.

Do not use an on/off Location Services sequence to force a particular country's channel availability, or assume that disabling it eliminates every background scan or stream freeze. Use the correct regional network configuration and investigate timestamps and logs first.