C. Schaffhausen

Tried VHHH-CYYZ, similar issue. Tested for a full day with a few flights, only arrived once but with AP disconnect, LNAV mulfuction, and on approach ILS autotune failed and LS not showing correct info. On my last flight, I was able to fly all the way to close to 55N120W without AP issues, but the sim froze and I had to end the sim forcefully. I switched over to the in-sim navdata and the issue persist.

I'm sure something here has mentioned already, but I'll mention here as well. The shape of the flaps, and lines along the trailing edge, is quite inaccurate. *Original screenshot *Non-edited shot for reference The pictures should explain why I think the current A350 wing looks like an A330 port. Not only the A350's system has its issues, the model also desperately need a v2 upgrade. I hope the team can take some time to reflect how to capture the essence of the modelled aircraft; while the current model looks ok, I don't think it captured the aerodynamic shape that makes the aircraft so efficient, which is a big deal for the A350. Otherwise, the A380 project would likely suffer from the same problem. Thank you team, for your effort!

I've been very lucky, since I cleared WASM, uninstalled and re-installed the A350, the LNAV issue seems to be gone. I haven't tried VHHH-CYYZ though so I can't be sure yet.

I have this issue with a fresh A350 install consistently, wasm cleared, everything uninstalled, then re-installed 1.0.8.

Did you use time compression as well?

No key binded at all. I'm now approaching TOD to KLAX and the aileron does droop a bit, on both sides too. Very inconsistent. The F/CTL page does show a greater droop on the inboard ailerons as well.

I just take another look, when cruising the ailerons are neutral, during descent the ailerons both pointed downwards.

As titled, after landing and the use of med autobrake, the brake indicator does not work anymore.

Yes it is. I cleared the WASM folder as well. I have uninstalled everything again and reinstalled again. I think it might be related to LAT/LONG waypoints, since my flights didn't deviate when following waypoints.

AP remains connected, but NAV and ALT CRZ are both off; my flightpath drifted to the left. Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Listed Below Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Multiple attached 1745319043.bin 1745317420.bin 1745317937.bin 1745318309.bin 1745318679.bin

I can confirm as well, both left and right aileron are lower than the neutral position

I flew my route for the second time, same behaviour at the same position. WASM crashed between AKISU and 50N170E. Here is my route: VHHH-CYYZ RTE: DALOL V631 ENVAR M750 MUKEP Y891 OVSUN Y893 IGMIS Y57 POROT A590 DOVIX OTR5 ADNAP R591 ADGOR AGEDI AKISU 50N170E EYWAK RADIC 55N160W 56N150W 56N140W RIBIT 55N120W 54N110W 52N100W 49N090W OTNIK BOXUM7

After my WASM crash, I tried to resume my flight by loading the Autosave. However, the ALT*/ALT/ALT CRZ function does not work, the aircraft would overshoot the target altitude and keep climbing/descending. Aircraft: A350-1000 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Listed Below Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Attached 1745217633.bin

Added to OP

Just had a WASM crash during cruise, Time compression at 4x. Aircraft: A350-1000 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related WASM Error: Listed Below Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: Attached 1745215663.bin