OnCourse Software

I wish you all the best in your well deserved retirement Dave.

LFPB - LEBL

No issues. Departure and arrival vectors great.

I am getting descent clearances "when ready" or "at your discretion" which I really like. Sometimes the TOD is miles away so being able to start descent when ready is good.

KHND to KLAX 1.) Last intercept for the ILS was shallow, I think I would have ended up inside the FAF and above the slope so I adjusted the intercept 20 degrees toward the localizer. 2.) After landing "Exit right first available taxiway..." There is no exit right on 24R KLAX The rest of the flight ...

I ran into this too until I figured it out. The first time you run a new pf3.exe file you need to right click on the file > click properties > general tab, look at the bottom of the page and there is a checkbox "unblock" this exe file. I must have some elevated security setting in Win 11 that ...

I ran into this too until I figured it out. The first time you run a new pf3.exe file you need to right click on the file > click properties > general tab, look at the bottom of the page and there is a checkbox "unblock" this exe file. I must have some elevated security setting in Win 11 that blocks ...

Thanks Dave

Not sure what happened here, RJOO-RJTT. All went well with reasonable vectors and speed control but the last cleared altitude for the vectored ILS22 at RJTT was 9000'. I had the FAF altitude set to 2000'

Did I miss an altitude clearance?

No issues EGLC-LFPB, vectored departure and arrival, using FSLTL for traffic. I find that if I keep the last enroute waypoint 20+ miles away from the airport there are no problems with the vector for the approach. One question: Is there a way for PF3 to say "cleared the RNAV approach [runway ...

I'm sorry to say but that is a placebo effect :D That option is now defunct and default to 'ON' within the code (it's hard coded) and has been that way since beta release 3.21.140 I noticed in you original post you mentioned noticing this whilst on the ground... if that is the case the likely cause ...

Your fix has worked Martin, thankyou. Using beta 3.22.8