Cursor Setup
-
This is how I got my Warthog cursor setup.
Horizontal (X) and Vertical (Y) movements work very well when making a Mark with HUD SOI.
But when adjusting the FLIR image, the X and Y move just the opposite.
Anybody else have this? -
Do you mean when you’ve got the FLIR on the HUD, and you’re boresighting that image to the real world (seen through the HUD, behind the projected FLIR image)?
This sounds like something I wrestled with a while back:
I ended up deciding that “I think wrong”, and I just had to be careful which image I’m concentrating on, when I boresight the FLIR.
-
Do you mean when you’ve got the FLIR on the HUD, and you’re boresighting that image to the real world (seen through the HUD, behind the projected FLIR image)?
This sounds like something I wrestled with a while back:
I ended up deciding that “I think wrong”, and I just had to be careful which image I’m concentrating on, when I boresight the FLIR.
After working with the Mark HUD (SOI), I realized that the cursors don’t move UP/DN, LT/RT in the same direction for FLIR and MARK. The cursors move in the opposite direction for FLIR and MARK(HUD SOI). Cursor Down on MARK-HUD is up for FLIR. Cursor Right on MARK-HUD is left for FLIR. etc. I’m leaving my Avionics setup the way it is. That means I prefer the movement applicable for the MARK-HUD. For FLIR, I’ll have to remember that cursor down moves the FLIR image up, etc., unless the DEVS fix this :D. Here are some images I made of the FLIR.
FLIR image separated from HUD imageFLIR image after cursor DOWN. FLIR image moves UP.
FLIR image after cursor RIGHT. FLIR image moves LEFT.
-
Thanks for posting those screenshots, jc1.
When I was trying to noodle this out, back in January, I was distracting myself with another problem: I didn’t correctly understand what “cursor X” and “cursor Y” meant. My understanding of those two axes was wrong. I think that when I came up with the “mind hack” of trying to move the real-world image with the cursors, I was just so happy to have gotten cursor X and cursor Y straightened out. But I hadn’t realized that the cursor movements are reversed, when one compares MARK-HUD with FLIR.
One other thought occurs to me, though… and someone should definitely check me on this, because I tend to get these things backward…
I wonder if, when boresighting the FLIR, a cursor-down movement of the cursor switch is meant to slew the FLIR camera’s aim point downward, relative to the fuselage of the aircraft? That might explain the upward movement of the FLIR image in the HUD, relative to the frame of the HUD.
In which case, the engineers who designed all this stuff in the aircraft might say “The cursor switch slews the FLIR camera the same way it slews the TGP camera. We wanted to keep those two mechanizations (sp?) consistent”. And this would mean we’re stuck doing my “mind hack” with the real-world image.
Of course, I could have all of that bass-ackwards, as I often do. But it makes me wonder if this is all about the direction in which a camera’s aim point is being slewed…