All Activity

The modelling accuracy on LOD1 looks better than on LOD0 around the ventilation area beneath the side windows. Please take this into account for version 1.2.7.

I saw the implementation of an electrical management system in the Inibuilds Globaljet. Does that mean we will get an implementation of Avionics Network?

Hello. I loaded up the Etihad paint last night to do a flight and noticed that the elevator and rudder were stuck into odd positions. The elevators showed full nose up deflection and the rudder full left. However they were simply cosmetic and the actual flight control page showed correct placement (neutral when not commanded to move). This persisted the entire flight and movement of the indicated surfaces did not seem to be visually showing anymore.

This page in general across all the ini airbus fleet is very buggy and error strewn. Here from the A380: Predicted speeds in cruise given in IAS - 281. Until at ELIVA where it suddenly goes to 0.67 Mach for no reason. Also inconsistent use of “ for indicating the same speed as above. The first waypoint on the page should always give the speed numerically. Then it should always be ‘’ unless there is a change of flight phase or speed. Or if you were to climb higher than here, at the first waypoint where the predicted speed would be in Mach rather than IAS. Again which is tied to when the IAS becomes equal to the target Mach, not just at some predefined altitude. Likewise the display on the FCU and FMAs of speed or Mach, the correct one is displayed depending on whether the aircraft is targeting a speed or a Mach number, it doesn’t just change from one to the other at some pre defined altitude. This is bugged on a350 as well of course, as are the things like those mentioned above on the F-PLN page, but really hoping they’ll be fixed in 1.2.7 So in this shot going down the waypoints it should be 306 “ 281 “ “ 303 “ 250 I actually need to check what the speed at T/C should be. I can’t remember off hand whether T/C is still predicted at the climb speed or whether it is the cruise speed. But I think it’s correct as T/C predicts climb speed and not cruise speed. Though of course here it should be indicated by “ and not the numeric value. Oh and the speed limit pseudo waypoint is complete missing. Which should show the altitude at which the aircraft will begin to decelerate to 250kt for the 10000ft restriction. It’s sad to see such basic systems in a page that is used all the time in flight to be so full of bugs yet again. This is just looking at one page, and the aircraft is full of things like this on many other pages and displays.

A350-1000 — WASM crash after T-P → HOLD → COMPUTED — MMMX to MMMZ Hello iniBuilds team, During a flight from MMMX to MMMZ in the A350-1000, I experienced a WASM crash while attempting to create a holding pattern in the FMS. Sequence immediately before the crash: Selected T-P. Selected HOLD. Clicked COMPUTED. Immediately after clicking COMPUTED, the main cockpit displays turned orange and showed “WASM module crashed”. The thrust levers and landing gear controls stopped responding, and most aircraft functions became unusable. The simulator continued running, and I could still control the aircraft manually, but without usable flight instruments or navigation guidance. Error shown in the screenshots: Package: inibuilds-aircraft-a350 Module: /SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm Affected gauges visible in the screenshots: EFIS, CTR and MFD. Aircraft: iniBuilds A350-1000 Simulator: Microsoft Flight Simulator 2024, PC Departure: MMMX Destination: MMMZ Aircraft version: Not yet recorded. I am attaching two screenshots showing the failure. Could you investigate this issue and advise whether there is a known workaround? Thank you.

Nope, @spottersim Magenta Dot is the Target-of-Speed-Limit (SPD-LIM on FMC), either: Target-of-Deceleration for Descend Phase,OR Target-of-Acceleration for Climb Phase, Both implies for the Target Speed from speed 251 knots and above. Please refer to the highlighted area: So depending on your phase of flight, it marks the precise spatial point where that speed constraint or limit becomes active. Hope that is helping you to understand the situation. Cheers!

no, I don't have a problem :)

i also agree that its more vertical winglet rather than too tilted.

did apporach to EGLL rnav F-loc was captured was flying at apporach speed and plane turned wrong way

Opening FIX INFO from the FPLN page will open up the last viewed page, e.g. FIX3. Shouldn't it always revert to FIX1?

The engines over- and undershoot the new target for a few seconds until eventually settling at the manually set thrust. During takeoff, it sets more than the reference thrust and only attains it well into the takeoff roll. IRL: https://youtu.be/pHui34_ODnc?si=5S60ZZLikMzVVFl1&t=14

Is the magenta SPD LIM circle correctly positioned in this scenario? Shouldn't it be located at the 250kt CSTR since its more limiting?

The latest changelog mentions the following: FIXED ECON SPD mismatch Unfortunately, this does not seem correct. On ground: .83 shown as cruise speed on FPLN page, .85 shown on CRZ page (seems to refer to the speed at/after the first STEP), speed changes with S/Cs In flight: Cruise speed .85, but WPT prior to STEP shows .83 (please verify whether the aircraft resumes the original climb schedule for a cruise climb), no more speed changes throughout the FPLN, regardless of HWC/TWC, ISA, and FL changes.

Well, it is just a guess😅

Please bring the cabin to the A350 on Xbox @iniBuilds

Really looking forward to this aircraft. Finally a long distance continent to continent bizjet!

Impossibilité d'intégrer le PDV de l'EFB dans le FMS,le bouton Init Request reste toujours grisé

hey thanks man i was looking for something like that, so your sure about your prediction? it’ll take 2-3 weeks?

Hi! In the latest development update article they said that they submitted the A380 version 1.04 to the Marketplace, which plans to bring compatibility for PS5. It does need some stability testing still, so if that takes up more time, they will release it for PS5 on update 1.05. So, I would say within 2-3 weeks we will have the plane.

Hello there! Just had the very same crash today on MSFS2024 after selecting the SEND command on the CPDLC... Changelog from v1.0.12 (13MAY2026) says "FIXED - WASM Stability enhancements"... I would say that there is still room for enhancements. Waiting for the support to contact me for deeper analysis. Cheers!

I don't see a reply to this confirming or denying if it'll come to 2020??????

Hi, Thank you. Please could I add another item, the take off distance available sign next to taxiway A/runway 25 Thanks

Hi, I am writing to let the developers know that there is an issue with both the CAPT's and FO's Side stick disconnect button (or their Lvar's or events). I am writing a couple of scripts for the A380 and it seems that the event that is used to trigger the AP disconnect button once pushed in does not return to the released state. I assigned the AIRLINER_SIDE_STICK_DISCO_CPT event as a KEY DOWN event with a value of 1 and as a KEY UP event as 0 and it is triggered by my physical side stick hardware I have (Thrustmaster HOTAS Warthog). The even does press the in-sim button in, however it never releases it. This is confirmed by another user on the forum (the post I can't find anymore). I remember that the team responded to the user saying that they are aware of the issue, but two updates later it seems it might have been missed. The consequence of this not being fixed is that no single user can assign their joysticks / hardware button to disconnect the autopilot. The same goes to the Auto throttle disconnect button. That also does not return to the released position if pressed in by the event / Lvar.

This is now resolved. When you set the axis in the MSFS controls, the throttle will select the Rx and Ys axes, but it also assigns the CL button as well. This must be deleted, which then allows the input to travel from 0 to 100% and not set itself back to 50%. Once done, calibrate via the EFB in the usual fashion.