CookieChiara

March 19

6 minutes ago, Awemeter said:

I am pretty sure this is less of an ini issue but a sim/vatsim issue. I remember reading a post on the vatsim forums a while ago about the sims and their different atmosphere simulation causing issues but this was a long time ago so I cant find it n

I kinda doubt it because the planes are displayed at the correct altitude so the data must be somewhere.

March 19

It would appear to me that even in 1.0.4 the relative altitudes are still not correct, ENT7741 is showing at the same altitude as me on Vatsim, yet 700ft below on TCAS.

QNH in the area was 1007, so I have a hunch that you're comparing the traffic's true altitude to my pressure (or indicated, I have no way of telling) altitude instead of using pressure altitude for both like the real TCAS does.

March 15

On 3/10/2025 at 5:45 AM, richboy2307 said:

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.

To me an obvious solution would be to use a table of the most common aircraft types to lookup the WTC, and just hide the indicator if the type isn't on the list. As a user I prefer no info over incorrect info. Just something to consider

March 2

When flying an offset non-precision approach with FLS, the F-LOC beam projected by the FMS presents a straight runway extension instead of the offset approach path as described by the FCOM. See the following pictures for an example from EBBR on the VOR 07L, which is offset by 15°.

Note the difference between the magenta-dashed FLS beam and the solid green NAV path. According to the FCOM however the FLS beam should extend from the MAP (recoded as EPxxx, here EP07L) on the reciprocal of the final approach course, see the FCOM reference below:

This makes FLS basically useless for offset approaches in the current implementation.

Behaviour is consistent across FS20 and FS24 with both NG and default navdata and tested at various airports.

The requirerd data should be available in the NG dataset at least, see the below excerpt from the NG database for the Prepar3D FSLabs A32X with the relevant data highlighted in yellow:

February 28

Are you by chance viewing the offside OIS? The options are only on the left side OIS

February 28

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

February 28

Another issue that just popped up, re-entering an approach without re-entering the arrival breaks the routing, even if the arrival is applicable for both approaches.

Steps to reproduce: Initially enter FAOR AVAGO 1C ILS Y 03L, then change to ILS Z 03R without reselecting the arrival. Results in the last waypoint of the route (in my case ITROL) being connected with a direct to CI03R

Similarly when just reselecting / changing the arrival, the approach will be removed from the routing.

Using Navigraph Database in FS2020

February 28

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.

February 28

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.