💡 OPEN FEATURE: TrackIR

[Krishty]

TFXplorer’s rendering needs a few adjustments because

1. There is much more hardware transform & lighting than before, e.g. contrails and terrain rendering.
2. Camera commands need to be adjusted to the new input API.
3. There is a bug with MFD views waiting to be fixed.
4. There is a bug with MFD vibration waiting to be fixed.

Since this needs touching anyway, it should be made compatible with head tracking. TrackIR is easy to implement (can be done in 100 lines of code), so it is a perfect candidate.

[Krishty]

Head tracking for cockpit views will be in the next version, but a few details still need to be worked out. For example, how to use head tracking in external views and nose view …

[Krishty]

First version has landed. Only cockpit view so far; external/nose views still need fine tuning. We may also need a Settings page.

[Krishty]

Just noticed that there is a bug in the current version. To fix, please open TFXplorer.cpp, line 2303, just before if(ui.isTrackingHead). Delete the line Geo::Matrix4x3_float_reg eyeToEntity; just before it.

[Krishty]

The next version will have a very basic flag in Settings that indicates if head tracking was found or not:

image.png (5.04 KiB) Viewed 55 times

I made the check box read-only because a) I’m lazy and b) the TrackIR documentation says it’s best practice to always connect and let users enable/disable it via button on the TrackIR hardware.

[mikew]

At least the check box is square.

[Krishty]

Well the code definitely looks like it should be a radio-edit-combo-box 🤣

[Krishty]

The latest version brings TrackIR to the chase cam (F7).

No solution for nose view and external view yet. Nose view clashes a lot with how HUD is computed and displayed; external view clashes a bit with how I internally compute viewer position.

I tried TrackIR in explorer mode but it was utterly confusing. With no reference point (like a cockpit), things become very weird quickly.