Oculus Bridge

With the impending release of the Oculus Rift, many existing platforms are quickly adding support for this amazing new hardware. One area where support is lacking though, is the browser. Given all the incredible work going on with WebGL it seemed worth the effort to build a simple solution to solve this problem. The Oculus Bridge is our attempt at a solution.

This project includes two pieces, one is a native application that acts as a bridge between the Oculus Rift hardware, and the browser (via websockets). The second piece is a very simple javascript object that manages the websocket connection and messaging. The result is a simple drop-in solution to make use of the head tracking data for any web based experience.

This project has already been used internally at Instrument for several prototypes built with THREE.js and is proving to be quite easy to work with. Most of the example code is based on THREE.js, but the library has no dependancies and can be used with any other javascript framework just as easily (we've even hooked it up to work without webGL at all, using CSS shaders). The bridge app and javascript are intended to be a simple and general-purpose as possible.

This project isn't the first websocket utility for use with the Oculus Rift, but after looking into the existing solutions we thought we could improve on the existing offerings.

Notable Features:

- The application, web content, and hardware can be connected/opened/closed in any order and the system will remain stable and automatically reconnect as soon as all the components are online.

- Single C++ code base for Windows and OSX

- Display metrics (screen size, physical dimensions, etc) are not hard-coded in the javascript, but are instead read from the Oculus Rift API and transmitted over the websocket connection. This means no javascript changes should be needed for future hardware variations.

- Requires no browser extensions, custom drivers, etc.

Download and try out Oculus Bridge here.


Close Video