nfeuchtho

Check your fluid levels in the Maintenance tab. My guess is your engine/APU oil level is zero, which can cause a complete failure, since APU does not start your aircraft is out of power. Congratulations! You now have a savestate for a deadstick landing with deployed RAT 🙂

Got to be way more than 50%. The FMS is almost feature complete now, only few things like LL crossing and RTA missing, flight model has now been tweaked in .10/.11 to feel realistic in manual flight though there seems to be an issue with some hardware having a dead zone in roll (I use TCA airbus sidestick/throttle quadrant without issue), check your hardware to make sure you don't run into this issue. There should be about 200 ECAMs by now, which is quite a big percentage of the real thing. Failures are definitely not study-level yet, simply because some are missing. TCAS is now present and working for me (2024, A359). Circuit breakers / reset switches are not there (not a big thing, maybe one or two sections in FCOM require circuit breakers or reset switches). So much for the features. Don't get me wrong, there are still bugs, but those are being ironed out. Most significant issues right now are arguably: PERFORMANCE! The real aircraft is extremely complex and computerized, and simulating that to a high fidelity takes computational resources. Lots of them. Especially VRAM for texture rendering, make sure you boast at least 12GB of VRAM, else be prepared to tone down your settings, at least in 4K. I have an RX 7800XT (16GB VRAM), and run out of VRAM with textures set to High (4K, HDR). Also, due to its complexity, the plane is quite CPU heavy. Check reddit/discord for expected FPS with your specs. Performance on 2020 is also apparently way worse than 2024. Works well in SU3 Beta, though, apart from some LOD issues on load. ETA for waypoints may be way off in descent. This is reproducible and being worked on by the team. AP disengages on long flights. This has been traced to MSFS live-weather updates which may cause rapid attitude change, thereby disengaging AP. If you have AP protection enabled in the OIS, then AP will switch into HDG mode instead and you go off your flight plan. Annoying for people who go to sleep during long-haul cruise, I am not one of those. Have not experienced this on long-haul/ultra long-haul with time acceleration. Some managed speed/VNAV issues. Specifically, sometimes the aircraft miscalculates the descent path and shows it will meet speed/alt restrictions when it will clearly not. Secondly, the anticipated speeds on climb/descent are different on PERF page and F-PLN page. This is only this low on the list because, ultimately, it is the pilot which is responsible for the aircraft and its trajectory. You should never ever fully rely on automation, but use it as an assurance to your own calculations. If you see you are too fast to meet the speed restrictions or you are high on profile, you help by e. g. applying speed brakes or setting SEL speed to increase descent rate. Even in real life, as every software engineer will know, software may and eventually will glitch, your brain, however, should not. If it does anyway, you have a PNF 🙂 Apart from that, there is still the occasional WASM crash (have not experienced any since 1.0.7), but with the Autosave feature, that is no longer a flight ender. You just reload the flight and apply the latest savestate. Done. Objectively and on every level, fidelity has climbed tremendously from release. The reason everyone only focuses on the negatives on, say reddit, is the - sorry to say this inibuilds - horrible release. Some people gave up on the A350, but by now the aircraft is approaching / has maybe already reached the state it should have been released in. Fly it, you will have fun now and I am sure it will get even better.

Are there any news on this? Thanks.

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!