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. Donia joined the community
  3. jeanpy33 joined the community
  4. Today
  5. doriano joined the community
  6. batmandd joined the community
  7. Schoffler822 joined the community
  8. NH321 joined the community
  9. Yeah, that’s what I do too, but it’s nicer to use the physical keyboard like we can do with the MFD… Especially when the EFB itself says there shouldn’t normally be any conflict...
  10. hi again found the problem ! it s a small scenery near KLAX thats causing interference. have nice flights
  11. Yeah have noticed this. I just use the onscreen keyboard on the OIS that you can pop up to avoid any conflicts.
  12. souma joined the community
  13. Jungwoo430731 joined the community
  14. Hello! I recently purchased the A350 and honestly, I’m really happy with it so far! The aircraft is absolutely beautiful and has always been a dream aircraft for me, so I can already tell I’m going to have a great time flying it. After a few hours of testing, everything seems to work perfectly from what I can see, except for the keyboard input on the OIS / EFB, which does not properly lock the keyboard inputs. For example, with some keys I can still move my joystick assignment or deploy the flaps while typing things into the OIS, even when the message “Aircraft control disabled when inputting text with physical keyboard” is displayed. I searched online and through the Discord, but from what I found it either seems to be a rare issue or people have the opposite problem of being stuck with the keyboard, or something that may have been fixed in previous updates? I already restarted the game after fully configuring the aircraft, but the issue is still there. I’d also prefer not to unbind some keyboard keys since I use them during flight... Thank you very much in advance for your help, and apologies if the solution is actually simple and I somehow missed it...
  15. FlyingMaximus joined the community
  16. I noticed that the fuel consumption seems to be very accelerated and inaccurate. Has there been a fix yet for this? Also i noticed that once i turn on one engine. It kind of automatically turns on the other engine. the heat blur turns on for the engine thats is not turned on at all. Not sure if its a visual glitch or it could be contributing to the fuel burn. I also noticed that it only acts this way on the a330 300 not 200
  17. As soon as you have activated 4x in the EFB, you can increase the sim rate further using the assigned keys for sim rate.
  18. pna joined the community
  19. ??? I aware of that.. but that's for auto tune in case of the VORs but when we manually tune?.. Mind you, the A300 auto tunes too. That's not what I'm asking... in case you don't read properly, or you're making your own suggestions out of others posts? I will write again, can we pilots hear the tones, NOT the avionics, US PILOTS, when pulling the corresponding knob on the ACP, which are there for that reason.. ?
  20. Hi, we did make changes to the runways for the FS2024 version of the scenery and were able to get FSLTL to use the full length of the runway. BATC seemed to be dependent on other factors, but beyond our ability to control. Best, Steven
  21. Hi, in the A340 and A350 there is no need under normal operation to listen to nav radio morse tones in order to identify them. They are automatically identified by the aircraft - when the LS or VOR identifier is shown on the screen, the navaid has been tuned and identified by the avionics.
  22. Hi Mikai, regarding the GPWS sounds, there are actually several different soundsets that are used depending on the airline and specific equipment installed. We have even heard a boeing style "TWENTY-FIVE hundred" call in some recordings. The current recording are the highest quality and cleanest samples we have from an actual aircraft, so for now they are what we will stick with. Best, Steven
  23. Yesterday
  24. I have the sound code open on my laptop right now, funny enough. I’m working on a mod to fix this.
  25. Any news on this? i miss the 108
  26. hi i have the same trouble with lax enhanced scenery.its impossible to take off or land. so much stutters. Among other runway 25 and taxiways too. i ve uninstall the scenery and clean the catch. but no result. no problem with others sceneries. Any help appreciate Thanks in advance Pierre
  27. 3 Minutes and 30 seconds THE 2000 .... 500
  28. Hello, first of all, I want to say that the new callouts are really well done overall. You can clearly tell that a lot of work and attention went into them, and most of the announcements already sound very close to the real-life versions. Big thanks to the ini team for that! However, I noticed that the “2500” callouts are still not fully accurate compared to the real ones. Right now, the ini version sounds more like a direct “2500”, while in reality it sounds more like a separated or stretched “2000…500”. That small pronunciation/detail is what makes the real callout sound more natural and authentic. Besides that, all the other calls already sound really good, which is why this one stands out a bit more. It would be great if you could take another look/listen specifically at the 2500 calls and adjust them a little closer to the real-life version. I attached an example in the topic so the difference is easier to notice. Still, huge compliments to the whole team — the overall work is really impressive! Best regards
  29. No airline pilot has ever had to remove these things on a walk round check. It's completely unrealistic. It annoys me every time I load the plane. Please make them optional and removable from the OIS. It's very annoying to get halfway through a cockpit setup then find you have to get out and click them in walkround view.
  30. I'll pass this along to the team.
  31. I usually just click somewhere in the MDCU after installing the update, usually a route page or ATC COM page, something that takes away from the INIT Page with the Data Cycle, and then I enter back into the INIT Page and the cycle is always updated. I've never had to reload the sim to refresh their navdata nor do I personally know anyone else that has yet to do so. I'll ask the team about keeping the prior data on-board and the feasibility of that as it could be helpful. Let me know if this helps
  32. kletten posted a topic in Systems
    Love flying the Beluga! However, when I enter an approach in the MCDU, it seems to pick up the wrong approach fixes in another continent and build 5000+ nm legs to get to those. So whenever I try to load an approach, the fmgc just computes insanely long legs that mess up my flight plan. Is anyone experiencing this problem? I have updated navigraph airacs.
  33. I asked this last year and still no response. I have 1.2.6 installed, have downloaded the latest AIRAC in the OIS but the FMGC still will not update in the sim. You have to reload. Why can't this be done in the Navigraph Hub, would be much easier?
  34. I'd like to ask how the 350 8x speed is achieved? The EFB only supports up to 4x speed, and the built-in game speed options don't apply to 350
  35. This means, your system is overwhelmed. If the system can't maintain a stable FPS with high sim rates, it is decreased. You have to reduce settings in order to use higher sim rates. I can use the A350 up to 4x all the time, and during cruise even up to 8x.
  36. The A340 and the A350 are completely useless.
  37. Had given the latest a340 update another chance and ended up with the same result.
  38. This is still a problem in the current version of the scenery and is especially noticeable when using BATC.

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.