OnCourse Software

Hi John, I've checked the taxi routing that you were given and it's absolutely correct for the default FS2004 scenery. Here's the output from my test system and how it looks when overlaid on the scenery as seen in ADE: 2024-04-06 12_03_49-CompatWindow.png 2024-04-06 11_26_27-Window.png Is it possibl...

From your log it seems that you again had STAR disabled, so Approach would have carried on giving you vectors for the ILS, and I can see that PF3 was set to do this. You chose to override this by requesting cleared to finals, so at that point it became your responsibility to line up for the landing....

Definitely! Unfortunately, as Dave said, *all* keystrokes are picked up by MSFS as well as being passed through to FSUIPC and then on to PF3. I had a similar issue recently that I have been trying to raise as a bug with Asobo - 'Y' is assigned as 'Slew' in MSFS, but for me C/S/Y was also activating ...

I can see from the log that PF3 had a problem with the frequency lookup for KLEX, which is the cause of your problem - this is one for Dave I'm afraid

Martin

Great minds think alike, I'm already looking at something similar

Martin

I think the best way to set that up is mark AJJAY as the STAR entry point (which it is) and use OOSHN as the last waypoint, which is where the handoff to Approach will take place (typically within about 50 nm of the airport). At OOSHN, vectoring begins or clearance is issued for approach at pilot's...

I think the best way to set that up is mark AJJAY as the STAR entry point (which it is) and use OOSHN as the last waypoint, which is where the handoff to Approach will take place (typically within about 50 nm of the airport). At OOSHN, vectoring begins or clearance is issued for approach at pilot's...

Perhaps someone can review Bill's log and see what happened; he never got a handoff to Approach as far as I can tell. OK, I've taken a look at Bill's log and can see that the COM frequency was changed from 118.25 to 124.5 just before WP 7 (MRM) so PF3 lost contact. Don't know why this happened, but...

Hi Dan, Yes, I did wonder about that when I was setting up the trial flight - I know that there has been discussion in the forum previously about the distances involved in approach procedures in the US, which is one reason why I chose this particular route. I used the Flight Plan Filter feature to l...

I have no problem with flights where my STAR entry point is the final waypoint, this is my normal set-up. Yesterday, as an experiment, I took a flight from Halifax NS (CYHZ) to Boston (KBOS) - here's how the flight plan was loaded into PF3: waypoint.0=CYHZ, A, N44* 52.46',W63* 30.36',+000477.00 wayp...