MrFickles

Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: https://www.simbrief.com/ofp/flightplans/WSSSWIII_PDF_1751544575.pdf WASM Errors: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty Specs: Ryzen 7 7800X3D, RTX4070 12GB, 64GB RAM. Trigger: Lowering spoilers after landing. 1751551214.bin

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.

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.

The EFB should not load cargo in the forward cargo hold on the ULR because all ULRs have deactivated forward cargo holds.

At mine they're all off so it's really airline dependent. What would be great though, is to let the user save their own panel state.

Still occurring on v1.0.8 after loading an autosave in cruise, I suspect the C.G. is totally out of whack as the FBW is flying with extreme pitch trim angles.

Don't forget that the seats on the route are minimally premium economy costing maybe $1000 or perhaps thrice that for business. The route is probably profitable even with low load factors. Even Singapore Airlines found it worthwhile to operate WSSS-KJFK in the middle of the pandemic when load factors were like 30-40%.

Just a simple one, on the MFD POSITION/TIME page with time reference set to AUTO, you can still select the time and date as if it was on MANUAL even though they aren't supposed to be editable. You can't actually type anything and can only hit ESC to cancel text editing.

Mostly fixed as of version 1.0.6 but the auto-tuned frequency is still incorrect. Manually tuning to the LDA frequency is possible and flying the approach using LOC is possible. No further issues after manually tuning the LOC frequency.

When selecting an LDA approach, the approach defaults to FLS following the runway extended centerline which should not be the case. An LDA is simply an offset LOC approach using ILS symbology with a visual turn to final. In addition, the aircraft may auto-tune a garbage ILS frequency with the wrong frequency and wrong identifier for the LOC. Manually tuning the LDA by either using its identifier or its frequency does not work as it should. Even though the RAD NAV page may correctly identify the LOC, the PFD doesn't display the localizer and the approach must be completed on NAV/APP-DES mode. Reference: this video at around 1:41:20: The aircraft is set up for the LDA 23 approach at RJTT with the PFD indicating "ILS" as expected.

Is it possible to insert a STAR without also inserting an approach? At current I am forced to select both an arrival procedure and approach before the *INSERT shows up. This would be more typical at airports where there the entry into the STAR starts from hundreds of miles away with multiple arrival runways being used simultaneously such as in the US. ATC would usually assign the landing runway halfway down the STAR.