Systems

When flying SIDs, it is very common to have instructions of the kind "Takeoff runway 28L: climb heading 284 to 520 [feet], then..." For instance, the TRUKN2 departure out of SFO runway 28L and 28R (https://resources.globalair.com/dtpp/globalair_00375trukn.pdf). When loading into the FMS, this shows up properly as an ARINC 424 CA or VA segment (with a white "520" as the waypoint). I've purchased the ini A380 (1.0.5) and ini A350 (1.2.6). Neither of these auto-sequence these legs - when you takeoff, the FD guidance just indicates you should fly heading 284 forever. I have to manually find the next waypoint and use direct-to functionality to sequence past the altitude segm…

I have spawned in at the gate in Heatrow, everything was normal and sudanlly my brakes started to heat up, up to 1020 degrees. If i use the brakes hot thing they doesnt cool up. I think its a bug.

Some NPAs do not include the THR WP in the procedure as the MAP is located earlier, but the iniBuilds A380 always forces the THR to be part of the procedure. This has already been reported in the A340 and A350. NG navdata used.

When I was intercepting the F-G/S, the aircraft pitched down a massive amount and I was fully configured and stabilized right before the FAF, and the aircraft pitched down to like -5° AOA. It overspeed and then at some point it pitched back up to a norm lol pitch to follow the glide.

In version 1.0.5 after entering a step, the CLB in the CPT MFD that displays becomes unresponsive. The cursor changes over to the FO MFD. Clicking the CPP MFD isn't possible because the system "thinks" the active display is the FO MFD. Clicking buttons don't help either. The display is seems just frozen. Turning the FMS switch from "NORMAL" to "BOTH ON 2" or "BOTH ON 1" and back to NORMAL fixes the issues. I don't know if this is a normal procedure; if not, then it is probably a bug. Thanks. Roy

Hi Team, I recently purchased the A380 Airliner, but i found that there is no terrain data. I have logged in Navigraph with unlimited subscription. Regards, Leo

these items including apu hours dont appear to be changing , depleting, etc. Is there a setting somewhere to activate these maintenance items that i may have missed?

Hi, is anyone experiencing extremely slow and sluggish moving map on both efb and ois? I didn’t have the issue on a flight I did yesterday but today I experienced the issue for the first time. Many thanks in advance! Reza Behrooz

Adjusting the runway length does not change the LDA. I also noticed that ABRK settings 2 and 3 resulted in identical distances on a wet runway with reverse considered, HI was only 2m less. Is this accurate?

Hi, Units are set to LBS Total FOB showing pounds correctly, but individual tank quantities appear to show KGs. (Does not add up to total)

HEllo, i've noticed that i always landed below the planned Simbrief flight plan EFOB even with fuel offset of +10% I dont know if the Ini 380 consume for fuel than irl or if the simbref profile is not accurate seems that i need to add an offset of +20%

Greetings, Team Our lovely FMGCS have many function, also act as SUPER-COMPUTER for Pilots. But seems it misses some point. FMGCS CREATING WAYPOINT FMGCS known is able to create waypoints whenever is needed to help either targeting route or to "guard" some altitude. Directly to the FPLN Page or STORED WAYPOINT. I am flying SVO-AMS today, I can't help but notice that it having some problem, like 2 samples below: Sample 1: On FPLN Page is not able to create "Place-Bearing/Place-Bearing" Waypoint which identifies as PBX##, but whenever I tried to insert it on PILOT STORED WAYPOINTS, it goes funny 😂 I try inserting "ISENG" Waypoint which consist of SPL-020/FRO-350 which lik…

Hey guys, Huge fan of what you’ve built bringing Airbuses into MSFS! I did want to mention a bug I’ve noticed regarding Flaps behavior on everything from the A320 to the A380. I’ve seen this issue since the A350 in MSFS20, and it’s still happening in MSFS24 on the A350 and A380 (I usually depart using Config 2 on IniBuilds jets). See the picture below: Whenever you set Config 1, the plane defaults to Config 1+F instead of standard Config 1. During heavy takeoffs or direct Config 1 departures, this drives S-speed way past flap retraction speed and right up against VFE. It happens on approach/landing too. Looking at the FCOM snippets for ARS and AES below: Picture 1: Autom…

Dear Team, When simulating L UPPER AVNCS smoke, the OVHD panel SMOKE red indication on the AVNCS button, extinguishes after all AC electrical buses are powered off (i.e. Engines and APU for an emergency evacuation). Although this SMOKE indication is dependent on DC Electrical feed. On Battery power the DC ESS BUS ensures the avionics smoke detectors remain powered and active. Also the essential CIDS/SDF channel is tied to the essential DC power backed by the battery network to maintain critical smoke detection during emergency configs. So the discrete red SMOKE legend inside the AVNCS SMOKE pushbutton is driven by the active detection loop/FWS output. Because of this circ…

Hi, After updating the A380 to version 1.0.3, I have a problem where the OIT display no longer works. As a result, I no longer have access to the performance tool, since it is located there rather than in the EFB. best regards Benjamin

Setting up the A380 a is very time consuming and borderline complicated process. Preliminary loadsheet received, crew calculates fuel figures needed via the ofp/tablet and shares with engineer. Relevant figures entered in the FMS (ZFW, ZFWCG and Pax Numbers). Pax numbers needed to configure the air-condition system. The FQMS page on the OIT should now show the crew trim tank fuel needed. Target is 39.5. Normally trips requiring more than 47 tonns will require trim tank fuel to be loaded. If not available, crew will use the loadsheet application (not simulated) to determine the trim tank fuel quantity. If fuel still not balanced to company or crew satisfaction, crew will u…

OMG - It’s hapenning again after latest update …

I have an active navigraph subscription, I logged in 2x and tried logging out and resetting, but the update navdata button is missing from here. I installed the latest AIRAC through the navigraph hub as well globally.

Hi, Just purchased the xbox variant of the inibuilds a380 airliner. Is it normal for the jetways to not be connected

Hello, Could you consider adding DCLB 1 & 2 for the RR engines, along with any other options available on the real A380? Currently, these options are only available for the EA engines, whereas the real A380 equipped with RR Trent 970 engines also has them. As an example, on a British Airways flight operated by aircraft registration G-XLEA, fitted with RR Trent 970 engines, the pilot can be heard calling, “Thrust, DCLB 2, Climb Autothrust”. I'll attach the video with the exact timing of the callout for reference.

Hi iniBuilds team! Loving the A380. This is a very polished product that you all should be very proud of! I'm really happy with the hand flying, she feels heavy and the flight dynamics feel really awesome. I have noted several bugs over the last month of flying - some of which I'm not sure if it's just related to the systems of A380 that is different. This list is current as of V1.0.4 - I've just done a full test flight with it. 1) VSD During climb phase the selected altitude (eg. initial departure altitude) only becomes part of the VSD level of indication after the plane goes into ALT* mode near capture, rather than during climb phase itself During approach, the grou…

BTV, wet and dry line should be Magenta. Current build, wet line is white. "Adjust Desired Track Or heading" should show up on the FMS whenever doing Course Intercept on approach. Pull heading is the correct action, removes "adjust desired track or heading message". Course intercept for approach is currently bugged/incorrect. Needs to be revisited by your programmers. Minor stuff.

As tittle says,what is happen now with the navigraph map on the EFB,when zooming in or out, the images stack up inside a small box, and the zooming action is far too slow...this never happens with previous version...and please don´t forget the FD colour mesh with PFD issue "logged by the team". Thanks for any clarification.

In version 1.04 the OIS screens stay black. Several reinstallions and WASM Folder delete did not help.