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.

Systems

  1. Hello, Please find in this message my bug report with video evidence. Video: https://medal.tv/nl/games/microsoft-flight-simulator-2024/clips/lvqkZwrEJuQbgbhgD?invite=cr-MSxiWVcsMzA1Mzc3ODA2&v=210 How to recreate: A340 on ILS 25L in EDDF, initiate a Go-Around, then direct CHA (Charlie). WASM crashed completely, no response in MCDU, PFD and ND stuck. Autopilot kept the aircraft in a left bank while descending into the ground. Hope it helps. Kind regards, William Arnauts

  2. When setting a Preselect speed in the PERF CLB page, it seems to respect it (per the FMA) but as soon as you enter climb mode, it gets replaced/overridden by the Managed FMS speed.

  3. Started by Der Michel,

    Company MSG should only be displayed for anything inside AOC. ATC messages (like CPDLC) shouldn't trigger that Memo.

  4. Started by Hélène CIZERO,

    Hello, the aircraft doesn't respect the acceleration altitude when entered manually in the PERF / TAKEOFF page. It always accelerate at the same time as the thrust reduction. In the following case, it accelerated at 2000ft instead of 3500.

  5. Started by Der Michel,

    - EFOB and EXTRA for VERT REV of Destiantion are not matching FUEL PRED/INIT B during preflight - LSK2L has to show a magenta default small font 250/10000 for CLB and DES SPD LIM. You show it in the F-PN but have it not in the VERT REV page...that's not logical ! - LSK3L SPD CSTR brackets have to be large font - LSK2R is missing RTA>s

  6. Started by Hélène CIZERO,

    Hello, after a 10 hours flight, it is impossible to get 0 GS displayed on the NDs. There should be a residual 2-3 Kts because of the IRS drift. So I investigated further and checked the DATA / POSITION MONITOR page and it shows 0.1 NM error for the 3 IRSs which is also totaly impossible after 10 hours of flight. Could you add some drift to the IRSs to reflect more reality ? Below is a table of the acceptable drifts vs flight time.

  7. Started by Swisspilot1986,

    Users like Der Michel, Hélène or Dectenor2 (I forget other good ones) make a great job with reporting bugs. Let me please advise all users to precise on their reports if the bugs are also concerning other IniBuilds aircrafts. By this way we can expect that a dev will apply the same correction on the fleet.

  8. Started by Hélène CIZERO,

    Hello, did a FAOR -> FACT and return without powering down the aircraft. Everything fine during the first flight. However, during return flight preparation, the FMGS displayed a weird total FPL distance (screenshot attached). Distance went back ok during initial climbout.

  9. Started by Hélène CIZERO,

    Hello, please review the Flight Directors ground engagement logic. First, as I said in a previous post, they should be always ON when the FMGCs are powered up. Also, in normal "managed" conditions, before applying takeoff power, the FMA should display "CLB" blue instead of V/S 0 green. The FCU windows should all display "dashes". See FCOM 1.22.30 for more details. SIM : REALITY:

  10. Started by Hélène CIZERO,

    Hello, during a HOLD, pressing LSK 1R "IMMEDIATE EXIT" should turn the aircraft directly to the Holding Fix while remaining within the protected area. Instead of doing this, the aircraft continues the Hold normally and exits when reaching the fix. See the below screenshot taken after pressing IMMEDIATE EXIT. I draw in blue what the aircraft SHOULD do and draw on the ND, but instead it continued to fly the HOLD until the fix.

  11. When loading the aircraft, even without GSX and just using Instant Load, the aircraft does not import the correct planned ZFW. You can see the difference between PLAN and LIVE.

  12. There is a discrepancy between the target speeds on the F-PLN page and the PERF pages. For example here, The F-PLN page shows the descent and .76 and then 288 on conversion, whereas the DES page shows .79 and 289 on conversion.

  13. Started by philw06,

    Hello, there is no trans alt/std alert ?

  14. Started by dectenor2,

    The PRED TO values on the CLB PERF page is incorrect. As can be seen on the ND we are just under 40nm away from TOC (FL400), but the PRED TO FL400 on the CLB PERF page is showing 560nm, basically same distance as the entire route. And also the predicted UTC time, is the same as the destination. It seems to work for custom entered altitudes, but when left at the default FCU selected Altitude it is just showing the total remaining flight distance and time.

  15. Started by dectenor2,

    The constraint logic needs some work. Here you can see the aircraft is indicating it will be at FF24L at 2500ft. You can see in the second capture, that the constraint here is AT 2500. So it is incorrect that the aircraft should indicate this constraint will not be met.

  16. 1. Dashes have to be ALWAYS !!! white (large font) and the correct format is: ----.--/-----.-- 2. LSK6R: SEL has to be in small font 3. Line 5: OFF, ALIGN, NAV x.x has to be in small font 4. LSK3L label depends on availability of GPS

  17. Started by Der Michel,

    1. LSK3L remove the space behind ILS

  18. Started by Hélène CIZERO,

    Hello, I noticed the FDs are always OFF after powering the aircraft from a Cold and Dark state. According to the FCOM 1.22.30 it should not be the case.

  19. Hello, This happens after every pushback with GSX with the A340. Who can help me?

  20. Started by Der Michel,

    Hi, this will be the start of a series of topics regarding issues with the FMS pages. Still the work assumes that ini switched from P4 to P3 since update 1.02. Please change the menu layout. You already replaced ACARS with ATSU at LSK2L. But if ATSU is used it has to be at LSK6L. Also add LSK5L SAT for airplanes equipped with SAT.

  21. Started by Der Michel,

    I spawned at the Airport, imported the Simbrief and have this numbers. Why is the Live PLD and ZFW so high? I didn't start loading at all. I would expect a Live PLD of 0, a Live ZFW of 123000 and a Live TOW of 131000. Also, according FAQ the MACZFW and MACGW are the current ones...so the Live value? Maybe you can clarify that at the EFB. Because we need the planned ZFWCG for the FMS and have to wait until loading is done, before we can take this into the FMS. Also think about renaming from MACZFW to ZFWCG...So every user knows, that is the value for the FMS.

  22. Started by Der Michel,

    1. Just after INIT REQUEST, there is already Wind data uplinked into the WIND pages. That shouldn't happen. WIND has to be separately requested via the WIND page. 2. It has to be GRND, not GND 3. The layout of the uplinked CRZ wind page is somehow wrong regarding filled lines. 4. CRZ Wind page is missing scroll arrows lower right up/down 5. CRZ Wind shouldn't have HISTORY WIND 6. Uplinked WIND has to be shown in small font 7. DESCENT WIND: The ALT for the Alternate has to be small green font as it's based on FMS itself: "Flight at flight level 220, if the airway distance is less than 200 NM; otherwise, at flight level 310." 8. Filled WIN…

  23. Started by Hélène CIZERO,

    Hello, inserting a waypoint in the Active F-PLN in flight is immediately added instead of triggering the temporary F-PLN. Is it normal ?

  24. Started by Donald Douglas,

    Departing FWKI, I had an NADP2 scenario where I hard keyed THR RED at 1500 agl (5500 MSL in this case) and ACC at 3000' AGL (7000 MSL)-- however, upon reaching Thrust Reduction, the aircraft began to accelerate immediately.

  25. When I use CPDLC for clearance request in the ini A340, I can send the request,I see it in BATC, then see the response in BATC, but it never comes to the flight deck, so there's no way to respond or acknowledge it. This seems to work fine in the A350.

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.