Local Manager Part 3: The PICO-Specific Configuration Layer Most Operators Never Reach
Part of the series: The Operational System Behind Reliable VR Attractions The first two parts of this Local Manager series covered more ground than expected. Part 1 walked through the operational backbone of SynthesisVR’s VR arcade management system — how it unifies PCVR and standalone headset management into a single interface. Part 2 went into the features operators tend to discover only after something goes wrong: the sleep state indicator, Quick View, Spectator View, and the Steam licensing setup that trips up more venues than it should. The feedback from both was consistent. Operators recognised things they had been doing manually for months. A few reached out to say they had not known certain tools existed at all. Part 3 covers the layer above that. Specifically, the PICO Enterprise configuration built into Local Manager, the LBE tab, wireless ADB, map sharing across a headset fleet, Environment Profiles, and PICO Business Streaming. These are the tools that separate a headset fleet management operation running smoothly at scale from one where staff are still walking into the arena to fix headsets between sessions. If you are running PICO 4 Enterprise or PICO 4 Ultra Enterprise headsets, everything in this article is already available to you. Wireless ADB: What It Unlocks and Why It Matters On consumer VR headsets, enabling USB debugging means physically plugging the device into a PC every time it restarts. For a fleet of eight headsets across two arenas, that adds up quickly. PICO Enterprise headsets handle it differently. Open Settings on the headset, go to Developer, then Business Settings, then Lab, and activate Wireless Debugging. Once enabled, Local Manager connects ADB wirelessly with a single click. No cables. No manual intervention per device before each session. That connection unlocks a set of controls that are not available by default in your VR venue management interface: Install APK pushes any application file from your PC directly to the headset, useful for sideloading content or updates outside the standard commercial licensing flow.Uninstall APK removes applications remotely. Restart Headset and Restart SynthesisVR give staff the ability to recover a device from the desk without stepping into the play space, which matters when a group is waiting.View Log pulls diagnostic logs from each headset directly through Local Manager, the support team will ask for these when troubleshooting persistent issues, and having them accessible without physical access to the device saves significant time.Licenses shows every commercially licensed standalone game available to install on that headset, which is the fastest way to provision a new device or recover one after a reset. For any LBE operator managing a multi-headset fleet, these are not advanced features. They are the baseline for running efficiently. The LBE Tab: Fleet Control Built Into Local Manager When a PICO Enterprise headset is registered under a SynthesisVR account, the platform detects the built-in LBE software automatically. The LBE tab appears in the headset settings without any manual activation. For operators coming from consumer headsets or earlier enterprise setups, this is where standalone VR management starts to look genuinely different. The most operationally significant setting is Large Space mode. Disabled by default, enabling it expands the supported tracking area up to 30x30m (98x98ft), the range that free roam titles running in larger arenas require. When you enable it, Local Manager prompts you to name the map before the creation process begins on the headset. Naming maps clearly from the start, “Free Roam 10×10,” “Escape Room 6×6”, pays off when managing multiple configurations across a venue. Beyond Large Space, the LBE tab surfaces several controls that most operators reach only when something goes wrong. Texture Scanning scans the physical environment and returns a real-time quality rating, Good, OK, or Poor, before a map is finalised. Part 2 of this series covered why plain walls undermine inside-out tracking. Texture Scanning is the tool that confirms whether the space is ready before guests arrive, not after a session fails. Hardware button controls allow operators to disable the power button, volume button, back button, and system menu individually on each headset. Disabling these during active sessions is straightforward once configured and prevents the most common source of mid-session interruptions, a player accidentally pressing something they should not have. Screen On/Off, Recenter, and Seethrough Switch round out the remote control options, all manageable from the Local Manager desk without physical access to the headset. Map Sharing: One Calibration, Every Headset Calibrating a boundary map on each headset individually is one of the more time-consuming parts of free roam VR setup. For a ten-headset fleet, doing it manually on each device is an hour of work that can be reduced to minutes. Once you create and calibrate a map on one headset, Export Device Map to Proxy saves it to the Admin PC. From the LBE button in the top right corner of Local Manager, you can push that map to every connected PICO headset simultaneously. All devices share the same boundary. No redrawing. No recalibration per unit. Two things need to be in place before this works correctly. Temporary boundaries must be disabled, and automated streaming must be enabled from Local Manager. If someone deployed the map directly through the PICO Business Suite outside of SynthesisVR, it needs to be removed first, it can overwrite the boundary being managed through the platform and force-close an active session, which is not a recoverable mid-group situation. For venues running multiple space configurations, a larger free roam footprint for evening groups and a smaller setup for daytime walk-ins, deploying different maps to the fleet on a schedule is where the next feature becomes relevant. Environment Profiles: Saving What Works Map sharing handles deployment. Environment Profiles handle the operational layer above it. Once a boundary configuration produces consistent, reliable sessions, a specific map combined with a play area setup and headset configuration that the team trusts, Environment Profiles let operators save that state and restore it without starting from scratch. For VR venues running multiple experience types with different
Week 6: Networking: The Invisible Backbone of Free Roam
Part of the series: From First Headset to Fully Operational VR Arena Week 5 covered the physical layer of a free roam arena: walls, floor plans, and why access point placement should follow player movement rather than cable runs. Week 6 goes deeper into the network itself. Not the theory of WiFi, but the specific failure patterns that appear in live LBE VR operations and why operators so often misdiagnose them before finding the real fix. The network is invisible until it breaks. When it does, what operators usually see is a tracking complaint. Why Networking Failures Feel Like Tracking Issues A player reports that their headset lost position mid-session. The instinct is to check the headset: boundaries, calibration, firmware. In many cases, the headset is fine. The network dropped a packet at the wrong moment, session state fell out of sync between players, or latency spiked past the point where the experience could recover cleanly. The result looks identical to a tracking failure. The cause is completely different. And the fix lives in the network configuration, not the headset settings. This misdiagnosis pattern drives some of the most consistent wasted troubleshooting time across free roam LBE VR operations. The good news is that networking rarely needs constant attention once it is configured correctly. Operators who invest the time upfront to set up their network properly, right band, right access point placement, right roaming configuration, tend to stop thinking about it. The issues that surface for everyone else simply do not appear. Without that foundation in place, operators fix the wrong thing first. Every time. What a Standalone Headset Actually Needs from a Network Before getting into configuration specifics, it helps to be precise about what the network carries. A standalone headset running a free roam VR experience (like the PICO 4 Ultra Enterprise) processes and renders the game locally on the device. WiFi does not carry video frames, it carries multiplayer session data: player positions, game state, synchronisation signals between headsets, and platform management traffic from your VR arcade management system. Real-time multiplayer systems typically exchange small packets containing positional and state updates rather than media streams, which keeps bandwidth requirements relatively low but makes latency and reliability critical to maintaining a synchronized experience across players. This differs fundamentally from PCVR streaming, where every rendered frame travels over WiFi from a PC to the headset. PCVR is bandwidth-intensive. Standalone free roam is latency-sensitive. The network does not need to move large amounts of data, it needs to move small amounts of data reliably, fast, and without interruption. That distinction changes how operators should think about everything from hardware selection to configuration priorities. A network built around raw throughput handles PCVR well. A network built around low jitter and stable roaming handles standalone free roam well. In a venue running both, the configuration needs to serve both simultaneously. WiFi 6E vs WiFi 7 in Player-Dense Environments Week 5 recommended the 6 GHz band for free roam headset networks. The question for operators making a hardware purchase right now is which generation of that technology to invest in. WiFi 6E introduced the 6 GHz band to commercial WiFi, expanding available spectrum and reducing interference from legacy devices, and it remains the current standard across most LBE VR deployments. It delivers clean spectrum, wide channels, and strong performance in environments where the 5 GHz band suffers from congestion. (2.4 GHz, now primarily used for IoT devices like smart lights and thermostats, is no longer a realistic headset band in most venues.) WiFi 7 builds on that foundation with a capability called Multi-Link Operation (MLO), which allows devices to connect across multiple frequency bands simultaneously rather than committing to one, improving reliability and lowering latency in high-density wireless environments. For free roam VR specifically, MLO improves reliability and reduces latency because the headset maintains connections on more than one band at once, if one path degrades, the other compensates without the headset noticing. WiFi 7 also targets lower latency by design, making it well suited to the real-time demands of multiplayer free roam sessions. The PICO 4 Ultra Enterprise supports WiFi 7 natively, which makes it the current best match for WiFi 7 infrastructure in a free roam LBE VR environment. One important physical consideration applies to both generations: 6 GHz signals do not penetrate walls well. Higher-frequency wireless bands experience greater attenuation when passing through building materials, which means signal strength drops more quickly through walls or structural obstacles compared with lower-frequency bands. Their effective range drops significantly through solid obstacles. In a single open play space with clear line of sight between access points and headsets, 6 GHz performs excellently. The moment walls or structural elements break that path, signal quality drops. This is one more reason why an open, unobstructed arena floor is an infrastructure decision, not just a layout preference. The practical guidance: Operators building new infrastructure today should target WiFi 6E as the baseline and WiFi 7 where budget allows, particularly for venues running PICO 4 Ultra Enterprise headsets. Operators on existing WiFi 5 or early WiFi 6 infrastructure running standalone headsets may find their current setup adequate for session coordination traffic, but will hit limitations as headset counts grow or PCVR streaming enters the mix. Band Steering, Congestion, and Roaming Clients These three issues cause more live session problems in free roam VR arcades than any other network factor, and none of them appear on a speed test. Band steering directs client devices toward a preferred frequency band. In a well-configured arena network, access points steer headsets onto 6 GHz and keep guest devices and staff phones on 5 GHz. When band steering is off or misconfigured, headsets end up on a congested channel that also carries every customer’s phone traffic. Separating headset traffic onto its own VLAN removes most of that risk. Congestion in a free roam context rarely comes from headsets alone. The session data each standalone headset generates is relatively light. What creates