Decimated

Strange NavData/PFPX issue

Recommended Posts

Hello,

 

I recently switched from Navigraph to NavDataPro but last night I found a very weird bug that I'm currently experencing with PFPX and generating FP's.
Is anyone able to explain why any lat/long waypoint I use with the Aerosoft NavDataPro is put into a very bizzarre format within PFPX?! (See below)

 

Aerosoft NavDataPro:

 

N0480F320 CPT UL9 KENET UN14 BAKUR/N0480F340 DCT DOGAL/M084F340 DCT N54 00
W020 00 N54 00 W030 00/M083F360 N53 00 W040 00/M085F380 N51 00 W050 00 DCT
ALLRY/N0485F400 N377A TUSKY DCT PLYMM PARCH3

 

Navigraph:

 

N0482F320 CPT UL9 KENET UN14 BAKUR/N0480F340 DCT DOGAL/M084F340 DCT 54N020W
54N030W/M083F360 53N040W/M085F380 51N050W DCT ALLRY/N0485F400 N377A TUSKY DCT
PLYMM PARCH3


Of course the NavDataPro FP won't validate with CFMU for this reason, as both the remarks and ATC FP are presented in this strange way!
Navigraph seems to do it fine however, so can only assume it's a NavDataPro related issue rather than PFPX.

 

I've tried to uninstall/reinstall the NavData multiple times, but doesn't seem to have made any difference.

 

Many thanks in advance for any help/ suggestions!

 

BW

 

Ben

 

Share this post


Link to post
Share on other sites

Which version of PFPX is installed Ben ?

 

As I recall in the past PFPX was updated following a change in the NavDataPro  data format.

Share this post


Link to post
Share on other sites

Thanks for that Stephen,

 

Just installed the hotfix, but it's still producing the same thing:

 

N0482F320 CPT UL9 KENET UN14 BAKUR/N0480F340 DCT DOGAL/M084F340 DCT N54 00
 W020 00 N54 00 W030 00/M083F360 N53 00 W040 00/M085F380 N51 00 W050 00 DCT
 ALLRY/N0485F400 N377A TUSKY DCT PLYMM PARCH3

 

and from the default PFPX FP format:

 

DCT      5420N     279  FL340 010         489  177      63.2 /  21.4   22  01.36
         N54 00 W020 00       P06 235/019 472 2291  N5400.0 W02000.0 ...../.....

 

It's really strange!!

 

BW Ben

Share this post


Link to post
Share on other sites

Ahh you're right it was still at 1.28 for some reason.

 

Just re-followed the instructions on that hotfix and now it's at 1.28.9i and has fixed the problem!!

 

Thank you very much for your help. Much appreciated!!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now