Would I be able to use the CV1 controllers in conjunction with a lighthouse tracked headset?

[Figgyloola]

I would like to use the CV1 controllers with my Index as the main HMD, I am aware that the CV1 HMD must be connected.
There is a way to do this on Windows, with oculus_touch_steam_link.
Essentially, I am asking if this software can be used in a way that makes the CV1 HMD act as a dongle for the controllers and tracking sensors.

Any help would be appreciated.

[AIIX]

Thanks for asking, and for the clear description.

Unfortunately RiftLinux can't do this at the moment. It's built to run the Rift CV1 as your headset: the SteamVR driver always adds the CV1 itself as the headset and drives its display, and there's no mode yet where it only adds the Touch controllers next to another headset like the Index. SteamVR expects one headset, so with both drivers active they would conflict.

Even with a controllers-only mode, two more pieces would be needed:

• The Touch controllers and Constellation sensors track in their own space, and the Index in Lighthouse space, so the two have to be lined up with a calibration step, which RiftLinux doesn't have.
• RiftLinux currently measures where the sensors stand by watching the headset move, so a CV1 lying on the desk as a dongle couldn't place them yet.

It's a reasonable thing to want, and I've noted it as a feature request. I can't promise when or whether it will happen, though, as I don't have an Index here to test with. If anyone with both headsets is interested in helping test such a mode later, that would make it much more likely.

[Figgyloola]

Okay, thank you for the information.

I will also ask, I used RiftLinux to just play with my old CV1, the headset tracked perfectly, but the controllers would often drift 5-10 cm away from their actual position. Is this something that has a simple solution?

And if you need people to test the feature if you do implement it, I would be willing.

[AIIX]

Thanks for testing.

1. Have you tested controller tracking with the 0.1.3 release?
2. Were the controllers in a clear line of sight of the sensors, or was something obstructing their view?
3. Were the controllers at rest, or were you actively moving them when the drift occurred?

Controller tracking is something I am still working to improve. Currently, going by USB packet numbers, they track within 2% to 3% of Oculus on Windows when in a clear line of sight.

To help reproduce the issue and figure out what is happening, could you provide a quick summary of when and where the drift occurred (e.g., in a specific game or in SteamVR Home) and what it looked like?

An initial few seconds of drift is expected during sensor calibration. By default, SteamVR Home hides the controllers until this process is complete. However, if calibration is active while a game is running, the controllers might still be visible and could drift for a few seconds. This behavior can also occur if the line of sight between the sensor and the controller is physically obstructed, such as by a laptop screen.

[Figgyloola]

1. No, I was using the 0.1.1-1 release, will try 0.1.3
2. I had my sensors set up as 1 straight ahead and 1 behind me, what would be the best positioning for them?
3. They were being actively moved when the drift occurred.

The drift was mainly caused during "controller stacking", but would drift without it too, and they would also lose tracking altogether sometimes even when I was not "controller stacking".

[Figgyloola]

After using 0.1.3, the drifting issue was greatly reduced, but still present

[AIIX]

That is some unique sensor placement, I haven't tried something similar with two sensors on the opposite ends. But general sensor positions I have tested are the normal layouts (2 sensors front) (+1 back optionally - for full room):

If there are only two sensors available, maybe try the two front sensor layout above and check if it helps.