OnCourse Software

Here is an interesting issue that I've found.

PF3 ATIS and Chatter is now leaving off the intended runway designator (Left or Right). However, when ATC speaks directly to my aircraft it uses the correct designator. For instance on my current flight from KMIA to KLGA, ATIS at KMIA stated that landing and departing runway is 26 when in fact there is Runway 26L and 26R, and RWY 2, there is no 26. When I tuned to ground I could hear aircraft also being cleared to runway 26. When I requested taxi clearance ATC cleared me to 26L, but continued to clear all other aircraft to 26. AI traffic does taxi to the correct runway for takeoff.

I'm running Prepar3d v4 (which, by the way, is holy grail of flight simulation!) and I did update the database with MakeRwy (latest version) which requires a little extra step to get the correct information into Prepar3d v4. However, I did verify that the database is correct in PF3.

Has anyone else experienced this?

Mike T.

Please attach a zip file with the contents of the PF3\Logs folder so we can take a look what happened there.

Mike T wrote: *

Tue Aug 01, 2017 8:54 pm

and RWY 2,

I assume you mean 27. Yes, please zip and attach the logs as Thomas requested.

Here ya go. Logs attached.

As you say, it looks like PF3's database is correct, in that it has runways 26L, 26R, and 27, and you were in fact given 26L for departure.

Code: Select all Runway data for KMIA WP:0 Usage set to: 2 Rwy Num: 26 Rwy Ltr: 1 -------------------- Usage set to: 1 Rwy Num: 26 Rwy Ltr: 2 -------------------- Usage set to: 1 Rwy Num: 27 Rwy Ltr: 0

But the AI sweep shows the runway designator for the AI as simply runway 26:

Code: Select all 8/1/2017 1:06:09 PM: 830 - #1 Initial sweep shows AI using runway 27-0 8/1/2017 1:06:09 PM: 830 - #1 Initial sweep shows AI using runway 30-0 8/1/2017 1:06:09 PM: 830 - #1 Initial sweep shows AI using runway 26-0

which is why the calls for the AI refer to runway 26. I'm going to have to defer to Dave on this but I think the AI's runway designator is obtained not from PF3's database, but from the AI traffic tables via FSUIPC, so the runway 26 designator for the AI is likely coming from the sim and not PF3.

Am I the only one flying PF3 with Prepar3d v4 and experiencing this issue? The issue does not occur with FSX-SE (which I have since deleted).

I've noticed this runway issue too in P3Dv4

Ice

Apparently the old "Radar Contact 4.x" is having the exact same problem with P3D v4. It seems it has something to do with the way the runways files are generated in v4 which is why we need to use Addon Organizer to get Make RWY to work now.

Thanks for that Mike

Sent from my SM-G920F using Tapatalk

Guess what? I've only dicovered a problem that I don't suffer from....err....cross fingers like mad!

John