how to get the TIR F9 pause/start to be on the HOTAS?
-
@huffer2 said in how to get the TIR F9 pause/start to be on the HOTAS?:
@Robf4
Thanks for your input. I have opened TIR, and I reset the Hotkey for PAUSE to the DX btn on my flightstick for CMS-Left. When I tested it out in flight with BMS, the CMS-left is turning on/off like it should, however, since I had previously assigned in my keyfile the DX btn for CMS-Left, now I get CMDS release with CH and FL every time I hit CMS-Lt.
I am hoping there is a way to modify my keyfile for the CMS-LT to remove the DX assignment. I could see the line for this command but I did not want to try deleting that line since I do not know if that will cause harm to the keyfile.
Any thoughts?It won’t. Just make sure you delete the DX bind at the bottom (no quote marks and label text). If you really wanted to do it via the UI then you could bind that CMS left button to some other command and then rebind that other command to the correct key. E.g. bind “TMS up” button number to CMS left and then bind “TMS up” button to TMS up. That will have the same effect.
-
@Frederf
Great info! Thnks -
@Atlas
Atlas, I just reread my post to you. I mistyped and made no sense. Sorry. But I did fix my issue. I am leaving the CMS alone. I made the hotkey for TIR/Pause to be assigned to the TQS Btn 3 with DX. Then in BMS I assigned the command Pan Pit 3D to the same Btn on the TQS. -
I also use VoiceAttack for my TrackIR – have two voice commands controlling them, “Pause” and “Set” … the first one presses the F9 key to pause tracking (or unpause it), and the second presses the F12 key to re-center tracking.
There is also a “RecenterTrackIR” callback in the keyfile(s), I do use this for the ‘recenter trackIR’ on my public X52 profile ‘Falconeer’:
-
same here using foxvox and opentrack… assigned the pause / reset keys in opentrack, then told foxvox to send this keypress on “tracking stop / start” or “tracking reset”. Works like a charm and I think @foxster even integrated it in his latest library update for 4.37.2.
-
@hoover when you ‘pause’ opentrack does your pov freeze in place, or does it snap to forward-center?
mine snaps to forward, which is not helpful for trying to click cockpit switches and dials… I suspect I’m doing something wrong
-
@airtex2019 That’s how it works… from there you use your mouse (if in 3D Pan Cockpit mode) or 2D and snap around
-
@SemlerPDX I don’t think my mouse works for mouselook, when OpenTrack is running … even when paused.
Hmm… maybe the pov-hat or the keybd callbacks for view panning work… haven’t tried.
-
-
@hoover yeah that’s what I’m missing – how do I do that?
on OpenTrack options menu page, I just noticed there are separate commands “Toggle”, “Toggle while held” and “Toggle tracking”.
is one of those the “Freeze”?
-
Try Opentrack with this flag and report. It may work , but not sure - its complicated
Freeze is exactly just “Toggle” (2nd bind) in Opentrack equivalent. -
Yep, toggle basically freezes the view in place and then releases it again when pressed a 2nd time.
Cheers, Uwe
-
@white_fang oh weird I read that as something to do with clearing the location of the DLL (?) when tracking is stopped.
which tbh I also don’t understand at all… what the heck is this DLL and why must it be overwritten? it’s bizarre. I have 30 years of Windows/C++ programming experience and I’ve never seen interprocess communication done this way
-
@hoover so for me, “Toggle while held” works as expected… but just “Toggle” seems borken – it snaps to front-center and doesn’t ever re-engage when I click it a second time. until I stop and restart tracking (via the buttons or the “Toggle tracking” command binding).
Maybe it’s a bug, specific to my input source (I’m just a gamepad thumbstick to test some things).
It’s open source so I suppose I should dive in and investigate… it’s a little scary for there to be a bug in something so fundamental as “button-click” vs “button-hold”. I expect it will either take 2 minutes to fix, or it will require a massive code cleanup and refactoring… lol
-
@airtex2019
These are my settings in vs. 2.3.12. For me Toggle does what it says on the tin (highlighted):It might be that some releases after the one I’m using are buggy in that respect. I updated at one point, but it didn’t work as well as my now old version
-
@jayb thanks, yes I see what you mean… recent releases seem to be a mess – worse than I reported – tracking doesn’t work at all unless OpenTrack window is foreground / focused.
so eg. I’m in BMS cockpit… no tracking… I hit alt-tab to OpenTrack to make sure it’s running and suddenly the pov starts panning around in BMS, in the background… lol
last update (Oct 2022) was to fix a very similar sounding issue… but apparently it was only found/fixed for Wii-U tracker input? wtf
once again I’m dumbfounded how something as fundamental as “window in foreground vs background” is somehow a codepath specific for the different input sources. [smacks forehead in despair]
-
@airtex2019 yeah, from quickly reading through the list of releases they seem to have been busy adding all sorts of tracker solutions. So somewhere along the way fundamental functionality went out the window
-
@jayb @airtex2019 said in how to get the TIR F9 pause/start to be on the HOTAS?:
recent releases seem to be a mess – worse than I reported – tracking doesn’t work at all unless OpenTrack window is foreground / focused.
Wait a bit… something is wrong on your end 100%.
What version are you using… latest is: opentrack 2022.3.2.
All is fine…
That what are you describing is a nightmare
I never experienced anything like it.
Yes, POV is not working in BMS from day1, but that 's it…How is then working for other 90% of users … ha?
Guys, are you sure that you have “ALL” configured correctly?I’m not trying to say all is peachy,… as for you it isn’t … but, for me … Opentrack is working FROM DAY 1 … and never, NEVER … had problems.
Do try to reinstall , EVERYTHING… and vc++redist(s)86/64.
Check your profiles-ini / filter … tracking… clip dimensions… recalibrate. - CAMERA DRIVER(S) ?
So… EVERYTHING. -Then report. We’ll see what is happening.Cheers
-
@white_fang yes 2022.3.2 … I suspect a lot of the weirdness is specific to input source = joystick. same kind of crazy bug was found and fixed, for Wii tracker
https://github.com/opentrack/opentrack/issues/1499glanced at the code, it’s really terrible. it’s confused about the number of axes on a DX device (should be 8 … some buffers in the code allow 8, others 6). it has unexplained hardcoded limits for various axes, which explains some of the squirrely behavior when it does work.
it has off-by-one errors that they correct, then correct again later, which become off-by-one in the other direction. I’m pretty sure it’s resulting in random heap corruption.
https://github.com/opentrack/opentrack/blob/master/tracker-joystick/ftnoir_tracker_joystick.cppI opened some new issues… maybe I’ll contrib some fixes. in meantime, I’ll give up getting this to work.
-
@airtex2019
Aaah… well, (joystick, wii) those aspects of Opentrack I never used.
You seem to go deep in the matter … I never did. I was betatesting with Stanislav in early years … but that’s it.I use it only for plain original trackir function and that’s good enough for me. - and I can vouch 100% that stuff works oob , and works well … or at least how is configured
Yes there were bugs with time (along years) in pointracker interface, but neither of them were real showstopper for me… calibrate… go.
I am actually amazed how many stuff he (they) implemented, what can you use as tracker, even VR - no big surprise there - coordinate system.But, back to problem… that the OT window MUST be in foreground…
DO you use github builds , or you compile/fork your own ? (forgot to ask)