Post by Markoz on Aug 1st, 2014 at 3:15am
SORRY FOR HIJACKING ROB'S REPAINT TOPIC WITH THIS INFO. :(
I highly recommend both FSC (v9.5) and PFPX. Both are good in different ways. While both can save to the FSX Flight Plan format (which the 777 FMC can load and use), I only save FSC plans in that format.
What I really like about PFPX is that when I add a waypoint and select the next Jet Airway, it highlights the entire Jet Airway, and that allows me to choose the ending fix, or intersection that the next Jet Airway starts at.
I just created and saved a PFPX flight plan in the .rt format for use with the CS777. It saved the departure airport name (KSEA) and runway (RWY 34R), but not the SID, and the arrival airport (KJFK), but not the STAR and runway. The route doesn't show up in the RTE1 pages, all I see is this:
The LEGS page does list all of the waypoints, so the route IS there to be used:
So PFPX does all right even though I have to add the DEP and ARR info in the FMC. ;)
I highly recommend both FSC (v9.5) and PFPX. Both are good in different ways. While both can save to the FSX Flight Plan format (which the 777 FMC can load and use), I only save FSC plans in that format.
What I really like about PFPX is that when I add a waypoint and select the next Jet Airway, it highlights the entire Jet Airway, and that allows me to choose the ending fix, or intersection that the next Jet Airway starts at.
I just created and saved a PFPX flight plan in the .rt format for use with the CS777. It saved the departure airport name (KSEA) and runway (RWY 34R), but not the SID, and the arrival airport (KJFK), but not the STAR and runway. The route doesn't show up in the RTE1 pages, all I see is this:
The LEGS page does list all of the waypoints, so the route IS there to be used:
So PFPX does all right even though I have to add the DEP and ARR info in the FMC. ;)