TrackIR not working in OpenBeta only for M2KC module

[rale26]

Hi folks,

Upgraded to OB 2.7.8 today and tried M2KC after very long time. TrackIR works absolutely fine in all modules but M2KC. Both lights on TracIR are green my Mirage doesn't budge. It works totally fine in M2KC stable 2.7.7 module. I also noticed that if I try to load profile for my x-56 Rhino, it loads all stick mapping but nothing on throttle side.

Any idea what might be off here?

[Ramsay]

17 minutes ago, rale26 said:

Any idea what might be off here?

No idea about TrackIR as mine is still working as normal.

For the "X-56 Rhino", a number of default keybinds have changed, so it's expected that some assignments might need to be updated i.e. I had a handful of keybinds that I reassigned.

Edited November 22, 2021 by Ramsay

[Frederf]

Fair chance some of the action bindings changed with such a large update. It's possible something on your profile is not compatible with the new selection of actions. If that's the case it's probably best to delete the .diff.lua and bind that controller again. Make a backup of the new .diff.lua as a profile. Save the old .diff.lua for that throttle if you like but unless you know exactly what entry is not compatible you'll never get it to load properly.

TrackIR has bindings just as the regular joysticks. Check the axes section and cross right-left to see all device columns. The TrackIR axes should be bound to absolute view axes.

[rale26]

Just checked other modules where TrackIR works fine. TrackIR has no bindings in any of those profiles. Column is greyd out and if you hover mouse over it, popup will say: "No command available for this device". The other controller columns are blue.

[Frederf]

[rale26]

Darn! If I choose "All" controls, TrackIR is options disabled, I can't edit them. But when I chose "Axis Command" it gave me the option to set it up.

Thanks Frederf, this was really helpful, it works well now!

 

 

[Frederf]

Yeah "All" shows all button commands and none of the axis commands.