C. Schaffhausen Posted Monday at 06:56 AM Posted Monday at 06:56 AM 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
Swisspilot1986 Posted Monday at 07:34 AM Posted Monday at 07:34 AM known issue unfortunately not solved, yet
FelixM Posted Monday at 12:20 PM Posted Monday at 12:20 PM (edited) I would like to add the following. Autothrust is also not working for me, plane continues with almost stall speed. It is not accelerating to the original speed. Even with manual thrust control. Engine is running at full capacity but no speed gain. Ore in other words Autosave recovery is useless at the moment. Sry for those harsh words, but I just spend 5 hours of my life on a long haul flight, got CTD (as always, this time after 4hours. longest flight so far yeahh) and tried this new feature. Iam really looking for the Vatsim cross the pond event, that will be CTD festival with the A350. Edited Monday at 12:29 PM by FelixM ---------------------------------- AMD Ryzen 7 7800X3D Nvidia GeForce RTX 4080 16GB 64 GB RAM Dell Alienware AW3432DWF 3440 x1440 165 Hz
richboy2307 Posted Monday at 01:43 PM Posted Monday at 01:43 PM 8 hours ago, C. Schaffhausen said: 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. Thanks, issue is logged and team is actively working on it. 2 hours ago, FelixM said: Autothrust is also not working for me Please confirm after reloading your autosave that - A/THR is enabled on the FCU - Your throttle axis is in the CLB detent - FMA reads SPEED / MACH / THR IDLE / THR DCLB depending on phase of flight as an indication of thrust control Your hardware input of primary flight controls, particularly throttle axis prior to loading the autosave can affect the status of that control after reloading. Hardware inputs will override the autosave variable always (same as it does in active flight). Thanks! Vrishabh Sehgal ( @Richboy2307 ) Community Team Member & Tester iniBuilds Ltd. | inibuilds.com
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now