Inibuilds A330-200/300 RR error in arrivals

ISSUE DESCRIPTION

Description of the issue:

I have had errors with STARs in both the 330-200 RR and 330-300 RR. There is at least one waypoint thats several hundred miles away from the selected STAR in the MCDU.
The 330-300 GE worked fine.

This happened on a flight to ZBAA in the -200 and on a flight to VHHH in the -300 RR

If applicable, which aircraft is experiencing this issue: Default a330-200 RR and a330-300RR

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue? No. Too much hassle to remove everything.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

One time on each aircraft. Haven`t tried more times

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Select the a330-300 RR
  2. Start at ZSAM with a flight to VHHH
  3. Select the ABEY4A arrival with the ILS 07C approach, LIMES transition.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant: Not relevant.

[PC Only] Are you using Developer Mode or have you made any changes to it? No.

[PC, MSFS 2020 Only] Are you using DX11 or DX12?

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Rename your community folder to Community.bak. Once you start MSFS 2024 a new Community folder will be generated with nothing in it. After you’re all done testing simply delete the Community folder and rename Community.bak to Community.

Do you have the same issue if you follow the OP’s steps to reproduce it?
• Yes, but also at random other airports/STARS.

Provide extra information to complete the original description of the issue:
• Occurs for me in all default Airbus aircraft in FS2024. For example, the JIIMS4 arrival to KPHL. While the waypoints are correct, the distance between some of the waypoints is over 4,600 miles long. Was using 3rd party scenery for KPHL, but it occurs even with the scenery deactivated. Occurs at random airports, while others are fine. Only affects the FMGC in the default Airbus aircraft. Garmin GPS systems are fine.

If relevant, provide additional screenshots/video:

Has anything been done about this? This happens to me in both Live and SU3 Beta in all Inibuild Aircraft (A333, A321N, A320N) using default AIRAC. This doesn’t happen with any payware aircraft utilising both default AIRAC and Navigraph data. Thanks.

there have been pretty much no fixes to any of the default airbus planes since release of the sim, this bug plus the one where certain ILS approaches lead to a wasm crash are still not fixed despite existing since the release of the simulator almost a year ago.

Happened to me as well, but different airport. The ILS would never be set properly when flying inibuilds’ A330s. Hope this was fixed in the latest update, if it hasn’t it would be very bad to lose progress after an almost 9 hour flight.

Have you installed WFSS ZBAA and/or VHHH addons? I have heard WFSS addons may have a chance to destroy native navdata of the game and you may need to reinstall FS24 without WFSS addons installed.