All Activity

Is there any plans on bringing planes like the a350 or a340 to the msfs 2020 marketplace on xbox?

I had this WASM crash when I clicked Active in FMS1 then Flight Plan after creating the secondary flight plan To reproduce Create Flight Plan Create Sec flight plan Click Active on FMS1 Click Flight Plan Information Aircraft: A350 Simulator: FS2024 Version: v1.2.1 from Ini Store Navdata Method: NAVIGRAPH OFP: Attached Specs: Intel i5-12400, RTX 4060 Ti, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: WASM: Error during MFD_gauge_update execution. Error code : 0xc000001d LFBOEGCC_PDF_1771183502.pdf 1771186575.bin

As Pilot061 said, there’re are workarounds but no fix as of yet. Three easy workarounds that are simple to accomplish but are definitely immersion killers: 1.) Unplug your MCDU and plug it back in, screen functionality restored until next time 2.) Using a powered and switchable USB hub, a power cycle (off/on) does the same as #1 3.) in SimApp Pro, select the MCDU and you can switch the MCDU from Pilot’s command (left side) to co-pilot’s command (right side) and back again if needed for the next freeze. This too restores functionality but like in all cases, the freeze returns. IT NEEDS TO BE SAYS SAID: Both the Fenix and FSLabs airbuses when using the same WinCTRL gear, same SAP NEVER freeze up. Never been a problem for them, only the ini a340-300 which is the ONLY ini airbus with a working external physical MCDU. Unfortunately it does not remain working but better than no working external physical MCDU I suppose. -A

I had this WASM crash when I clicked Active in FMS1 then Flight Plan after creating the secondary flight plan To reproduce Create Flight Plan Create Sec flight plan Click Active on FMS1 Click Flight Plan Information Aircraft: A350 Simulator: FS2024 Version: v1.2.1 from Ini Store Navdata Method: NAVIGRAPH OFP: Attached Specs: Intel i5-12400, RTX 4060 Ti, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: WASM: Error during MFD_gauge_update execution. Error code : 0xc000001d 1771186575.bin LFBOEGCC_PDF_1771183502.pdf

The packs have been deprecated and are no longer supported. Lose the packs and all will be as it should be. Blue skies, -B

When I initiate a flight with the A350 in msfs20204 and I use one of the airline packs downloaded via die ini manager, the whole Virtual Cockpit is missing. No texture loads. The whole VC is "missing" When I use the default cabin OR no cabin, the VC is loaded normally

Aircraft: A350-900 Simulator: MSFS2024 Version: 1.2.1. - inistore Navdata Method: NAVIGRAPH WASM Error: Unfortunately missed to screenshot anything before shutting down the simulator. Specs: Intel i9 13900K, GeForce RTX 4090, 64GB RAM Screenshot/Video: Unfortunately missed to screenshot anything before shutting down the simulator. Airport: MMUN (Cancún) Runway: 12R STAR: NOSAT1B Transition: RIDUG Approach: ILS X 12R Issue: Selecting the RIDUG transition after loading the NOSAT1B STAR consistently causes a WASM crash. Reproducibility: ✔ Occurred for two users ✔ Happens immediately upon selecting the transition ✔ Repeatable on multiple attempts Thank you for fixing this issue. See autosave attached 1771183394.bin LSZHMMUN_PDF_1771142828.pdf

Hi, I'll bring this up with the team, thank you

Hello, Same issue here. Only happenning when i use Active Sky. with MSFS24 live weather it's fine.

I had this WASM crash when I entered the OCK 'VIA' into the MFD on approach to EGLL To reproduce With existing F-PLAN loaded, enter the ARRIVAL page on the MFD from EGLL and modify TEMP F-PLAN changing VIA to OCK Doing so appears to trigger a WASM crash I had the same happen previously when entering OCK into the flightplan at the beginning of the flight, but unfortunately did not retain the details to log sufficiently. On second attempt (this event) I decided to save entering the VIA until after receiving clearance via BATC. Unclear whether specific to this procedure, product newly purchased/installed Information Aircraft: A350-1000 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Attached from Simbrief Specs: i9-11900k, RTX 3070, 32GB RAM Autosave: Attached latest .BIN file before crash WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-1000/panel/inibuilds-A350.wasm 1771098877.bin KJFKEGLL_PDF_1771070127.pdf

Is it normal for the battery to wear so much? At this rate the aircraft would only complete about 5 flights before needing new batteries. Not a gamebreaker, just curious.

its common after installing a new livery/scenery of even the latest update for it to take a while to load. find it to be the case the first time i load a flight. it loads faster there after.

After the last update, a problem that used to occur very frequently, though less frequently recently, has returned. After selecting a livery and airport, I can't load the plane in the selected scenery, and the loading wheel spins endlessly. After selecting a different plane, the problem disappears. I've read various strange methods online to "work around" this, but none of them actually work. Is the source of the problem known, and is there a proven solution?

Thank you

Hi, Sorry you are having these issues, have you tried uninstalling and reinstalling the aircraft. If so and that hasn't worked then try clearing the WASM folders and then relaunching the aircraft so it can recompile and that could resolve this issue. You can find the steps for that below, let me know if this helps.

Hi, While I don't know why this is occurring and haven't seen it myself; I can offer three solutions, one is to logout of Navigraph in the OIS and that could resolve the issue. Second is to uninstall and reinstall the aircraft. The third option which you can try afterwards if that doesn't work, is to clear the WASM folder and allow then relaunch into the sim which will recompile the aircraft. You can find instructions for the last option here, let me know if any of these options help resolve your issue.

Decided to give this plane a spin tonight. Encounter a major issue with the autopilot though. After selecting an ILS approach and fly direct to the IAF, the plane started hunting left and right the GPS course. Both the CDI and GPS needles appeared to be shaky. Once in the main menu, had a CTD (could be related). Love this plane, but the execution and quality standards have been utterly disappointing. https://www.youtube.com/watch?v=nhMEyUxRwX8

Thank you for your explanation. I will try again.

After another WASM crash. Cleared WASM directory. Errors again.

Not quite resolved - FO displays are still corrupt

In the real aircraft you really can’t hear the speedbrakes in the cockpit at all. There is some airframe vibration, but not much audible. I really hope this could be adressed, as I often find myself decreasing my speakers’ volume whenever I use the speedbrakes.

v 1.2.1 fs24 MS Store version Trying to resolve WASM issues. First saw when upgrading to v1.2.1. resolved by clearing WASM folder. Has MFD WSM crash. Cleared WASM folder then uninstalled.. Reinstalled and had MFD display issue again. Cleared WASM folder and it was resolved.

Hello The autothrottle disconnected all of a sudden when I was about 500 nm from my destination, I had to enable it again. I'm just wondering why this happens? I'm using a joystick and a throttle addon hardware. Thanks for any help. /Amir

I switched to FS2024 and I can't use A350 anymore 😞 Right after the loading the aircraft, it immediately crashes. Then it is visible it is "moving itself" somewhere (by itself). In the systems I specifically set up Cold and Dark as a default, but it is not avail. I tried various locations, on the runway, anywhere, but it always crashes. A350 is for 3 months unusable for me.