I'm working on LZIB, but I get the warning, that the end of rwy 31 is in the wrong spot. The Wedbot scenery interprets the runway with a 240m blast pad. As seen on google earth this looks more like a 240 m runway threshold. Because in WED the runway length excludes the blastpad area but includes the displaced threshold, the CIFP runway end would have to be extended by 240m.
greetings Ben
For runway issues between CIFP data releases, you may elect to:
1. Adjust the runway numbers or thresholds in WED to match the data as a temporary measure
2. Utilize a transparent runway (for decommissioned runways)
3. Delay submitting your airport to the Gateway
I'm working on LZIB, but I get the warning, that the end of rwy 31 is in the wrong spot. The Wedbot scenery interprets the runway with a 240m blast pad. As seen on google earth this looks more like a 240 m runway threshold. Because in WED the runway length excludes the blastpad area but includes the displaced threshold, the CIFP runway end would have to be extended by 240m.
greetings Ben
Julian Lockwood December 27, 2018 11:39 PM
The FAACIFP file is an ARINC424.18 file provided by the Federal Aviation Administration. It cannot be changed between publications.
See: https://developer.x-plane.com/article/navdata-in-x-plane-11/
For runway issues between CIFP data releases, you may elect to:
1. Adjust the runway numbers or thresholds in WED to match the data as a temporary measure
2. Utilize a transparent runway (for decommissioned runways)
3. Delay submitting your airport to the Gateway
liebbe10 December 27, 2018 11:45 PM
Thx for the quick response!
Can you subscribe to my YouTube Channel?
My YouTube Channel is That Bald Gamer