[Fixing CFMU flight plan validation in pfpx]

If an error occours in IFPUV enter one error waypoint in the 'Permanently prohibitet Airways, Waypoints....' section and try again. If an error occours again enter the next error waypoint etc. Also play around with your STD (Scheduled Departure Time). Autorouting avoids particullar Time-closed Routes/Waypoints/Airspaces based on your STD even if at the time of the closure your are not at said Route/Waypoint/Airspace. This helps getting the route build a little bit faster through Europe

[KORD departure routing question]

[KORD departure routing question]

autorouting wil prefer the first fix

Am 19.2.2023 um 14:37 schrieb Will C:

Interesting, that's helpful but it doesn't solve the mystery. Take a look at the first VATSIM chart, the one titled "KORD RNAV (GPS) Departure Routes/Fixes."

 

It shows a preferred route to the northeast of RAYNR BRTMN TAAYZ and so on. 

 

In both the cases above, I was going to the northwest. So I would think PFPX would give me PMPKN NEATO DLLAN RONIC BAE (etc.)

 

But in any event, the route to TAAYZ going north doesn't really take me off course until PETTY, which is the first intersection to the east. That's the one that takes me out of my way. It would be appropriate for a northeast departure, but it's odd for a northwest departure.

 

For a trip to KSFO, I think PFPX should have picked the PMPKN-BAE segment on that chart, not not the RAYNR-PETTY-BAE segment.

 

Steven, thanks, I can find that window on PFPX but it seems to only show the preferred initial fixes? 

Are you using PFPX v2.04? I had the problem that with v2.04 Autorouting always prefers the first fix from the Airport Data/Departure Waypoints section. Enter PMPKN as the first fix like my screenshot let's see if that helps. Nonetheless you must have Direct Routes between the waypoints after the first waypoint PMPKN, EBAKE, RAYNR etc. manually saved in your Database like Stephen did. PFPX cannot find a direct route between waypoints which are not in any database. Over the years I have made hundreds of manually Direct routes in my database mostly US/Canada.

[Question about fuel burn in long approaches]

ok I have Installed v2.03 from scratch and the problem is still there. Entering 10nm in the Airport Data 'Circuit Out' at GMMN the Routeplanner use it as 'Circuit In'

 

 

[Question about fuel burn in long approaches]

vor 6 Stunden schrieb srcooke:

 

I prefer to use v2.03

 

Thx I will completely reinstall pfpx to v2.03

[Question about fuel burn in long approaches]

Am 3.12.2022 um 18:39 schrieb srcooke:

You could enter the 10nm difference as a circuit in distance on the route section of the planner.

 

Additionally you could enter an average or maximum circuit in distance for the various approaches in the airport editor for automatic application on any arrival.

Unfortunate with PFPX v2.04 'Circuit In' in the Airport Editor has no effect. Entering a number in 'Circuit Out' the Routeplanner wil use this same value as Circuit Out or Circuit In respectively.

[Missing AIRAC 2208 data for PFPX]

 

[Missing AIRAC 2208 data for PFPX]

oh nice. I bought 1 year navdata accses today just for use with pfpx and pmdg. I had no information that AIRAC support for PFPX has been stopped. If I had known earlier I would have saved myself the money. that annoys me now