All Activity

Hi, I would like to clarify the procedure regarding loading the aircraft with GSX. As copied below from the FAQ, it seems it is mandatory to first enter the ZFW & ZFWCG in the FMS Fuel page before loading the aircraft. I do it, but numerous Youtuber do not do that, & maybe some others users don't. Could you please confirm that this is a mandatory procedure ? If so, maybe some reported bugs are due to improper loading procedure ? Then maybe a better communication about this procedure could help ? A warning message on the EFB GSX page could be an idea. Is it not possible to load the FMS value internally when clicking the Load with GSX button in the EFB so we don't have to mess with FMS right away? Entering ZFW & ZFWCG in the FMS takes time because you have to load the INIT page first then can access the fuel page, then you need to wait for PRELIM LOADSHEET to get the value Below is the procedure from the FAQ : ⚠️Note: Always enter your ZFW and ZFWCG before fuelling to ensure correct CG loading. ⚠️ Failure to do so means the FQMS will fall back to a "single vector method," filling the tanks using a hardcoded, safe default sequence rather than an optimized distribution. A GWCG above 40.5% may cause the aircraft to tip backwards. Whenever this limit is reached, fuelling will be stopped automatically to prevent tipping. Entering your ZFW and ZFWCG on the FMS ensures the Fuel Quantity Management System (FQMS) can perform active CG targeting during the fuelling process to maintain GWCG within those limits. Best regards, Pierre

Can't see any improvements. CI127, RR Phase Plan kg/h Sim kg/h Δ Weight-adjusted Δ Climb 27,080 24,470 −9.6% −9.7% FL350 14,140 12,520 −11.5% −11.8% FL370 13,300 11,770 −11.5% −12.4% FL390 12,110 10,730 −11.4% −13.3% FL400–411 11,210 9,860 −12.1% −15.1%

Also note that it does not seem to consider the FOB entry for the display of the GW when on ground.

All of these issues have been present in the A340 and A350 already.

It also predicted a different alt than the constraint alt at FAP, even though it showed the correct GP angle.

DECEL waypoint was once again incorrectly placed and moved around quite a lot during approach. Also note the strange vertical profile, likely the result of creating a DTO w/ CRS IN.

Also note that the VSD should not be showing a dashed profile line.

Turn predictions should not be shown on the MAP path. Same issues reported in the A340 and A350, again... I think it was eventually fixed in one of those aircraft.

Hi team, Thought I'd just advise that with the latest sim update (I presume anyway) this issue has gone away. Cheers

Leaving the field empty and selecting ENT will populate the current ZFCG. Microsoft Flight Simulator 2024 2026.10.13 - 10.20.45.05.mp4 During deboarding with a cleared MCDU, the GW still shows and decreases.

The contrails move straight back for a few hundred meters, then curve according to the wind... Why hasn't this been noticed? This issue has also occurred on other iniBuilds aircraft and it's been documented.

Thanks for your input. It would be great if ini managed to fix this in the A380, A350, and A340 consistently.

This thread needs more action, come on! Where are all my bizjet people at?!

@dectenor2 That display value and FMGS calculation are actually correct, let me correct that: Speed / Mach Calculation: At FL250, an indicated/calibrated airspeed (IAS/CAS) of 281 knots accurately translates to M0.67 (Assuming FL250 ambient pressure of ~376 hPa and a local speed of sound around 602 knots, 280 kt CAS gives roughly M0.672). Rather, my point was the inconsistency in Managed SPD/Mach. At FL250, past the T/C, the system should be holding M0.67 instead of displaying 281 knots, as it ought to be in Mach mode during cruise (Refer to DSC-22-FMS-10-50-20 or Highlighted Picture below). T/C Target Speed: The Top of Climb (T/C) is the pseudo-waypoint marking the transition from the climb phase to cruise. Therefore, the target speed displayed here should be cruise speed, not climb speed. SPD LIM Missing: The (SPD LIM) disappears because there is a FLT PLAN DISCONTINUITY in your FMC. Once you clear the discontinuity and connect your flight plan continuously to the destination, the (SPD LIM) waypoint will reappear on the ND/FMC. Hopefully, this clarifies what's going on each time you fly this route/aircraft. Cheers!

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