OnCourse Software

YSSY to YPDN. YPDN approach gives me runway assignment 34L, the RWY I took off from at YSSY. This happened twice before, at different APTs, and I just assumed it was one of those "hidden" RWYs that are sometimes used in addon APTs. It almost seems as if something got broken in one of the recent updates (since Dec of 20).

Altitudes: I sometimes hit L+n for a lower altitude to avoid steep approaches (which happen way too often, can that be fixed?); E.G. L+n down to FL220; then after contacting approach, the next descent they give me is maybe to FL190; then my co-pilot says something like: "Qantas 290 at 31000 descending 19000". I wasn't at 31000, I was at 22000... or something to that effect.

I do all my FlightPlans via SimBrief and it is sometimes very time consuming trying to get those approach distances within PF3 parameters... try then edit etc, etc, etc.

This FYI and at your leisure, looks like you are busy.
Thanks for a great 'app'
max

The incorrect runway has been fixed in the latest release, version 3.11.0, release 23/7/21

Re your altitude issue, please recreate with the latest version then let me see the debug log

I updated to 3.11, will re-run exact same FLT and advise.
Thanks
max

RWY issue fixed and did several ALT changes resulting in correct wording. PF3 Displayer did not always show correct updated
ALT, but very minor low priority item IMHO. I L+n'd to every waypoint (as was shown on FMC -PMDG 737NGXu) from 150 or so NM out from YPDN; IOW, I didn't give ATC a chance to assign a lower ALT to begin descent. This in order to insure that the descent 'seemed' realistic but mostly to keep proper speed. I do try to plan my last WPT to be no greater than 40nm from destination; I like to get the RWY assignment ASAP since it gets pretty busy at the end of the FLT.

All things considered, I like the way PF3 works and sounds.

Thanks
max

Thanks for the feedback

miraclemax wrote: *

Fri Aug 20, 2021 9:36 pm

I L+n'd to every waypoint (as was shown on FMC -PMDG 737NGXu) from 150 or so NM out from YPDN; IOW, I didn't give ATC a chance to assign a lower ALT to begin descent. This in order to insure that the descent 'seemed' realistic but mostly to keep proper speed.

You can also adjust the waypoint altitudes on the PF3 waypoint page before the flight, which will reduce the need to 'L+n' during descent. If you are descending via a STAR you can enter the crossing altitudes on the waypoint page, or adjust the altitudes so they will more closely correspond to your FMC (you need to adjust the PF3 altitudes before connecting PF3 to the sim). Also note that when you adjust an altitude on the PF3 waypoint page, the other altitudes are not automatically adjusted, so check the distances to nearby waypoints (including XXX) to see if those need to be adjusted as well. Hovering your cursor over the waypoint names displays a popup which will show distances to adjacent waypoints as well as to the airport.

Got it! Thanks, Dan