As has already been submitted more than a year ago (
XSG-1770
Done
and
XSG-3177
Done
), Scenery Pack 27058, which is currently the XP11 default, has outdated runway information: the single runway 18/36 has been changed and is now 01/19. This leads to an issue in the XP11 FMS when trying to enter a departure from or arrival to SELT: error message RW01/19 doesn't exist. I believe the fix is simple. I have been working on a 3D package for SELT. Line 100 in my apt.dat file is as follows:
100 45.11 1 1 0.25 1 3 0 01 -00.92301945 -078.61696945 0 0 2 0 0 0 19 -00.89415555 -078.61480833 0 0 3 7 0 1
I am confident of its accuracy. When I replace that line in the default apt.dat file with my data, the FMS works perfectly. I respectfully suggest that the Gateway data be amended in the same way and included in an upcoming update.
So much for confidence. In validating my scenery package for the Gateway, I discovered I had mishandled the displaced threshold. My runway coordinates are now in line with the Gateway CIFP data; line 100 reads:
100 45.11 1 1 0.25 1 3 0 01 -00.92301900 -078.61696900 0 0 2 0 0 0 19 -00.89018100 -078.61450800 439 0 3 7 0 1
You must be logged in to participate in the discussion
Current runways in X-Plane are 18-36, but they should be 19-01.
Jan Vogel March 27, 2021 1:27 PM
This was fixed in recent uploads.
As has already been submitted more than a year ago (
XSG-1770
Done
and
XSG-3177
Done
), Scenery Pack 27058, which is currently the XP11 default, has outdated runway information: the single runway 18/36 has been changed and is now 01/19. This leads to an issue in the XP11 FMS when trying to enter a departure from or arrival to SELT: error message RW01/19 doesn't exist. I believe the fix is simple. I have been working on a 3D package for SELT. Line 100 in my apt.dat file is as follows:
100 45.11 1 1 0.25 1 3 0 01 -00.92301945 -078.61696945 0 0 2 0 0 0 19 -00.89415555 -078.61480833 0 0 3 7 0 1
I am confident of its accuracy. When I replace that line in the default apt.dat file with my data, the FMS works perfectly. I respectfully suggest that the Gateway data be amended in the same way and included in an upcoming update.
Seawinder October 6, 2018 5:51 PM
So much for confidence. In validating my scenery package for the Gateway, I discovered I had mishandled the displaced threshold. My runway coordinates are now in line with the Gateway CIFP data; line 100 reads:
100 45.11 1 1 0.25 1 3 0 01 -00.92301900 -078.61696900 0 0 2 0 0 0 19 -00.89018100 -078.61450800 439 0 3 7 0 1