EDDK RWY 31L an 31R not correct reflected in the acutal NAV Data Base 2404 and World Map

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

n

Have you disabled/removed all your mods and addons? 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 Community Support section.

y

Brief description of the issue:

EDDK RWY 32L an 32 R getting renamed during magnetic shift to 31L an 31R. All Aircraft with the default NAV Data Base still show 32L and R with no SID/ARR to select. All ACFT with Custom Nav Data like PMDG show the correct RWY number 31L an R

Provide Screenshot(s)/video(s) of the issue encountered:




ICAO or coordinates (DevMode > Debug > Display position)

Detailed steps to reproduce the issue encountered:

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

after fs_base_nav update from 18 april 2024


: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:

imagine you should fly the CTP 2024 from EDDK this saturday… ^^

MS/Inibuilds and Aerosoft will have to update their sceneries.
The issue affects basically all aircraft except Fenix/PMDG which have their own navdata which is consistent.
With the FBW you select the runways (can only select the old names) and it doesn’t offer you any SIDs or STARs.

correct all aircraft using default navdata are affectec. all with seperate navdate like pmdg maddog fenix etc working fine.

It would be nice if asobo could rename the runways for their default and inibuilds asobo scenery, repainting can be done later.

I have still done this via the WorldHub today, but the updated airport will distributed with one of the next updates and not immediately.

Here the approval, that this change was accepted and ready for the release with one of the next update:

So at least in the near future, you should have the correct runway-idents for EDDK in the stock scenery too - what means, you can select all terminal procedures than.

Cheers,
Richard

3 Likes

Thx, will it work for the asobo / inibuilds scenery aswell which was a gift from microsoft?

Nope, neither will it fix the issue of Aerosoft scenery.

Aerosoft already confirmed in their forum they are working on an update

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

no

Have you disabled/removed all your mods and addons?

no

Brief description of the issue:

EDDK got a runway number change with AIRAC2404 from 32/14 to 31/13
This isn’t updated in default EDDK and causes issues.

Provide Screenshot(s)/video(s) of the issue encountered:

ICAO or coordinates (DevMode > Debug > Display position)

EDDK

Detailed steps to reproduce the issue encountered:

Check Airac updates

PC specs and/or peripheral set up if relevant:

Are you using DX11 or DX12?

Are you using DLSS?


: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:

Aerosoft’s EDDK update is coming in the next hours.

Nope, no update still. Aerosoft’s last official word on their forums on Friday was that they are working on the update but have no release date for it.

There’s a community workaround that was included in the CTP briefing for EDDK, but it’s just a workaround to have the runways (additionally) in the FMS.
It can be found in the vatget KB (link is in the red box):

Dear Asobo Team!

Let me tell you about runway designators:

Runway designators are extremely important especially for the landing and taking off of aircraft. They may undergo minor changes over time. That is because shifts occur in the magnetic poles of the world at distances of up to 60-70 kilometers per year. Which means, that the magnetic heading of the runway changes as well. You know, that is the thingy the compass shows and depends on where you are on this planet.

So it happens that airports may have to change these runway designators from time to time - and all procedures and approaches with them. I trust you are familiar with procedures and approaches.

Anyway, EDDK stands for the Cologne-Bonn airport, a not-so-small hub in Germany. You surely know where that is. They had to change the designators for their main runways a couple weeks ago.

And many in the German online flying community (we simulate real air traffic there, you know) were hoping that you would fix that soon. Primarily those who use aircraft which are based on the navigational data of the simulator. Which in turn means that all current nav data for EDDK are unusable with these aircraft at the moment.

Well, you missed it. SU15 came, with lots of content updates, and nothing changed. Would have been a good opportunity, wouldn’t it? But then again, it may be that you are making a game and not a simulator.

In this case, at least, give us access to these data and let us do it ourselves. As we did in other simulators before this one.

3 Likes

I had heard that runway designators could be fixed via the World Hub? Perhaps it can be tagged by staff as such and a community member will be able to fix it for a future World Hub update.

the world hub entry for this got approved 3 days after the release of the current airac cycle, which also updated world hub data.

I guess we will have wrong runways until the next airac cycle mid june, assuming it comes with a world hub update.

World Hub Airports & Navdata Update (Cycle: 2405) - May 16th, 2024 - Official Microsoft Flight Simulator / News & Announcements - Microsoft Flight Simulator Forums

@NAVData

Would it be possible to change the runways in the Inibuilds Asobo Scenery? When controlling on vatsim and pilots have those scenery and the standard navdata they do not have runway 31r/l 13l/r. Its not so important if the visual signs in the scenery are wrong. alternatively just add those runways in the scenery database to the old ones 32r/l 14l 14r, that would help us quite a lot.

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

no

Have you disabled/removed all your mods and addons? 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.

no

Brief description of the issue:

with AIRAC 2405 EDDK changed the runway desgniations from 14L/R to 13L/R and 32L/R to 31L/R. This change did not happen to the scenery airport. this mismatch make it impossible to choose SIDs/STARs for this runways and 13L/31R is the mainly used runway at EDDK

Provide Screenshot(s)/video(s) of the issue encountered:

no

ICAO or coordinates (DevMode > Debug > Display position)

EDDK

Detailed steps to reproduce the issue encountered:

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

after AIRAC2405 update


: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: