I submitted BIRF, so will update the package when the change takes effect. The change is not in this month's issue of the AIP, nor is it shown in the next issue (12 Oct 2017).
However ... I notice that there is a default CIFP: "Resources/default data/CIFP/BIRF.dat, which lists the available runways as 06/24 and 11/29. Since this is set in stone for the duration of XP10, perhaps we have to leave the runways IDs as is???? WEDbot is likely to insist.
Default data/CIFP is overriden by custom data/CIFP (that's where all AIRAC updates e. g. provided by Navigraph belong). If you leave the scenery as it is now users will simply at some time not be able to load any procedures for BIRF after updating to a newer AIRAC cycle. And I read XP 11.10 will introduce a certain possibility to keep the runway IDs in track with real life...
Default data/CIFP is overriden by custom data/CIFP (that's where all AIRAC updates e. g. provided by Navigraph belong). If you leave the scenery as it is now users will simply at some time not be able to load any procedures for BIRF after updating to a newer AIRAC cycle. And I read XP 11.10 will introduce a certain possibility to keep the runway IDs in track with real life...
The runway IDs changed from 06/24 to 05/23 (runway 11/29 is not affected).
Source: https://www.isavia.is/c/notam/c-notam-no-0045-17-birf-rwy-designators/58311
xris October 2, 2017 8:07 PM
I submitted BIRF, so will update the package when the change takes effect. The change is not in this month's issue of the AIP, nor is it shown in the next issue (12 Oct 2017).
xris October 3, 2017 12:03 AM
However ... I notice that there is a default CIFP: "Resources/default data/CIFP/BIRF.dat, which lists the available runways as 06/24 and 11/29. Since this is set in stone for the duration of XP10, perhaps we have to leave the runways IDs as is???? WEDbot is likely to insist.
An unknown user October 3, 2017 2:28 AM
Default data/CIFP is overriden by custom data/CIFP (that's where all AIRAC updates e. g. provided by Navigraph belong). If you leave the scenery as it is now users will simply at some time not be able to load any procedures for BIRF after updating to a newer AIRAC cycle. And I read XP 11.10 will introduce a certain possibility to keep the runway IDs in track with real life...
An unknown user October 3, 2017 2:28 AM
Default data/CIFP is overriden by custom data/CIFP (that's where all AIRAC updates e. g. provided by Navigraph belong). If you leave the scenery as it is now users will simply at some time not be able to load any procedures for BIRF after updating to a newer AIRAC cycle. And I read XP 11.10 will introduce a certain possibility to keep the runway IDs in track with real life...
xris October 11, 2017 3:43 PM
Regarding renaming 06/24 ->05/23, it will happen on 07 Dec 2017 according to eaip.samgongustofa.is. I will submit an update closer to that date.
Julian Lockwood October 29, 2017 5:14 PM
For Gateway community.
xris October 31, 2017 7:18 PM
Of course, anyone else is welcome to make the update!
Julian Lockwood November 6, 2017 3:38 PM
Fixed and will be included in next Gateway export to X-Plane.