OnCourse Software

Dave, I don't think it's anything to do with the beta version and I'm still convinced you didn't actually do things correctly. There may well still be a problem but it's not as you describe when looking at the log.

I've shown the relevant points from the log below... all of these took place within 2 minutes after reaching WP 13 (5420N), where you gave your position report, and at 160+ miles from WP 14 (DOGAL) where you would cross from Shannon Oceanic into Shannon Control airspace.

Your position report at 54N 20W WP13
13/09/2023 18:15:02: 230 - Transcript: 'Shanwick Radio Virgin 1467 at 54 North 20 West Flight Level 370 speed Mach .82 ground speed 509 54 North 15 West next '

Shannon Radio's confirmation
13/09/2023 18:15:23: 490 - Transcript: ' Roger Virgin 1467 54 North 20 West Flight Level 370 at 54 North 15 West Contact Shannon Control on 127.5 '

You rogering the handover at 54N 15W (DOGAL) WP 14 (160+ miles away)
13/09/2023 18:15:39: 720 - Transcript: 'Contact Shannon Control on 127.5 at 54 North 15 West Shannon Control Virgin 1467 '

These show the distance to DOGAL and the COM radio frequency
13/09/2023 18:16:17: 340 - Current Waypoint No: 14 Dest: 32 iLanding: 0 iClimb=2 Dist to next WP: 165.0219

13/09/2023 18:16:17: 340 - Ground Altitude=0 ClrdAlt=37000 Terrain=0 COM=123.95 Trans:2000

Then you changed the COM frequency to 127.5
13/09/2023 18:16:19: 380 - COM Changes at #1

13/09/2023 18:16:20: 390 - Current Waypoint No: 14 Dest: 32 iLanding: 0 iClimb=2 Dist to next WP: 164.5627

13/09/2023 18:16:20: 390 - Ground Altitude=0 ClrdAlt=37000 Terrain=0 COM=127.5 Trans:2000

Then you hit Hotkey #0
13/09/2023 18:16:22: 430 - ****** HotKey #0 detected!

13/09/2023 18:16:23: 470 - Transcript: 'Shannon Control Virgin 1467 Level at Flight Level 370 '

They INCORRECTLY Answered... although I'm not sure what distance you could actually reach them
13/09/2023 18:16:32: 550 - Transcript: 'Roger Virgin 1467 Squawk 5636 '

13/09/2023 18:16:39: 670 - Transcript: '5636 Virgin 1467 '

The you were told to re-contact Shannon Oceanic, but on the wrong frequency
13/09/2023 18:16:47: 770 - Transcript: 'Virgin 1467 Contact Shanwick Oceanic on 127.5 '

So yes, there were a couple of issues here but it was, I believe, because you didn't follow instructions correctly. I'd like to see how PF3 performs when you do so and then I'll see if I can handle a case like this when there's pilot error.

Dave,
The plot now slightly thickens.
I did a new flight CYUL-EGLL,using PF3 3.20.0 the maintenance release version.
Upon reaching Shannon Control and told to tune 127.50, i thought right...not going to tune anything,this was 1810 approx....some 20 mins later and i was away from PC when i heard the radio crackle into life,went back to PC and saw that it had tuned to Shannon Control on 127.50 and that was about 1830,everything went ok right upto landing and taxi to gate.
So i'm now wondering if this is the same as beta 3.20.5 getting a 20 min delay on auto tuning to Shannon Control instead of straight away,

No that's different Dave. If you're TOLD to tune to a control then yes, you should do so and if you don't you will get nagged and eventually PF3 will intervene. However, in your other scenery you were told to tune to xxx at the NEXT waypoint.

dmarch wrote: *

Sun Sep 24, 2023 9:25 am

No that's different Dave. If you're TOLD to tune to a control then yes, you should do so and if you don't you will get nagged and eventually PF3 will intervene. However, in your other scenery you were told to tune to xxx at the NEXT waypoint.

From the help PDF:
CP Mode 2 - In this mode you start to work your VCP a little harder and
make him/her (yes there are some hers available) handle all your
communications with ATC plus handle any necessary frequency changes.

I use CP Mode 2 and it works just fine until i reach Shannon Control...that's when i have the issue!
Once i leave Shannon Control it carries on as it should,

Ah, okay... perhaps I'd better take another looksee

Now fixed