All Activity

Bought the A380 today and have been trying to fly from Heathrow (Inibuilds scenery). Spent all morning trying to get the jetways to move. Tried everything: multijetway tool, GSX jetway operation, EFB jetway operation, changing stands, etc. Reinstalled everything I could think of at least once. Stand 563 for most of the testing, if anyone cares. Ini A359 has no issues at the same stand. Jetways move as expected. So seems to be something with A380. Help! :)

Hi, Thanks for reaching out. I will forward this to the dev team for further consideration. Thanks again!

Great news!

I will forward this to the team for further clarification. Thanks for your patience!

Thanks for your report. Will log for the team to investigate!

I will bump this with the team. Thanks for the reminder!

Will forward this to the team for review! Thanks.

Thanks for your report. Will test this and forward to the team for further review.

Key words we hope. No definitive timeline. Please understand, we are just as eager to get our aircraft in your sim as you are! I am extremely hopeful that it will be very soon. Thank you for the continued patience and understanding.

Hi iniBuilds team, I'm the developer of Remote CDU, a free add-on on flightsim.to (as TeeWoine) that puts the PMDG 737/777 CDU on a tablet. I'd love to build the same thing for your A350: the MFD and KCCU on an iPad, for people who fly from a desk or a home cockpit. Most of it already works: - the MFD image is mirrored from the pop-out window, - every KCCU key works through your L:INI_MCDU1_* / L:INI_MCDU2_* variables, which is great. The one missing piece is the cursor. Clicks on the MFD only reach the gauge through the mouse in the 3D cockpit, and the pop-out window doesn't accept clicks. So an external app can't select a field, a waypoint or a menu. Would you consider exposing an external input for the MFD cursor? Any of these would be enough: - L:vars (or a CommBus / client data event) for cursor X/Y in screen pixels plus a click, per side, - or making the MFD pop-out window clickable. This would also help home cockpit builders with a physical KCCU. I'm happy to test and to credit iniBuilds in my add-on. Thanks for the great aircraft! TeeWoine

Welcome to Louis Armstrong New Orleans International Airport (KMSY) for Microsoft Flight Simulator 2024! ✈️Today, we’re delighted to officially unveil the next scenery project joining our collection, releasing soon: iniBuilds Louis Armstrong New Orleans International Airport (KMSY) for Microsoft Flight Simulator 2024! Serving a city renowned for its music, food and vibrant culture, Louis Armstrong New Orleans International Airport is the gateway to the Big Easy and southern Louisiana. With a varied mix of domestic and international operations, New Orleans offers plenty of opportunities for your next flight. From its distinctive modern terminal to the busy apron environments and wider airfield, KMSY brings its own character to our scenery collection. Capturing that identity and recreating the airport in detail has been at the centre of development from the very beginning. Bringing New Orleans to LifeRecreating New Orleans has meant focusing not only on the passenger terminal, but also on the surrounding infrastructure and smaller details that give the airport its distinctive appearance. Throughout development, careful attention has been given to the terminal’s architecture, apron environments, ground markings, signage, airport equipment and the numerous buildings and facilities across the airfield. The result is a recreation designed to capture the atmosphere of this Louisiana gateway, whether you’re arriving after a short domestic flight or preparing for a longer journey. Development ProgressDevelopment is now progressing through its final stages, with work taking place across every area of the airport. From detailed terminal exteriors and interiors to bespoke ground textures, signage, lighting and airport clutter, the team has been bringing the different areas of KMSY together into a cohesive recreation. As always, performance remains an important focus throughout development, with assets and Level of Detail implementation carefully considered to provide a detailed airport environment while maintaining smooth performance. Scenery FeaturesHand-crafted ground textures with bespoke runway, taxiway and apron materials Highly detailed terminal interiors and exterior modelling True-to-life landside recreation with custom vegetation, decals and infrastructure Accurately modelled dynamic airport lighting Custom taxiway signage built to real-world specification Bespoke airport clutter, service vehicles and ground equipment Up-to-date airport layout reflecting the current real-world configuration Official GSX profile included Optimised LODs throughout the scenery for balanced performance Built using the latest Microsoft Flight Simulator 2024 SDK features Full iniManager compatibility Routes & OperationsNew Orleans offers a varied network of routes, making KMSY a versatile addition to your simulator. From short domestic sectors to longer flights across the United States and international services, there’s plenty to explore. For pilots who enjoy recreating busy domestic operations, KMSY provides an ideal setting for regional and narrowbody flying. Build it into a day of shorter sectors, connect with a major hub or settle in for a longer flight across the country. Whether New Orleans is your destination or the starting point for your next adventure, there’s plenty of flying to look forward to. Below you’ll find a few more in-development previews showcasing various areas of Louis Armstrong New Orleans International Airport. From the terminal buildings and apron environments to the wider airfield and surrounding infrastructure, these screenshots provide a closer look at the detail being brought to the project. While we’re not quite at release yet, we’re incredibly pleased with how New Orleans is coming together and can’t wait for you to explore KMSY for yourself. As always, thank you for your continued support. Stay tuned for more previews and further details as we get closer to release! iniBuilds Team ❤️

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?

LFMN RNPA04L.

CI172, EA A388, ini EA SB profile Fix Time since T/O plan / sim Δ (min) Mach plan / sim GS plan / sim (kt) Fuel on board plan / sim (kg) Δ fuel Δ burn since T/O TOC (plan’s top of climb) 0:22 / 0:20 −1.6 0.84 / 0.84 (still climbing, FL305) 397 / 452 76,271 / 76,745 +474 −6.9% MODOG 0:31 / 0:30 −1.6 0.87 / 0.85 417 / 412 74,372 / 74,243 −129 −0.3% LOTAN 1:42 / 1:41 −0.5 0.86 / 0.85 455 / 464 60,615 / 62,191 +1,576 −7.0% TUSYR 2:50 / 2:50 0.0 0.85 / 0.85 461 / 451 47,988 / 50,816 +2,828 −8.0% YAA 3:51 / 3:51 −0.2 0.85 / 0.85 445 / 453 37,247 / 40,841 +3,594 −7.8% TALAS 4:38 / 4:37 −0.4 0.85 / 0.85 428 / 432 29,178 / 33,221 +4,043 −7.5% GARGA 5:15 / 5:15 −0.7 0.84 / 0.85 433 / 444 22,861 / 27,157 +4,296 −7.1% ELB 5:51 / 5:50 −1.9 0.85 / 0.85 430 / 440 16,867 / 21,088 +4,221 −6.4% KERIT 6:06 / 6:02 −4.2 0.58 / 0.65 (FL180 / FL172) 311 / 361 15,675 / 20,034 +4,359 −6.5% NERAS 6:15 / 6:08 −6.9 0.56 / 0.46 342 / 275 14,644 / 19,200 +4,556 −6.7% LFMN touchdown 6:30 / 6:20 −9.8 — 253 / 128 13,490 / 17,455 +3,965 −5.7%

So which speed would the FMGS usually show at an FDP that is at 3000’+?

At 8:16, you can see the magenta dot at ALONU. Once sequenced, it shows again at LAKOL (8:33).

LKPR/06 N0418F280 DOBE8E DOBEN DCT NIRGO T108 LANDU LAND2A EDDM/08L Saved file and photos showing loc and gs not re-activeAB--LKPR-06-----EDMM-08L.bin

Hi Kyle, Just a quick question as it's been over a month: is this actively taken care of? The positioning and sound falloff of the exterior pack sounds are particularly disappointing at the moment. They can literally be heard from miles in front of the aircraft’s nose (seriously, give it a try — the sound seems to extend an absurd distance ahead of the aircraft), yet they almost completely disappear as you move towards the wing box, which is where the sound should actually originate. The current spatial positioning and attenuation of exterior sounds feel completely off and significantly detract from the overall sound experience. Hopefully, this is something that can be looked into and corrected. Thank you!

Hi everyone, I just wanted to let you know that the beacon/strobe sequence sync is broken again on v.1.0.5. Timing between beacon and strobe flashes is again determined by when you turn on the respective lights. Thanks for checking!

Well, finally it is the same. The flight plan in the Simulator EFB must be the final one you would like to use. If this is the case, you can send it to the avionics of the plane. This is the way how the MS flight plans are applied. Some planes need additional settings in order to accept flight plans from the simulator EFB. In some planes the sync makes problems. So I usually skip the MS internal tools and use Simbrief. It is much more reliable.

There are all the problems with throttle calibration that are listed in all the topics and as listed here. Is it unclear why the topic is closed? Many people have the same problems. Synaptic couldn't even make it possible to reset the settings to default. Now this plane is always in the maximum reverse position when loading, and this is not fixed in any way. My advice is that it's better not to touch anything there. It's useless to contact discord, no one there will help you in any way. I've reread a bunch of posts with similar problems and there's no solution anywhere. Maybe someone has found a solution and will share a link. ALL other planes are operating normally. In general, this plane is one big disappointment. I hope that no one will be offended by the criticism. With respect...

Could you clarify which NPAs you're talking about? For: RNAV/RNP approaches generally feature a runway point, though chart labeling depends on regional regulators (e.g., RW##* or a 5-letter named waypoint). But Non-precision approaches like VOR or NDB may lack a dedicated runway point based on where the ground facility is located. Specifying the exact approach would help clarify, please

which one? can you specify me what should I see from the video?

There are actually two ways VApp targets are handled on approach: Stabilized Approach: Entering the approach from 2,000 ft AGL, target VApp at the FAF/FAP. Decelerated Approach: Entering from 3,000 ft AGL or higher, target VApp by 1,000 ft AGL. Either way, reaching VApp is established long before arriving at the Final Decision Point (FDP) due to of Stabilized Approach Criteria factor. For some reason, IniBuilds calculates this logic on the runway instead of following the proper flight phases.☹️

That's a shame, then.-