Platform updates are most painful when each product looks healthy on its own but the integrated developer workflow stops working. I made this video for developers who had an existing DK2 setup and suddenly needed to reconcile a new runtime, Unity's VR support, Oculus integration files, controller drivers, and input configuration.

Why I made this

Moving to Oculus Runtime 0.7 introduced failures at more than one layer. The headset could lose video while the Xbox One controller failed inside OVRInput, leaving developers to determine whether the problem belonged to Oculus, Unity, Windows, the controller driver, or the project configuration.

The available information was distributed across products and assumed that the reader already understood how those pieces fit together. A developer returning to a DK2 project needed one ordered recovery path, not another isolated setting or code fragment.

What I did

I begin from the upgrade problem and rebuild the environment in dependency order: the Oculus runtime, Unity's VR configuration, the integration package, controller support, and OVRInput mapping.

I keep the real failures in the walkthrough. Instead of showing only a prepared final project, I connect the symptoms to the layer that caused them and verify the corrected behavior in Unity.

That completeness mattered to viewers. One developer later commented that the detailed walkthrough helped them finally get the stack running; another described the tutorial as useful years after publication.

A note on the archive

This tutorial documents the Oculus DK2, Oculus Runtime 0.7, Unity 5, the Oculus integration package, OVRInput, and Xbox One controller support as they existed in October 2015. That software and hardware stack has been replaced and should not be used as current Meta Quest or Unity XR guidance.

The source video does not expose a usable caption track, so I didn’t invent chapter timestamps. It stays here as a record of what early VR development was actually like: several moving dependencies, one broken stack, and a lot of careful checking to get everything talking again.

Published October 2, 2015. Preserved with context. More DevRel work →