All Activity

Hello ini team, Two things for the suggestion box. First: There doesn't appear to be a filter for airports when shown on the Navigation Display, meaning huge amounts of clutter. -Would be nice to be able to filter out airports using a setting the EFB for runway length (easy mode) or.... -Would be GREAT to only show suitable A380 airfields on the ND (hard mode - I appreciate this would be a lot more work!) Second: Transition from a relatively low flex setting takeoff to a higher climb/de-rated climb seems abnormally abrupt. I know the aircraft does this is in real life under certain conditions but it does seem rather excessive in the sim. Maybe the logic could be looked at here and verified with a real A380 pilot (A320 IRL so not much help here, but it does seem a little off!) Otherwise, nice initial release which I know will keep on being worked on. I'll get back to the bar on the A380 now and enjoy some snacks before descent into SFO! :

Hi, Thanks for your detailed feedback. A few things to note: GSX Profile: Have you downloaded the official GSX profile for the A380? I'm currently unable to reproduce this issue on my end. Charts: I'm also unable to reproduce the charts issue. As a first step, please try logging out of Navigraph and then logging back in. Steering: Please make sure you don't have any conflicting keyboard keybinds that may be interfering with the aircraft's steering. ILS: I've noted the ILS bug and will keep an eye on it, although I have not yet been able to reproduce the issue on my end. Taxiing to the Gate: This may have been related to a severe weather update. I'll also try to reproduce this on my end to investigate further. Thanks again for taking the time to provide such detailed feedback!

I am going to do another flight tonight when I get home but I confirm there is no Terrain Data and I also never saw any TCAS traffic show up on the ND. Confirmed TCAS was on auto, and on TA/RA and TA came on and went off above and below 1000' like it should. Will report back tonight after another flight regarding TCAS traffic on the ND.

Hi, Thanks for your feedback. We have addressed this issue in the next update. Thanks for your patience!

Hi, 1.0.9 released on the marketplace and we're fine tuning 1.0.9 for the iniManager. Thanks for your patience!

You are correct. We're fine tuning 1.0.9 for release on the iniManager. Thanks for your patience!

Marketplace version is 1.0.9 as far as I know.

Hi, Not a typo or fix needed, this was to simply bring the Marketplace version and the iniManager version to the same batch (v1.0.8) Thanks for your understanding!

Something clearly broke in the inibuilds manager. 2.1 gigabytes were downloaded in the A220 update.

Hey Wolfgang. I experienced the exact same issue as you. It turns out the resolution of the OANS map is directly tied to your texture resolution in your graphic settings. No doubt you have set yours at medium or lower. If you bump it up to high, the map resolution looks perfect. 👍🏼 Hope this helps.

Hi, I noticed while creating my AAO script for the stream deck, that the APU START button is controlled via the "AIRLINER_APU_START_Toggle" B-variable or the Input Event "AIRLINER_APU_START" Problem is, the button is stuck in the on position and I can't find any other variable to release it except clicking on it with the mouse. Not a big issue but I had issues before where buttons are stuck and this created the wildest problems later on in the flight. Maybe this is something you might consider to fix in a later patch. Thanks. EDIT: this also concerns the External Power switches and I guess all toggle-only buttons.

Hey guys. Not sure if its just me, but ive now completed 3 flights. Each time ive set BTV for the autobrake. Choosing the appropriate runway/taxiway exit point. The aircraft will slow down and at roughly 10knots i hear the audible click of the Autobrake knob dissarming but I dont hear any audio that should say "autobrake off" Have I got this right? Or have i got that around the wrong way? If i tap the brakes before the chosen exit point does it make the audible call out? 🤔

Hi, Thanks for your report and feedback. I'm sorry to hear that your first two attempts were unsuccessful. I haven't heard of anyone else experiencing issues with their EFB settings, but I'll make a note of this on my end for further investigation. Thanks for bringing this to our attention!

Hi Team, I just found out that I cannot load in my Simbrief flight plan by clicking CPNY F-PLN REQUEST, It just pops back up after like a minute or so. I have tried to clear my WASM folder with no luck. Regards, Leo

Hello, I planned a flight from OMDB to EDDF. Two attempts to perform the flight were unsuccessful. The first attempt ended in a freeze of MSFS about one and a half hours after departure from Dubai (around Jeddah). Unfortunately, no reports were found in the Windows logs, but the MSFS log is attached. The second attempt ended in a failure of the A380 systems a few minutes after departure. I am not sure what the reason was, but at that exact moment, the chart provider in the EFB changed from Simulator to Navigraph. The sim froze for a few seconds and all data was lost (flight plan and performance data). Furthermore, some settings in the EFB are currently not persistent. Almost all settings from before the first flight were reset to default for the second flight (except for calibration and third-party settings). Lastly, GSX had some problems reacting correctly with the aircraft during the second attempt, whereas during the first flight, everything worked fine. I think it is best to delete the WASM folder before starting the third attempt. AsoboReport-Crash-1960707156.txt

I can confirm that I am experiencing what appears to be the same VR-specific issue. It has occurred on two separate flights, with a complete computer reboot between them. When the problem begins, entire groups of cockpit controls highlight blue simultaneously. The mouse remains active, but it operates multiple controls at once—or controls other than the one being pointed at. At the same time, virtually all cockpit lights and annunciators illuminate as though the cockpit light-test function had been activated. I am also seeing displaced cockpit geometry. The most obvious example appears to be a windshield-wiper control knob or dial floating over the windshield rather than remaining attached to its panel. This sounds very similar to the floating knob mentioned in the original report. The problem only occurs in VR. Pressing Ctrl+Tab to leave VR immediately restores the cockpit to normal, and the aircraft remains completely flyable in 2D with no relevant warnings or system errors. If I re-enter VR, the broken lighting, highlighting, geometry and mouse interaction return. The failure occurred on approximately the same timeline during both attempts—about 10 minutes after takeoff. I initially noticed it while configuring the arrival and runway in the FMS during climb-out. However, I now suspect the FMS activity may be coincidental and that the actual trigger may be time spent airborne. On my second attempt, I completed the aircraft setup considerably faster, but the problem still appeared at approximately the same point after takeoff. I have not been able to reproduce it while the aircraft is on the ground, regardless of how much time I spend setting up the aircraft. Both tests used the same SimBrief-planned KDEN–KDFW flight and departure: • Headset: Pimax Crystal Light • VR software/OpenXR runtime: Pimax Play • CPU: AMD Ryzen 9 7950X3D • GPU: NVIDIA RTX 4090 • RAM: 64 GB • Simulator: MSFS 2024 • Simulator versions tested: SU6 and SU7 beta • A380 version: Marketplace release-day v1.0.0 • Flight-planning integration: Navigraph One occurrence was under SU7 beta and the other under SU6, with a computer reboot between tests. The behavior was effectively identical in both simulator versions, so it does not appear to be confined to the SU7 beta. Attempting to restart or reload the flight after the corruption appears has also resulted in a crash to desktop. After completely restarting the simulator, the A380 works normally in VR again for approximately 10 minutes after takeoff, after which the same problem returns. Unfortunately, I will not have an opportunity to record a video immediately, but I wanted to add an independent confirmation because the issue is repeatable and currently prevents completing a flight in VR. I would be happy to provide any additional settings or configuration information that may help isolate it.

Yes, that's a great suggestion. Right now, they only swing side to side with the same animation for all engines at the same time. In VR or on a big wide screen monitor the static wing is a huge immersion killer. I will be nice if the pylon is animated so it dynamically jolts or shake along with the wingflex and add a little bit of swivel to it (of course only in turbulence or heavy touch down or something like that) . Like in Xplane 12's A330, that just makes the plane feel heavy and not static. A330-300 Engine Goes Wiggle Wiggle 😳 | X-Plane 12

Plase pass this along to the team also for the A340 and the A350,because it´s a real torture to follow the horizontal FD bar....

Sorry, didn't see your request until now. If you're still trying to work on this, I can try and show what I did: Import the FBX into Blender In Layout, select the fuselage Select the Shading tab, and in the bottom half, check the Fuse_Main material is selected, and add an Image Texture to the Principled BSDF - Base Colour In the Image Texture box, click New, name it "A380_FUSE" (not essential, but this will help with export), set the Width and Height to 2048, I like to set the Colour to have an Alpha of 0 so it's transparent initially, and the crucially, MAKE SURE you tick "Tiled" Go to Texture Paint mode, and focus on the 2D Paint side. In the Image menu at the top right, you need to focus on the UDIM Tiles section. You should have 1001 there. Click the plus. Set the Colour again if you want the alpha, and then Add. It will create 1002. Keep going until you have 1001-1005. Click the plus again, but now change the number manually to 1011. Add more up to 1015. (Optional Step) Go back to Layout mode, and select the underbelly of the plane, then go back to Texture Paint. This only aids visibility of what's going on, doesn't really affect what you need to do. Now add more UDIM tiles, 1021 and 1022. These cover the belly sections. (Optional Step) Go back to Layout mode, and select the tail, then go back to Texture Paint. This only aids visibility of what's going on, doesn't really affect what you need to do. Add 1023 and 1024 for the tail sections. For the Engines now, you go back to Layout, pick the engines you want (GP or RR), and we need to do a similar thing, albeit less complex. Go to Shading again, the Material for the engines should be selected hopefully. Add an Image Texture as before, same settings (named A380_RR_COWL or GP as needed). Go back to Texture Paint mode and add UDIM tiles up to 1004 That's it from what I recall! Now when you save those images, it will split them up for you with the right numbers to match what you need. You can paint every section of the fuselage, tail and engine cowls. Wingfences are just one file, so I haven't gone over that. Hopefully this helps you, or someone who stumbles upon it!

I've had the exact same, not sure what I'm doing wrong.

The manual mentions the need to install "A380 Airliner Terrain Data", but it's not included in your screenshot. Furthermore, I tried using A350 Terrain Data, but it didn't work either

Hello, I'd like to request some additions to the paintkit, if it's possible? I'm far from an expert in painting and modelling for MSFS, but there's some things I've run into here that I can't find solutions to easily. As it stands, it doesn't seem possible to build a fresh livery without cannibalising some elements of existing liveries. For example, just making a livery using the texture files the PSDs, putting them into the folder etc., when you get into the sim, the window surrounds disappear: Not sure why the fallback model is missing these (assuming that's what it is). There's also the matter of the window plugs, something that isn't in the Paintkit, the FBX doesn't seem to mention them, so this was a bit of a surprise too. And then if you borrow models to fix the window frames, you get additional windows plugged, depending on the livery you borrowed from! There's an A380_PLUGS_ALBD file in some of the liveries, but there's 220 windows in there at my count, so determining which ones to paint is quite a faff! For 'fictional' liveries like the one I'm making, I think the 'White' base would be fine to borrow these elements from, as it seems to be the most simple form of the plane, no extra plugs, everything is straightforward. But as it's part of the marketplace plane and not a Community download, thus encrypted, I can't find a way to get at the files to finish off my design. When the iniManager release arrives, I could probably do it, but that's a while away... Requests: Would you be able to include the model files for the standard 'White' livery? Could you include a plugs texture, so we can paint these as needed? Could you also include the various placard/decal files? I'd like to be able to change the text colour in places so it's not red on red! I'd love to get flying this beast as soon as I can get myself sorted! Any help would be appreciated (even if it's to tell me that I'm doing it all wrong!).

same problem here, after loging out and in on navigraph it still shows latest as 2303 r1

my hardware adpation is done, FYI https://youtu.be/L96wadHWAbM

iniBuilds' A380 releases today, and our overhead panel is already fully adapted.I don't think any other manufacturer on the market can pull that off. The quality of a software architecture determines how difficult it is for a manufacturer to adapt to a new aircraft. If the architecture isn't good enough, adapting to a new aircraft can take weeks—or even months. Only with a truly solid architecture can we get our hardware working directly with the latest aircraft for our customers as quickly as possible, with no waiting required.