unable to reproduce track ir is slaving to the tdc in the a10 c when using HMCS

[Raven434th]

 track ir is slaving to the tdc in the a10 c when using HMCS and when i press the slew it also follows my head tracking...should it be this way??? shouldn't it only follow my tdc input and not where i look?? as it is now  my head movement is being in-puted which has consequences and can throw the targeting off by mistake.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Edited Sunday at 06:24 PM by Raven434th

[Yurgon]

3 hours ago, Raven434th said:

track ir is slaving to the tdc in the a10 c when using HMCS and when i press the slew it also follows my head tracking...should it be this way???

I'm afraid you'll have to rephrase that question.

The TDC is the cursor you get in the HUD with the HUD as SOI. It doesn't have anything to do with the HMCS though.

You say TrackIR is slaving to something, but you then describe the opposite, which is something being slaved to your TrackIR. What do you mean by "pressing the slew"? The slew control on the throttle has a push or "Z-axis" command, but that doesn't do anything in our A-10C. Do you simply mean "slewing the HDC using the slew control"?

3 hours ago, Raven434th said:

shouldn't it only follow my tdc input and not where i look??

It depends on a few factors.

• Which sensor is your SOI?
• Did you hook anything in the HMCS?
• What's your SPI?

Generally speaking, when you have set the HMCS as SOI, the slew control will move the HDC around. The HDC is ground stabilized. But the HDC can only be slewed inside the HMCS' field of view. So if you look at a certain point you can slew the HDC around, and if you look away and then look back, the HDC will still be where you left it. But as soon as you tap the slew control, the HDC will reappear inside the HMCS' field of view.

So if you have a crappy slew control that maybe sends small inputs all the time, the HDC would appear to follow where you look all the time. This problem could be eliminated with a center deadzone for the 2 slew control axes (or with better hardware ).

But maybe I'm misunderstanding the issue you're having, in which case it would help if you could stick to the module's terminology quite precisely. A short track might also help explain the issue a little better.

[Raven434th]

sorry for taking so long...wild fires here in my place of residence.  ok...my mistake in terminology, I mean the HDC...it will follow the track IR head movement if it detects any input from the slew axis that is mapped. meaning I can then turn my head to slew...and its wildly exaggerated. Seems to me that should not happen...track ir should have no affect. howerever if it does track the pilots line of sight then I guess that makes sense too...similar to the apache IHADS monocle.

Edited yesterday at 02:40 PM by Raven434th

[Yurgon]

23 minutes ago, Raven434th said:

I mean the HDC...it will follow the track IR head movement if it detects any input from the slew axis that is mapped

That sounds like it's working as intended. Like I said, if there is axis jitter that leads to this behavior, you can tune the slew control axes and add a center deadzone.

The HDC itself is free to be on any spot on the ground, but if you slew the HDC, it'll snap to inside the HMCS' field of view (if it's outside the FOV when the slew is commanded).

I don't quite understand what you mean by exaggerated. Can you record a short track that shows the issue?

[Raven434th]

rgr....here's the track. I think you can see what Im getting at...it happens at towards the end.

LastMissionTrack.trk

Edited yesterday at 05:03 PM by Raven434th

[Yurgon]

4 hours ago, Raven434th said:

I think you can see what Im getting at...it happens at towards the end.

Thanks for the track! But I still don't understand the issue. For 2 minutes everything looks perfectly normal, and at the end I can't tell from the track what kind of inputs you're providing. The switching of SOI and SPI all throughout the track also makes it hard for me to understand what you're trying to show.

At this stage I'll go ahead and say that everything looks to be working as intended as far as I can tell.

[BIGNEWY]

Hi Raven, 

the team have tested and they are not seeing any issues.

could it be a local issue, some strange keybind? 

[Nate--IRL--]

On 8/10/2025 at 7:23 PM, Raven434th said:

 track ir is slaving to the tdc in the a10 c when using HMCS and when i press the slew it also follows my head tracking...should it be this way??? shouldn't it only follow my tdc input and not where i look?? as it is now  my head movement is being in-puted which has consequences and can throw the targeting off by mistake.

I actually want to keep this behaviour as it allows rapid Targeting of the SPI from the HMCS.

Nate

[Raven434th]

Ok so Nate...you get (or seem too) what I'm trying to convey...maybe you can explain it differently to the beta team ?....I just wanted to know if this is how its supposed to work.

 

Edited 6 hours ago by Raven434th

[Nate--IRL--]

NO! I want to keep it 

Basically with HMCS s SOI, the SPI when moved by the HAT, moves relative to the HMCS view area, rather than relative to the position on the Ground. 

So I can slew the SPI with the hat to the left, at the exact same time move my head to the right, and the SPI will move with my head to the right.

Using this quirk I can, for example, move the SPI 180 degrees from my 9 o'clock to my 3 o'clock in less than a second.

Nate