C. Schaffhausen

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

Just had WASM crash during cruise. 1745215663.bin

Same issue on 1.0.8, Autopilot disconnected when I was AFK during a turn, but ended up flying straight and level to Alaska instead of Toronto.

I'm on FS2020, and I could consistently achieve a loss of sound in the virtual cockpit if I enter my route manually. It happens when you enter the route by selecting airways, then entering the airway and waypoint using your physical keyboard. The sound in the VC will mute after a few entries and won't recover unless you reload your sim. The build is 1.0.8, a fresh install, and all wasm folders are cleared.

FS2020, APU external sound still too loud from outside view, especially if you're near the tail cone.

Your wife? Or the plane?

Yes that's what I thought, the speedbrakes operated like Boeing ones on the Inibuild A350.

Your plane is very rude. No this is not funny, not at all.

I too have an AP issue on my previous flight, AP remains on but NAV is off, ALT was in V/S mode +/- 0ft/min.

The N1 animation accelerated way too quickly, there are some good references available for comparison with the in sim behavior.

Just tried in 1.0.6, seems to work now

If the plane is in HDG mode, and if the heading selected is not reached, LOC* won't engage even if the plane is right on the localizer. For example, I'm on approach RWY 09 from the north, HDG 180. I select HDG 120 to intercept, if the plane is close to/on the localizer, but is still in the left turn to HDG 120, LOC* won't engage and would overshoot the localizer.

Just to raise this issue a bit, the volume is normal-ish in 2024, the issue is with the 2020 version only.