Tim,
FSX and FAA Nav Aid Charts show DVOR ranges that are different than Plan-g. I have rebuilt the Plan-g Database in hopes of capturing the current AIRAC 1413 cycle updates, but to no avail. For example:
DVOR CYN in Plan-g shows a range of 195.2 miles. It is actually 130 miles. DVOR RBV also shows 195.2 but it is now 40 Miles. The FSX NavAid files all show correct. How can I correct the navaid ranges?
Update - 12/16/2014 I now have found many instances where Plan-g has the wrong DVOR/VOR range while FSX has the correct data after using Herve Sors' Navaid Update Tool (Currently AIRAC Cycle 1413).
Does anyone have a suggestion how I can update Plan-g's Nav Data?
Another Update 12/16/2014
WOW. Disregard my previous messages. Not at all sure what happened but I rebuilt the FSX data in Plan-g a third time. Now the two VORs I mentioned are correct. I guess it must be the Christmas Ghosts (and old age) playing tricks. >:D :a035:
Another Update 12/17/2014
Oh Well. Spoke too soon. Must of been a fluke yesterday that another rebuild fixed the issue. Added a new airport today, rebuilt the FSX database, Radar Contact Database, and finally Plan-g. All the corrections that occurred yesterday are gone and back to the incorrect ranges. I am totally lost. Any help would be appreciated. BTW, Radar Contact and FSX are using the correct ranges. Plan-g is the only application with the incorrect range data. However, I still will never abandon Plan-g. It has too many benefits for me.
Don :c002:
SOLVED 12/23/2014
Problem was induced by 3rd party freeware/payware airport developers/providers who extensively modify the NavAids surrounding their airport solutions. I discovered some made changes to the VORs within a 100 mile radius. Makes no sense. Using Scruffy Duck's ADE tool, I have been able to correct these ranges as I come across them.
Don
Have a MERRY CHRISTMAS ALL :a035:
FSX and FAA Nav Aid Charts show DVOR ranges that are different than Plan-g. I have rebuilt the Plan-g Database in hopes of capturing the current AIRAC 1413 cycle updates, but to no avail. For example:
DVOR CYN in Plan-g shows a range of 195.2 miles. It is actually 130 miles. DVOR RBV also shows 195.2 but it is now 40 Miles. The FSX NavAid files all show correct. How can I correct the navaid ranges?
Update - 12/16/2014 I now have found many instances where Plan-g has the wrong DVOR/VOR range while FSX has the correct data after using Herve Sors' Navaid Update Tool (Currently AIRAC Cycle 1413).
Does anyone have a suggestion how I can update Plan-g's Nav Data?
Another Update 12/16/2014
WOW. Disregard my previous messages. Not at all sure what happened but I rebuilt the FSX data in Plan-g a third time. Now the two VORs I mentioned are correct. I guess it must be the Christmas Ghosts (and old age) playing tricks. >:D :a035:
Another Update 12/17/2014
Oh Well. Spoke too soon. Must of been a fluke yesterday that another rebuild fixed the issue. Added a new airport today, rebuilt the FSX database, Radar Contact Database, and finally Plan-g. All the corrections that occurred yesterday are gone and back to the incorrect ranges. I am totally lost. Any help would be appreciated. BTW, Radar Contact and FSX are using the correct ranges. Plan-g is the only application with the incorrect range data. However, I still will never abandon Plan-g. It has too many benefits for me.
Don :c002:
SOLVED 12/23/2014
Problem was induced by 3rd party freeware/payware airport developers/providers who extensively modify the NavAids surrounding their airport solutions. I discovered some made changes to the VORs within a 100 mile radius. Makes no sense. Using Scruffy Duck's ADE tool, I have been able to correct these ranges as I come across them.
Don
Have a MERRY CHRISTMAS ALL :a035: