OnCourse Software

Two new issues Not sure if the first is related to beta 135 or not.

1. I am getting no text on the com log. It opens OK when I connect to PF3 but the ATC text never appears. Was OK until yesterday, but past few flights - blank window. The remote text window is fine.

2. ATC asked me to descend for final approach less than a minute after I had taken off. Can't see anything odd with my PF3 flight plan (which I suppose will be in the log). What did I do wrong?

Thanks as ever for any feedback on this.

No much of a log unfortunately, but very strange...

1. Looking at the log there's no problem. Was RemoteText showing as 'connection established'?

2. I'm going to recreate you flight and try it myself... see if I can get the same issue... but that won't be till tomorrow now

Quote:

Was RemoteText showing as 'connection established'?

Yes, it does

Quote:

I'm going to recreate you flight and try it myself... see if I can get the same issue... but that won't be till tomorrow now

Thanks

Hi Martin,

Just tried your flight and had no issues at all, but I can see why you did. I notice you're still using the original sectors file but if you change that to use the extended sectors you wouldn't have had the problem. You set it from the 'Select a Flight Plan' page.

' '
However, having said all that, PF3 should have handled things much better than it did, so I am looking into that now

I'll set the extended option

Quote:

PF3 should have handled things much better than it did, so I am looking into that now

Will of course be interested to hear your conclusions Dave. Thank you.

martinlest wrote: *

Wed Feb 07, 2024 11:25 am

I'll set the extended option

Quote:

PF3 should have handled things much better than it did, so I am looking into that now

Will of course be interested to hear your conclusions Dave. Thank you.

In the next release

FIXED a problem that could cause PF3 to think you'd bypassed all waypoints and that you were now heading for the last one. This happened after a bizarre set of conditions were met... including you were flying a SID, your 2nd waypoint was closer to your departure than the first waypoint and your published procedure had your initial heading going away from your 1st and 2nd waypoint. All this, coupled with the fact you were running with the original sectors file rather than the extended one.

Quote:

FIXED a problem that could cause PF3 to think you'd bypassed all waypoints and that you were now heading for the last one. This happened after a bizarre set of conditions were met...

Wow! "Dr Reason's Swiss Cheese Model" You are 'on fire' Dave!

(I come and look for new betas every day now!)

(Any further thoughts on how to get my COM log showing text?)

martinlest wrote: *

Wed Feb 07, 2024 10:17 pm

Quote:

FIXED a problem that could cause PF3 to think you'd bypassed all waypoints and that you were now heading for the last one. This happened after a bizarre set of conditions were met...

Wow! "Dr Reason's Swiss Cheese Model" You are 'on fire' Dave!

(I come and look for new betas every day now!)

It's that time of year when there's not much to do outside

martinlest wrote: *

Thu Feb 08, 2024 10:30 am

(Any further thoughts on how to get my COM log showing text?)

Are you using Web Display?