I work at Kuwait. The ICAO identifier changed earlier this year. Because the CFIP file hasn't caught up yet the old designation of OKBK will have to be used here until it is changed to OKKK. There is no way to run duplicate 4 letter ICAO designators. Until the WED database is updated we are stuck with it.
Maybe Julian can give an idea of when the update might happen.
The ICAO ID has NOTHING to do with the CIFP data. You can simply change it in the meta data field and upload it with your submission, that will change the ICAO ID in Xplane.
Thanks Jan. That's interesting because other discussions in threads Ive seen (and been involved with) suggested that the ICAO 4 letter ident would have to remain as is until the databases were updated in either WED or XPLane (cant remember which)
Im just wondering then if I make the ICAO ID OKKK and its still only shows in XPlane as OKBK , what will happen??
Robert a quick clarification is that the Airport ID will remain as OKBK forever, but the metadata ICAO code can be changed. That means that besides being OKBK the Airport ID for gateway management purposes, you can still use the new ICAO. The challenge is that this require somebody to do the submission, so as you have, you can basically do it in the properties and change it, so for next update it can get to all the users. Attached the image from WED which I already changed in my local installation
The image is on the right, but in order to see it, you need to click on the broken image simbol (very strange at least in my computer).
Thank you for your comments and interaction
Thanks for the information. Not sure about OKBK staying forever. IN all the FMS databases it is OKKK as well as in the ICAO docs it is OKKK.
I am about to submit again so I'll change it to OKKK and see what happens. From memory last time I tried that it rejected when checking Meta data but you never know what can happen. Anythings possible!
Ive just changed the ICAO code to OKKK in the WED file and reloaded it in XP12. it seems to have picked it up OK because I have changed a few items on the taxiways and they appear to be there. We will see what happens when I submit. Fingers crossed.
I have just loaded my latest update in XP12 using OKKK. As the current XP12 still sees OKBK as well, the scenery titled OKKK does not overwrite it so we end up with duplicated everything. The ICAO designator will need to stay as OKBK until "whatever" in XP catches up.
In my case I did only change the ICAO Code, but maintained the OKBK as airport ID, and that did the trick. No duplication. Not sure if that is what you did as I least I did try to explain that is what need to be done.
Showing you the location with the attached screen shoot. I was searching for OKBK but shows the ICAO Code OKKK
Paulo
I am very well aware the new code is OKKK. I was working there last year when it changed.
However
Until XP12 catches up with the new code and the database changes (how long that will be is anyones guess) then it must stay at OKBK.
Sad but true!
The airportID of this airport will forever be OKBK. The ICAO ID is OKKK and that is already reflected in Scenery Pack 97995 which was released with 12.0.8.
It will stay this way, and it is fine - no point in waiting for anything. Laminar will never change the airport ID from OKBK to OKKK.
You must be logged in to participate in the discussion
There is no taxi flow from runways to ramp starts, as a result World Traffic 3 arriving aircraft get deleted before turning off from runways.
I guess there is no way to have multiple ICAOs for compatible purposes, so need to be validated what implications this may have.
Robert Grant May 15, 2023 6:29 AM
I work at Kuwait. The ICAO identifier changed earlier this year. Because the CFIP
Maybe Julian can give an idea of when the update might happen.
Jan Vogel May 15, 2023 8:27 AM
The ICAO ID has NOTHING to do with the CIFP data. You can simply change it in the meta data field and upload it with your submission, that will change the ICAO ID in Xplane.
Robert Grant May 15, 2023 12:09 PM
Thanks Jan. That's interesting because other discussions in threads Ive seen (and been involved with) suggested that the ICAO 4 letter ident would have to remain as is until the databases were updated in either WED or XPLane (cant remember which)
Im just wondering then if I make the ICAO ID OKKK and its still only shows in XPlane as OKBK , what will happen??
Marco Del Vecchio May 15, 2023 7:22 PM
Robert a quick clarification is that the Airport ID will remain as OKBK forever, but the metadata ICAO code can be changed. That means that besides being OKBK the Airport ID for gateway management purposes, you can still use the new ICAO. The challenge is that this require somebody to do the submission, so as you have, you can basically do it in the properties and change it, so for next update it can get to all the users. Attached the image from WED which I already changed in my local installation
Marco Del Vecchio May 15, 2023 7:24 PM
The image is on the right, but in order to see it, you need to click on the broken image simbol (very strange at least in my computer).
Thank you for your comments and interaction
Robert Grant May 16, 2023 12:08 AM
Thanks for the information. Not sure about OKBK staying forever. IN all the FMS databases it is OKKK as well as in the ICAO docs it is OKKK.
I am about to submit again so I'll change it to OKKK and see what happens. From memory last time I tried that it rejected when checking Meta data but you never know what can happen. Anythings possible!
Ive just changed the ICAO code to OKKK in the WED file and reloaded it in XP12. it seems to have picked it up OK because I have changed a few items on the taxiways and they appear to be there. We will see what happens when I submit. Fingers crossed.
Jan Vogel May 16, 2023 5:19 AM
I suggest reading here:
https://forums.x-plane.org/index.php?/forums/topic/288520-airport-code/#comment-2553555
Robert Grant May 20, 2023 5:14 PM
I have just loaded my latest update in XP12 using OKKK. As the current XP12 still sees OKBK as well, the scenery titled OKKK does not overwrite it so we end up with duplicated everything. The ICAO designator will need to stay as OKBK until "whatever" in XP catches up.
Marco Del Vecchio May 20, 2023 7:04 PM
Did you change the Airport ID then?
In my case I did only change the ICAO Code, but maintained the OKBK as airport ID, and that did the trick. No duplication. Not sure if that is what you did as I least I did try to explain that is what need to be done.
Showing you the location with the attached screen shoot. I was searching for OKBK but shows the ICAO Code OKKK
Marco Del Vecchio May 20, 2023 7:07 PM
Also did the same searching with Kuwait and with okkk, same result, only one airport.
Marco Del Vecchio May 20, 2023 7:08 PM
The other screenshoot
Robert Grant May 21, 2023 6:21 AM
Thanks Marco Ill give that a go.
The new Airport Code is OKKK. I already made the change, but I can't send it because the id is the old one
Robert Grant January 23, 2024 2:53 AM
Paulo
I am very well aware the new code is OKKK. I was working there last year when it changed.
However
Until XP12 catches up with the new code and the database changes (how long that will be is anyones guess) then it must stay at OKBK.
Sad but true!
Jan Vogel January 23, 2024 6:40 AM
Nothing will change, ever.
The airportID of this airport will forever be OKBK. The ICAO ID is OKKK and that is already reflected in Scenery Pack 97995 which was released with 12.0.8.
It will stay this way, and it is fine - no point in waiting for anything. Laminar will never change the airport ID from OKBK to OKKK.