All Activity

i believe so. however after flying about 100 miles manually the GPS randomly came back 🤷‍♂️. so for now everything is good. coming in to land soon so we'll see what happens

Is this your first flight immediately after downloading and loading into the aircraft?

you solved it! i saw in the APU diagram that the vent was open and leaking air out but i had no clue how to close it. i must have hit that switch on the ground a while back but the cabin altitude didn't become a problem till i was up at cruise because of the leak. thanks!

hadn't heard of that but just checked:

Hi, the issue is that your vent extraction is on manual override. This should be closed in flight, but the manual override opens it, which is why you cannot reduce your cabin altitude.

Do you have GPS Jamming enable in the EFB?

I will pass this along to the team, Thank you.

I’m currently North of Norway at FL330 when all of the sudden I lost all GPS navigation systems. Is this accurate, is there no GPS at all between Norway and Svalbard? (also I’m getting a constant audible message saying “pull up!” over and over that began when I lost GPS…related?)

Just got a big warning that the cabin altitude is too high. I'm at FL330 right now. I can't get the cabin V/S to go back down it won't go any lower than 200fpm even when on manual.

I was inspecting the APU and was excited to see pretty much the full internal model of the APU engine has been modeled. However I'm not sure if it's supposed to be more centered or if this is correct?

It's proprietary, ultimately the only options are Simbrief or Manual via MCDU, sorry for the initial confusion regarding the files and importing.

thanks. i found the directory but no flightplans folder. does this need to be created manually? in terms of format, I use LittleNavMap to create and save flight plans, which format does iniBuilds use so I know which one to save?

Hello, You can insert the files here, however it uses our own format so it's possible that it will not accept the usual .pln files. If you use simbrief, even the free version you can still generate flight plans and import them from there to the aircraft without having to save physical plans to your storage. \Microsoft Flight Simulator 2024\WASM\MSFS2024\inibuilds-aircraft-a340\work\flightplans

When playing via Steam, where on my harddrive should i place my .pln files so I can load the route in the A340 FMS? Thanks

hate to bump this again, but wondering if we could get an update on this?

I love the IniBuilds Airbus aircraft. A job well done by IniBuilds with the A330 for Asobo. Also the A340 a very nice aircraft, but….. The A330 is not compatible with the WinCNTRL MCDU. The A340 has no separate screen pop outs. I just don’t understand why the developers make these std features unworkable in MSFS for little performance gain. The future in general flight sim is in hardware and more screens since they have become more affordable and available. @IniBuilds developers: Please stop fooling around with the features your customers need! You filled an (Airbus) gap but dug another whole full with frustration of your customers.

Thank you! And you’re seeing normal textures when testing on the in-house Xbox console? Hmmm I’m open to thoughts on what could be causing this then, suggestions welcome. Thanks again!

Hi Nick. Thanks for the report. We'll investigate this as it's not happening on our end.

Hello, I have encountered a weird navdata problem when flying A320 v2 to Cork (EICK) I was flying inibuilds/Asobo A320neo v2 and the ILS frequency in the FMS for runway 26 was 109.5, whereas it should be 109.9 I believe. In any case it did not work. As this happened immediatley after the navdata update, I first reported the issue to Navigraph, as I thought something was wrong with it. Their support investigated the issue, and came out with the following: Problem seems to be specific for A320neo v2, or at least on some other aircraft it does not occur, Problem only occurs if the handcraftdd EICK is on - if it is off, the ILS works, Problem occurs also on default navdata. They also noticed a strange behaviour of the FMGC, where the ILS frequencies are not displayed. Not sure if this is a scenery or aicraft issue. For details see: https://forum.navigraph.com/t/ils-freq-eick-26/22727/2

WASM Crash Report When the crash occurred, I was switching my approach into VHHH from RW25C to 07L on the flight plan page of the MFD. The exact moment I clicked the transition point "LIMES", the WASM crash occurred. Aircraft: A350-900 Simulator: FS2024 Navdata Method: NAVIGRAPH OFP: RJAAVHHH_PDF_1771894529.a10404a1.pdf WASM Error: WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 Specs: Ryzen 9 5900X, MSI RTX 4080, 64Gb DDR4 3600Mhz Autosave File: 1771907873.bin

If you've also got the message that says: vhf1 reception not selected Then right click the VHF1 knob to pull it then turn it up to receive ATC audio

When the plane touches the ground, the chicks and GPU appears… it disappears a few seconds later. Chocks and GPU off in the EFB doesn’t affect the landing at all, but I don’t think that was supposed to happen 😅

You can see here that the VNAV path calculation still needs work. The aircraft is predicting that it will not meet the AT 4000 constraint at CAMEL. However, the calculated descent path is just too shallow. The aircraft is only descending at 500 fpm and having to add thrust to maintain speed. Why not calculate a steeper path that can be done as an IDLE descent and therefore also meet the constraint at CAMEL? This is just one example of what is not an isolated incident. Of course there are plenty of other errors with VNAV and the aircraft's altitude and speed predictions which I have reported elsewhere and am looking forward to seeing some progress on.

Hi, attached some tail screenshots and a cockpit one. I apologize but a video was too big to be attached. I tried. Anyway, you can see the jagged edges visible only at night with logo light on. There are artifacts also above the cockpit with the torchlight on. I have to correct myself since on the A300 there is some minor problem of the same nature on the tail and the cockpit too. The A340 is perfect, no issues at all. I run MSFS24 in 4k with TAA and ULTRA settings, full screen. These kind of artifacts happen on the edges of the 3d model when under direct lighting, for example when using the torchlight in cockpit, and in AMD RX9000 video cards. New drivers helped to solve the issue on others planes but is still present on the A350 (and A300). Hope this help and thanks for your support. Cpt Dart

IT's ok. I solved my own problem. For those who are trying to do something similar with a Streamdeck+ or a 7-segment display. When you preselect a speed whilst in managed mode, the displayed value is L:INI_PRESELECT_DIAL not L:INI_AIRSPEED_DIAL. You can then monitor "L:FCU_SPD_TIMER" which will be a non-zero value all the time the preselect value is displayed before it defaults back to ---. Don't precisely know how inibuilds have done it themselves but this works for me.