All Activity

This seems to be an issue in the newest Su4 beta build. If you restart the flight it should correct itself.

I have the same issue, anyone from ini can take a look at this?

Hi all, are you all running in Su4? If so, keep in mind that it is a beta version of the simulator and new builds are being pushed quite frequently. As such, we cannot test and guarantee stability in all situations as there are multiple updates a week oftentimes. If you are unable to fly the aircraft, I would recommend returning to Su3 in the meantime until Su4 is finalized.

Hi all, are you using the Su4 beta? if so, let us know if you experience the same issues in Su3 so we can determine if it's the aircraft or an issue in the newest beta build. Keep in mind that running a beta version of the sim will always possibly introduce stability issues, especially as there are builds being pushed sometimes multiple times a week we cannot validate or test the aircraft on every version before the release version is finalized 🙂

Got the same to. Orange screens all the time when loading a flight. New beta build for me to. A340 is not flyable at all.

Hey! I've noticed there's no "parking brake" message on the ECAM page as I know it from the A320. Is that real? Or is this a bug? I was a bit surprised that there was no topic about this so far. Regards, Dominik

I slowly get the feeling that the Honeycomb throttles have problems with ALL aircraft and there's always anything that doesn't work as it should. For example: My HC Bravo throttle only works properly in most aircraft when the "throttle 0-100%" axis is selected. Most addon designers tell you exactly NOT to do that. The "normal" throttle axis within the MSFS menu either gives me half of the throttle range only (physical 0% starts at 50% in the sim, lower isn't possible), in the sim the throttles only start moving when the physical throttles are at 50% or higher (so: 50% physical for 100% in the sim). FSUIPC either either gives me the same results or full range, but inverted (the FSUIPC setting where you cannot set inverted). The only way for some aircraft (including the A340) for me is to set "throttle 0-100%" in the MSFS menu and then adjust in the individual calibrating system in the addon aircraft, if available. Never had such problems with earlier throttles.

I was just wondering where the liveries are for the console version of A300 for msfs 2024.

The original version of this aircraft, for me and my system, was the original version! I was flying all over the world. Then, iniBuilds issued two updates, and the issues presented in this thread started happening to me. How do I downgrade?

had the issue again yesterday on v1.0.2 I'm still running SU3.

Howdy iniBuilds. When do you see the freezing issue with WNWING MCDU being addressed and resolved? WINWING has issued two updates. Ini has acknowledged that the ball is now in their court and a software change is needed for the 340 to be fully functional with the WINWING MCDU ( and FCU/EFIS). Having expensive hardware designed for use with specific aircraft is wonderful but when that is not possible due to issues with that specific aircraft the magic is gone and the specific aircraft goes into the hanger. Can ini please provide a timeline for resolution? Please and Thank You -A

please if i bought this i can find air algerie livery want play my country company AIR ALGERIE thx to reply

I encountered GPS jamming inflight and followed the ECAM procedure which essentially tells me to turn off the GPWS. I did that but the ECAM procedure did not go away once the button was pushed. Also it says TCAS Fault, which means it doesn't work anymore. Shouldn't I not see any traffic on the ND anymore if that is the case? The screenshot I took was made after I pressed the GPWS Sys button. Also on a side note, I have to manually reselect my GPS Jamming option in the EFB every time I load a new flight. The option is not saved.

Good evening everyone, I've been having this problem for a while now. I updated the 350 with the latest update, deleted the WASM folder, but the problem persists. I also uninstalled and reinstalled the 350, but nothing... I still have this problem with OANS. I have Navigraph active (paid), I also linked the aircraft to Navigraph, and I have the AIRACs updated. But the problem persists. How can I fix it? Sometimes, on the Options page in the 3rd Party section, when I start the aircraft in Cold and Dark, I have to relink Navigraph. Can you help me solve this OANS problem?

So here we go: as I told you before the vertical profile shows a ground color (now it was red/brown earth, not blue water). As further the ND map doesn't show any water areas in blue. I made some marks in the screens.

Hi @sgb478 That is very odd and not normal. Not seeing any widespread reports of any of the listed issues, nor have we seen that in our own testing. Additionally, there are no drastic changes implemented in the updates that would cause such a vastly different experience compared to release either. So something else has to be amiss here. CTDs are very likely related to unstable GPU driver or corrupted shader caches if you're receiving DXGI_Hung errors shown above. For everything else it could be a result of bad update or cached files. Not all driver versions are created equally, and not all of them work stably across the spectrum of GPUs. Try the latest first, but it may not always be the best so try to google for last known "stable" version for your particular GPU. Can you also please try the following Close the sim and manually delete the A340 (fs24-inibuilds-aircraft-a340) from your Streamed Packages folder. When you relaunch the sim next, it will initiate a fresh download/streaming of the package. The paths will be as follows: Steam: %APPDATA%\Microsoft Flight Simulator 2024\StreamedPackages\fs24-inibuilds-aircraft-a340 MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\StreamedPackages\fs24-inibuilds-aircraft-a340 Set Turbulence to LOW via Settings > Assistances menu. This is to avoid AP Disconnection due to exaggerated turbulence effect on CFD aircraft like the A340. Ensure control profiles have not reset during any sim update, and the correct ones are still applied to the A340. Increase your Rolling Cache size to atleast 2x your installed physical RAM (i.e. 32GB Rolling cache if you have 16GB RAM). This will flush the cache initially to rid of any out of date data, and also help ensure a smoother experience when dealing with streamed packages. Try conducting ILS approaches at different airports to rule out any airport specific issues. Again, there have been no changes implemented amongst the updates that would have any bearing on this part of the simulation, so it doesn't make much sense for it to stop working after an update due to anything in the update itself. If you still are having issues, please post a video along with detailed reproduction steps (airport, approach, variant, navdata method used, sceneries used) that would allow further investigation. Thanks!

Hi richboy2307! Thank you so much for the explanation. In my particular case, I had issues mirroring ChristerH's that began after the updates. I bought the A340-300 that day it became available, and I actually downloaded it instead of streaming it. I was enjoying the A340-300 tremendously. Whether I was flying from KMDT to KCLT or KLAX to LIRF, the flights were unmatched. Then, I upgraded to version 2 and have had issues since - autopilot not engaging, nose-dive crashes in rare instances where the autopilot did engage; CTDs mid-flight, autoland ignoring the ILS signal. I wish I would get back to the original version.

I'm wondering if it's possible to downgrade from the A340-300 v2 to the first version? In the first version, I was happily flying all over the world - to any airport and from any airport. Plus, I experienced no CTDs. I was enjoying the flights. As soon as the Streamed Edition went to v2, however, I can no longer fly the 340. MSFS 2024 crashes to the desktop shortly after completing the cold and dark process, shortly after takeoff, during climbs, and during the approaches. Plus, the FD disengages every time I engage the autopilot, if the autopilot even engages. Finally, v2 no longer autolands, because it isn't picking up the ILS signal. I had none of these issues with the original version. To get MSFS 2024 functional again on my system, I installed a new SSD, reinstalled Windows 11 Home, reinstalled MSFS 2024, and I disabled the A340-300. Now I'm happily flying all over the world again. If I may ask, what changed so dramatically in v2? Thank you.

I've noticed that the cockpit sun visors do not appear to be functional. With the sun positioned directly ahead (at 12 o'clock), there is no noticeable reduction in light or shading on the Captain's seat upon deployment. Is this a known issue with the aircraft model? Many thanks!

Good day! On my last flight with the great A340-300 i faced wet conditions in Montreal. The Runway was wet which increases my landing distance. So i selected wet runway in the efb for my calculation... and the landing distance was not as much as with a wet runway. Im pretty sure this is not how it would be in real life. I also added 2 Pictures showing what i mean. I already posted it in the discord but i didn't get an answer. I do care about the product getting better! Perhaps its a known issue but i would have not found a Topic about that.

Hi @Louis P Thanks, would you happen to know whom Wilson is trying to reach out to (Discord username) by any chance? If not, can you ask them to reach out to me (@richboy2307) on discord and I'll handle it from there. Thanks!

Please give us an option to disable the Table / Keyboard Extension. It comes out many times durring a flight, unwanted, because we click on it for camera movements.

video_2025-11-04_12-43-23.mp4

Good day! I would like to report on the animation of the tires of the landing gear struts of the aircraft that is not working (they simply do not rotate), only the discs are set in motion, and on the nose landing gear strut, the textures of the metal part of the landing gear itself change color. I also noticed that the windshield brushes do not clean the water.The aircraft is loaded and has been reinstalled several times. video_2025-11-04_12-43-30.mp4

I'm trying to install my purchased airbus products in my X-plane 12 folder. Ini Manager automatically finds the x-plane folder, but gives a warning that no simulator is detected, and I cant install the aircraft.