Mandalay Airport Layout updated [Festival May 2017]

[IAHM-COL]

I just did

https://github.com/FGMEMBERS-SCENERY/VY ... 0e751e2d14

So @V12

Code: Select all

git pull

or download again, and try again


Thanks for reporting,
IH-COL

[V12]

Didn't help because on terrasync is treshold.xml equals to the erased file.
But I found right coorinates for VYMD.threshold.xml via uncle's Google sat map :

Code: Select all

<?xml version='1.0' encoding='ISO-8859-1'?>
<PropertyList>
  <runway>
    <threshold>
      <lon>95.974097</lon>
      <lat>21.719826</lat>
      <rwy>17</rwy>
      <hdg-deg>170.60</hdg-deg>
      <displ-m>0.0</displ-m>
      <stopw-m>61.0</stopw-m>
    </threshold>
    <threshold>
      <lon>95.980757</lon>
      <lat>21.682334</lat>
      <rwy>35</rwy>
      <hdg-deg>350.60</hdg-deg>
      <displ-m>0.0</displ-m>
      <stopw-m>61.0</stopw-m>
    </threshold>
  </runway>
</PropertyList>


[SHM]

Delete the threshold file in terrasync directory also.

Circa FG 2017.1 apt.dat can be supplied along with custom scenery from where FG will fetch the coordinates.

But I found right coorinates for VYMD.threshold.xml via uncle's Google sat map

But if you want to get the coordinates it is recommended to open the VYMD.dat file in World Editor and get it (That'll be most accurate).

[V12]

When I deleted VYMD.treshold.xml from terrasync AND custom scenery folder, spawn position is bad. Coordinates acquired from google maps are very precise, as You can see :



Another similar problem with ILS :



Beam is out of the runway axis.

EDIT :
I changed VYMD.ils.xml :

Code: Select all

<?xml version='1.0' encoding='ISO-8859-1'?>
<PropertyList>
  <runway>
    <ils>
      <lon>95.981306</lon>
      <lat>21.678840</lat>
      <rwy>17</rwy>
      <hdg-deg>170.62</hdg-deg>
      <elev-m>91.44</elev-m>
      <nav-id>IMIA</nav-id>
    </ils>
  </runway>
</PropertyList>


But not tested yet.

[SHM]

Could you also check if there is VYMD threshold file in fgdata/Scenery/V/Y/M/ ?

[SHM]

Coordinates acquired from google maps are very precise, as You can see

Not all airports have their runways in the right position, in which case its better to acquire it via WED.

Also as you can see Mandalay had a wrong position in terrasync version but when I made the layout I corrected the position as per real life.

[V12]

Yes, of course, WED is better solution, but in this case position from Google Maps is very good. I will check ILS treshold as soon as possible.

EDIT :
Custom scenery ILS treshold is same as in terrasync. And I found some nasty terrain glitches at tile boundary. There is not smooth transition from terrasync scenery terrain to the custom scenery terrain, I observed this around 7 - 10 miles north of the rwy 35 treshold.

[SHM]

Just like the smurfs there "We don't support terrasync "

Use terraGit and those seams will be gone

[IAHM-COL]

But not tested yet.

I think this would not help, but editing the nav.dat could

[V12]

I tested ILS approach and autoland. With modified VYMD.ils.xml is all OK.