Systems

I was just loaded to my gate (Atelic LPMA), set a few custom views, start the batteries, and had a WASM crash just launching the GPUs. Aircraft: A350-900 ULR Simulator: FS2020 SU 15, DX12. MSFS was clean installed a few days ago, including everything in Roaming/Microsoft Flight Simulator. Already tried clean the WASM files multiples times after that Navdata Method: Unknown, guess it's the Sim Default but I can't really verify since the plane never started OFP: N/A WASM Error: 12:09:32 | WASM: Exception c000001d in gauge HUD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900ULR/panel/inibuil…

While completing an approach to rwy 22R at KJFK the aircraft states rwy too short even though this is a usable runway IRL for said type. This is an incredibly glitchy and annoying system. Please either fix it or outright remove it. Also updated in-house (ini) liveries for the 1000 break the aircraft exterior.

Hello, please take a look at this screenshot: EPALO is 18.9NM away, yet in the VSD it is drawn at about 7NM. The procedure was LGIR 27 EPAL1V. There is a 8000ft at or above restriction at EPALO. It seems that it was drawn at the point where that altitude was reached instead of the real distance.

With the same screen brightness, the upper and lower MFD(I think that's what it's called on the 350) have different brightness levels

Hi, I was flying just this evening into Istanbul LTFM following the ERSEN1A arrival. That is quite a demanding STAR ad it has quite a lot of altitude and speed restrictions that forces you to fly below the econ descent path. Basically the aircraft ignored all the speed and altitude restrictions and kept me way too high on approach. It seems like it calculated the descent path down to be at 5000 feet at the FAF (which is the correct altitude) like there were no altitude restriction whatsoever. So the profile would have been correct for the track miles flown if there were no restrictions. Is it a common issue or is this something spurious?

Hi, New issue, the A350-900 no longer start moving under idle thrust even light loaded. I have to increase thrust to around 28% to move the aircraft. That's not the case IRL.

I encountered a problem which I consistently get a sim freeze every time I import and load a simbrief FPLN. I've cleared WASM folder and tried different plans, long-haul and short-haul. All resulted in a sim freeze which I have to close forcefully. The issue was not present on 22 Jun 2025. Aircraft: A350-900 Simulator: FS2020 Stable Release Navdata Method: Navigraph OFP: Not related WASM Error: Unsure Specs: 9800X3D, RTX 3070 8G, 64G RAM Autosave File: N/A

Aircraft: A350-900ULR Sim: FS2020 Navdata Method: Navigraph OFP: WSSS/20C TOMAN5B TOMAN L625 MEVIN B462 KAZIK Y59 AZAMA Y57 POROT OTR11 LEPKI DCT 40N160E 43N170E 46N180E 46N170W 45N160W 44N150W 43N140W 41N130W DCT TRYSH DCT AMAKR BDEGA4 KSFO/28R WASM Error: WASM: Exception c000001d in gauge EFIS in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900-ULR/panel/inibuilds-A350.wasm Specs: Intel Core i7-14700f up to 5.4ghz, RTX 4070 12GB Autosave file attached 1751301645.bin

As per the title. 1.1.0, I cannot insert airways into the FMS. I'm getting 'Out of range' or 'Airway/Waypoint Mismatch' Despite them being valid for AIRAC 2506. I don't have this issue in my other, 3rd party aircraft, such as the iFly MAX. This isn't the first issue I've had with the A350 and its issues with data implementation data from Navigraph. All these issues have arose around the 1.0.8 update. Here's the link to my previous issues with your inability to implement navigraph data into the A350. The issues still exists, and is part of a growing list of issues surrounding navdata; Cant enter airways Improper r…

I was really excited when I saw the changelist, but could't even make a single flight so far.. First I couldn't download the update. It stucked on the installation process. After couple attemps, I failed without any chance until I saw one topic in the forum that suggests the alternative download section in iniManager. It worked to install the updates, but... Secondly, after update, there were no aircraft at all! Just cones and ground equipments. I tried many liveries and finally Finnair livery has worked, but.. While I was trying to prepare the aircraft to the flight, FMS is frozen completely.. And also, there was really weird stutter that happens ever…

Digital RMP PA function detail on version v1.1.0

Just done the update from the app but im still only seeing the 900 and the 35K. I have removed and reinstalled the plane but still not getting the ULR. Am I doing something wrong?

Team, As per the title, with the latest update, when using the keyboard to enter data (Pressing CTRL then using my physical board) there is input lag, that gets worse with more data being entered, occasionally not registering any input. Reverting to the keyboard on the FMS is the solution currently. Along with that, the curser on the MFDs lags too when panning across the screens.

Hi, Never had this issue before. At the end of the landing roll, right after autobrake is off, all aircraft animations (nose gear steering, control surface movement...) and cockpit displays (PFD, ND, OIS...everything) freezed. Aircraft is still controlable and lights work fine. Update: Did a reinstall and aircraft freeze again at same point (end of landing roll, about to vacate runway). Error on console: WASM: Exception c0000005 in gauge MFD in module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/inibuilds-aircraft-a350-900/panel/inibuilds-A350.wasm

When I am doing a Long-haul flight, in the descent preparation status, after I changed the ILS appr to RNP appr, the WASM crashed, and all the things were frozen. Aircraft: A350-900 Simulator: FS2020 Navdata Method: SIM DEFAULT OFP: YSSYWSSS_PDF_1751177369.pdf WASM Error: WASM Report Message.txt Specs: i5-14600kf, 4060 Ti 16G, and RAM 64G Autosave File: it has been overwritten

Hello, I own the iniBuilds A350. In MSFS 2020, when I select an airport and try to start a flight, the simulator gets stuck on the loading screen. I waited for about an hour, but the game never loaded. I tried clearing the "work" folder and launching again, but it didn’t help. I also emptied the Community folder and tried again — still no success. I uninstalled and reinstalled the aircraft, but the issue persists. If anyone knows a solution to this problem, I’d really appreciate the help.

Hello, I'm trying to insert an airway into a route and I'm not having much success. I'm only familiar to the A300 and the A320 and I'm new to the A350. I fill out the INIT page: Then I select the departure 33 AMLU2G, I press TMPY F-PLN and INSERT TMPY: Then I select AMLUH airways and enter the enroute segment: Again, I press TMPY F-PLN, but the enroute segment is not visible: Am I doing something wrong?

As title says, cannot get HUD to deploy in new update.

While in cruise at FL410, I decided that I want to save a bit of time and go at 0.88 Mach, the problem being that the aircraft does not want to accel past 0.873 Mach even though it had plenty of thrust available.

Hi all! After updating my liveries through Inimanager, A350 became invisible when I choose any livery. It just is visible when no liveries are chosen. A have already uninstalled all my liveries and A350, but the issue persists. Can anyone help me? Thanks!

On FS2020 version 1.1.0 only the basic ULR livery appears, the others do not, including those contained into ini manager like updates , which is still a big problem.

I can't use the a350 passenger plane to enter the game. it keeps jamming on the loading page.

Bug 1: The spoilers should not be so actively involved in the turn at smaller flap configurations (config 0,1,2). See video: In the sim, spoiler extend as the same among with ailerons during turns in clean configuation which is wrong behavior. Ailerons should be enough for this turn. In sim: https://youtu.be/VoafNH16j50 In real life: https://youtu.be/WvjRsKMI0fs Bug 2: Worng modeling of spoilers at flap config full, R/L7 spoiler should be aligned with the wing surface. In sim: In real life:

After updating to version 1.0.12, when importing the simbrief route, it got stuck and retreated to the CPNY F-PLN REQUEST interface. It took several minutes for "RRECEIVED CPNY F-PLN" to be displayed. It also gets stuck when requesting the weather using ATC COM, especially after a long flight. (Requesting the weather before descent after 17 hours of flight until landing was not displayed, and it was stuck for at least half an hour) Previous versions were all imported in real time

Selecting the ILS 28 or RNAV 28 leads to the runway fix not being loaded. It ends at RAMEM (FAF) and it shouldnt be like that. Runway 14 works just fine This is ILS 14 (loaded ok with runway fix in green) Here it ends at RAMEM for ILS 28 for some reason and it shouldn't be like that and the runway fix is in blue (RNAV 28 gives the same issue)