The Data Transfer Tool assists Administrators in transferring session reports from one or multiple VR device(s) to promisevr.comin the absence of wifi.
This tool works on PC and Mac operating systems. Your computer will need access to wifi before and after the session logs are transferred, but wifi access is not a requirement while logs are being collected.
This guide will help you install, log in, and operate the tool.
Note: The DTT is currently compatible with Quest VR devices, which must have developer mode turned on. Please disable wifi on headsets when using the DTT.
Note: Future updates will be prompted within the app—no need to revisit the download link. After installation, you might be prompted to provide access to your computer’s Keychain or Credential Vault depending on your OS. Please click “always allow.”
2. Logging In
Upon first launching the Data Transfer Tool, you will be required to log in. Once you have logged in, you can use the tool offline until you need to send data to the cloud the next time you go online.
Open the app and click the yellow Login button.
Enter the email you use to access the portal and click Sign in.
Check your email for a magic link and click it. Your app should update and display Logged In within a few seconds.
3. Connecting Your Headset
If you're using ArborXR, please exit the home screen of ArborXR to accept the USB-C connection. NOTE: The notification to accept the USB connection may be in the notifications area (the bell icon on the Meta Quest toolbar).
Connect your VR headset via USB-C to your computer. If initially unsuccessful, please retry the connection.
In-headset: select "Yes" and "Allow" to enable the USB-C connection.
On your laptop: select "Allow" when asked "Allow accessory to connect?" in a pop-up window.
Once connected, the button labeled Import session data should turn green, indicating that the headset is recognized.
4. Importing Data
Click on Import session data to load your session files into the app. These should appear in a table on the right side of the window.
5. Syncing to Cloud
To sync your data, click Sync to cloud.
You will see each session's sync status update to either Success or Failed (check any failed sessions for issues).
6. Updating the App
Select the .zip file to update using the Choose file button.
Click Update and wait for the update process to complete. If it takes longer than a few minutes, check for any error messages.
To verify the update, disable wifi on your headset and launch the Moth+Flame App.
Q+A
Q: How does the DTT zip file behave in a pre-existing ArborXR/MDM environment?
A: The DTT zip file successfully versions up the app in a pre-existing ArborXR environment, even if the headset is offline. This streamlines the update process, eliminating the need to update the headset with an Arbor package separately.
Q: What is the advantage of using the Data Transfer Tool (DTT) for updates?
A: By using the DTT, you can handle all application and module updates exclusively through this tool.
Q: What should we expect in terms of app version metadata in the ArborXR home launcher after using DTT for updates?
A: The app version metadata displayed in the ArborXR home launcher will not change. For example, if you click the "more info" button under the Moth+Flame icon, it will still show the old version information. However, when you launch the Moth+Flame App and check the "About" section in the menu, you will see the updated version that was sent via DTT.
Q: What happens if a headset goes online after being updated with the DTT?
A: If the app version in ArborXR is updated to match what was placed on the headset offline, the headset does not require a new download of the app when it goes back online. This ensures a seamless experience even if the headset transitions between offline and online states.
Q: Will headsets that receive updates using the DTT copy over active classes?
A: Yes, active classes associated with the module files will be transferred.
Q: A headset that received the update using the DTT is associated with a different device group than the headset that was used to make the zip file. What happens?
A: Here's an example: Headset 1, registered to device group X, downloaded class list A before going offline. A zip file was then created using Headset 2 from device group Y with class list B and pushed to Headset 1. Headset 1 (while offline) will only have access to the modules from device group Y and display only class list B during training. After the session, Headset 1 will show its own device group (X) in the csv file, but its data will appear in the classes that were assigned to it from Headset 2.
If a fleet of devices requires an update and the headsets do not have access to wifi, and the Data Transfer Tool is not available or there was an error, there are two ways to deploy module updates: 1. Use an MDM (ArborXR) configuration package 2. Use ...
If a fleet of devices requires an update and the headsets do not have access to wifi, there are two ways to deploy module updates: 1. Use an MDM (ArborXR) configuration package 2. Use SideQuest to clone a VR headset - Prerequisites for using this ...
Release announcements for the latest app version will appear here. If you have any questions, please don't hesitate to contact us at support@promisevr.com. If you would like to suggest a product improvement, please submit your idea here. Release ...
Moth+Flame's Browser Player extends the immersive and interactive experiences of our VR platform directly to your web browser. Without the need for specialized hardware, learners can access the same rich, engaging content from virtually anywhere. ...
Below are periodic updates to the Perform web portal. If you have any questions, please don't hesitate to contact us at support@promisevr.com. If you would like to suggest a product improvement, please submit your idea here. Release Update: 5/4/23 ...