OnCourse Software

I have been letting PF3 'do its thing' for so long, that now I am trying to intervene in some of the many optional settings, I am beginning to lose sight of what is going on - what is down to me and what might possibly be a bug. Using my last flight (with the current beta) as an example, can I ask please:

1. Why was I asked to descend to 26000 at waypoint BIG (far from my ToD)? My PF3 waypoints page shows me as being programmed to remain at cruise alt (FL280): it already had the correct value, so I didn't add one to the box. I reset the altitudes to very different values, as PF3 didn't take into account a long, circling STAR and transition

2. Why was I cleared to land with no further descent instructions from FL260?

3. Why am I told to slow to 200kts, then 180kts, when I am still so far from the airport and still at about 20,000'? I just ignored this, as slowing to 180 would involve setting flaps.. not very realistic at that altitude. I have reverted to "- Select Approach Speed" in the profile box, rather than have a set value, and am hoping that PF3 will not now give me any speed instructions (I'd prefer to manage them myself, rather than be asked to slow so much at such a high altitude).

I wonder if any of this is due to my using my full flight plan (with SID/STAR) and having the FP Filter active?? Maybe not. Whatever, it'd be good to know what I did (if it was me) that lead to the three situations above.

Thanks, as ever!

Martin S.

Sorry Martin that log's almost empty... try attaching the Old debug file

Oh, I wonder why. The old log is the same size as the current one - I have been testing stuff so it won't help I'd imagine. No matter, I'll run a new flight tomorrow (with 3.21.99) and see what happens Thanks.