All Activity

I found this in the Fenix discord ISSUE: Sounds in FS2024 misbehaving, especially after changing views or pausing FIX: Caused by outdated Chaseplane installation, switch to the latest ‘Preview’ branch for SU7 compatibility. I do use chaseplane. I wonder if @Opelix and @Aaron Anderson and @RYR73MAX8 all were using chaseplane too when they experienced this?

This is a known issue when downloading local packages through the marketplace. It happens that the download completes early, without downloading certain files, and displays Ready to install.

Dear iniBuilds Team, I am writing to express some concerns regarding the performance of the Airbus A321neo (A21N) on Xbox Series X in Microsoft Flight Simulator 2024. While the A320neo V2 and the A330-900 run flawlessly and feel incredibly stable on the Xbox platform, the A321neo currently suffers from two major issues that deeply impact the simulation experience: Payload and Fuel Sync Bug: When importing operational flight plans via SimBrief on the EFB, the values are correctly read by the system, but the actual fuel and weight are not applied to the aircraft, forcing Xbox users to rely on immersion-breaking manual workarounds via the MSFS weight menu. Flight Model & Over-sensitivity to Turbulence: The aircraft feels disproportionately nervous and unstable during manual flight. Even with low turbulence settings, it suffers from severe wing rocking and excessive sensitivity to wind/CFD forces compared to the other default Airbus aircraft in MSFS 2024. Since this aircraft is highly anticipated and loved by the community, could you please provide a valid, concrete update on whether a definitive fix is actively being worked on for the Xbox platform, and what the expected timeline for these core system updates might be? Thank you for your time and for your continuous hard work. Best regards, Francesco

And what about enabling customer-made liveries put in the community folder, for how long will that be blocked?

Hello ini team, I’m writing this ticket hoping to get some kind of new response from you guys, and not the usual “we don’t know”. I understand this has been asked a lot but please it’s serious. The amazing A350 loses 50% of its potential and beauty without the MANY and IMPORTANT (ESSENTIAL) liveries that are NOT present via marketplace. It is not acceptable that we still not have ITA, EDELWEISS, SWISS, some of the most amazing world special liveries, the new KLM PH-ZNA, and so on. Please add them with the V2 update and if you can reply to this ticket with some infos about it. Me, like many others, have not bought the aircraft due to the lack of liveries.

I noticed this too-could the signage please be updated to be more current as Spirit Airlines no longer exists in a DTW update?

I got it fixed after a reinstallation of the A380.

Hi Kyle, Following up with another critical update from my latest isolated testing today Sunday November 1st, 2026. To narrow down whether this is purely a network uplink/parsing bug or a deeper core FMGC issue, I tested both manual data entry and direct uplink interaction. Here are the exact behaviors: Manual Entry Blocked: I am completely unable to manually type or store departure, destination, or waypoints directly on the MCDU (INIT A / ROUTE pages). The scratchpad entry fails to parse into the system. Uplink Prompt Stuck: When attempting the SimBrief import, the AOC RTE UPLINK prompt appears at LSK 6L on the INIT A page (as shown in the attached MCDU photo), but selecting it fails to ingest the flight plan into the FMGC. Partial ACARS Functionality: The MCDU successfully receives and processes basic AOC messages (like loadsheet data), but any navigation data processing—whether uplinked or typed manually—remains completely frozen. Reinstallation: A second fresh uninstall and reinstall of the A340-300 in MSFS 2024 produced the exact same results. Since both manual scratchpad entry to the FMGC and local payload ingestion (.fpl/simbrief.json) are locked up—yet basic AOC message reception works—this strongly points to a WASM navigation database access crash or memory lockup in the A340's FMGC gauge initialization thread, rather than a network connection issue. Could the development team check: If the A340 FMGC WASM module is failing to bind to the active MSFS 2024 NAVDATA index or database handle? If there is a compiled WASM binary/cache location that requires manual deletion beyond standard simulator reinstallation? Standing by if they need my MSFS 2024 WASM debug logs or console output to analyze what happens when AOC RTE UPLINK is triggered. Thanks again for your help!

Hi, I made my first flights today and had a problem :on approaching, the speed request stay at 210. It should decrease to lading speed, but does not. Any solution? Thek's Yves from ELLX

RTO kicking in is very strange, since the Autobrakes functions from 72 kts on. Below that, there is no Autobrake working for RTO. At least this is like it should be. In my issues, the braking started always at about 45 kts and without doing anything, the bird started accelerating again at about 7 kts.

Any news regarding this? Hasn’t made it in all the updates so far.

I am not sure if this is related, but I noticed once in air turning my sim rate to x4 helped cool them, they seemed stuck at over 1000 before that (but it is also possible it just sped up the cooling). Brake fan was on and didn't seem to do much beforehand.

with my experience, uninstall the aircraft and then reinstall it

Can we have the FLS button back pls. There is no A350 without it.

After going thru the entire process of loading the SIMBRIEF flight plan into the FMC, as I push back, the entire plan vanishes. The fuel, passengers etc are all there but the route is GONE! I cannot load the route again as the REQUEST FOR FLIGHT PLAN is greyed out. I have looked for conflicts in my key bindings etc to no avail. The A350 is fine. Any help is appreciated

The inertia is in all directions.

This won’t really help if you don’t want to use a mouse, but you should get a mouse :) I’m on XBOX, and using a mouse really helps a ton. I still use the controller for controlling the aircraft, but it’s a lot easier to click buttons inside the cockpit, and also, mouses come with binded keys to push/pull buttons in MSFS2024. For example, right click is Push, clicking the scroll wheel is Pull for me.

I have the same issue in all a380, a350 and a340 too

please see the thread a couple down. Kyle confirmed that they are looking in to fixing the RTO behaviour. (I am seeing it too).

I also have just experienced this on the A380, it manifested in the exact same way as the A350 and deactivating the auto-brake during the takeoff roll brought performance back to normal again, just like in the 350

You know I like to have a theory on this thread lol But I have updated to V1.0.6. Last night I operated EGLL - WSSS. I did not use the OANS system and on take off I had no stutters. This morning I loaded into a EGLL - KSFO with BAv, did not use the OANS to taxi around and again no stutters 🤷‍♂️. I still Nvidia App installed. Anything in this do you guys think?

Here you have......no turbulence. 1.mp4

Ok, I just learned that my issue is Autobrake related. I also have this Speedbrake indication coming here and then. But there is no surface deployment, just an indicating issue see screenshot.

Hi, I saw the post about autobrake activating during takeoff in the 1.27 of your A350 (which I do not own). However, today I had the same issue with the a380. The autobrake cicked in in two seperate instances between V1 and VR. First time closer to V1 resulting in a rejected takeoff, second time closer to VR where I managed to takeoff but had brake temperatureg going through the roof. Please investigate this. Thanks.

It happens with the A380 too. Tried to take off in Narita to Tokyo, decel short after V1 for no apparent reason.