As I was writing yesterday in other topic on this forum, I had very long brake in PC using and flying (no updates, PC off), before everything was working almost nice in PF3. I came back to flying several days ago, updated win 10, PF3 and after that PF3 became unplayable for me in VFRs (IFR have not checked yet).
VFR Start and landing from uncontrolled airfield, fly through controlled airspace and request flight following.
First contact with FSS to open flight plan, then with local multicom/unicom, then contact with ctrl and request flight following, next contact with local destination airfield.
What I have discovered.
"pf3_display" occasionally does not show "key" column, it is coming back after restarting "pf3_display" aplication.
During communication with FSS, the station does not give us any information about to who should I contact after take off, no ctrl. or departure freq's. There is no informations about altitude to rich after take off
BUT when we will contact with ctrl at 4000ft then controller says to descent to 3000ft , when we will descent to 3000 then controller gives permission to climb to the flight plan altitude for example 5500ft (YT movie time stamp 04:20). So just to avoid it I always try to contact with ctrl before I rich 3000ft or just hold climbing on 3000ft.
Contact with ctr. after take off and request flight following: Here the circus starts
First the pilot during first contact with ctr. should describe own position and altitude
to make easier to controller identify echo on radar before he give us transponder code but during this contact pilot just says "call sign with you at altitude" and adds crazy "request radar service terminated"
instead of "request flight following"
. (YT movie time stamp 07:30)
Problem when you closing up to the uncontrolled airfield and ctr. want to pass you to approach (YT move time stamp 10:20).
Controller gives you information that radar service terminated SQ7000 contact appr freq. Then you go to appr freq and check in pilot again says wrong "request radar service terminated"
, controller gives you new SQ code and right after that he cancel it and gives you new the same frequency. When you try to check in again, the story repeats.
When you are close to uncontrolled airfield controller should give you information "call sign, airfield is x NM, xx direction of you, descent to xxxx ft at pilot discretion, report airfield in sight" then when you reported airfield in sign the controller should say "call sign, radar service terminated SQ 7000/1200, frequency change approved, contact unicom/multicom at xxx,xx"- like that it was in previous versions of PF3 and it was quite good.
Now the controller does not inform you about direction to airfield and distance, no info about descending, no report airfield in sight and no information about premission to change freq to unicom/multicom.
Before entering to traffic pattern of uncontrolled airfield we should check in to unicom multicom, and say "call sign, describe our position and altitude" - before it was working.
Downwind, base leg, final reports works fine, but from unknown reason I can not change runway to land or force it.
P.S 6-8 month ago version of PF3 was working almost prefect on VFRs. Sometimes just needed to tweak waypoints or add small corrections in .pln files by notepad ++.
Any possibilities to revert to older versions? Just asking because fixing those above surly will take some time for you
I rebuilt PF3 database with make rwy's etc. Nothing helped
To this topic I attaching logs from PF3, flight plan, PF3 database files and short as possible non-public movie on YT.
Movie on YT