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. Hi Carl, Sorry to hear you’re experiencing issues with the A350 on Xbox. My first suggestion would be to uninstall and reinstall the aircraft through the in-game marketplace, as this can sometimes resolve issues caused by corrupted or incomplete files. Let me know if that helps. Thanks!
  3. I’m using Xbox Series X + MSFS 2024 + iniBuilds A350. The problem occurs when starting the aircraft from a Cold & Dark state. I follow the normal startup procedure and import my SimBrief flight plan through the EFB. Flt Ops Sts and Load Sheet information both load normally. However, when I perform FPLN Request on the FMS, it remains stuck on “Pending Request” for about 20 seconds and then automatically returns to the previous screen. The flight plan is never loaded. I have repeatedly tried various troubleshooting methods, including re-importing the SimBrief flight plan, restarting the aircraft, reloading the flight, sending the FPLN Request again, switching through CAPT OIS/Center OIS and then importing again, as well as other related settings and procedures. I believe I have already tried pretty much all of the obvious troubleshooting steps. I have also seen other Xbox Series X players on YouTube using this function successfully, so I’m wondering whether this could be related to corrupted A350 data, cached data, saved aircraft data, or an Xbox-specific bug. If anyone knows how to completely reset the A350 data or fix the FPLN Request getting stuck on Pending, I would really appreciate your help.
  4. Today
  5. CptRei11 joined the community
  6. namlass joined the community
  7. Carl Hwung joined the community
  8. Hopefully they can track down the issue. Personally, I haven’t experienced any issues with this behaviour, and I’ve completed around 30–40 flights now. Could a keybind possibly be causing the issue? Do you have any keyboard keybinds assigned to roll, yaw, or any other flight control inputs? Thanks!
  9. admsanch0 joined the community
  10. AndrewHorvoc joined the community
  11. I have just posted this in their discord if others can follow suit with the same issues. https://discord.com/channels/648650013613883415/1539288446324056166
  12. I have also just had this, But it was flying in AP on approach. But also when flying manually it does it every flight, hard banks but normally recoverable. This time it was in AP at FL040 and banked hard right in and crashed into the ground! Cleary there is an issue somewhere.
  13. Avatar-X joined the community
  14. Hi, For the A35K, does this occur while you’re on the ground setting up the aircraft, or does the EFOB simply stop continuously updating as you fly along your flight path? Thanks!
  15. Hi, Thanks for your inquiry. The 707 we developed in collaboration with Working Title and Asobo/Microsoft is based on the “Combi” version of the 707. Hope this helps! Thanks!
  16. zorinoo joined the community
  17. Hi, Thanks for your feedback. We truly appreciate the time and effort you’ve put into sharing it. I’ll be sure to pass this along to the team for future consideration. That said, looking at the pictures you attached, I’m not really seeing a significant difference between the two. Thanks again for taking the time to share your feedback!
  18. iniKyle replied to Jimbojumbo's topic in General Discussion
    Hi, Sorry, I didn’t realize you were on Xbox. Unfortunately, the terrain radar is not available on the Xbox version of the A350. Thanks for your understanding!
  19. 3bood_l10 joined the community
  20. Great question! I believe we’ll have more information on that in the not too distant future. In the meantime, be sure to follow our usual social channels to stay up to date with the latest news and announcements. Thanks!
  21. Hi everyone, Microsoft/Asobo would be the best point of contact regarding this, as they ultimately control the outcome. Thanks for your understanding!
  22. Hi, Without an official paint kit, I can only imagine how difficult it must be. This is definitely a strong talking point and may be worth bringing up on the MSFS forums, as they ultimately control whether or not a paint kit is made publicly available. Glad to hear you're enjoying the aircraft! Thanks for your support!
  23. Hello, The team is aware of certain simvars not being implemented correctly and is working to get this resolved. Thank you for your patience and continued support!
  24. Thank you! The team is currently working on an update for Luton. Keep an eye out on our usual social channels for more info! Thank you again for your continued support!
  25. nasa00 joined the community
  26. Phum joined the community
  27. Ich habe inzwischen sogar mein windows 11 und den msfs 2024 komplett neu installiert als letzten versuch. Fazit ist,dass sogar das nichts gebracht hat und wirklich bei mir nur bei der a340 das problem besteht. Werde also die rückerstattung beantragen. Besten dank trozdem für die hilfe.
  28. In english sorry Title: Elevator trim switch and engine start crank unresponsive — A220 v1.0.4 Aircraft version: v1.0.4 (latest stable) Platform: MSFS 2024 Issue description: Two specific cockpit elements do not respond to any form of interaction, while every other switch/control in the cockpit works normally: Elevator trim switch — does not move Engine start selector/crank — does not move Interaction methods tested, all with no effect on these two elements only: Physical hardware (WinWing Ursa Throttle): input is correctly detected/highlighted in Options > Controls, but no action occurs in-sim Keyboard: same events (ELEV_TRIM_UP/DN, ENGINE_MASTER_1/2_TOGGLE) bound to keyboard keys for testing — no reaction either Direct mouse click in the 3D cockpit — no switch movement, no visible reaction Important point: every other cockpit switch and control responds normally to the mouse. The issue is therefore clearly isolated to these two specific elements, which rules out a general configuration issue, hardware problem, or MSFS2024 cockpit interaction mode — this points to a software bug targeted at the trim and engine start selector specifically. Expected behavior: The trim should move in increments when the switch is activated, and the engine start crank/selector should toggle between its positions on click or button assignment.
  29. Titre : Trim de profondeur et sélecteur crank (engine start) non-réactifs — A220 v1.0.4 Version de l'avion : v1.0.4 (dernière stable) Plateforme : MSFS 2024 Description du problème : Deux éléments précis du cockpit ne réagissent à aucune interaction, alors que tous les autres switches/commandes fonctionnent normalement : Switch de trim de profondeur — ne bouge pas Sélecteur/crank de mise en route moteur (engine start) — ne bouge pas Méthodes d'interaction testées, toutes sans effet sur ces deux seuls éléments : Manette physique (WinWing Ursa Throttle) : input bien détecté dans Options > Commandes, mais aucune action en jeu Clavier : mêmes événements (ELEV_TRIM_UP/DN, ENGINE_MASTER_1/2_TOGGLE) assignés en test — aucune réaction Clic souris direct dans le cockpit 3D — aucun mouvement du switch, aucune réaction visible Point important : tous les autres switches et commandes du cockpit répondent normalement à la souris. Le problème est donc bien localisé à ces deux éléments spécifiquement, ce qui exclut un souci global de configuration, de matériel, ou de mode d'interaction cockpit MSFS2024 — cela pointe vers un bug logiciel ciblé sur le trim et le sélecteur de start. Comportement attendu : Le trim devrait bouger par incréments à l'activation du switch, et le crank/sélecteur engine start devrait basculer entre ses positions au clic ou à l'assignation bouton.
  30. Hi, also the mapping of the plane is a nightmare as a painter, the texture of the handle protection came from the door itselft. The rudder is also very bad, we got 5 different part for one side and this is not even symmetrical^^ Also the junction between the wing and the fuselage being on a different texture than the fuselage is also a nightmare to use, you can't easily make a old livery with big line across the fuselage without taking 3/4 hours to got a nice result (bad for a plane when 90% of the operator got this kind of livery) Anyway thanks for the plane it's still very fun to fly Regards
  31. At least the 320C with all the windows and with only cargo or only pax and the 320B would be nice.
  32. And the guy updated his livery, he ameliorated the engines pylons color to make them even better. It's a so real livery, I just can't fly any other plane than my beloved B707. I waited 40 years for a such beautiful aircraft. Thank you so much Inibuilds, you have no idea how you make me happy with this aircraft. Hope you will really do some updates to fix different things I suggested.
  33. Thanks for the info! Will existing A350 owners get the upgrade for free?
  34. Is there any way to make other variants of the 707, for example the -400 or -300 with JT4D engines? I would be very happy if such a possibility existed
  35. Not sure if you can do this on the Xbox . If you can are you able to kindly show me . Many thanks

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.