Skyrock

any idea what caused this? I'm always getting a WASM crash in cruise only there without me doing anything. It's quite frustrating.

Just cruising along at FL410, no inputs or anything. Screenshots attached. Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes WASM Error: It for some reason only shows vdgs related items? But clearly the displays are frozen and my A/C is flying to the northeast instead of east. Specs: Ryzen 9800X3D, RTX 4080 Super, 32GB of RAM Autosave File: Included JX119_YWG_FRA.pdf 1766248844.bin

Did they at least fix the Time bug where it's showing an ETA in the past for the next waypoints? I missed that in the changelog...

A fixed derate is useful in cases where you need to lower Vmcg (Minimum control speed on ground) and subsequently V1, e.g to increase your performance limited takeoff weight on short and/or contaminated runways. On for example contaminated runways, Flex takeoffs are not allowed, hence you would only be able to do TOGA takeoffs. The main problem in these cases: if you have an engine failure. Now, you have to have a higher VMCG and V1 in order for the rudder to have enough authority to counter the asymmetric thrust during an engine failure with TOGA power. With a fixed derate, in case of engine failure, the remaining thrust on the operative engine remains at the derated thrust level. It's actually prohibited to advance to TOGA with a fixed derate (unless during a windshear or if above F-Speed), because it might lead to a control loss. Therefore, with a fixed derate there is lower asymmetric thrust and with that, the VMCG/V1 can be lower since the rudder can achieve enough authority to counter the moment by the asymmetric thrust at a lower speed. The Performance Limited Takeoff Weight increases in those cases. Most of the time, your takeoff performance calculator will still present a Flex temp and only in rare occasions (like contaminated runways) it will provide a fixed derate. On Boeing aircraft, a fixed derate and a flex (here called assumed temperature) can be combined (e.g TO-1 42°C), so in case of engine failure by pressing the TOGA button, only the assumed temperature would be removed but the fixed derate would remain. On Airbus aircraft, a fixed derate can not be combined with a Flex, so it's either one or the other.

And it happened again...this time (yes I said I wouldn't do it, but I did anyways) enroute from SIN to JFK, after 9hrs over the pacific. I was not doing anything (again) and everything froze. I forgot to check the console for the WASM crash, but at least this time I managed to save the last autosave. The WASM crash or display freeze happened about 10min after the autosave... I'm done with this. Uninstalling the A350, will revisit next year or so. It's way too frustrating (despite the autosave feature) to always be waiting for the WASM crash to happen. But I'm not willing to deal with this anymore 1757833492.bin

Same. Yesterday I did SIN-SYD without any issues so I was kinda hopeful that I could do SIN-JFK tonight. But nope, not under these conditions. 50% reliability is not enough...

Hello, Aircraft: A350-1000 Simulator: FS2024 Navdata: Navigraph OFP: included Specs: CPU: AMD Ryzen 9800X3D, RTX 4080 Super, 32gb RAM Autosave: unfortunately already deleted. WASM: apparently none? I'm currently enroute from SYD to SIN in the A35K and after about 2hrs, overhead Alice Springs (AS), my displays froze completely. Why did I not write "WASM crash"? Because apparently there was none. According to this screenshot: I don't know whether this helps to trace down the issue or not. This was the only error shown. I was not doing anything, in fact, I was laying on my couch and realized that the time in the ECAM had stopped 30min prior and with it all other displays. The ND was showing me going offtrack though before it froze. I was cruising at FL380 using Sayintentions. I merely just realized because my FO kept checking in with new sectors despite CPDLC not showing any handoffs or messages apart from the usual "connected". At this point the A350 is just frustrating for me. Every 2nd flight I get a display freeze (WASM crash or not, idk) and despite the autosave feature, it kinda ruins the experience. Last time I got it enroute from EDDF to WSSS after 4hrs into the flight. Unfortunately I didn't check the log. I attached the OFP just to be sure. VS119_SYD_SIN.pdf