MrFickles Posted 8 hours ago Posted 8 hours ago For 5 times in a row on version 1.0.12 and 1.1.0, the A350 systems are freezing in fight. It happens any time between 5-15 hours in cruise. I lose all ability to control the aircraft with either the FCU or with physical controls. Along with the autopilot freeze, the PFD, ND, and ECAM are also frozen. OIS and MCDU works ok other than a loss in FPS. All other cockpit switches work fine. There are no WASM errors reported in console. I have tried clearing WASM folder and reinstalling the aircraft, to no avail.
Xenon341 Posted 6 hours ago Posted 6 hours ago Hi there, Can you add some informations requested in those instruction ? That would help the team find the cause. Thanks !
Lukasz Krajnik Posted 5 hours ago Posted 5 hours ago 1 hour ago, Xenon341 said: Hi there, Can you add some informations requested in those instruction ? That would help the team find the cause. Thanks ! Hi, He wrote it is not a WASM crash. I have had same issue on every flight since 1.0.12. No need to do time consuming WASM crash report if we veryfied it is no WASM crash.
MrFickles Posted 4 hours ago Author Posted 4 hours ago 2 hours ago, Xenon341 said: Hi there, Can you add some informations requested in those instruction ? That would help the team find the cause. Thanks ! This probably isn't a WASM crash. In a WASM crash, the whole aircraft is frozen and nothing will work. Here, I can still do things like switch on and off stuff using the switches, or even mess around with the EFB/FMS. The only things that don't work are the FCU, PFD, ND, ECAM. For reference, this is my console after encountering the issue: Note that there are no errors shown.
YS0430 Posted 4 hours ago Posted 4 hours ago 11 minutes ago, MrFickles said: This probably isn't a WASM crash. In a WASM crash, the whole aircraft is frozen and nothing will work. Here, I can still do things like switch on and off stuff using the switches, or even mess around with the EFB/FMS. The only things that don't work are the FCU, PFD, ND, ECAM. For reference, this is my console after encountering the issue: Note that there are no errors shown. Strange, I just encountered something similar in my 4 hours (+1hour prep) flight and suddenly the plane can still follows the flight path, fms works, but the AP panel, auto pilot altitude hangs, the knobs can be turned but not working..
Xenon341 Posted 3 hours ago Posted 3 hours ago 1 hour ago, Lukasz Krajnik said: Hi, He wrote it is not a WASM crash. I have had same issue on every flight since 1.0.12. No need to do time consuming WASM crash report if we veryfied it is no WASM crash. Yes but there are WASM crashes that don't output logs, I had some that I've reported and we are not alone. Still reporting the same information can be useful for the dev team.
Lukasz Krajnik Posted 1 hour ago Posted 1 hour ago 2 hours ago, Xenon341 said: Yes but there are WASM crashes that don't output logs, I had some that I've reported and we are not alone. Still reporting the same information can be useful for the dev team. How do you know if it was WASM crash if no WASM error saved in log? I had plenty of such without any WASM connection, reported some here without response from IniBuilds, neither confirmation that it is WASM. If we get WASM crashes without any log that it is WASM fault then IniBuilds is in deep… I just wonder how was it possible that P..G found workaround to this which works for most (but not every) users.
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