Systems

As title says, WASM crash after rapidly loading autosaves. To reproduce: Do a normal flight to get a couple of autosaves Load into the sim on another flight Load one autosave Load another autosave, try and do so as quick as possible, as soon as you load one start pressing the button to load another Repeat process, load autosaves as quick as possible, until displays freeze OIS will likely not be frozen, but it will be useless as autosave loading is now not possible Info: Aircraft: A350-900 Simulator: FS24 Navdata Method: NAVIGRAPH OFP: Not related Specs: Intel i5-13400F, NVIDIA RTX 3060 12G, 32GB o…

Hi There I've noticed in the latest version of the A350 for 2020, when I look at the EFB screen on the captain's side, I get a real FPS drop. Not sure why or what may be causing that, when I look away, FPS returns to a normal buttery smooth. Anyone else had this? For context, just flew OMDB --> VAAH, did a GSX turnaround and now flying back, no sim restart. Not looking for a hotfix, just want to report it. Thanks =)

See attached video Aufzeichnung 2025-04-05 171057.mp4

The behaviour in Go Around seems generally quite poor. Today I tested 1.0.7 at FAOR 03R using the ILS Z approach. On the first approach I went around around 500AGL using the soft GA (works quite nicely on a superficial level) However passing 7000ft the Missed App calls for right turn to 206. The aircraft simply maintained runway heading and climbed as usual. When I checked the FPL page, the approach had reset and the next NAV point was "Manual" which is not correct for a missed approach. Additionally, on the second approach I landed the aircraft before performing a second Go Around again using Soft GA. This time however the autobrake never disengaged, so the a…

I am flying at FL390 and then FL410. Winds aloft data is not loading for my current altitude but for lower as seen below. This messes up the DEST ETA and EFOB. Is this a known bug or a new one?

Like the title. I noticed this issue with the recent updates, maybe started from 1.0.5 and later. When the plane in approach phase and both LOC and G/S are captured, the plane starts going pitch up and down slightly, but the closer it got to the airport, the worse it got. As video I posted shows, It almost plummets to the ground itself.

Hello all What about this message please (see attached file) ?

Hey! I have calibrated my throttle quadrant in the OIS and everything, but when I set my physical throttle quadrant to TOGA it takes at least 3 - 5 seconds or more for the engines to go to full power in the sim and its pretty annoying, and I don't know whats wrong because I don't have this problem with any of the other airliners I have. I hope someone knows how to fix this.

HI, I have created a number of custom waypoints in the DATA menu, names EEP, ETP and EXP. They have been saved but when I come to enter them into the fix page they don't show up. Am I missing something? Thanks Jon

Hello, I am interested in obtaining LVAR states for the A350 so we can use them for our virtual airline. We need to be able to track autopilot when it’s enabled disabled, fuel flow, flaps settings. Can we get a list of these for us to utilize in our acars program? It would help out our virtual airline a lot if we could get some assistance with this. Best regards, Joe

I don't know if this has been reported or not but with the new update 1.0.6, the "100 Above" and "Minimums" callouts do not work even if the appropriate values has been inserted on MFD/FMS (Baro or Radio).

When I select an instrument departure or arrival for VHHX, the plane freeze. The simulator still works and I see animations of knobs and buttons but I every function doesn't work, it's like the plane know the waypoints exist (because there is the list on the flight plan) but after activating the flight plan, everything dies,hope you will get it fixed

As photo shows, I am confused that I cannot start the engine after I upload to V1.0.5。

Hey, Got the following flightplan and on flightplan import on INIT Page, I get a WASM Crash, on 1.0.6. CYYZ VHHH DCT IMEBA DCT YVO DCT 50N077W 60N073W 65N071W 70N070W/M085F330 DCT INGUM DCT 76N060W 80N050W 82N040W 84N020W DCT RITAK/K0919F350 T572 ANODI N611 DOSON R705 OKASA/K0898F370 R705 BRT G490 SERNA/K0876S1130 Y520 POLHO/K0878S1160 G218 TMR/K0882S1130 B458 VADKA/K0882S1190 B458 DADGA/K0896S1160 W37 GUSIV/K0906S1190 W37 PEXID/K0907S1160 W37 OMBEB/K0898S1190 R473 NNX/K0909S1160 R473 WYN W18 NLG W23 ZUH R473 SIERA DCT I wiped out all of my cached WASM files. Still happens. Benny

I had the issue indicated in https://forum.navigraph.com/t/i-can-no-longer-log-in-to-simbrief-dispatch-in-msfs-2020/18061/27. The solution allowed me to log on to simbrief in msfs 2020 lobby, but in game on the ois, I still got os error 29 and couldn’t log in. And when the problem was temporarily solved, I had some other error that prevented me from updating the navdata. In dire need of help

Aircraft: A350-900 v1.0.4 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Not related to route (but I can provide it if needed, it was departing runway 14R, FISTO7A SID) WASM Error: WASM: Exception c0000005 in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: CPU: Intel 14900k, GPU: Nvidia RTX 4080 Super, RAM: 64GB DDR5 Description of the problem: Had a WASM crash on the ground at LFBO when trying to display the airport map Video of the crash: Crash is at 14:56 and I show the console at 15:50, but i uploaded the whole flight preparation maybe the…

Hello Inibuilds, Couple of weeks ago tried to do some longhaul flights with the new A350. But first we had the WASM crashes and that did occure to me couple of times and when update 1.03 was available i tought the issue was gone and could do some longhaul flights. But when i tried the first time 1 hour in the flight the autopilot disconnected inflight and when i returnd to my pc the aircraft was at that moment a boat in the atlantic.. So i agian stoped with using the A350 and with the new 1.06 update i did try to use it again to give it another change... But today again it happend 1,5 hours into the flight the autopilot disconnected out of it self ands wh…

As per title. Mid flight when setting up for descent ARPT NAV disappears. However, Enroute map and terml charts are still available in OIS. The OIS generates new QR codes to connect but it is impossible to connect, it does not do anything.

WASM Crash on Version 1.0.6 after swapping SEC1 F-PLN to ACTIVE: Aircraft: A350-900 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: No OFP - Route after swapping: LFBO/32L N0490F430 FIST7B FISTO DCT PERIG DCT ADABI DCT BOKNO UN858 VALEK UM163 DIK N853 ARCKY T853 IBESA T860 ERUKI T856 DEPOK DEPO2N EDDK/31R WASM Error: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm Specs: , 13700k, 4080 and 32Gb

Almost immediately after loading flight plan from LSZH to PHNL (after requesting it) WASM crashes. It does not happen with any other flight from LSZH or to PHNL (LKPR to PHNL works fine for example). To reproduce Load at LSZH Power on aircraft (Battery, GPU) Click INIT Request company flight plan Load company flight plan Systems freeze Information Aircraft: A350-900 & A350-1000 Simulator: FS2020 Navdata Method: NAVIGRAPH OFP: Any flight plan from LSZH to PHNL (seemes to happen even when I selected another route) Route: DEGES3S DEGES Z1 SUDEN/N0502F340 DCT LBU N851 RIMKI Z99 ELNAT P605 HAM M852…

For both A350-900 and 1000 variants the taxi lights for the main landing gear under the wings are not working, Here are the settings in the OIS, am i missing something or the bug is still there?

Hello Guys, I have a problem from the beginning with the ENROUTE MAP At the start of the flight I can see the different charts like IFR Day, IFR NIGHT, WORLDMAP or VFR DAY etc.. The problem is that the aircraft remains in the center of the screen but the map moves down. So the airplane leaves the area of the map and the area becomes more and more black. You can see it on picture 1 and after some time on picture 2. The standard map behaves differently. The map moves, but does not leave the screen

Vatsim traffic is being shown with incorrect wake vortex category on the ND traffic information symbol The aircraft here is listed on Vatsim as aircraft type A359 and correctly identified as a heavy on vatsim Radar, however the traffic information symbol shows it as a medium. the traffic information window on the SURV - TRAFFIC Page does not list a wake turbulence category at all. FCOM Reference:

Just decided to give the A350 another go after a few updates. I did two flights and was unable to complete either. Here are some issues I am still dealing with. I wiped my WASM and reinstalled same deal. 1. The fuel calcs are crazy off. One flight it was 4000LBS off another it was 6000LBS+. I am not changing anything about the climb derate etc. Again the winds are loaded in the FMS so I am not sure why these are so far off. 2. I am now having a problem with the NWS on take off and landing and no I don't have them split in the options. Its like the Y/D is being way to aggressive or something. I can go full left or right and it barely turns etc. 3. Both FPLs …