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. Should also say - this applies to the A350 as well. Thanks for all your work. Cheers, Chen
  3. This one is related to VSD profile on landing Currently the ground rises up as the plane descends on approach and the aircraft symbol is pinned at the middle of the VSD (see the red arrows added in this shot), the vertical scale of VSD goes into -1000ft upwards to 2000-3000ft ai The real one in sequence on this video -> https://youtu.be/qcXQKQukxkI?si=ivNivgynFUgnU0cD Before capture of GLS/ILS After capture the plane goes to the middle of VSD scale The the yellow plane symbol moves down the vertical scale part of VSD and the ground remains at the bottom, instead of the ground rising up from below to meet the plane symbol at the middle.
  4. Thanks Kyle I'll separate the 2 issues with the VSD with separate posts. This one is related to VSD profile on climb only Initial selected altitude is 5000 on MCP, but currently there is no level off indication on VSD during initial take-off/climb out. When the plane first enters ALT* capture mode as it nears 5000, in this case passing through 3800, it briefly shows the correct indication - I believe this should be the way it shows it from the start of take off. And then very quickly - this is what it shows -> MCP altitude is 5000, plane is climbing through 3900, the level off horizontal profile is showing at 3900feet, and this goes up with the plane until the actual level off at 5000. Real video footage from this -> https://www.youtube.com/watch?v=pHui34_ODnc
  5. jaceperaiscool joined the community
  6. Today
  7. After the 1.0.4 update, everything works fine. Thank you very much for the support.
  8. yowsiza joined the community
  9. Have you got the plane downloaded and installed locally, or are you streaming it?
  10. Thanks mate! Question, is there any chance of additional QF rego’s being made available? Selfishly, I’ve sat on the flight deck of OQD and would love to have that in sim, but being on Xbox I realise I’m severely limited to what liveries will ever be available
  11. Yesterday
  12. da_winner5 joined the community
  13. Helpisucc joined the community
  14. Hoque replied to Hoque's topic in General Discussion
    Hey kyle 🙋‍♂️ yet there’s no information about launch of A380 on ps5? Guys contact ms/asobo whatever and ask them to drop the aircraft on ps5 marketplace if all good please🙏 i just can’t wait man, i just don’t like any other 3rd party aircraft except you guys, inibuilds makes best aircraft you guys are the🐐🙏🙏
  15. Thank you, please apologize for the insistence. It's been a while without news, and now with the new launch of Doha for X-Plane, it's literally impossible to install it on Mac because of this.
  16. alvaroM joined the community
  17. Hello, so there is currently no way to get my hands on the A310? Looking forward to your response and thanks in advance.
  18. Thanks Kyle, unfortunately, no change.
  19. Hi, Thanks for you inquiry. I'm not entirely sure myself, will forward this to the team for further clarification. Thanks!
  20. I haven't received any news to report. I've just pinged a request for an update, will post here when I receive one. Thanks again for your patience.
  21. Hi, Thanks for your report. I have not seen any other reports of this recently, so I'm not entirely sure whats going on. Are you part of the Synaptic discord? They may be able to assist and troubleshoot with you further than I can. Thanks.
  22. It seems like the servers may be having issues/slow right now. Please wait and try again. Thanks!
  23. Hello, has there been any news? It's been a while...
  24. ibrahimlamis joined the community
  25. HanSolo joined the community
  26. idontknowmyname joined the community
  27. I flew the A220 without any issue with the external power last week. This week after su7 launched, the external power will not enable. So far I've: Made sure the plane was disabled in the marketplace. Uninstalled/Reinstalled from inimanager tried various liveries no dice. I do not want to recreate my whole community folder as all other 3rd party planes work, and it's an excessive amount of data in there. Just a pain of a process to go through for one airplane. This is localized to the a220. I had the exact same issue in the past but it was due to migrating to inibuilds from the marketplace. This time, the same resolution does not work. Thanks in advance, but for now I'll shelf the plane.
  28. yLPDG_3 joined the community
  29. bocchidez joined the community
  30. Does anyone know the exact size I need to make my canvas to make a internal Reg plate I don't seem to have a file for it in the paint kit?
  31. allansaurusrex changed their profile photo
  32. Having the same problem - it's not selected in the free flight menu either.
  33. This is also happening to me. I just loaded after 8 minutes and 49 seconds and every flight is like that. I'm on SU7 "official" as of today (I'm never on beta builds). This is also happened in SU6 to the point that I gave up using the aircraft. I knew it was normal to have a long load after an aircraft update but there hasn't been any updates in a long time so I can't explain this. My FS install is untouched (I don't mess around with conf files, ini files etc.). My addons are very typical of Airline flying - Navigraph NavData, Fenix A32X, FBW A380 and Injector A350 1.2.6 FS24 SU7
  34. Was hopeful that would solve the issue. I'll keep digging around. Thanks for your continued patience!
  35. Hi Kyle, Thanks for the suggestion. I gave the clean Community folder method a try, but unfortunately, the result is still the same — the EFB and AOC messages load fine, but the FMGC MCDU still returns ERROR DOWNLOADING DATA on INIT REQUEST or nothing loads at all. It is very frustrating and I am at a loss! Since resetting the Community folder doesn't clear out local state data, I also went ahead and purged the aircraft's WASM work/cache folder located in %APPDATA% / %LOCALAPPDATA%, verified I am using my numeric SimBrief Pilot ID (rather than username) in the EFB keyboard, and tested on the default house livery. Since the EFB successfully fetches the OFP via web API while the MCDU/FMGC WASM datalink request consistently fails across all fresh reinstalls and clean folder tests, it seems like a specific local state or WASM uplink handler issue. For reference, I have attached: My raw simbrief.json payload The compiled .fpl route file (CYULLFMN_INA_1792172214.fpl) A screenshot of the blank MCDU screen on INIT REQUEST As you can see, the route files generate fine in the work directory, but the FMGC fails to ingest or parse them into the cockpit session. Is there anything specific in these payloads or local files that could be causing the FMS parser to reject the import? Thanks again for continuing to look into this! simbrief.json CYULLFMN_INA_1792172214.fpl
  36. I have the same issue still in version 1.04. But for me to close AUTOFPS solve the issue immediatly. It's not good at all but I can finish flights in VR. The A380 is the first Aircraft where I have those problem. Even the A350 wokrs fine. I will try some other Airplanes on the weekend and see if this linked to the A380 only.
  37. Just ran the A380 on V1.0.4 with latest AIRAC from Navigraph into EDDF and the FMS definitely recognises the approach but doesn't use the SLS guidance; it reverts to FLS as other have stated. The GLS approach does work as expected. I also tested the approach identically in the A350 and it does give correct SLS guidance
  38. Simpilot replied to Simpilot's topic in Other
    Whatever was the solution it's now according to version. Thanks
  39. There is no fix on the horizon because we cannot reproduce this issue in testing or daily use. That being said, have you tried re calibrating your headset or ensuring your roomscale is correct for the POV?

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.