runway mismatch

[john1383 3]

This is not a bug with P2Atc, I think, but for a change I decided to fly to Calgary CYYC today and P2ATC correctly gave me instructions to approach and land at runway 17L but P3Dv4 has the runway as 16 with a different ILS frequency.

So P2ATC correctly told me off for landing on the wrong runway when I did land on 16!

I don't understand how the data in P3D can be different from that used by P2ATC. Is there a way to make sure both sets of data correspond?

[Dave-Pilot2ATC 828]

Pilot2ATC gets it's Runway data from Navigraph or NavDataPro AIRAC data.  P3D scenery information is not taken from the up to date AIRAC data and can be out of date.  So runways in P2A may exist that are no where to be found in P3D....as in this case.

Sometimes, you can update the scenery with an add-on and get more up-to-date runways in P3D.  Otherwise, you can figure out whether 16 in P3D matches to 17R or 17L  (I believe it's 17R in this case) and then force P2A to use that runway.  

Dave 

[john1383 3]

Thanks Dave.

I wish P3D could link itself to an updateable source like Airac, just to keep up to date!