All Activity

I don't believe so, it happens on most if not all flights I operate.

MORA.

I am experiencing a consistent issue in both the default Microsoft Flight Simulator A320neo and the FlyByWire A32NX. Whenever I set up a flight and select an RNAV (GNSS) approach in the MCDU, the aircraft still behaves as if an ILS approach is active. Problem description: In RAD NAV, an ILS frequency is always present, even on cold & dark start. If I try to delete or change this frequency, it either returns automatically or gives a format error. After loading a route and powering the aircraft, the ILS frequency is always auto-tuned regardless of airport or runway. Even at airports or runways without ILS, the system still shows or uses an ILS frequency from another airport or previous state. Flight behavior issue: When I select an RNAV approach in the MCDU, the Flight Mode Annunciator never shows FINAL APP. Instead, when pressing APPR, the aircraft always enters ILS logic: LOC (armed and captured) G/S (armed and captured) There is no indication of RNAV vertical guidance at any point. What I expected: For RNAV approaches, I expect FINAL APP mode instead of LOC/G/S. ILS frequencies should not affect RNAV approach logic. RAD NAV should not remain “locked” to an ILS frequency across flights. What I have already tested: Happens in both default A320neo and FlyByWire A32NX Happens on cold & dark starts Happens at multiple airports and different routes Happens even when selecting RNAV-only approaches Summary: It seems like the aircraft is permanently defaulting to ILS approach logic and auto-tuning ILS frequencies regardless of selected RNAV procedures. I am unsure whether this is: a nav data issue, a simulator assistance setting conflict, or an avionics state persistence bug. Any guidance or fix would be appreciated. Thank you.

I am experiencing a consistent issue in both the default Microsoft Flight Simulator A320neo and the FlyByWire A32NX. Whenever I set up a flight and select an RNAV (GNSS) approach in the MCDU, the aircraft still behaves as if an ILS approach is active. Problem description: In RAD NAV, an ILS frequency is always present, even on cold & dark start. If I try to delete or change this frequency, it either returns automatically or gives a format error. After loading a route and powering the aircraft, the ILS frequency is always auto-tuned regardless of airport or runway. Even at airports or runways without ILS, the system still shows or uses an ILS frequency from another airport or previous state. Flight behavior issue: When I select an RNAV approach in the MCDU, the Flight Mode Annunciator never shows FINAL APP. Instead, when pressing APPR, the aircraft always enters ILS logic: LOC (armed and captured) G/S (armed and captured) There is no indication of RNAV vertical guidance at any point. What I expected: For RNAV approaches, I expect FINAL APP mode instead of LOC/G/S. ILS frequencies should not affect RNAV approach logic. RAD NAV should not remain “locked” to an ILS frequency across flights. What I have already tested: Happens in both default A320neo and FlyByWire A32NX Happens on cold & dark starts Happens at multiple airports and different routes Happens even when selecting RNAV-only approaches Summary: It seems like the aircraft is permanently defaulting to ILS approach logic and auto-tuning ILS frequencies regardless of selected RNAV procedures. I am unsure whether this is: a nav data issue, a simulator assistance setting conflict, or an avionics state persistence bug. Any guidance or fix would be appreciated. Thank you.

Just got the F406, here is a list of bugs in MSFS 2020: Right emergency exit doesn't open (show open in EFB though) Only the right main door open, the left main have no option to open it Propellers axis are inverted (fixed in MSFS binding though, but still) In cold and dark bleed source select should be OFF not BOTH (PT-6s are never started with bleed open) Trim needed for takeoff (either empty or max gross) is WAY out AFT of the white range Trim effectiveness is very poor/slow, should be much more effective and precise Torque variation is almost non-existent when changing propeller pitch Torque variation is almost non-existent when opening/closing the inertial separators all 3 attitude indicators's blue and brown colors should be totally filled up with their respective colors, not 2/3 with the rest black The flaps indicator pointer should move at the same rate than the flaps speed, not at the same pace you move the flaps handle Hope you'll fix those quick...

I'll see where the team is with this issue.

Hi, You are on PC correct, if so you can just do an marketplace transfer by following this link: https://forms.inibuilds.com/order-transfer I will raise the issue of deprecation to the team. Thank you :)

I just bought this during the Sale for 10 dollars on the MSFS 2024 Marketplace. I should have realized something is wrong for the price. When I spawn in at KBUF I get pink missing texture tiles on trucks and baggage carts. After doing a little digging it appears the MSFS 2024 Marketpace version is Deprecated. It's version 1.0.3 and shows it was made for MSFS2020. I see that in the Inibuilds manager the newest version is 1.1.1. I don't want to buy this again. It should just work. Is there a way to fix the missing textures? Or is there a way to get a discount on the v 1.1.1 at Inibuilds. I assume inibuilds is making no plans to update the depricated version on the marketplace, so I just wasted 10 dollars. In that case, can you at least have it removed so no one buys a deprecated version. Regards, Andrew

Any update or is it another lost cause again ?

I have just purchased this in the sale on MSFS2024 Marketplace and have experienced the same problem, I have contacted the support team so I hope it can be fixed!

Hi, I just bought the IniBuilds YBBN airport and I really love it with all the detail that was added :) Only thing I noticed is that there are no tire skid marks anywhere on the runways. In the product gallery in the iniBuilds store there is one screenshot that shows skid marks on the touch down zone. This looks to me like the textures are created but simply missed to add into the download package. I would greatly appreciate if they could be added. Without it the runways look kind of bland in my opinion. I added a screenshot from MSFS24: Best Regards

Besides the built in planes of MSFS 2024 I did not found any of your Airliners able to be used in career mode. Why is that? I would like to buy more of your planes but as I am playing a lot of career mode your planes are no option for me. So my question is if it is planned to bring your planes in career mode in the future? Wll the upcomming A380 support career mode? Regards

To clarify: While other developers have provided versions of EDDF, a contemporary, high-fidelity project is still missing. The existing scenery often struggles with performance optimization and does not fully capture the complexity of the current infrastructure, including the nuances of the new Terminal 3. Standard sim updates are also not a replacement; they lack the immersion, interior detail, and ground handling precision that professional third-party developers deliver. A modern iniBuilds project would not just be 'another' version, but a necessary benchmark for performance and accuracy that currently is unavailable on both PC and console platforms.

And there is a handcrafted version of EDDF from one of the World- or City Updates. This should also be available on consoles.

Here you go. Thanks for passing this along.

Thank You!..Very much appreciate the reply. Looks like I am going to purchase it. It's on sale right now as well as the A340 which I am also interested in. Thanks again!

Given you mention just console there wouldn't be much point to just develop it soley for console users. I'm sure most of ini's scenery market is on PC, and PC users already have the solid Aerosoft Frankfurt.

These are not functional, given the expectation/norm is using the mouse.

Next update what is the chance of displaying the correct lead in lines for Gates 1 and 2 plus add a Jetway at Gate 2? Gate 1 is actually Gate 1L and 1R Gate 2 is actually Gate 2L and 2R. Utilizing Gate 2R would allow for a widebody aircraft at that position. Getting a Jetway to work at 2L and 2R might be tricky but not sure. Thank you, nwajlg

Hi, The Marketplace version of the Aircraft is the Premium Edition which is FS2024 Native with the additional features that come with 2024 as shown on the IniManager/Store Pages

Just want to know if the Market Place version of the same aircraft (A300/600) for MSFS2024 is and does it have the same features as the one on Inibuilds website/iniManager called Premium Edition for MSFS2024? I see no mention of it on the Market Place as being "Premium" Edition, the reason I am asking. Simple question I hope someone at Inibuilds can answer. Thanks in advance!

Thanks for the explanation. It seems to me that circumventing default PG terrain has quite a lot of drawbacks in the case of EGLC. I know default terrain wouldn't be perfect, but at least we'd have proper ground texture detail, grass and GSX compatibility. It somehow worked for the other EGLC sceneries, but those obviously have other issues so I'd still prefer ini if it weren't for the terrain. I'll keep the scenery on my shopping list for now and hope for future improvements.

Hello, As this is Double T's scenery you will have to reach out to them at this email here: Tienvip26842@gmail.com Additionally there is a fix here on FSTO that might work in changing the identifiers. https://flightsim.to/addon/106004/doublet-skbo-runway-fix-for-batc

The display map will show at position 0,0 until Alignment is completed , AND MSU Mode Select knob is set to NAV, AND Execution of TK CHG in AUTO or MNL mode from 00 to 01. All of these are necessary to initialize the system. You can then re-center the map to your actual position by clicking the aircraft icon. Because when you spawn on the runway, it automatically aligns the INS to your present position. The map in the center is an INS DISPLAY MAP, its driven by coordinates from INS1, 2 or 3 respectively. Its not a GPS map that is always aware of your position. So when you spawn at a gate, cold and dark, it places the purple dot at 0,0 as it has no known position until the alignment and initialization process is completed as per above.