Understanding Free Roam VR Tracking and Calibration
Introduction This article is a work in progress and will be receiving updates Standalone VR headsets use a tracking technique called visual simultaneous localization and mapping (vSLAM)*. The exterior cameras on your headset create a map of your surroundings, and the headset estimates it’s position based on its approximate distance to various landmarks in your map. *To learn more about SLAM, visit: https://www.mathworks.com/discovery/slam.html How Does Free Roam VR Tracking Work? When you are drawing the “boundaries” on your standalone VR headset, you are drawing the SLAM boundaries. When an headset is reporting its position, it reports its position relative to the SLAM boundaries. SLAM creates a “map” file. When all the HMDs have the same SLAM map: This is how it is kept accurate for everyone. Advantages and Drawbacks of Different Headset Choices HTC VIVE Focus 3, Pico Neo 3 Pro, Pico 4 Enterprise have superior tracking accuracy for Free Roam VR These headsets have superior tracking accuracy, because of a feature called boundary sharing. This means, you can draw the boundary on just 1 of the headsets -> then export that boundary file -> and import it into the other headsets. Then they have exactly the same SLAM map. As long as they are physically in the same space, it is very accurate. Meta Quest Disadvantages Meta does not allow boundary sharing and there is no way to export/import a SLAM map onto multiple headsets. Therefore, your tracking accuracy is determined by how well you are able to replicate and redraw your boundary on each headset, one at a time. Headset Calibration HTC VIVE Focus 3, Pico Neo 3 Pro, Pico 4 Enterprise When you are using HTC VIVE Focus 3, Pico Neo 3 Pro, or Pico 4 Enterprise, there is no need to calibrate your setup. Meta Quest When using Quests, calibration is needed. The calibration is like this: If, during gameplay, a player performs the quick recalibration (by holding the Oculus button for 3 seconds), then the HMD has to be recalibrated at the X spot.
Environment Profiles – Store and Swap VR Boundaries
What’s an Environment Profile and why it’s needed? The SynthesisVR Environment Profiles cover headset variables such as boundaries, button states, scheduled HMD restarts, and other configuration and environment adjustments. With the growth of the LBVR segment and the VR industry in general, we do see more and more standalone HMDs released for business purposes. As of March 2023, there are multiple established platforms and HMD models: What SteamVR has been great at for so many years is providing a unification between all the PCVR HMDs. Regardless if you go for HTC Vive, Valve Index, Oculus, PiMax, or another PCVR HMD, they always get linked to SteamVR and become a viable LBVR option. With the growth of standalone HMDs, this has dramatically shifted. The manufacturers bundle their products with custom software and functionalities that cannot be used on a competitive brand. This all creates a bit of chaos and not to make it any easier – all of the standalone HMDs have the option to operate as Wireless PCVR HMDs (as a way to fuel more power / stunning visuals). Getting familiar with the specifics of all manufacturers and making them part of your daily operations can be challenging. SynthesisVR is the first LBVR platform to unify the environment variables into Environment Profiles in a simple yet powerful interface. Setting up a new Environment Profile: Step 1) Find the Environment Profiles page Head to “my.synthesisvr.com >> Administration >> Devices” and switch to the brand new “Environment Profiles” tab: Step 2) Creating an Environment Profile There are a few simple concepts behind the Environment Profiles: Example Configurations: Room-Scale: Free-Roam: Room-Scale profile for PCVR->HMD streaming: Free-Roam profile for PCVR->HMD streaming: Step 3) Specify the hardware platform that will be used for the specific Environment Profile: Please note that upon applying your selection, you no longer would be able to change it for the current Environment Profile. Luckily, deleting a Profile and creating a new one is quick enough. Upon defining the hardware platform, the next step is to define platform-specific actions. Examples: An HTC Focus 3 profile that disables the Focus 3 popup menu and, if there are any boundary changes (like switching between room-scale and free-roam spaces) – then the HMD gets restarted. Once the session is over, the Focus 3 popup menu is re-enabled and the HMD is shut down to save battery: A Pico profile that automatically turns on the screen at the start of the session and disables the screen upon the session ends. During session, the screen will be always on, regardless if the HMD is actually in use: Disable the 2D menu for Free-Roam sessions: Step 4) Export and Sync the boundaries: Click the boundary icon right from the Environment Profiles page: The pop-up will guide you through what devices(=HMDs) are online and which ones match the hardware platform: As can be seen on the screenshot, the Environment Profile won’t let you export SteamVR chaperone data from a PC streaming to an HMD. In that case, you have to run Synthesis on the HMD and use an Environment Profile with the appropriate Hardware Platform. Upon clicking the Save button, the export signal is submitted to the HMD: Please wait until you see a confirmation popup: Your boundary data is saved in two locations: Known Limitations: HTC Focus 3: Pico 4 Enterprise: Meta Quest 2: