OnCourse Software

Hi Dave:

I found I bug that I can reproduce. When asking ground for a different runway than the one assigned, everything is fine at first and the new runway is approved and taxi directions given. However, a minute later I get a strange transmission (cleared to <blank>, altimeter is <blank>) and then there are no more communication with any facility for the rest of the flight. PF3 is still running and I can even get ACARS but no coms. Similar behavior also happens on approach if a different runway is requested, the strange second clearance happens, but in that case communications continued.

Also, I think the algorithm for detecting the proximity of the aircraft to parallel runways is off a bit. I can be parked right next to a runway, but get cleared to a parallel runway on the other side of the airport. In this case I was at KMIA parked at the H gates which is close to RWY 17 but received clearance to 16L which you'd have to call an Uber to get to it's so far away LOL!

Debugs attached.

Hi Mike,

Thanks for the report

There was indeed a problem when requesting another runway if (a) your existing clearance included a SID and (b) your new requested runway did not. This has now been fixed and a new beta will be uploaded shortly.

With regard to runway assignments, PF3 will always check first to see if any AI traffic is currently active either landing or taking off and will then use that same runway. If there's no AI traffic then we use wind direction. So in your example I would imagine we detected AI traffic, although you didn't include a log for that particular scenario

Windows Defender keeps deleting the pf3.exe file when I extract it from the latest beta (Version 3.19.20) - says there's a severe Trojan. Never had that before!

Maybe this will help?
https://www.microsoft.com/en-us/wdsi/filesubmission

John

It's OK thanks.. I will wait until there's a beta which restores the VCP setting the Squawk code.