Skip to content
View in the app

A better way to browse. Learn more.

iniBuilds Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

All Activity

This stream auto-updates

  1. Past hour
  2. Tried again. Same flightplan. This time I stayed at 6000 feet well past the point when the error occurred the previous times and everything worked as it should. Smooth sailing. Then I set FL320 and started the climb. At around FL090 the cockpit glitched out. Again. Tried on the ground before takeoff. If I switch to external view, and then switch back to cockpit view, for just a few tenths of a second all the lights in all the buttons are lit. Then go back to normal. At FL090 this samer thing happens but without switching views and it stays like that.
  3. Smashruru joined the community
  4. the clock background light is indeed controlled by the INTEG lights potentiometer. If that doesn't do something, there seems to be a bug. I can't tell you what it is though unfortunately. For me it works normally. Even though it doesn't exactly work like it's supposed to, I can't quite see the disadvantage... The clock and Chrono works fine without it.
  5. Wheelie98 joined the community
  6. For some reason I am not getting any blue backlit on the chrono/clock. I have looked for an hour already what the culprit is. Turned on max integ lights, flood lights, ambient light, storm light. The light that controls the blue backlight of the autopilot panel but the clock stays black.
  7. Boris joined the community
  8. Hi everyone, I have just followed the steps required for your GSX profile and its coming up as GSX cannot read the aircraft type, am I doing something wrong or is there a fix for this? Thanks!
  9. jroberts joined the community
  10. The same to me. This is not a good user experience!
  11. Today
  12. Hi was just wondering about the terrain radar on Xbox in the a380.Every time I turn it on it shows there is just water and no actual terrain when there is I have uninstalled it and reinstalled it and the same issue is happening. Is this something that is implemented to save performance on Xbox or is it a glitch Thank you :)
  13. RONALDO1 joined the community
  14. They said they would release v1.2.7
  15. When taxiing the nose wheel steering is very weak and it is hard to get onto other taxiways
  16. Hey guys, I can now confirm that my WASM crashes were related to adding and/or tampering with the SEC F-PLN. I usually use it for EO procedures on departure. Whether mid-flight or close to the destination, whenever I modified the main flight plan or performed any action that required the FMS to recalculate data, the WASM module always crashed if the SEC F-PLN had been used. I am aware that the WASM module runs in a sandbox and you guys did your best to squash all these crashes, but this particular flight plan-related crash is quite annoying since it is still present in the A350 and now in the A380. I hope it gets fixed in a future update. Since Friday, I’ve flown the A380 for over 30 hours with zero WASM issues simply by leaving the SEC F-PLN untouched. I tested the aircraft thoroughly with last-minute arrival changes, holds, and DIR TOs via both the ND and MCDU, and it all ran completely smoothly. SIAI Issue Fix: For the SIAI issue, I managed to fix it by selecting a different CPDLC provider in the EFB, clearing the SIAI API key, closing the sim, re-opening it, re-inputting the key, and selecting SIAI as the provider again. I believe certain SIAI updates break the communication between the SIAI addon and the aircraft, but this reset fixes it.
  17. Version 0.9.5 — Major Gate Assignment and TELEX Update https://fr.flightsim.to/addon/115219/a380-gate-assignment-telex-acars-beta-version Changes since version 0.9.4: Reworked the automatic Expected Gate TELEX sequence. The separate cruise and descent confirmations are replaced by one operational message sent at planned flight time minus 30 minutes. Flight time now starts when the landing gear is fully retracted after takeoff. Added a visible airborne elapsed-time counter so the detected takeoff point and T-30 progress can be checked directly from the panel. Simulator time acceleration is now supported. Elapsed flight time follows MSFS simulation UTC rather than real-world time. Added late-flight recovery using the SimBrief estimated or scheduled takeoff time. If the add-on is loaded after departure, an already-overdue T-30 message can be sent immediately, including during descent. The in-flight SEND button now refreshes the OFP, checks the current assignment and explicitly sends the Expected Gate without waiting for the automatic milestone. The fresh two-snapshot VATSIM check performed at T-30 is now limited to 45 seconds. If the public feed remains cached, the last verified gate is sent instead of entering repeated one-minute waits. Added visible VATSIM verification progress, remaining waiting time and last verified gate information. Gate reservations are now prioritised by estimated arrival time. The flight arriving closest to the gate availability time receives priority. An occupied gate can now be displayed as expected to become available before arrival, including the occupying callsign and its planned departure time. Added FREE xxxxZ, RESERVED xxxxZ and DEP DELAYED gate states. Added visible gate-assignment criteria: Company + Departure + Destination Company + Destination Destination only The panel now identifies the user's allocation with YOUR GATE and displays the flight's live ETA position among other VATSIM arrivals. Corrected Company Traffic filtering: departure and arrival traffic are no longer shown in the wrong views. VATSIM controllers, route traffic and Company Traffic remain available even when the destination has no verified gate records. The gate remains UNKNOWN instead of reporting a false VATSIM failure. Historical provider stand identifiers are no longer displayed directly as passenger gates. Verified references are converted to their current public chart labels. Added verified public-gate corrections for several US airports, including KBOS, KJFK, KMIA, KSFO and PHNL. Ambiguous remote stands, obsolete terminal references and unsupported provider codes are now suppressed instead of being presented as real passenger gates. The embedded A380 database has been enriched and now contains: 61 destinations 576 physical stands 2,554 ranked gate candidates Hoppie delivery now uses a dedicated flight-specific OPS sender, for example BAW902AOPS → BAW902A, to avoid conflicts with generic airline endpoints already used by other clients. Settings now displays the aircraft receiver, the dedicated OPS sender and the latest receiver check. Existing saved assignments are automatically migrated to the corrected public gate references whenever a verified correspondence is available. Numerous native-runtime, persistence, interface and TELEX reliability improvements. When no verified public gate can be determined, the add-on now deliberately reports UNKNOWN/PENDING rather than inventing a gate. VATSIM and Company Traffic continue operating normally in this situation.
  18. Ben9781 joined the community
  19. Hi So far I’m loving the aircraft. But a few points. mid flight autopilot disconnects, no sound warning no notification just disconnects, the aircraft follows the flight path slightly off the direction coordinates (if that makes sense) Wing flex on ground. Really crazy wing flex when taxing on ground wings bend up and down Looking forward to the update and thank you for such a amazing aircraft
  20. A380ollie joined the community
  21. Having same issues as well, hopefully a fix isn't too far off :D
  22. I do not own the A380 just yet, I damn hope by next week!! But, based on what I do on the a350 despite reading all messages on the OIS is to click ATC COM on the KCUU then go to all messages and read through all of them should fix it. @Eurosky saw your other post with the company MSG inside as well, lmk if it works
  23. Hi, it is worth checking other devices such as keyboard mouse that may have rudder binded as well. Also check sensitivity settings for the Z axis. If you have any other control profiles try switching to them and see how the aircraft behaves with the rudder and if it works after say 2 test flights adjust the profile to what you need to be if there are changes. (Duplicate it) Worth also calibrating the sidestick via sim app pro which you can download here if you haven't already, try using a profile you can download there and see if the rudder works, just find something for the Fenix (you may have to rebind autopilot disconnect button to be autopilot off, for some reason they made it like that) SimAppPro download (requires login to your Winctrl store account, otherwise create a new one): https://winctrl.com/view/simapppro.html
  24. https://forum.inibuilds.com/forum/779-systems/ Probably best to post in here, you can just put the link to this thread and post it there so it gets seen.
  25. Hi. 1. Bindings and other mappings are more than likely in the aircraft manual, you can find this here as well as other FAQ's for the aircraft: https://forum.inibuilds.com/topic/40789-aircraft-manual-a380-airliner/ 2. Liveries pack (if you are on console) is available on the MSFS marketplace for a limited time for free, however I am unsure if it is still available for free currently, do pick it up ASAP if you are on console, otherwise if you are on PC it is available on the iniManager 3. That may also be detailed in the manual, however you will have to set up throttle calibration and simbrief settings among other things such as items that are personal preference in the EFB. Feel free to also watch some tutorials. Or just read the manual.
  26. Hi, this is something to report on the MSFS forums, as I'd presume this is more so out of ini's control. https://forums.flightsimulator.com/
  27. Hello, i just bought and installed v.1.0.9 from the inibuilds store. The rudder trim is not working for me. When I click on the clickspots, the rudder trim knob doesn't move. There is no conflicting keybinding for rudder trim on any input device. If I add a rudder trim keybind, it does not work either. (not just not visibly turning the knob, but no reaction of the rudder) On the aileron trim there are not even mouse clickspots visible and it doesnt function either as far as I can tell, elevator trim functions. Please find attached a video KR Alexander Screen Recording 2026-09-20 094836.mp4
  28. Would love this on the a380 too
  29. Waiting for the WW tiller but till then which of these would you guys suggest?
  30. you cant reach them to close them in VR they are too high, same with APU cowls however they have a close option on the tablet so ok.
  31. im not sure why the images in the FAQ say not available in my region?
  32. Hello, this is the a350 V2 update, not V1. The reason why it hasn't come yet is because the first update for the 350 before A350 V2 will be "A350 Systems and Performance Update 1" I'd reckon a350 v2 would come out very early next year if they want to make it fully polished or in a few months. For more information check out the latest dev update here: https://forum.inibuilds.com/topic/37603-inibuilds-a380-airliner-development-update-august-2026/ (You will have to scroll down)
  33. The PMDG 777 has their own animation behaviour that realistically animates the gear tilt by driving the angle of the bogie with their internal simvar. (Which is calculated inside their WASM) Source: https://www.reddit.com/r/MicrosoftFlightSim/comments/1eo22js/comment/lhagz0z/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button I would hope inibuilds could do something similar though I'm sure they have the expertise for it, all these aircraft that have these unique bogies and behaviour on touchdown would be nice to see implemented. Since there hasn't been any updates @iniKyle would be nice if the team could look at this one! Cheers

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.