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. Today
  2. I've recorded a complete full flight along the VMMC–VHHH (Runway 25C) route. I uploaded the video to YouTube using some alternative methods. My recording setup and procedures weren’t very standardized or professional, and the video might be a bit longer than usual, so please bear with me. Also, could you help me figure out why the ILS approach was unavailable?
  3. The list has been submitted to the team, I can't guarantee what is added, or when. Thank you.
  4. IniJamir replied to LineDX's topic in Systems
    Hi, this issue has been raised to the team, I will add this to the log for them, thank you.
  5. Hi, do you have Hues Core or any other mods. Is this PC or Xbox?
  6. skyhangar joined the community
  7. RAVA SIMULAÇÃO joined the community
  8. werisq2 joined the community
  9. LineDX replied to LineDX's topic in Systems
    Comparison with Fenix A320: In the Fenix A320, the SID altitude constraint is correctly capped at 7,000 ft and is consistently displayed on the altitude tape, navigation display (ND), and FMS, even when the FCU altitude is set to FL370. In contrast, on the A350, recent builds appear to have a regression. The altitude tape does not display the SID altitude constraint during pre-flight setup. Instead, the constraint only becomes visible after takeoff, once thrust is reduced to CLB. This behavior was not observed in earlier A350 builds, suggesting a recent issue affecting constraint visualization during initial flight setup.
  10. JAGD joined the community
  11. benbenlan1009 joined the community
  12. tankyfranky joined the community
  13. Yesterday
  14. I've removed all the liveries, and I've removed and reinstalled the aircraft itself. Nothing is working.
  15. rezkii joined the community
  16. Luxov joined the community
  17. After hours of troubleshooting, I found a fix to this problem, but it only works if you have Navigraph subscription. The cause: This problem is actually not specific to just iniBuilds default A320/A330, it's applicable to all Asobo-distributed aircraft, such as ATR. It's caused by combination of factors, among them how MSFS2024 handles package priorities and how some 3rd party airports are able to override any other navdata. Apparently, some 3rd party airports somehow override MSFS default or Navigraph data, but they don't have airport-related fixpoints and other things properly defined in them, so this causes those fixpoints in airport's SIDs and STARs to have 0,0 coordinates. This is a reason why this problem never occurs for default airports. Many custom airports are also working fine. It's just those custom airports that have their own navigation layer are causing this problem. In my case, I specifically had it occur on freeware airports developed by x-flight team. The fix: If you are using Navigraph, you can fix this by setting priority of Navigraph data higher, so it takes over navdata in airport scenery. Open your Content.xml (located in [your_windows_username]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\[your_MSFS_username]. In the file, find following entries: <Package name="communityfs24-navigraph-nav-base" active="Activated"/> <Package name="communityfs24-navigraph-nav-jepp" active="Activated"/> Now give highest priority to this data: <Package name="communityfs24-navigraph-nav-base" active="Activated" priority="100"/> <Package name="communityfs24-navigraph-nav-jepp" active="Activated" priority="100"/> After I did this, all my SIDs and STARs started to load correct for both iniBuilds default Airbuses and ATR. Sorry, I don't know if it's possible to fix this if you are not using Navigraph.
  18. MikeMike joined the community
  19. Jack B joined the community
  20. Any acknoledgement from the Ini team please? Don't forget that a serious competitor is rising up.
  21. That’s great! For me it would be the air transit liveries and variations, KLM, American, Lufthansa, delta! Many thanks!
  22. Ok, it doesn't sound like an ILS/LOC button issue. Can you upload a screenshot of the instrument panel including the glaresheild? Do you use this aircraft with the GPS?
  23. UPDATE: Workaround: I restarted the simulator, powered up the aircraft (battery + ground power), waited for the GPS to boot up and the ENT button on the GPS worked as expected to get past the "OK?" prompt. Restarting the flight would be worth a shot if anyone else runs into this. Key here is to make sure the GPS is fully on before performing a bunch of other steps then realizing you can't interact with it. Will incorporate this in my startup procedure. Might be worth suggesting in the following topic https://forum.inibuilds.com/topic/35983-how-to-gps-navigation-ins-gps/
  24. TriStar version 1.0.4 MSFS Update 5 version 1.7.27.0 Mode: INS + GPS Is there any trick to getting past the "OK?" blinking prompt on the Garmin 530? I started by trying the ENT button then all other buttons on the unit (including the big push buttons). Tried with various power sources--ground, APU and all engines on. Plus, double checked that all bus ties were connected (w/ all engines running). Ensured the master radio buttons were turned on. Tried after INS was fully aligned and in NAV. And tried unmapping the Avionics Master key binding which was set.
  25. Xylem 33 replied to e4g231's topic in Support
    Hello, the new update 1.0.4 is still not available for the marketplace version. If you have the inibuilds PC Version...you should have the newest Version.
  26. I just hope they complete the rest of the Airbus fleet, they are doing an awesome job at trying to give us almost all the airbus’s :)
  27. frank_m replied to Aya's topic in Systems
    For me it works perfect in SU5. Have you analysed the CTD in the Windows logs?
  28. Have reinstalled the plane twice now, and every time the aircraft gets stuck in a holding pattern, the aircraft autopilot lights light up, but it will not follow any route in GPS or INS or heading I have checked my controllers plane is not currently usable in this state.
  29. Me too. The a320ceo-321 would be really great for Console
  30. Hi, just to confirm that your Photogrammetry is on? Additionally the default EGGP isn't loaded under our scenery?
  31. No WASM on my end with 1.2.5, no CTDs or ghosts even on 17+h hauls. SU4 and SU5. But I noticed since 1.2.5 and SU5 dramatic stuttering and FPS drop mainly in VR. Anyone?
  32. In the latest version, climb thrust seems to be defaulting to CLB instead of AUTO-DERATE in the CLB perf page. Not sure if this is a known issue.
  33. Then these two standalone instruments are definitely not working either. The DME always shows 0000, and the HSI stops functioning once INS navigation ends. However, after activating the VOR, the HSI displays a straight line pointing toward the 254 heading. I’m really sorry, but uploading videos to YouTube isn’t possible from my current region.
  34. I'll have to double check this but it should be a file in the actual folder for the scenery, should be a .nool file if memory serves me correct. For Example as you reminded me I needed to remove the file/folder from my LSZH scenery since I use GSX. So in this folder as structure varies between developers, I found here in a subfolder of SimObjects and clicked the noolaero folder and deleted it outright.
  35. Hi! Here is a video what's happening: https://streamable.com/m384ty
  36. Hi, do you have a TCA throttle per chance?

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.