[TCAS] Consolidated TCAS issues post

[CookieChiara]

Vatsim traffic is being shown with incorrect wake vortex category on the ND traffic information symbol

The aircraft here is listed on Vatsim as aircraft type A359 and correctly identified as a heavy on vatsim Radar, however the traffic information symbol shows it as a medium.

the traffic information window on the SURV - TRAFFIC Page does not list a wake turbulence category at all.

FCOM Reference:

 

Edited February 28 by CookieChiara
Renamed topic to more accurately reflect the contents

[CookieChiara]

Furthermore, with FLT ID DISPLAY ON ND set to OFF, the ND should still show a basic aircraft symbol instead of just the TCAS other traffic symbol

Note also the padding issue around the TCAS symbol with the relative altitude overlapping the traffic symbol.

[CookieChiara]

Yet another issue I discovered, had another traffic crossing opposite direction on the same airway, 1000ft above and in level flight, yet TCAS marked them immediately as an RA intruder from about 20nm out. To my understanding of TCAS and from how it's implemented on the A220 I fly IRL, that should only have resulted in a proximate traffic symbol at most. Of course I'm not too familiar with the A350 irl, but I cannot imagine that this represents realistic behaviour

[Awemeter]

Another issue I have noticed is that I never receive TCAS RAs. The ND will display the conflicting aircraft in red, but I never receive climb or descend instructions on the PFD.

[richboy2307]

Hi,

Thanks noted above items.

On 2/28/2025 at 9:07 PM, CookieChiara said:

The aircraft here is listed on Vatsim as aircraft type A359 and correctly identified as a heavy on vatsim Radar, however the traffic information symbol shows it as a medium.

We are aware of this one. We are parsing the traffic data via Simconnect from within the sim. The issue is the sim doesn't relay any variable wake turbulence data in any exposed variable that we can poll for this information from within the sim. Same is true for vpilot or other injected traffic such as FSLTL. We're looking at solutions but this is largely a "sim limitation" with regards to data available for the moment.

On 2/28/2025 at 10:44 PM, CookieChiara said:

Yet another issue I discovered, had another traffic crossing opposite direction on the same airway, 1000ft above and in level flight, yet TCAS marked them immediately as an RA intruder from about 20nm out. To my understanding of TCAS and from how it's implemented on the A220 I fly IRL, that should only have resulted in a proximate traffic symbol at most. Of course I'm not too familiar with the A350 irl, but I cannot imagine that this represents realistic behaviour

This one should be fixed as of v1.0.2 update.

4 hours ago, Awemeter said:

Another issue I have noticed is that I never receive TCAS RAs. The ND will display the conflicting aircraft in red, but I never receive climb or descend instructions on the PFD.

Is this in the incidences mentioned above by Chiara, where traffic is "erroneously" flagged as red on ND when they aren't really a threat? Or do you mean in genuine instances where traffic should have been threats? Just for testing I tried with FSLTL injected traffic and was able to receive RAs for genuine traffic threats.

Thanks!