If you don’t know what the Oculus Rift (OR) is, it is a virtual reality (VR) headset that covers your eyes blocking out any sight other than what it’s embedded screens show you. The OR tracks your head movements and where you are in space which is mimicked on the screens in front of you.
The OR hardware consists of two parts, the headset itself and an infrared camera that sits on top of your monitor just like a traditional web cam. These are all linked together with cables and connected to a PC. The version of the OR that I was testing was the DK2 which is a development version and not the final product that will be released to market.
The PC requires a space HDMI output, two free USB sockets (one for the headset, one for the camera) and a standard 3 pin power socket. These are all connected via cables, and generous length cables are included, especially to the headset.
The PC I was testing on was a high spec PC running Windows 10: i7 Extreme, 16GB DDR4 RAM, X99 board, 2x Nvidia 980GTX, Evo 850 SSD. Connecting everything up was fairly simple, the guide provided by Nvidia was easy to follow.
The software installation was also fairly simple, you download the latest SDK from Oculus which in my case was version 0.8. This has a standard installer which installs the drivers and weighs in at around 45MB.
Once installed, I anticipated being able to launch one of the demos and off it goes, but the orange ‘standby’ light was on the headset and the light on the camera was unlit. I opened up the Oculus configuration tool which is installed with the SDK (and resides in the system tray) to look at the logs and run the diagnostics, and with that open the OR came to life. It appears that the config tool needs to be open (not just running in the system tray) for the OR to work. The headset light was now green and the light on the camera was lit up blue.