Skip to content
nicolas-riera edited this page Jul 26, 2026 · 6 revisions

Welcome to the ODTKRA wiki!

This is where I'm going to put useful information about ODTKRA.

This program was originally made to use it along mm0zct's Oculus Touch Steam Link to use your Rift CV1 setup with other headsets, and this fork aims to maintain and improve it.


This wiki currently has 2 pages :

Why ODTKRA??

Using your Rift CV1 Touch controllers as FBT trackers is a very effective way to have quality full body tracking, comparable to Vive tracker quality, for extremely cheap (I got the headset, 3 Touch Controllers and 3 sensors for €60).
It's also a solution to have quality controllers with headsets that don't (like Windows Mixed Reality headsets).

As you don't wear the headset on your head, one difficulty is to keep it awake so the controllers don't stop randomly working.

ODTKRA was made exactly for that.

In addition to keeping the headset awake, it reduces as much GPU performance overhead as possible.

How it works?

This program does multiple things, separated into 2 categories.

During startup

When you start the program, it will instantly open OculusDebugToolCLI.exe and will change those following settings :

  • Disable ASW (we don't need it).
  • Set set-pixels-per-display-pixel-override to 0.01 to reduce as much GPU overhead as possible.

While running

There's also one setting that we have to change which is Bypass Proximity Sensor Check, but that can't be changed through OculusDebugToolCLI.exe as this setting is only in the GUI version of the Debug Tool.
Moreover, Meta Horizon Link has the tendency to automatically disable that setting every 10 minutes, so we have to "refresh" it before that point.

This refresh has to be as less disturbing to the user as possible, while being functional. This fork has the following behavior :

  • A refresh is triggered every 9 minutes if there isn't any user interaction (keyboard/mouse).
    Note: the first refresh will wait a 15 seconds idle before triggering.
  • If there's a user interaction at some point :
    • The program will try to do an anticipated refresh if there isn't any user interaction for more than a minute and if the scheduled refresh is in less than 5 minutes.
    • If it reaches the 10 minutes mark while the user is still interacting, it will trigger a refresh regardless to avoid the headset going into sleep mode.

When you close ODTKRA, it will revert set-pixels-per-display-pixel-override back to 0, which is the default value and is the resolution set in Meta Horizon Link.

Clone this wiki locally