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.

A380 feedback

Featured Replies

  1. RA callout tonality
    The RA callouts are the same copy and paste ini has once used/ or currently using for the a350 and a340 which imo is just from (aircraft name here gpws on youtube). Given this is another headphones approach here is a video of what it actually sounds like through the headset as Qatar Airways likes to hook up their audio to the ACP panel to hear ATC https://www.youtube.com/watch?v=ajV6XYKCjEw
    Sounds a bit different, no?
    Terrain ahead pull up sounds accurate to the a380/fbw so a bit confused why the other stuff is different, but not at all detrimental to functionality
    But of course we don't want to do any major changes on short final so perfectly acceptable to change this in a future update to the product if good samples cannot be sourced.

    2. Retard Logic- As with my other posts on the a350 and a340, please check those the retard logic (idle thrust levers) used in other ini products is not accurate according to the FCOM, this is a very basic thing but it must have been skimped in other bigger fish to fry issues with 350 and 340 and probably missed in the a380 some way shape or form. I understand but considering the system depth and completeness of this addon being said I would have an expectation this is correct.
    Also to add, the retard callout will cutoff callouts that is in it's way if that makes sense, it will not intertwine with the RA callouts and will instead override with FWS priority, however that would require a bunch of effort
    image.png







    Other than that I must say the aircraft looks very good, doesn't takeoff like a helicopter to, that I definitely noticed.

  • Staff
7 hours ago, limbo said:
  1. RA callout tonality
    The RA callouts are the same copy and paste ini has once used/ or currently using for the a350 and a340 which imo is just from (aircraft name here gpws on youtube). Given this is another headphones approach here is a video of what it actually sounds like through the headset as Qatar Airways likes to hook up their audio to the ACP panel to hear ATC https://www.youtube.com/watch?v=ajV6XYKCjEw
    Sounds a bit different, no?
    Terrain ahead pull up sounds accurate to the a380/fbw so a bit confused why the other stuff is different, but not at all detrimental to functionality
    But of course we don't want to do any major changes on short final so perfectly acceptable to change this in a future update to the product if good samples cannot be sourced.

    2. Retard Logic- As with my other posts on the a350 and a340, please check those the retard logic (idle thrust levers) used in other ini products is not accurate according to the FCOM, this is a very basic thing but it must have been skimped in other bigger fish to fry issues with 350 and 340 and probably missed in the a380 some way shape or form. I understand but considering the system depth and completeness of this addon being said I would have an expectation this is correct.
    Also to add, the retard callout will cutoff callouts that is in it's way if that makes sense, it will not intertwine with the RA callouts and will instead override with FWS priority, however that would require a bunch of effort
    image.png







    Other than that I must say the aircraft looks very good, doesn't takeoff like a helicopter to, that I definitely noticed.

Hi,

Thanks for the detailed feedback! I’ll make sure the development team has a chance to review this.

Thanks again for taking the time to share your feedback!

Kyle - Community Manager

iniBuilds Ltd. | inibuilds.com

  • 2 weeks later...
  • Author
On 9/3/2026 at 11:48 PM, iniKyle said:

Hi,

Thanks for the detailed feedback! I’ll make sure the development team has a chance to review this.

Thanks again for taking the time to share your feedback!

Hi Kyle,

Any updates on these items? I haven't bought the aircraft yet but hoping to in a few weeks

  • Staff
2 hours ago, limbo said:

Hi Kyle,

Any updates on these items? I haven't bought the aircraft yet but hoping to in a few weeks

None yet, but I forwarded this thread to the team!

Thanks!

Kyle - Community Manager

iniBuilds Ltd. | inibuilds.com

First I want to say what a fantastic job your team has done with the A380. The detail has me blown away and it’s been bringing back so many memories of my travels. I was a frequent traveller on the A380 as it was my ride to and from home.

Just a little bit of feedback about a few things:

The performance calculator might need a bit of tweaking for long haul flights. In FS2024 I was flying EK242 (YYZ-DXB) on a GP7200 equipped A380. With the appropriate fuel load and a near full load of pax and cargo. The FLEX setting the performance calculator gave me was 67. Looking at the thrust it would give me on the ECAM it seemed like a suspiciously significant derate. I changed the FLEX to 50 before taking off and still used almost the whole runway. I feel if I kept it at 67 an overrun would be probable.

Next: Sound.

The GP7000 in the sim is a little bit too quiet and the buzzsaw pitch at full power is lower than what I’ve experienced as a passenger.

here’s some links to videos I’ve taken while on the A380 for you to use for sound reference for Engine Alliance GP7000 sounds.

This first video was taken on EK242 (YYZ-DXB) on a winter day from runway 33R. Seat is 4K (upper deck)

This one was taken at seat 9A. Same flight, EK242 (YYZ-DXB) taking off on a winter day from runway 23

This one was taken on EK242 (YYZ-DXB) from runway 06L in December. Seat is 2A (upper deck). This is on a day where it’s still cold but no active precipitation. The engine is quieter but still very noticeable.

Thank you for taking the time to go through the videos and wishing the team nothing but success.

Regards,

Alek Boisjoly

Create an account or sign in to comment

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.