Getting Started with Software

This page goes over the general setup you should do after you've finished building and calibrating your headset.

Verify your headset is working properly.

You'll want to make sure that your headset works properly, plug in the power to the integrator board or driver board first, then display. On newer headsets (Deck X and beyond) this is not an issue, however, there can be an issue where plugging the display in first causes the driver board to get enough power through the display port connection to boot, but not enough power to run properly. If you run into this issue unplug your headset and then plug-in power first, then the display connection.

Set Windows Display Settings

Your Northstar display will show up as a normal monitor and will look "upside-down" if viewed through the headset. This is normal, we compensate for this in software written for the headset. Make sure your headset is set up so it's to the right of your main display(s), and that the resolution is 2880x1600. You'll also want to make sure that the scale and layout section is set to 100%. By default, the headset will run at 90hz. You'll also want to ensure that your headset is set to extended mode and not mirrored.

Install Drivers

Leap Motion

There are a handful of demos that require leap motion's multi-device beta driver, located here. If you're having issues with getting your leap working in demos or unity this is probably the reason. Once you have the drivers installed open the leap motion control panel and make sure that the connection is "good", as shown in the figure below.

Realsense SDK

In order to use your t261/t265 sensor you'll need to install the realsense sdk, located here. Once you are finished installing the sdk, open the realsense viewer application to ensure that your realsense device is connected. If you are using the Deck X headset and your t261 is not showing up you can take the following actions to resolve it:

  1. Push down on both circular buttons on the headset for two seconds to power cycle the integrator board. This should cause the realsense device to enumerate and cause windows to detect it.

  2. If step 1 did not work you can try unplugging the headset and plugging it back in, make sure your USB connection is plugged into a USB 3.1 port.

  3. If both of the above steps did not work you can try resetting the USB hub in device manager. This solution has solved most edge cases we've seen so far.

Northstar Development

There are currently three methods of getting software running on Northstar headsets.

  1. ​Esky This is the recommended developer experience. It has video passthrough with the t261/t265, built-in support for the mixed reality toolkit and support for both 2D and 3D calibration methods.

  2. Unity This is the default unity experience, it's barebones and built for the 3D calibration rig. If you're experienced with unity and want to tinker with the original source code for Northstar this is the place for you.

  3. ​SteamVR The steamvr integration allows any SteamVR game to run on a Northstar headset. Hand tracking isn't a replacement for controllers yet so you won't have a fun time in beat saber, but for demos like cat explorer or the infamous cubes demo you'll have full support for hand tracking a

  4. Prebuilt Examples There are a handful of prebuilt demos for Northstar including LeapPaint, Galaxies and others. These will be linked on a separate page/database at a future date, for now, join the discord and check the #showcase channel