All Activity

Hey guys, I am on the newest version on 2024 and got this weird glitch on the winglets?

I have the same problem, i don't recieve an ILS signal. I cleared the whole WASM folder. I reinstalled the A350. I updated the Navdata with Navigraph. I don't recieve any ILS data. The NAV-Page shows the ILS with correct FREQ and Identifier but the PFD does not recieve info and APPR1 (or else) will not capture any LOC or GS. (Only the ILS Freq is shown on the PFD, like if i don't recieve a signal). I am SU4 Beta.

1.1.7 MSFS 2024 SU4 Navigraph RX 7800 XT, I5-13600KF, 32GB RAM WASM: ERR_FATAL_FILE_ERROR (-239 / ffffff11) WASM: Error -239 / ffffff11 [fsdt-msfs-bridge.wasm] fsdt-msfs-bridge: Simconnect Dispatch proc set. [noolaero-vdgs-lsgg.wasm] Sim | EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-ksea.wasm] Sim | EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-lszh.wasm] Sim | EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-ksfo.wasm] [noolaero-vdgs-ksfo] EXCEPTION 25: The AI operation requested cannot be completed [noolaero-vdgs-bikf.wasm] [noolaero-vdgs-bikf] EXCEPTION 25: The AI operation requested cannot be completed [AirshowAssistant.wasm] AIRSHOW ASSISTANT: variable set success [inibuilds-A350.wasm] Error: Unable to open directory [inibuilds-A350.wasm] \work\autosaves\ [inibuilds-A350.wasm] WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty It happened when I was loading the departure in the FMC. OMAAKORD_PDF_1764146865.pdf

No they didn't....

The one inibuilds has modelled is the a340-313, should be correct although idk

Hi The Max fuel in A343 is low 113K Liter instead of around 140K+. It seems you use A333 tanks not A343. ISSUE 52-A340-300 SPECS.pdf

Not sure. I use the shoulder buttons for steering. Is it possible to steer it with the normal stick on the Controller? So i dont need to adjust the rudder. And how can i get the rudders back to neutral if they get stuck?

That is for sure a problem in your controller configuration. I use a dedicated axis on my controller for the tiller moving bach to neutral position automatically and have no issues. Maybe you assigned not the analogue axis but the button event of your axis?

I think its the monitor near the 1L entry in the cabin. There you can change the lighting.

Simbrief loading error - Instance was null... Well, we don't like seeing red messages in the aviation LoL.. Anyway, at least managed to get the Simbrief plan to start properly loading in the MCDU through the AOC menu and then in the INIT page (at first it was doing nothing). I noticed the Navigraph database was not updating, log out and log in again through the A340 tablet seems to have updated the database + fixed the issue with the MCDU. The "instance was null" error is still there though.

The copilot is not in the cockpit but here below

Hello! When the APU bleed is activated, the cabin doesn't heat up. It works correctly when the ACU or the engines are activated. As soon as the ACU or the engines are deactivated and the APU bleed is activated, the temperature drops again. Furthermore, the ACU heats the cabin unrealistically quickly. This has been reported several times, but unfortunately nothing has been done since April 2025. Please fix this! Thanks!

Yep.I just checked as well.No stairs show when toggled with V1.1.7..I still have a copy of V1.1.6 and that has stairs. Please look into this Inibuilds.

Same issue. Initially app didn't launch, which is a very common problem I have with inimanager. Was able to open a previous version but app was unresponsive, i.e. nothing was clickable. Deleted the cache folders in %AppData%\Roaming\iniManager. Couldn't find any cache folders in %AppData%\Local\iniManager. App then crashed when opened. Uninstalled app and deleted inimanager cache again. Re-installed app which then launched fine. Now I have the current problem that everyone above is having. A350 just goes into a que. Closed app, deleted cache folders again, tried downloading A350 again, same problem.

Hi everyone, I think it's easier to report and keep track of bugs here in the forum. Discord is just too chaotic. 1. minor bugs avionics compartment: 2. same sort of bugs in the Cockpit, when HUD is enabled (it's the same on the rights side, but not that bad as on the left side) The first picture is only related to the 1000 variant! The other pictures on all variants. I think there are much more! 3. the best at the last - THE HANGER! This is not important, but this is for me personally the symbol of whats going wrong. Lots of small bugs. A simple reply indicating whether or not the bugs will be fixed would be very helpful. Nothing more, just a clear statement. I will report the system bugs separately to the appropriate department. Thank you!

Now NO stairs at all....🤐 1.1.7

No stairs here.

Thaks for the feedback. I'll pass it on to the sound team.

I have the same issue on Xbox. I also had a wasm crash shortly after… first time I’ve seen the orange displays. Second flight I was in cruise and during time compression I had another wasm crash or at least I think did because sim was working, but could not operate anything to do with aircraft except the EFB. Although I could operate the EFB I’m not actually sure it did anything because I kept pressing disable on time compression and the window would close like it was working but it still still displayed the green banner saying time compression. There were also no orange displays. I’m using SU4 .29 build though.

I've noticed that the A340 flight deck seems pretty quiet with regards to these sounds, compared to the A330, for example. I can barely tell the A340 has power because the hum and ventilation sounds are very quiet.

Hi! I noticed there's several "clunks" heard from presumably the avionics bay of APU related contactors switching when doing an APU start on batteries, as noted in this video. I think it would be nice to add these! https://www.youtube.com/watch?v=5F1EKtDFjIE

Hello. Every time i try to fly the a350 i have issues with steering. When i use the Controller, i steer with the rudder via the shoulder Buttons. Unfortunately the rudder then stays in that Position and i have no possibility to move the rudder back to the neutral Position. The plane then is only driving in circles, and take off is impossible. In other aircraft, the rudder turns back to the neutral Position automatically. What can I do? The tiller option makes no difference Steven

starts on 3:37h Here, a real A340 pilot is simulating a bird strike. He discovered some abnormal bugs, so the ini340 need some bugs fixed. The autopilot is malfunctioning. CATIII Dual is inoperative but will show up on the monitor later e.t.c. After one engine failed, the aircraft continued to climb far too steeply. A fully loaded A340 typically climbs at around 400-500 ft/min, not 1000 ft/min or more after takeoff with all 4 engines and here he only had 3.

Hi Thomas. Understand the frustration but this doesn't seem to be a widespread issue. Can you share your autosave and OFP/Flightplan details so we can try and reproduce the crash internally? The changes made to the model to reduce node and bone counts were really necessary, and not just for those on low-end hardware but even for those on higher end hardware, especially Intel and non-x3d chips. As mentioned in our post these changes significantly reduced stutters when looking around the aircraft or changing views, which of course benefits all of us even on the highest end chips and also helps with stability as these stutters can affect that as well. Regarding the cabin packs, unfortunately these changes broke them completely, and they were already very difficult for us to maintain as any minor changes to the interior 3d models had to be repeated manually for every cabin pack across every variant. With this change, it was a bit of a final straw, and we've decided that the time and resources needed to maintain them is simply not sustainable for us as these efforts are better focused on the core aircraft as well as our other upcoming projects. Hope that helps clear up the factors that led to our decision and helps everyone understand it wasn't taken lightly. (for others following along, I deleted the other posts that were not relevant to OP's issue so we can all focus on helping him)