Robin Peel
commented
in reference to scenery pack
42795on January 19, 2016 5:20 PM
I have moved the localiser and glideslope aerials to their correct locations for the rebuilt runway 04/22. This is in the data release that can be downloaded from the NOTAMs page. The new nav-aid positions are pretty clear on GoogleEarth, even though this still shows the runway itself as under construction.
But, I see errors with the submitted airport design. In real-life, this runway has not been significantly extended (as stated by the author), just shifted to the Northeast (an extension built on the approach end of runway 22, and a section decommissioned on the approach end of 04). The submitted design does not seem to reflect the new taxiway layout, as published on the FAA charts (which seem up to date).
Robin
EBOB_MARSH
commented
in reference to scenery pack
42795on May 4, 2016 11:26 PM
This AP is another example of one where the ground countours in the mesh are incorrect for the runways and taxiways to RW 4-22. This airport requires x-Plane operated with the unchecking of "airport follows land countours" in the rendering screen to work properly. otherwise the lumps in the RW and in the taxiways to RW 4 can catch a prop tip of some AC. With the new release of WED 1.5 airports like this can be selectively set flat as Ben has pointed out. KEVV will need this setting.
This is a great GA Airport with great features and I have generated the taxipaths for it to top off Bruce's fine design. I will submit the TaxiRoute data after a bit more checking of its correctness.
You must be logged in to participate in the discussion
I have moved the localiser and glideslope aerials to their correct locations for the rebuilt runway 04/22. This is in the data release that can be downloaded from the NOTAMs page. The new nav-aid positions are pretty clear on GoogleEarth, even though this still shows the runway itself as under construction.
But, I see errors with the submitted airport design. In real-life, this runway has not been significantly extended (as stated by the author), just shifted to the Northeast (an extension built on the approach end of runway 22, and a section decommissioned on the approach end of 04). The submitted design does not seem to reflect the new taxiway layout, as published on the FAA charts (which seem up to date).
This AP is another example of one where the ground countours in the mesh are incorrect for the runways and taxiways to RW 4-22. This airport requires x-Plane operated with the unchecking of "airport follows land countours" in the rendering screen to work properly. otherwise the lumps in the RW and in the taxiways to RW 4 can catch a prop tip of some AC. With the new release of WED 1.5 airports like this can be selectively set flat as Ben has pointed out. KEVV will need this setting.
This is a great GA Airport with great features and I have generated the taxipaths for it to top off Bruce's fine design. I will submit the TaxiRoute data after a bit more checking of its correctness.