Systems

Inibuilds A350 Master WASM Crash Thread v1.2.6 FS2024 This thread will be the new location for all WASM Crashes relating to the Inibuilds A350-900/1000 for Microsoft Flight Simulator 2024 Below this message will be where users can upload their WASM Crashes pertaining to the current version of the A350. NOTES: If you do not see orange expectations screens on your displays or "WASM exception in X gauge" in the developer console it is not a WASM crash. The "sim-freeze" is a separate event that is tied to something on the server side which we are investigating with Asobo. All WASM Crashes existing in this thread will be removed following the release of a new update. i.e. Any …

hi Sorry no pics, but having set up Star/App into EGBB, the TOD kept changing every 1-2 secs between waypoints, and hence times to descent point. It seemed to be recalculating continuously, resulting in these variations. I elected to descend using the first TOD and the variations then stopped. (The second calculated TOD wouldn’t have worked due to distance required anyway).

Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: PFD Attached WASM Error: WASM: Error during HUD_gauge_update execution. Error code : 0xc000001d WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty Specs: i7 14700f, RTX 5080, 16gb DDR4 RAM Autosave File: N/A I was trying to reload the approach ILS 04L into EKCH as after few vectors from the ATC, it doesn't say the arrival/approach type on top of the ND. Then the crash happened once i clicked on ILS04L on the arrivals page. WSSSEKCH_PDF_1779843119.8e8108bd.pdf

Hello! Whenever I am hand flying the A350, and I am turning, the spoilers seem to glitch and sputter. I have my spoiler axis programmed on the Thrustmaster Airbus throttle quadrant. Is there a solution to this? Thank you!

v 1.2.6 LFMN NISAR 8R ILS Z Rw 04L 1. Managed DES almost right at the T/D. Note the given path is FL340 at NISAR. 2. A much steeper vertical path replace previous one. Given path was much lower then FL340 at NISAR, and the path requires V/S over -3200 fpm. 3. Workaround: Do a direct to next waypoint force FMS recalculate the vertical path.

When we disconnect a hydraulik system the indication shows "ISOL". But when I connect again the "ISOL" remains and the Valve is still closed ? What is the reason or is ait a bug ?

Hello, I just experienced a WASM crash on the latest version of the A350. Do you have a solution to prevent this? I've already removed the WASM folder; the crash occurred when I tried to initialize my flight plan.

Morning, the option to "deselect SLS" should result in FLS being defaulted. At the moment this isn't the case. Thanks

Dear Inibuilds, its been a while since this the "brakes hot" warning is there and so far is still not solved. I am getting this warning in almost every flight even though i am barely pressing the brakes.. many thanks!

Dear iniBuilds Development Team, I am writing to report a recurring telemetry calculation issue in the A350 flight report system, specifically when operating at high-altitude airports (e.g., SEQM, elevation ~7,900ft). The Discrepancy: Upon touchdown, the aircraft’s landing performance was physically smooth, with the Radio Altimeter (RA) providing precise and steady closure rates (the 5-4-3-2-1 callouts were perfectly paced, confirming a stable and gentle flare). However, the generated in-built landing report recorded an inflated Sink Rate (-263.60 ft/min) and G-force (1.13G), which contradicts both the smooth tactile feedback and the reliable RA data. Root Cause Analysis:…

Hello! I recently purchased the A350 and honestly, I’m really happy with it so far! The aircraft is absolutely beautiful and has always been a dream aircraft for me, so I can already tell I’m going to have a great time flying it. After a few hours of testing, everything seems to work perfectly from what I can see, except for the keyboard input on the OIS / EFB, which does not properly lock the keyboard inputs. For example, with some keys I can still move my joystick assignment or deploy the flaps while typing things into the OIS, even when the message “Aircraft control disabled when inputting text with physical keyboard” is displayed. I searched online and through the …

Alt Prediction and Level Off Arrow Logic.pdf The following are some bugs that are still not fixed. It is quite disappointing to still be seeing so many so long after release, and especially disappointing that in the meantime, other aircraft have been released that also contain a lot of the same bugs. Please, please fix these, it is all basic functionality that should be correct in an aircraft of this price especially given how it is marketed. Many of these have been reported since release and whilst of course I appreciate the work that has gone into the aircraft, it seems little progress has been made in these basic things and its is most disheartening. These report…

Hello ini, Are you likely to activate the " LL Crossing " in the F-PLN INFO

I’ve been trying to read the V1, VR, and V2 speeds from local variables in the iniBuilds A350, but they always come back as zero. I’ve checked the SDK tools and tried reading the local variables (like INI_V1, INI_V2, INI_VR), but these values don’t change and always remain 0 when I enter the speeds in the MFD MCDU. Are they’re exposed at all? If not, is it possible to include them in a future update? Also, is there any plan to expose S/F Speeds via LVARs in the future? Any help would be really appreciated!

Using ZSAM DOVP7Y departure, the AM401 should be flyover point as displayed on MCDU, but the path on ND passes abeam of this point rather than overflying it.

This bug was introduced in V1.2.1 and still remains unfixed in the latest V1.2.6, and I have no solution to it. After entering weight data, the 90-degree right-angle turn route between AA263 and AA262 deviates during rendering, and the autopilot will follow this offset path in full managed mode. Even removing speed and altitude constraints of this waypoint cannot fix the issue. This problem exists in SID and STAR procedures at many airports.

I started using A350 in MSFS 2024. After some time, my engine dials changed from green to orange. I also then installed A350 in MSFS 2020 and used it for several months - in there the engine dials were always green. I have just recently fully reinstalled A350 in MSFS 2024, but the engine dials are still orange. This is mildly annoying, since orange means something needing attention. Do you have any idea why it is orange and how can I put it back to green?

Hello all I have read the topic : "https://forum.inibuilds.com/topic/24979-how-to-direct-to-dir-to-a-waypoint-via-the-mfd-fms-or-nd/" But it does not work. What I do : I am ready to fly on a runway I have not set any FPLN I just want to set an AIRPORT as a DIR TO Waypoint I click on the DIR knob - set my airport name - Insert it as TMPy .. But when I go to the FPLN I stay on PPOS .. Thank you for your help and ...advices

In VNKT RNP Y Rwy 02 (AR) Approach via IGRIS, the leg between KT552 and KT550 should be a RF leg, but in ND and MCDU, it's just a straight line KT550 is the last point in approach transition and the first point in final approach. There are two lines in database, the first line is approach transition with path_termination 'RF' and waypoint_description_code 'EE ', while the second line is final approach with path_termination 'IF' and waypoint_description_code 'E F'. So I think there is something missed when the aircraft processing the path.

Hi, I am having a problem with my A350. Whenever I load a save after a WASM crash, the aircraft starts oscillating in roll while on autopilot, and in manual flight I need to keep the joystick tilted to maintain straight flight. I am not sure whether this is a bug or some kind of system logic, but it always happens after a WASM crash and after loading the autosave. During the last crash (2-hour long-haul flight using AutoSimRate), the displays froze and the aircraft started turning in circles to the right. After loading the save, the aircraft began oscillating in bank on autopilot, and in manual flight it constantly banked to the right. The left and right fuel tanks are ba…

Hi everyone, I am having a recurring issue with the iniBuilds A350 in MSFS 2024. No matter which flight I plan, as soon as I import the SimBrief data and set up the flight plan, calculated points such as the Top of Descent are placed far away from the actual route, sometimes completely off the ND route line. As a result, the fuel prediction on the fuel page also becomes unusable and shows a negative value for fuel at destination. In my latest example, I planned a flight from EDDM to EDDH. The route appears broken on the ND, with green route segments drawn across the map in a “spaghetti” pattern. The FMS/ND also shows a point with a distance of around 2967 NM, which obviou…

I've run into what appears to be a bug (or at least very unexpected behavior) in the A350 FMS regarding vertical profile calculation when a holding pattern is inserted into the flight plan. I'd appreciate it if someone could confirm whether this is a known issue or if I'm misunderstanding how the FMS is supposed to handle this. Setup: Aircraft: iniBuilds A350 (MSFS 2024) Route includes a holding pattern at LUPIX (HOLD L), with LUPIX being the IAF/approach transition for the arrival into LJLJ (LJLJ30 STAR) Cruise altitude: FL330 What I did: I entered altitude constraints via VERT REV / ALT on the F-PLN page: LUPIX: AT 5000 FT (see screenshot 2) HOLD L: AT 5000 FT (see scre…

Hi, It is easy for us all to flag things when they don't go right, but we don't always share positives. So, I just wanted to say I have now completed a couple of flights with v1.2.5 including a longer sector using time acceleration. I have repeatedly kept changing the arrival rwy/star during the flight to see if it breaks it but so far I have to say it is taking it in its stride. Well done to the team. Regards, Kevin

Hi there, I have turned on the traffic display on the ND with full labels and I am connected to VATSIM online. My understanding is that the full label should the ground speed of the aircraft. In the example attached below, I can see 240kts on the ND (which is incorrect) for this particular traffic, but 466kts on the SURV TRAFFIC page when looking at detailed ADS-B data for the same traffic. Am I misreading the FCOM here, or is this a bug/limitation? Many thanks

Hello After updating version 1.25 these days, I used the new version to fly the ZBAA-LSGG-ZBAA route. The first leg of the flight experienced a simulated freeze and the plane crashed directly. After about an hour of recovery through AUTO SAVE, the simulated freeze occurred again and the plane crashed again. After recovering through AUTO SAVE again, it returned to normal. After landing, I cleared the WASM folder. After about five hours of flight, the second segment of LSGG-ZBAA experienced simulated freezing again. The plane deviated from its flight path and spun around. Normal after recovery through AUTO SAVE. Fly at double speed throughout the entire journey. The previou…