Yes, partly still not fixed. From what I can see is that runway designators have been adjusted so far. Also corresponding SIDs can be chosen. But STARs and Approaches for the two parallel runways 13/31 can still not be selected at all.
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:
Runway designation has been adjusted. Even after AIRAC Update Cycle 2501 from January 16, there is still no ILS for runways 13L/31R. SID and STARS are not available or incorrect. All landings are VFR only. AI ILS landings on runway 24 touch down well before the threshold and then roll through the âWahner Heideâ to the runway. Itâs not fun flying in Cologne right now. I hope for a quick adjustment.
1 Like
Can confirm that EDDK still has this issue, even the runway markings are out of date and still showing 32R for example.
1 Like
Is not AIRAC issue, is Scenery Side issue
A number of new Charter VIP 737max missions have just appeared for me in Career mode. All of these missions end at EDDK. The scenery for this airport is incorrect, and noting the date of the original post has been so for a very long time. The internal AIRAC cycle is correct, but the scenery is not. The flights direct me to RWY 32 or RWY 14, neither of which exist anymore. The only approaches available now are VFR even though the airport is fully equipped for instrument landing and IFR approaches. The mission I flew wouldnât complete because it didnât recognize that I arrived at the airport, several hours wasted. This seems like a joke played upon Career mode pilots based on the fact that this has been a long standing issue!
1 Like
SU3 live and this is STILL not fixed?
I suggest reporting it here. It will get much more traction.
Maybe, but this issue is known and reported for well over 2 years and nothing yet so Iâm not hopeful. Not sure why it takes this long to change a 14 to 13 and 32 to 31, I donât even care about the paint on the runway.
I thought I remembered seeing somewhere that this would be fixed in SU3 but it seems not.
It only has 22 votes so that may be a problem. Itâs not getting noticed.
Take a look here. Airports I reported in that thread have been addressed.
This exact issue is already logged in that topic you sent me though.
1 Like
Oh my apologies!
No problem, thanks for chipping in with a suggestion. Somehow BATC now canât fly from EDDK due to this issue, itâs getting worse lol.
1 Like
it is nice that the standard EDDK is now fixed but not the inibuilds/CityUpdate Cologne versionâŠ. there are still the old designator 14/32. so still incompatible with BATC
1 Like
Yep it is so sad as this makes many handcrafted airports around the world unflyable for IFR (for example LSZG is also affected eventhough there it wasnt even a magvar adjustment, the ingame runways were just renamed one day for no reason).
If it was just visual it would not be a dealbraker, but as it effects availability of Navdata, it is a huge deal.
SU4 beta dropped, no mention of EDDK. Theyâre never going to fix it are they?
Will this ever be addressed? This is such an easy fix.
1 Like
Issue has been reported in the main FS2024 thread: MSFS 2024 Airport / Helipad Issue Tracker
For clarity:
There are (at least) 3 different versions of EDDK. Aerosoft, Inibuilds sim version as delivered in world update something or other and the original in-sim version. The runway designations are correct for Aerosoft and the base sim version but not the WU inibuilds version.
Ergo - if you disable the WU version you can get correct runway assignments, but you lose the best rendition of the airport (i.e. Moxy hotel etc)