All Activity

Ok thank you! Hopefully I don’t have to wait too long because the sounds sound amazing coming from the a380!

I'm now having this exact same issue with the A220. All other aircraft are fine including the tristar. I've tried uninstalling and reinstalling the a220, also the inimanager and the aircraft. deleting the WASm folders...Tried different controller profiles that work ok with other planes. Lats resort may be to uninstall the a220 again, delete and reinstall the sim. This is on SU6.1

When will the A380, A350 and A340 be coming to PS5? 😭❤️ I’m a huge iniBuilds Airbus fan and would buy all three on day one! Xbox already has some of them, so I’m really hoping PS5 gets them soon. Any news? 🙏✈️

I’m experiencing severe performance issues and heavy stuttering at EGCC following the last update. Developer Mode consistently reports a heavy "Limited by Main Thread" bottleneck on my AMD Ryzen 7 9800X3D system, specifically when on the ground or in the airspace around Manchester. I have zero main-thread issues or frame drops at any other complex third-party or handcrafted airports, confirming this is isolated to EGCC’s latest build. Could the team please look into the optimization of this update, and let us know when we might expect a patch or update to address this issue?

WinCTRL Ursa Minor 32

Thanks. For troubleshooting purposes, which throttle are you using?

Hi, Thanks for your feedback! I will forward this video to the team for further review. Thanks again!

Hi, Thanks for your report. I believe this issue has been fixed in v1.0.2 or v1.0.3 Thanks for your patience!

Yeah it is, still problems on the takeoff run

Ive tried a few autolands now and i see the same behaviour each time, also saw same behaviour on a ini A380 youtube video too video too linked here at 2:40:40. The nose suddenly pitches up at the start of the flare instead of a smooth pitch up. Im not sure of thats realistic and true to the RW A380 or not but i wouldnt have thought so based on other autoland videos ive seen of many other airliners

Hi everyone working at the inibuilds development team! I would like to report a bug I have noticed while flying your new beautiful aircraft, now I do not know if this bug is within Microsoft flight simulator or if it is the aircraft itself but every time I go into showcase mode and use the for to see my plane taking off, the planes audio is fine until it goes directly in front of me and the. It just sounds like the engines are at idle and then once it goes past me it goes back to Normal, if this is a a380 issue could you please fix this? And if this is a Microsoft issue, could you please tell me the solution to this bug? Thank you

Hi, New users are unable to see or download the cabin packs. They are only visible to users who downloaded the packs before they were discontinued. Thanks!

Hi all, Thanks for the suggestion — I tested the SimBrief OFP settings exactly as shown above. I re‑enabled Detailed Navlog, ETOPS Planning, Plan Stepclimbs, and Runway Analysis just like in the screenshots. In my case, the issue is still there. To rule out any installation problems, I actually uninstalled the A340 completely from MSFS2024 and then reinstalled it again before trying these settings. Even after a fresh install, the behavior doesn’t change: AOC FLT INIT works normally INIT REQUEST still does not load the flight plan into the FMGC The EFB shows the SimBrief package correctly, but the FMGC never receives the uplink So this seems to be a different issue than the one caused by unticking Detailed Navlog. Just adding this here so the team knows this is not the same edge case. Thanks.

Hi, Is this issue still persisting for you? Thanks!

Hi, Thank you for the very detailed report! I have logged this for the team to review. We appreciate you taking the time to share your feedback. Thanks again!

Also having the same issue. Completely forgot that i'm also running SU7 beta

The update did not solve the problem. :-/

Thanks for the response. It seems certainly to be the case for me, as if maybe a variable in my account is activated and hence they show up. Certainly not worth doing this any more as they literally cause the entire cockpit to disappear (i.e. they cause a really bad bug) so I'd absolutely suggest their removal as being something that would help future users.

So it is nice that you’ve implemented the METOTS logic into the sim. However, there are still some inaccuracies in the way it currently works. The main issue is that the iniBuilds A380s METOTS logic appears to apply a thrust limitation without taking the target N1 into account. On the real aircraft, this limitation should only apply when the target N1 exceeds 78%. In all other cases, the engines should spool directly to the commanded takeoff thrust, without being held at an intermediate N1 value before reaching the target. For example, in the current iniBuilds A380, if the target N1 is 73% during take-off, the engines remain at approximately 68% until reaching 35 knots, before spooling up to the target thrust. This does not appear to reflect the correct METOTS logic. I’ll attach a couple of photos and videos of the real aircraft for comparison. SIM: During takeoff, Stuck on 70.5 N1 Until 35kts, and then spolled to 72%. (Incorrect Logic) IRL, Non METOTS takeoff: https://youtu.be/pHui34_ODnc?si=Lr03VQaoLh9DwGfn&t=13 IRL, Correct logic of METOTS Takeoff: https://youtu.be/7pX9hxn-cmE?si=xrmIlb2I1sst3Otm&t=770

Everyone, please keep this civil. Remember we are all here for the same reason. Thank you!

Hi, Thanks for your report. I'll test this on my end and report back. Thanks for your patience!

So I was trying to let my throttle “choose” where the detents were, you need to choose where you want them not the other way around. So just go into the efb set you idle at the bottom and your toga at the top and then choose where you think the flex and clb defends make the most sense. Then it will stretch them out. I hope that makes sense. It just another way to think about it I guess.

Now who is speaking for himself? You are insufferable.

RNP RWY 02 AR Approach (Airport SKPS) is coded wrong in MSFS2024 and is not flyable. Same approach is correct in MSFS2020 and the A350 flies perfectly. pls see the attached.

Oh that’s just brilliant news. Thanks so much. Looking forward to trying it when it’s out!