Default Airport does not track well in X Mapper-Pro, seems located about 3/8ths RWY 6/24 width to the north (move southward) and about 15 feet too far west (move eastward).
Default RWY 18L/36R located too far to the north about I/8th length of the RWY.
Nav obstacles in pavements, see Attached Photos, location IDs on Photo titles.
Align entry roads with actual wherever they are.
Hi Julian,
I see the latest submission for KMDH is from you and it says the taxi sign error is fixed. However, I still see this in the X-Plane 11 log.txt. Which version of this airport got included in the v11 airport export?
I am not sure when the global capture of airports was done for the current
XP11 beta. It may have been before that airport was fixed.
However, I validated it just not in WED and it failed for another reason -
because WED now has tighter controls than before.
So, I have done the following:
1. Fixed the validation error in WED.
2. Double-checked that particular taxi-sign is not present.
3. Placed this airport in my XP-11 Custom Scenery Folder.
4. Removed the Global Airports folder.
5. Rendered this airport in XP-11.
There were no log errors, so I have now made today's version the
"Recommended" submission on the Gateway. I must assume this will get picked
up if/when Ben and Tyler do a bulk Gateway export to the release version of
XP-11.
JL
You must be logged in to participate in the discussion
Default Airport does not track well in X Mapper-Pro, seems located about 3/8ths RWY 6/24 width to the north (move southward) and about 15 feet too far west (move eastward).
Default RWY 18L/36R located too far to the north about I/8th length of the RWY.
Nav obstacles in pavements, see Attached Photos, location IDs on Photo titles.
Align entry roads with actual wherever they are.
Jan Vogel March 26, 2021 8:04 PM
Airport was updated in the meantime.
Could not find tile 49 name is close-frame
{@L}B{@Y}{^ld}F{@L}Could not find tile 48 name is open-frame
(in sign '
|
{@Y}B2{^r}' from airport KMDH:Custom Scenery/Global Airports/Earth nav data/apt.dat)
Jennifer Roberts November 29, 2016 2:31 PM
Hi Julian,
I see the latest submission for KMDH is from you and it says the taxi sign error is fixed. However, I still see this in the X-Plane 11 log.txt. Which version of this airport got included in the v11 airport export?
An unknown user November 29, 2016 2:34 PM
The version in 11.00pb1 is old. My court to take the latest for pb2.
Julian Lockwood November 29, 2016 2:49 PM
Hi Jennifer
I am not sure when the global capture of airports was done for the current
XP11 beta. It may have been before that airport was fixed.
However, I validated it just not in WED and it failed for another reason -
because WED now has tighter controls than before.
So, I have done the following:
1. Fixed the validation error in WED.
2. Double-checked that particular taxi-sign is not present.
3. Placed this airport in my XP-11 Custom Scenery Folder.
4. Removed the Global Airports folder.
5. Rendered this airport in XP-11.
There were no log errors, so I have now made today's version the
"Recommended" submission on the Gateway. I must assume this will get picked
up if/when Ben and Tyler do a bulk Gateway export to the release version of
XP-11.
JL