Jump to content

PFPX stopped showing SID and STARS


Recommended Posts

Hi,

I started facing some "strange" behavior with PFPX couple of days ago. It stopped showing SID and STAR suggestions in the flight plans. I am using a VA trips from / to a particular airport for my flights where I know the applicable transitions. I thought this had something to do with the air cycle, but same is the situation when 1712 was released and installed.

NOTE: The above is a general situation and does not apply to my home airport only!

PFPX: Hotfix 1.28.9i

FSX:SE

Windows 10.

Any comments would be appreciated.

Link to comment
Share on other sites

Hi,

Here is the reply to both questions:

Please login to display this image.

You can see how the plan looks like. It starts with a WP, which has nothing to do with the SIDs applicable for OMDB. Same happens with any other AP. There is no STAR, because there is no such in OAKB.

I am using Navigraph Tom with yearly subscription. They published the new air cycle several days ago. I am using Active sky.

Please let me know, if something else is needed.

Link to comment
Share on other sites

Where did the route come from ?

 

PFPX cannot assign a SID to ATBOR as no such departure exists.

 

The route most likely needs updating to the current AIRAC standard.

 

 

Link to comment
Share on other sites

Hi,

This is the reason for my post. There is no SID to ABTOR, I know it very well. The road comes with the usage of Find function of PFPX. I also am unable to understand why suddenly all this started. The route can be changed, of course, but what is the use, if has to be made for every plan manually?

Please also note that the SIM and all related software like PFPX are updated to current AIRAC using the Data Manager provided by Navigraph.

Link to comment
Share on other sites

If you update your AIRAC data then expect to update your routes, these are not supplied in AIRAC.

 

Simply clear the route and use FIND, a new departure and arrival is generated WHERE available, eg RIKE4F RIKET B525 LALDO A791 KATUS M316 GOKSO M561 ASVIB G665 PG G325 KALAT J115 QT J140 ZB G325 HANGU J174 PC

 

I am not familiar with the arrival procedures to Kabul but ATC radar is required for vectoring to the IAF.

 

 

Link to comment
Share on other sites

Hi Stephen,

All this what you are mentioning above was done already. Every time after the AIRAC is updated, I clean and update my routs as per the new requirements. The rout, which you mention in your post I made also for my flight after manual editing. This was mentioned in my previous post also.

Here is another sample plan, which I just made. This time coming from the west:

 

Please login to display this image.

 

You can see that the famous ABTOR is again there, no matter that no STAR is related to it. 

I am using OMDB in the above examples simply because I know Dubai airport very well not as a simmer, but in real life also and got very confused when the PFPX started playing such nasty games. :( 

Link to comment
Share on other sites

Hi Stephen,

Thank you very much for the support and advises last night! Removing the restrictions actually worked, but it was too late for replying. Now the planner works as it should be.

In regards to the above and before Tom closes the post, I would like to say that one of the reasons to hate online updated software is exactly what happened to me last days and wasted me almost a week. Someone, sometimes makes changes in the code, they are applied and this "someone" forgets to announce them. Believe me or not, but I had never applied any restrictions to the airports, which PFPX uses. The airport data menu I hardly know and never used it since now. 

Even the golden rule RTFM does not work in the particular case simply because the restrictions concerning SIDs and STARs for OMDB look quite logical. There are simply following the applicable transitions for the AP, which makes the issue even more complicated. Analyzing all this I may even wish to say that there is a bug in the planner. It finishes or starts the route from a strange WP instead of following the restrictions for the AP. However, I am not a software developer and will leave the subject to the specialists...

Anyhow, I hope this saga may help someone else who breaks his head with such "strange" issues.

Thank you once again!

 

Link to comment
Share on other sites

1 hour ago, Goshob said:

I would like to say that one of the reasons to hate online updated software is exactly what happened to me last days and wasted me almost a week

 

Sorry Georgi I do not follow what you are trying to say here.

 

No updates from either PFPX or AIRAC contributed to the OMDB issue, you have either added those restrictions yourself of added the airport info from another source. The airport file is only created when you edit it.

Link to comment
Share on other sites

6 hours ago, srcooke said:

 

Sorry Georgi I do not follow what you are trying to say here...

 

Hi Stephen,

I can fully agree with your statements, except one - the restrictions to OMDB airport were not added by me!. No one else is using the SIM software on my computer, especially my wife, who hates SIMing, is the last person who can touch something :). I am using FlyTampa scenery for Dubai for months already and had no issues at all. The only thing recently added were some AI traffic, which I don't believe can make such changes, but who knows?

This what you stated above unfortunately adds another pile of questions without answer. Why all this happened almost at the time when the new AIRAC was released? Why the restrictions were not followed? Why a particular WP, ABTOR was used for starting and ending the flight plan? There are several more whys, but let me stop here.

Thank you once again!

 

Link to comment
Share on other sites

14 hours ago, Goshob said:

Why the restrictions were not followed?

 

The restrictions in the OMDB airport file were followed preventing the use of SID/STAR and that is why ABTOR was used.

Link to comment
Share on other sites

Hi Stephen,

Thank you for the clarification! I was definitely lost in translation, which resulted in confusion. The applicable SIDs and STARs were actually restricted for usage, which the planner actually followed. 

I am still trying to find from where these restrictions came, but with no success till moment. Strange things happen, which rings me the bell that it will be a good idea to check the airport constrains, if something looks abnormal in the plan.

Thank you!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Privacy Policy & Terms of Use