Forum Discussion
TrackIR conflict
Has anyone else been having issues with using the Rift and NaturalPoint's TrackIR client at the same time? It is possible to augment the rifts yaw/pitch/roll sensors with the trackIR interface to get reasonable x/y/z head translation. There is some work you need to do to get the trackIR to report 1:1 head motion but that is not the problem.
The issue is that if I first start the trackIR software (v4 or v5) then the rift can not connect to its sensors. I did find a workaround by first launching the Tuscany demo to occupy the rift sensors, then launching the trackIR client. If you open them in that order, and don't close the trackIR client, then you can shutdown the Tuscany demo and launch any other game (iRacing, for example) and use both the trackIR and rift at the same time.
I'm finding this to be a good combination, within a narrow range of application. The trackIR device has a small field of view (at least the v4 device I have access to) and can only support head rotations of between 30 to 40 deg in any one direction. So it works out well for driving a car around, but won't work as well if you need a full 360 deg view. For iRacing, the best feature is that we can now move our head around a bit to get a better view in our rear view mirror. This really opens up the mirrors a lot allowing you to see much more of the track, in spite of there relatively small size. In hindsight this is something you do all the time when driving in the real world, without thinking about it (moving your head around to get a better view in the mirror).
The issue is that if I first start the trackIR software (v4 or v5) then the rift can not connect to its sensors. I did find a workaround by first launching the Tuscany demo to occupy the rift sensors, then launching the trackIR client. If you open them in that order, and don't close the trackIR client, then you can shutdown the Tuscany demo and launch any other game (iRacing, for example) and use both the trackIR and rift at the same time.
I'm finding this to be a good combination, within a narrow range of application. The trackIR device has a small field of view (at least the v4 device I have access to) and can only support head rotations of between 30 to 40 deg in any one direction. So it works out well for driving a car around, but won't work as well if you need a full 360 deg view. For iRacing, the best feature is that we can now move our head around a bit to get a better view in our rear view mirror. This really opens up the mirrors a lot allowing you to see much more of the track, in spite of there relatively small size. In hindsight this is something you do all the time when driving in the real world, without thinking about it (moving your head around to get a better view in the mirror).
2 Replies
- What you need is the latest Opentrack build - see here: https://github.com/opentrack/opentrack
If you're on windows, download the latest build with oculus support. (Get 7zip to extract the .xt file)
What you can then do is use the Oculus as the primary tracker for rotation (Pitch, roll and Yaw) and the TrackIR or PointTracker for the X-Y-Z displacement.
Best combination I have found, and works well.
