Hacking the Oculus Rift DK2, part IV

Note: This is part 4 of a four-part series. [Part 1] [Part 2] [Part 3]

I caved and uploaded a snapshot of the current optical tracking sources, including a pre-release snapshot of upcoming Vrui-3.2-001 (please don’t use it outside of the tracking project; it’s bound to change some before it’s really released), to github: http://github.com/Doc-Ok/OpticalTracking.

4 thoughts on “Hacking the Oculus Rift DK2, part IV

    • Did you set the pattern slider to “1” before enabling the LEDs? If you change the value while the LEDs are enabled, the synchronization will not lock on. To experiment with the pattern value, disable the LEDs, change the slider, and then enable the LEDs, but ensure that the LEDs were off for at least two seconds. That will signal the recognizer to re-synchronize with the LED pattern.

      • That’s why I posted the video: https://www.youtube.com/watch?v=35bhi4pihnM 🙂

        It shows from the very start of the program: Activating “Modulate” and “Flash LED IDs”, setting “Pattern” to 1, clicking “enable”. Then I got the video feed that identified very few of the LEDs at the modulation 127 value. Going to the right to 163 (fir example) makes it identify more LEDs.

        Maybe different DK2s have different values here.

  1. Thanks for this exhilarating series! I don’t have sufficient knowledge in the field of computer vision or spatial geometry in general to get the fine details but I was able to understand most of the abstract and it was a great read. I hope you continue to write about the process as you keep going with this as I thoroughly enjoyed Hai ing some insight as to how the technology comes together

Please leave a reply!