reported Bug with TDS and thread bearing

[DaWu]

SA8 at your 3 clock for example. With TSD Map orientation set to Track Up you can see the SA8 in your TSD relative to your heli at 3 clock.

But if you set TSD to Map orientation N UP like I always like to do then the SA8 is relative to you not on your 3 but somewhere else what is complete wrong. This should be addressed and fixed

[Floyd1212]

Is the threat being shown at the 3 o'clock position relative to the direction your ownship is facing on the TSD?

In other words, if you have the map set to N-UP and you are flying east, and there is a threat at your 3 o'clock, is it drawing the threat along the bottom edge of the TSD, to the south?

Edited August 15, 2023 by Floyd1212

[DaWu]

The threat is in a different "clock" position of yours if you swith the map orientation

[Vakarian]

Well, yeah, that makes sense. "o'clock" positions should be matching the TSD only if it's in "track up" mode.

If you set it on "North up", you are flying due west and hear "SA-8 3 o'clock", you want the it showing UP on the TSD, not on the right side as that would mean it's at your 6, not 3.

You have to understand two different spatial references being in place when you put the TSD "north up" and you hear CMWS call in relation to your aircraft. They are not the same.

 

[Floyd1212]

I also like to fly with my TSD set to N-UP, so I often bring up the ASE overlay on the video feed from the TADS on the other display.  This ASE overlay still presents the threats in relation to the front of the aircraft being at 12 o'clock, even when the TSD on the other screen is showing the threats relative to the ownship icon and direction of flight on the map.  This way you get the best of both worlds.

[DaWu]

That would be an explanation but it isnt working like that.

 

1. Here you  can see where I am and where the SA8 is

So the SA8 is on my 2 o'clock right? I am the leading bottom Apache.

 

The TSD shows me the SA8 in my 11 o'clock

 

According to you guys with TSD not beeing altered by N UP or HDG Up this would mean the SA8 is on my 8 o'clock which would be completely wrong.

 

And the TSD Threat bearing does change with N UP or HDG UP as you can see here in the screenshots:

 

TSD with N UP:

 

TSD with HDG UP:

 

With HDG Up the SA8 is on my Nose around WP8 which is correct. With N UP The SA8 is somewhere else but not where it should be. For me its a Bug.

Even if you were right then with N UP the SA8 should be always on the same position (12 oclock) in both screenshots.

 

Trackfile is attached

null

null

Slingload Escortl-20230815-202533.zip

[Floyd1212]

What appears to be happening is the threat is shown as though the ownship icon was still located at the bottom-center, like where it would be when in HDG-UP mode.

In this screenshot I grabbed yesterday, the warning was "SA2, tracking, 5 o'clock".  In the ASE circle to the right, you can see the correct orientation.  In the threat display on the TSD to the left, while in N-UP mode, the dashed "tracking" line is not drawn to the ownship icon, but to the bottom-center position.  If the ownship icon were moved to that location, but kept facing the same direction, it would look correct.

This also seems to hold true on your screenshots (more or less).

Maybe a SME can answer if this is working correctly?

[Floyd1212]

Here is another track file to instantly demonstrate the issue/question.

ASE Test.trk

The ASE Page (right) shows the true orientation of the threats in relation to the aircraft; 3 o'clock and 7 o'clock.

The same threats on the TSD Page (left) when set to N-UP show the dotted line drawn back to the lower-center of the map, where your ownship would be shown when set to Heading-UP mode.  This gives you the impression that the threats are at 1 o'clock and 9 o'clock from your current position and orientation.  Is this how it works IRL?

[Lord Vader]

Hi all

I've reported this internally for analysis.