April 23Apr 23 Hi everyone, I’ve just updated to v1.2.5 and completed a few flights. I noticed several issues that seem to be new or persisting. I would appreciate it if these could be fixed in the next update. • Autopilot Disconnect Sound: When the AP is disconnected, the alert sound stutters or is momentarily interrupted. • LNAV / Direct-To Issue: When executing a "Direct-To," the aircraft does not follow the LNAV path correctly and turns in an unexpected direction. • Autobrake Disarm Voice: The "Autobrake Off" callout is extremely quiet (like a whisper) and hard to hear. • TCAS Reset on Takeoff: On my second flight, even though TCAS was set to ON/TA-RA, it automatically switched to OFF upon rotation/takeoff. • Company Message: The "Company Message" notification still does not disappear as expected. Thank you for your hard work on this project! Edited April 23Apr 23 by Yon
April 23Apr 23 Hello, what about the WASM stability? Thank you for your report! 💖 That DIR-LNAV thingy is very frustrating, I was surprised about it, I just clicked direct and got to set up something else, looked out and I am 40 NM somewhere else 😄
April 23Apr 23 14 hours ago, Yon said: Company Message: The "Company Message" notification still does not disappear as expected. Can't confirm. The notification disappears as soon as you have read the messages.
April 24Apr 24 Is it possible the update process was flawed - as in the wrong package was uploaded or incomplete? I just had my first flight in quite a while and updated I had about 10 - 15 weird things happen. - Could not get the autopilot pull function to reliably work - Approach mode armed itself. - G/S activated when aircraft was 2000 feet below the glideslope - After landing I got a NAV IR not aligned message - LS button was "always on" - Slide deployed when opening door at terminal - Step altitudes kept deleting themselves - Repeated CPU spikes causing glitchy performance - A range of interactive click spots not working (doors, etc.) This may be naive, but is it possible an older update file was used? Feels like the plane went many steps backwards in this update... - Daniel
April 25Apr 25 19 hours ago, danielsousvide said: Is it possible the update process was flawed - as in the wrong package was uploaded or incomplete? I just had my first flight in quite a while and updated I had about 10 - 15 weird things happen. - Could not get the autopilot pull function to reliably work - Approach mode armed itself. - G/S activated when aircraft was 2000 feet below the glideslope - After landing I got a NAV IR not aligned message - LS button was "always on" - Slide deployed when opening door at terminal - Step altitudes kept deleting themselves - Repeated CPU spikes causing glitchy performance - A range of interactive click spots not working (doors, etc.) This may be naive, but is it possible an older update file was used? Feels like the plane went many steps backwards in this update... - Daniel Dan, try to reinstall and clear the WASM folder and run the sim as admin after updating. Good luck.
Sunday at 02:20 PM5 days Author @イニジャミール I'm also awake. Slide deployed when opening door at terminal I truly respect the quality of your modeling and the hard work behind it, and I understand the complexity involved. That said, development currently feels inconsistent—two steps forward, one step back. Releasing new aircraft like the A340 and A380 is exciting, but it would be more reassuring to see each product brought closer to a complete and polished state before expanding further.
Thursday at 03:51 PM1 day On 4/22/2026 at 9:35 PM, Yon said: Hi everyone, I’ve just updated to v1.2.5 and completed a few flights. I noticed several issues that seem to be new or persisting. I would appreciate it if these could be fixed in the next update. • Autopilot Disconnect Sound: When the AP is disconnected, the alert sound stutters or is momentarily interrupted. • LNAV / Direct-To Issue: When executing a "Direct-To," the aircraft does not follow the LNAV path correctly and turns in an unexpected direction. • Autobrake Disarm Voice: The "Autobrake Off" callout is extremely quiet (like a whisper) and hard to hear. • TCAS Reset on Takeoff: On my second flight, even though TCAS was set to ON/TA-RA, it automatically switched to OFF upon rotation/takeoff. • Company Message: The "Company Message" notification still does not disappear as expected. Thank you for your hard work on this project! Hi, so this isn't to say that the issues aren't happening on your end, however I've done 2 flights on 1.2.5 since it released public. I have yet to encounter any of these issues outside of the "Autobrake Off". I'll give Direct To's another go as admittedly my route was pretty straight-line both times and one of the landings was into Quito so you can't really deviate there. I'll keep an eye on that TCAS one as well as I noticed yesterday on VATSIM my MODE C was randomly off even though I was set to TA/RA in SURV page. Thank you
Thursday at 05:47 PM1 day On 4/24/2026 at 3:06 PM, danielsousvide said: Is it possible the update process was flawed - as in the wrong package was uploaded or incomplete? I just had my first flight in quite a while and updated I had about 10 - 15 weird things happen. - Could not get the autopilot pull function to reliably work - Approach mode armed itself. - G/S activated when aircraft was 2000 feet below the glideslope - After landing I got a NAV IR not aligned message - LS button was "always on" - Slide deployed when opening door at terminal - Step altitudes kept deleting themselves - Repeated CPU spikes causing glitchy performance - A range of interactive click spots not working (doors, etc.) This may be naive, but is it possible an older update file was used? Feels like the plane went many steps backwards in this update... - Daniel Approach mode arms itself at a certain distance or configuration. I'm no pilot by any means but I do know Airbus does that. G/S I believe will activate when below glide slope. It shouldn't activate when you above it. I can't explain the Nav IR. Probably a bug. Dumb question...could you turn the LS button off at any point and it would stay off? Slide deploying at the terminal may be because you didn't disarm them before open the doors? Step alts deleting themselves should not happen. May be a bug. Have never experienced this. I personally input STEP ALTS manually to avoid the WASM crashes and screwy ETA and FUEL calculation issue that arise from the auto input STEP CLB setting. CPU spikes can't help with because I am on console. Click spot issues I have encountered. Can be a pain in the butt.
Create an account or sign in to comment