All Activity

Great news! This most likely means there is a corrupt or outdated folder in your community folder causing issues. Best practice, start adding 1 by 1 until you find the culprit. Thanks!

Hello Kyle, I followed your suggestion regarding the Community Folder. For now, the problem seems to fixed. Engines are starting as expected. Tomorrow I am going to conduct some more tests. Thanks. Forgot to mention: MSFS 2020, A350_900 , rel. 1.2.7 with default livery

Sorry, meant to ask you to attach a screenshot or two for me please!

Is more info needed here? It's a rather disconcerting bug 😂

Here's what the FCOM says about it.

Thanks for your report. I'll try and replicate this on my end. Appreciate your patience 🙂

I have also experienced this, OPT FL changing suddenly when I update something. I'm pretty sure they're supposed to be continuously recomputed but I suspect they aren't. Just a guess though.

I have iniBuilds EGLL, and I get no NAVAID warnings when selecting EGLL ILS approaches:

Although I can't promise any timelines, v1.0.6 will be the next update to the A380 on X-Box! The A350 hotfix should also fall in line soon! Thanks

Trust me, mate. This is blow my mind😓 I found out quite different how an aircraft handle this type of approach, see the differences: How TFDi MD11 handle this type of Approach => How JustFLight Fokker 100 handle the approach => It is identical on how IniBuilds depict the Approach. But quite different with how Boeing depict the Approach, see: BlueBird Boeing 757 => And how PMDG do that Approach => I don't know how in the real life handling this Approaches. But for me, as for now, I agree with how IniBuilds represent the LFMN RNP-A 04L/R. This is quite mind blowing for me.....

Thanks for looking into this and passing it along to the dev team, Kyle! Just to add a bit more context on why it seems isolated to the A340-300's local file ingestion: all of my other complex add-ons import SimBrief plans without a single issue on my setup. This includes your own iniBuilds A350, as well as the Fenix Airbuses (A319/20/21), PMDG (B777 & B737-700), iFly B737-8MAX, FlightSim Studio E-Jets 170/175, Just Flight BAe 146, and the ToLiss A340-600 Pro, to name a few of the ones i own. Since all of those (and the A350) ingest SimBrief data without hitch, hopefully the dev team can narrow down where the A340's FMGC gauge is getting hung up when trying to read that .fpl payload out of the WASM work/ folder. Really appreciate you following up with them today—standing by if they need any logs or further testing on my end!

Regarding Navaids, I encountered the issue at EGLL (3rd party). As for ILS, it occurred at LSZH (default) with the A350 and at LEMD (default) with the A380. I hope this is clear; the text has been translated from French.

Which ones? I can check too

Hi! I’ve also encountered this issue with Navaids at several airports—both third-party and default—and I’m wondering if it might be related to another problem I’m having with ILS capture… I consistently end up too high or too low during the approach (both with the A350 and the A380). Could this simply be an issue with the AIRAC version? Thanks.

Good evening, Inibuilds! I have a question regarding the 380 and 350 on Xbox. Can Xbox users expect update 1.0.5 for the Airbus A380 and update 1.2.7 with HotFix for the A350? Xbox users will be glad to see the update. Thanks!

Hi! It's a 3rd party airport. I also tried with that scenery disabled, and get the same thing. Same for ILS approached at all four runways at that airport btw.

is EDDL 3rd party or default scenery? From my understanding the R1/R2 navdata updates are only for the base airac, aircraft do not need to be updated! Thanks 🙂

Hi! When I try to select EDDL ILS24L I get NAVAID NOT IN DATABASE In the OIS, I note that the navigraph data is outdated: 2610 rev 1 is outdated; rev 2 was released about 2 weeks ago (https://forum.navigraph.com/t/release-notes-msfs2024-airac-cycle/18116) How do I get r2 into my plane? Pressing Update data does nothing, it's still r1 even after restarting the sim. (I get the same error with EDDL ILS23L on "sim default" data btw) I don't know if it's needed, but I have also installed the navigraph data in my community folder

Thanks for the clarification. Will forward this to the team for further review! Appreciate your time 🙂

Hi, thanks for looking at this. If you look at the ND, the waypoint I just overflew, DL426, also has 220 kts in magenta. That means the aircraft should have slowed well before passing DL426. The FMS PERF page on the MCDU (left) also says, if I am interpreting it correctly, that it's in managed speed mode with a 220 kt constraint. Also, while I can't 100% swear it now, I am pretty sure previous waypoints also had this restriction. The main point is this: There is a general issue with updating the flightplan with new runways/approaches/arrivals where the aircraft will plot crazy courses, fly off course, ignore vertical profiles and restrictions. I think anyone who flies this aircraft regularly enough would attest to that. It has happened to me at least 10 times.

Thank you again Mario! Will forward this to the team for review. Appreciate your patience 🙂

Thanks for the clarification Mario! The team is actively investigating the fuel burn 🙂

When in an exterior view, there is no first Officer, but a captain visible.

Hi Kyle, Thanks again for your quick answer, here is the link with access, sorry about that. https://drive.google.com/file/d/1jenJmgLh4BTAEBAZsV2tqSW9Aj649vMU/view?usp=sharing Kind regards, Mario Tena.

Hi Kyle, Thank you for your quick answer, it's indeed a solution, however is company policy to arrive at the destination with 9.0T or more and I also didn't have this issue in the previous versions. Hope the fuel burn calculations are resolved. Kind regards, Mario Tena.