No STARs at LEBL with AIRAC 2203

There are some problems with this last database, at least with the FBW a32X.
While the aerosoft FMC CRJ is able to correctly read the new LEBL runways with their corresponding SID/STAR, the FBW a32x DEV is not able to read the same data correctly.
It can read new runways in ARRIVAL but without STAR data, but in DEPARTURE it reads old runway numbering without SID.
At least in the tests I just did on MSFS2020.

Sorry about my poor english.
Juan.

2 Likes

Hi Juan,
no problem with your english - I´m also not a native speaker and mine is also not perfect :wink: … but I hope it´s enough to understand me …

This is “per design”, means … the scenery in the sim is outdated, the runway-idents are outdated/wrong. As you have possible read in the reference posting, the runways were changed from 07L/R and 25L/R to 06L/R and 24L/R at LEBL. The sim disable now all STARs which can´t be assigned to a runway.

Due the runway-ident change, all terminal procedures were also changed but not the MSFS scenery. In the MSFS you still have the old runway-idents and therefore the sim disable all new STARs and approaches (you see this because most of the approaches has no runway-ident).

The important thing here is now, this is not an issue on our side what we can fix. The same happened with the stock navdata also. Because with the WU8, they have also updated the AIRAC to 2203 and they have the same issue because the sim follows the same logic: No runway-ident found (difference between terminal procedures runway and scenery runway), no STAR, no approach available.

Sorry, please report this to ASOBO/MS that´s their part. We can´t do anything for that. We have reported this effect since day one, so over 2 years now … now, I guess, they will see the effect with their own data.

We have created a “known issue” list in Jan 2021, where we have exactly decribed this issue:

Cheers,
Richard

1 Like

Thank you very much Richard.
Yes, I have read other posts with similar problems.
It is curious the difference between the aerosoft CRJ, which is not affected while others cannot work as expected.
It will be a long way until ASOBO/MS and Latin VFR update runways.

Thanks again Richard.
Juan.

The reason, why this works in the CRJ is simple - the CRJ uses a own database and not the in-game data from the sim. So this addon works completely independent of any sim scenery, World-Update or similar else. Most of the new upcoming addons will do this because as you see, the dependencies are not so good …

We offer the new runways with all the new procedures and therefore you see it in the CRJ correctly, but we may not change the runway-idents in the MSFS stock-sceneries and therefore we have no chance for any workaround. Sorry.

Cheers,
Richard

1 Like

It´s clear that it is not navigraph fault.
Thanks for the clarifications.

Cheers.
Juan.

… but we also make mistakes, so it’s not always so clear - but thank´s for that :beers:

Cheers,
Richard

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.