zhangys10 Posted Tuesday at 07:21 AM Posted Tuesday at 07:21 AM I know this sounds strange, but it just happened to me twice, once in 1.0.8 and the recent one also in 1.0.9. Steps to reproduce: 1. start flight in cold and dark and setup as usual, 2. take-off and fly to cruise , turn on AP 3. insert the hoppie logon in EFB and use the ATC/COMM page to notify and request some D-ATIS 4. turn on auto time compression and set up to 4x 5. wait for the issue When this happens, all the avionics or flight control not working, in detail: - you can still click the button to switch pages, but all MFD page show blank. - all the MCP panel buttons and knobs are not responsed - the aircraft when out of control and starting banking left, all the input from my Yoke/throttle/Rudder can not take back the control The first time I do saw a WASM crash message in the debug console, but the most recent one it shows nothing, 0 error messages. This only happened when I use Hoppie logon, without the hoppie, I tested many flights and none of them had same issue. BTW, I loaded the autosaved one after the crash, and immediately removed the Hoppie logon code, after that, the same flight safely unitl landing on destination and shutdown.
Powie Posted Tuesday at 09:16 AM Posted Tuesday at 09:16 AM I have had some strange behaviours also.... My idea is that something goes wrong after pressing STRG to enter text in de MCDU... I have changed my handling, for me I now NEVER use the keyboard and enter all data via the mouse/keys in the aircraft. No problems like these since then.
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