Okay, so I have been trying to do a flight and I planned with PFPX and then I was ready, then I went into the pmdg 737 and did everything then I went to my depature side, and PFPX and PMDG 737 do not have the same SIDS.

 

 

 

Okay, so I have been trying to do a flight and I planned with PFPX and then I was ready, then I went into the pmdg 737 and did everything then I went to my depature side, and PFPX and PMDG 737 do not have the same SIDS.

 

Don't rely on PFPX to select your runway or SID. Your NGX does not select a SID for you. You select the runway and SID which is appropriate for your route. If you would like to be more specific you can indicate the airport, runway and transition. Could probably provide more help with that information.

Sounds like a navigation database issue to me. Have you got the same AIRAC cycle installed in to both PFPX and the NGX?

For some reason, PFPX does not always show all available departure procedures for some airports. Detroit (KDTW) for instance has seven different SIDS, but PFPX only shows four of them. Not sure if this a problem with the AIRAC I use (Navigraph), or a bug in the PFPX software itself.

Okay I was departing CYYZ (Toronto) using runway 24r and PFPX said bulge1 but bulge1 is not in the SID list. And 

Okay I was departing CYYZ (Toronto) using runway 24r and PFPX said bulge1 but bulge1 is not in the SID list. And

Are you running the current nav database from Navigraph or Aerosoft, or an older version?

Toronto airspace and depature/arrival procedures have undergone major changes in the last two years. there is no longer a BULGE1 SID. Based on that, I would suspect that your PFPX Nav Data is not the most current revision.

PFPX will not list all SIDs that Navigraph provides for PMDG but the ones omitted do not have specific routing such as JFK1 or OBS obstruction clearance departures.

 

Regardless, PMDG does not import the SIDSTAR procedures from PFPX or any other 3d party source. They are stripped from the route unless the route is saved by the PMDG FMS.

I just loaded PFPX with the latest 1505 Navigraph AIRAC, and it does not show the BULGE1 SID, so I'm pretty sure the OP is running an older version of PFPX nav data if it suggested using that SID in its routing page. I have verified that SID was discontinued.

Thats weird, cause a week ago I just restored windows 7 and just reinstalled PFPX yesterday. 

Okay Im gonna go get the Latest AIRAC cycle 1505.

Thats weird, cause a week ago I just restored windows 7 and just reinstalled PFPX yesterday. 

Okay Im gonna go get the Latest AIRAC cycle 1505.

 

PFPX comes with a stock AIRAC cycle (I think it's 1302).  Installing it does not update it. 

 

You have to purchase the monthly updates from Navigraph if you want to keep it up to date.  If you have a subscription to Navigraph, you can update both PMDG and PFPX at the same time.

Okay I was departing CYYZ (Toronto) using runway 24r and PFPX said bulge1 but bulge1 is not in the SID list. And

PFPX and the NGX need the same AIRAC cycle which currently is 1505. The charts I am looking at show the SIDS skip from BOMET4 to DEDKI3. Like Jim Barrett said there is no BULGE1 SID. You can't plan and fly a flight with out of date information.

Okay, can you send me a link to the AIRAC 1505 purchase thingy

I fixed it! I just bought the AIRAC 1505 and it seems to work now.

For some reason, PFPX does not always show all available departure procedures for some airports. Detroit (KDTW) for instance has seven different SIDS, but PFPX only shows four of them. Not sure if this a problem with the AIRAC I use (Navigraph), or a bug in the PFPX software itself.

I don't think it shows vectored SIDs (CAPITAL8 at IAD, etc), because they provide no routing advantage, and vectors are impossible to predict.