DevKit quick start

You have got your hands on our DevKit!
We prepared a step-by-step tutorial for quick start. Follow the instructions below.

Devkit quick start

You have got your hands on our DevKit!
We prepared a step-by-step tutorial for quick start. Follow the instructions below.

Prepare for setup Tracking area setup Software setup • Installing • Environment • Placement • Device Network Device update • Alt Tracker • Alt Tag • Alt Bracer • Alt HMD Radio Socket • Alt USB Socket • Alt PicoG2 Socket Wireless devices Download SDK Run samples Troubleshooting

Antilatency Service

With the release of the new SDK, the AltSystem application is renamed to AntilatencyService. Now AntilatencyService includes the functionality of the PropertyManager.

To run any applications that use the Antilatency tracking libraries you need to install the AntilatencyService utility. The AntilatencyService utility allows adding and configuring tracking areas and to change the placement of the tracker for different HMDs. You need to run AntilatencyService at least once to initialize the system. After the first time, you don’t need to run AntilatencyService after rebooting the system.

Installing

Make sure that you uninstall the AltSystem application before installing AntilatencyService

Prerequisites:
AntilatencyService for Windows is a Universal Windows Platform (UWP) app. It requires Windows 10.

  1. Download AntilatencyService from link: Download
  2. Extract AntilatencyService_11.0.0-rc.1.zip
  3. Run "Install.bat" as administrator to install it.
Run bat as administrator
  1. Click "Install"
Click install

Please note that the Developer Mode option should be enabled in your OS. If this option is not enabled you will get an error as follows:

Click install

To enable Developer Mode please follows the instructions: https://docs.microsoft.com/en-us/windows/uwp/get-started/enable-your-device-for-development

The instructions for Android are shown in the OculusGo/Quest and PicoVR HMD example. Instructions for other Android HMDs are similar.

Install software

Grant permission to the headset using a USB-device

  • Turn on the headset. Keep the sensor covered as you see on the picture to prevent the device from entering sleep mode
Oculus
  • In the Oculus app on your smartphone put your device into developer mode and connect it to the computer.
Set developer mode
Set developer mode
Set developer mode

Connecting headset to a PC

  • Connect the headset to your PC.
  • Put it on and allow USB debugging from the PC.
Set developer mode
  • Open the Platform Tools folder then open Windows PowerShell. To do this, in the upper left corner, find the "File" tab and select "Start Windows PowerShell".
Set developer mode Set developer mode
  • If the system issues an error or the commands don't work, use the following commands in sequence:
    .\adb.exe kill-server
    .\adb.exe start-server

Installing the software

  • Copy and paste the following commands into PowerShell:
  1. AntilatencyService installation
    .\adb.exe install -r .\AntilatencyService.apk
  1. Starting AntilatencyService for configuring the tracking area
    Oculus Go
    .\adb.exe shell am start -n com.antilatency.antilatencyservice/.MainActivity
    Open Vysor, click on the View button. Tracking area should be set to "DevKit" by default.
    Oculus Quest
    .\adb.exe shell am start com.antilatency.antilatencyservice/.MainActivity
    AntilatencyService will run through HMD
    Pico VR
    Run AntilatencyService through applications list

Environment
  1. Run AntilatencyService app.
    Tracking area should be set to "DevKit" by default.
  2. If you need to change the tracking area in the future, follow the instructions below:
Placement

Attach the tracker to the HMD

If you don’t need to track the HMD skip this section. When placing the tracker on the HMD, make sure that the tracker is securely attached. It is important that the pivot point of the tracker is placed in the correct position relative to the user’s eyes.

After attaching the tracker you also need to select the Placements tab in the AntilatencyService app and select the corresponding placement for your device.

You can find instructions below for using the wired USB socket with popular HMDs. It’s also possible to configure your own placement.

Use a USB OTG cable to connect the wired USB socket to a standalone headset. If the USB OTG cable is properly connected, the tracker inserted in the wired USB socket will flash green.

  1. Attach the wired USB socket as shown in the image.
  2. Select OculusGo_Migo on the Placements tab in the AltSystem app.
  1. Attach the wired USB socket as shown in the image.
  2. Select OculusRift on the Placements tab in the AltSystem app.
  1. Attach the wired USB socket as shown in the image.
  2. Select VivePro on the Placements tab in the AltSystem app.
  1. Attach the wired USB socket as shown in the image.
  2. Select PicoG2Universal on the Placements tab in the AltSystem app.
  1. It’s possible to configure your own placement by using the Placement editor:
  2. The pivot point of the tracker should be set relative to the center point between the eyes.
  3. The coordinate system of the tracker is shown in the following image. Please note that the pivot point of the tracker is located with an offset (2.62 mm) from the back side of the tracker.
Device Network

AntilatencyService allows you to read from and write to Antilatency device properties. Currently, only Alt supports user-defined properties, but you can already read from and write to predefined properties on other devices.

In most cases, this tab is used to set a “Tag” property for Sockets, Bracers, and Tags. Also, you can set a radio channel and connection limit settings for HMD Radio Sockets. The “Tag” property acts as a kind of device identifier, that can be used by your application to determine how this device should be used.

For example, you can mark one bracer with the “LeftHand” tag and other with “RightHand”, and set your app to look for such devices. Our BracerSample scene uses the same setup as in the SDK base Unity package.

When you open Device Network tab in AntilatencyService app, you will see this:

If there are no devices listed in Device Network, check that your devices are connected to the host and there are no other applications running which are using the Antilatency SDK. Only one application at a time can work with Device Network.

Using the image above we can see that 4 devices are currently connected: HMD Radio Socket, Bracer, and 2 Alt Trackers.

One of the trackers is plugged into Socket and one into Bracer. To open the device properties, click on any device, for example, such properties are used for HMD Radio Socket:

Common properties

  • sys/HardwareName – hardware device name
  • sys/HardwareSerialNumber – unique device hardware serial number
  • sys/HardwareVersion – device hardware version
  • sys/FirmwareName – device firmware name
  • sys/FirmwareVersion – device firmware version

HMD Radio Sockets properties

  • Connection Limit (ConnLimit) – is the maximum number of radio devices that can be connected to this radio socket simultaneously. Possible values: 0, 1, 2.
  • Radio Channel allows you to set a radio channel that will be used for this device, using these possible values:
    • -1 – automatic channel selection. The device will scan all channels and select the best one
    • 0, 1, 2, …, 32 – one of 33 channels that will be used by the device
  • Tag – a user-defined device identifier, for example, “LeftHand”, “Pistol”, etc., possible values of any string consists of 63 or fewer symbols.

Bracers and Tags properties

  • MasterSN can define a socket serial number to allow the Bracer to connect only to that socket.
  • Tag is a user-defined identifier, for example, “LeftHand”, “Pistol”, etc.
  • Vbat is the bracer's battery voltage. Currently, this value updates only at startup. We will fix that in a future SDK update.
For your convenience, we and our partners use cookies on this website. If you do not change the settings, we will treat this as consent with data usage policy on antilatency.com