Francesco Genti

Hello! Thanks for the reply! Do you have any sort of idea of when things are likely to be solved, also considering the fact that the two beta patches released after SU5 have been absolutely terrible? It feels it’s something that should improve really really soon, because it’s affecting the whole sim, most of simmers and 3d part add ons. But things don’t look so promising right now.

Hello, I would like to ask whether iniBuilds is currently aware of the significant stability and performance issues that many Xbox Series X users have been experiencing since Sim Update 5. In my case, the impact has been particularly noticeable on iniBuilds aircraft, including the A320neo and A330 family. Since SU5, I have experienced: Increased stuttering, especially during approach, landing and taxi. Occasional black screens and display failures. Memory-related warnings after arrival. General performance degradation compared to previous simulator versions. Reduced confidence when operating longer flights due to concerns about stability. What makes the situation confusing is that some other complex aircraft appear to be less affected, which makes me wonder whether there are specific interactions between the simulator changes introduced in SU5 and the iniBuilds aircraft systems. My questions are: Is iniBuilds aware of these issues? Have you been in contact with Asobo regarding the problems introduced after SU5? Have any root causes already been identified? Are there any planned updates, workarounds, or optimizations currently being worked on? Do you believe the majority of these issues need to be resolved by Asobo, or is there anything that can be addressed from the aircraft side? I understand that some of these problems may originate from the simulator itself, but many Xbox users would appreciate any information regarding the current status of the investigation and any cooperation between iniBuilds and Asobo. Thank you for your time.

Hello Platform: Xbox Series X Aircraft: iniBuilds A330 variants Simulator: MSFS 2024 I’ve been trying to use the Aerotone add-on by SoFly, specifically the ATC Chatter feature. The strange thing is that ATC Chatter works correctly in other aircraft, including the iniBuilds A320neo and A321neo, but it does not work in any A330 variant I have tested. What makes me wonder if this might be related to the A330 itself is that the radio behaviour seems different from other aircraft. Things I have tested: Autoplay ON and OFF. COM frequencies changed manually. UNICOM 122.800. Multiple airports. Multiple flights. Offline mode. Multiplayer OFF. Traffic OFF. Simulator restarts. Aerotone profile resets. In the A330, whenever I try to use frequencies required by Aerotone, they often revert automatically to another frequency, and ATC Chatter never plays. The rest of Aerotone works normally (cockpit sounds, cabin ambience, pilots, etc.), and ATC Chatter works in other aircraft. Could there be an issue with the way COM radios or frequency handling are implemented in the A330 that prevents third-party audio systems from detecting the active frequency correctly? Has anyone else experienced similar behaviour with Aerotone or other radio-dependent add-ons on the A330? Any help would be appreciated.

Can we expect it to be solved anytime soon? It’s a major issue guys

Thanks! Also other simmers are facing the same issue: https://forums.flightsimulator.com/t/a321lr-fuel-load-in-efb-does-not-equal-fob/749981/8 ! Some had this problem even before SU5. I personally started encountering it after SU5, even on beta. A20N & A330 are fine.

Thanks!

Hi Ini team, I would like to report a bug affecting the iniBuilds A321neo on Xbox Series X after Sim Update 5, including the current SU5 beta/hotfix. When importing payload/fuel through the iniBuilds EFB using SimBrief data, the values appear correctly inside the MCDU: BLOCK fuel, FOB predictions, ZFW/ZFWCG, etc. However, the aircraft itself does not actually receive the fuel. On the ECAM FUEL page: all tanks remain at 0 FOB stays at 0 KG fuel flow remains at 0 fuel warnings appear as if the aircraft is empty At the same time, the MCDU clearly shows the imported fuel values and calculations correctly. Important details: this happens only with the iniBuilds A321neo the iniBuilds A320neo works correctly the iniBuilds A330 works correctly if fuel is set manually through the default MSFS tablet/interface, it applies correctly to the aircraft the issue seems specifically related to the EFB → SimBrief → aircraft fuel synchronization process after SU5 Platform: Xbox Series X Version: Sim Update 5 current SU5 beta/hotfix I attached screenshots showing: EFB payload/fuel correctly loaded MCDU fuel predictions correctly calculated ECAM fuel page still showing 0 fuel everywhere Thank you very much for your work and support.

Hi Ini team, I would like to report a bug affecting the A321neo on Xbox Series X after Sim Update 5, including the current SU5 beta/hotfix. When importing payload/fuel through the iniBuilds EFB using SimBrief data, the values appear correctly inside the MCDU: BLOCK fuel, FOB predictions, ZFW/ZFWCG, etc. However, the aircraft itself does not actually receive the fuel. On the ECAM FUEL page: all tanks remain at 0 FOB stays at 0 KG fuel flow remains at 0 fuel warnings appear as if the aircraft is empty At the same time, the MCDU clearly shows the imported fuel values and calculations correctly. Important details: this happens only with the iniBuilds A321neo the iniBuilds A320neo works correctly the iniBuilds A330 works correctly if fuel is set manually through the default MSFS tablet/interface, it applies correctly to the aircraft the issue seems specifically related to the EFB → SimBrief → aircraft fuel synchronization process after SU5 Platform: Xbox Series X Version: Sim Update 5 current SU5 beta/hotfix I attached screenshots showing: EFB payload/fuel correctly loaded MCDU fuel predictions correctly calculated ECAM fuel page still showing 0 fuel everywhere Thank you very much for your work and support.

Then it’s really so weird. I’m absolutely not on vatsim and I experience exactly the same issue is described on the pics I attached in the previous post. Could it be related to a bug inside the simulator itself, which affects inibuilds aircraft’s?! I really do not know how to solve this issue. On the 2020 version I had no problem with ini A320neo V2. On the 2024 with both the A320neo and A21neo it’s all messed up when I have to use DIR TO and so on. Again, exactly what is described in the pics I sent previously. I’m really concerned because I love Airbus and I love ini aircraft’s.

Nope. It’s a known issue since the sim has been released…

Hello, I am flying on Xbox Series X using MSFS 2024 with the iniBuilds Airbus aircraft (A320neo / A321neo), and I would like to report a recurring audio issue. During flights, especially when switching between camera views (cockpit ↔ external), the sound can suddenly change or break: Cockpit engine sound becomes extremely quiet or almost disappears External engine sound volume drops significantly Sounds related to switches (e.g. seatbelt sign, cockpit interactions) are also affected It feels as if the overall audio mix is suddenly reduced or “muted” This issue can happen randomly and affects the whole aircraft audio environment until the flight is restarted. It seems to be triggered mainly by: switching camera views or general camera transitions during flight This makes the experience quite inconsistent and unrealistic, especially on longer flights. I would like to ask if this issue is already known and whether a fix is planned. Thank you for your support. Best regards, Francesco

Hello, I am flying on Xbox Series X using MSFS 2024 and the iniBuilds Airbus family (A320neo and A321neo), and I would like to report some major issues that are consistently affecting my flights. The main problems are: Using DIR TO often breaks the flight plan completely. The route may still appear correctly on the navigation display, but the aircraft no longer follows it. LNAV/NAV mode becomes unreliable after certain inputs. Even when NAV is shown as active, the aircraft does not properly follow the programmed route. After using HDG mode, switching back to NAV often does not work correctly. The aircraft may remain in a sort of “stuck” behavior despite indicating NAV on the PFD. Once these issues occur, the flight is usually no longer recoverable without rebuilding the route or restarting the flight. These problems are quite critical and seem to affect normal Airbus operations (especially DIR TO and mode management). I wanted to ask if these issues are already known and if a fix is planned in upcoming updates. Thank you for your work and support. Best regards, Francesco