nfeuchtho

Still no change (1.0.7), and with no weekly updates any more, it looks like we're in for some weeks of waiting. And that is if TCAS takes priority in fixing. Otherwise it could be months... The issue is TCAS conflict zones seem not simulated at all atm, making VATSIM flying quite tricky. Also be wary of traffic being displayed at the wrong relative altitudes. Deviation ranges from 0ft to -1'300ft.

This is a known bug, there is confirmation on Discord. Will probably be fixed when they address CPDLC, unfortunately that could take anywhere from weeks to months as far as we know with weekly updates cancelled. Also, have you tried submitting a WX deviation to mailbox? It will just vanish. Magic.

You use the checkmark button and the scrollwheel on the center pedestrial (panel below the FMS1/2) to run ECAM checklists.

Hello First of all, thank your for this amazing aircraft. It is very fun to fly and if you get used to the unique flight characteristics of the A350, it is also intuitive. Now for my issue: In any flight so far, whenever traffic comes close enough to warrant intruder classification, I always only get the regular potential intruder non-filled-out diamond. At one point, FSLTL traffic approached up to same flight level at 1 mile horizontal separation, but I got neither a TA, nor an RA (which should definitely be triggered with this CPA). Since no TCAS alert was triggered, there was also no indication on the PFD and I only noticed the traffic way too late since the airspace was busy. Am I doing something wrong? It happens on all TCAS range settings, even if it is set to TA/RA. Since TA/RA are not triggered, the aural alerts are also missing. I once had an issue where traffic that should not have been remotely close to causing a conflict (horizontal separation >>10 miles) were marked as RA zone intruders (red square), but still no alerts or indications on the PFD. I really enjoy this aircraft - if I could get the TCAS to work flights with traffic would be a lot more immersive. Thanks in advance!