Sign in to follow this  
Turlad

Nav data cycle still showing old cycle...?

Recommended Posts

Minor problem I have is that I get a 'NAVDATA OUT OF DATE' message... The cycle in the FMC ident page is still showing as the Sep' 13 one (which was shipped with the 777). The files in the SIDSTARs folder show the current feb//march data... I'm a little confused, there seems to be something out of whack somewhere. 

 

Anyone else had this?

 

Cheers

 

Adam

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Did you install one of our older aircraft after installing the 747? If so, this might occur.

Share this post


Link to post
Share on other sites

Did you install one of our older aircraft after installing the 747? If so, this might occur.

 

No, I've got the 777 installed but the 747 was installed afterwards. It looks like the actual data used is correct and upto date, but the ident page is getting the wrong title i.e showing the 0913 cycle name..... Can this happen?

 

Thanks.

 

Adam.

Share this post


Link to post
Share on other sites

Weird. That doesn't make any sense at all, especially since the 744 would've included the nav data as of yesterday. Check the file in the <sim root>\PMDG\NAVDATA folder (should be "cycle_info" or "nav_ident" or something like that). Make sure it isn't set to Read Only (right click the file, and select properties).

Share this post


Link to post
Share on other sites

Weird. That doesn't make any sense at all, especially since the 744 would've included the nav data as of yesterday. Check the file in the <sim root>\PMDG\NAVDATA folder (should be "cycle_info" or "nav_ident" or something like that). Make sure it isn't set to Read Only (right click the file, and select properties).

 

Yeah the files are there with the old idents. The files aren't read only but the NAVDATA folder is......

 

It's a minor problem, thanks for looking in to it when you've time.

 

Adam.

Share this post


Link to post
Share on other sites

Adam,

 

This definitely isn't normal, but I don't think it was caused by us. If it were, we'd see more reports of it, but so far, I've only seen yours. Change the folder permissions off of read only (uncheck the box), and then re-run the 744 installer as an administrator. It should update the files.

Share this post


Link to post
Share on other sites

Same issue here: The file ARPT_RWY is new, all the others are old. (FSX-SE)

 

Oliver Maertens

 

EDIT: The ARPT_RWY file seems to be created ingame only, as I do not have that file in the FSX-MS navdata folder. Files there are old ones, too. (Only flying in FSX-SE currently.)

Edited by The Undecided

Share this post


Link to post
Share on other sites

I would stay to delete the cycle and reinstall from the navigraph all over again

Share this post


Link to post
Share on other sites

Same issue here.

 

I'm getting this date:

AIRAC cycle    : 1510
Version        : 1
Valid (from/to): 17/SEP/2015 - 14/OCT/2015

 

Any idea on what to do?

 

Rgds,

 

 

Steve

Share this post


Link to post
Share on other sites

The airplane does ship with the latest Navdata (1702) but we do not automatically overwrite older data because there are people who deliberately fly using outdated data for compatibility with FSX ATC, scenery, custom made procedures, etc.

 

If you want the latest one to install, do this:
 

1. Go to your <sim root>\PMDG\ folder - delete the NAVDATA and SIDSTARS folders.

 

2. Rerun the 747 installer and choose repair.

 

It should put the 1702 data in.

  • Upvote 3

Share this post


Link to post
Share on other sites

The airplane does ship with the latest Navdata (1702) but we do not automatically overwrite older data because there are people who deliberately fly using outdated data for compatibility with FSX ATC, scenery, custom made procedures, etc.

 

If you want the latest one to install, do this:

 

1. Go to your <sim root>\PMDG\ folder - delete the NAVDATA and SIDSTARS folders.

 

2. Rerun the 747 installer and choose repair.

 

It should put the 1702 data in.

 

Hi Ryan,

 

tried the repair but to no avail.....my navdata is still showing up the same dates as before?

 

Rgds,

 

 

Steve

Edited by XCLTM3

Share this post


Link to post
Share on other sites

Weird. That doesn't make any sense at all, especially since the 744 would've included the nav data as of yesterday. Check the file in the <sim root>\PMDG\NAVDATA folder (should be "cycle_info" or "nav_ident" or something like that). Make sure it isn't set to Read Only (right click the file, and select properties).

 

Hi Kyle,

 

any chance someone can look into this further as I'm having the same issue despite carrying out Ryan's instructions.

 

Rgds,

 

 

Steve

Share this post


Link to post
Share on other sites

Steve,

 

Are you certain you deleted BOTH of those folders completely and ran the installer again?  If so were new folders created?  

Share this post


Link to post
Share on other sites

I was experiencing the same issue as well - on a virgin fresh Prepar3D, I installed the 737NGX, the 777, and then the 747.  On my 747 flight yesterday, the FMC was reporting an out-of-date data set - since I don't have a subscription to Navigraph, I didn't think too much about it until this thread.

 

Examining the existing files in NAVDATA, the various files (fmc_ident, wpNavAID, wpNavAPT, etc...) all seem to show the latest 1702 data with January 23, 2017 file timestamps.  Just like the original poster Adam, only one file in the existing folder (cycle_info.txt) shows a 2013 data set. I've also confirmed that this file was not read only. 

 

Upon backing up these files and moving them aside, I ran the 747's repair install. The two directories were recreated, and the same files (fmc_ident, wpNavAID, wpNavAPT, etc...) all appeared to be recreated with the same up-to-date January 23, 2017 time stamps. While all those files repopulated into the directories, the cycle_info.txt file was not recreated with the repair installation of the 747. 

 

Unfortunately, I'm doing this work remotely, so I cannot actually run the simulator right now to see what will happen next. I'll be watching the thread, and I'll give it a whirl when I get back to the home office to see what happens when I launch the sim and aircraft after the repair install.

 

-Greg

Share this post


Link to post
Share on other sites

Greg,

 

If the Navdata DATE is correct,  then check the Sim Date.  P3D is defaulting to September something last year so you need to reset it to System time for it to be accurate.

Share this post


Link to post
Share on other sites

Are you certain you deleted BOTH of those folders completely and ran the installer again? If so were new folders created?

 

Just for your information if there is some minor bug:

 

For some reason, on the initial install my SIDs/STARs were updated to 1702 but my navdata was not (I had 1613).  I looked at a few SID/STAR files and also the date modified (1/23/2017) so that was all clearly 1702. 

 

I renamed existing Navdata folder to something else and created a new blank NavData folder.  Installer wouldn't do a repair, so I did an uninstall/reinstall.  Now all my Navdata is up to date.  Cycle_info.txt file and other files in old Navdata folder all are cycle 1613.  The problem was definitely not a failure to overwrite the cycle_info.txt only -- none of the files was overwritten.  But a new, empty Navdata folder worked just fine -- all 1702.  As already noted, the SID/STAR files in SIDSTARS folder were 1702 from the first install.

 

Mike

Share this post


Link to post
Share on other sites

I also had this problem, tried to do a repair but it didn't want to repair for some reason so I de-registered and uninstalled. I had removed the NAVDATA and SIDSTARS folders before the re-install and they installed correctly but there was no cycle info text file installed. This must be a bug, I'll just install an older navigraph cycle that I have for now.

 

Cheers!/Andreas

Share this post


Link to post
Share on other sites

I also had this problem, tried to do a repair but it didn't want to repair for some reason so I de-registered and uninstalled. I had removed the NAVDATA and SIDSTARS folders before the re-install and they installed correctly but there was no cycle info text file installed. This must be a bug, I'll just install an older navigraph cycle that I have for now.

 

Cheers!/Andreas

 

See here:

http://www.avsim.com/topic/503119-nav-data-cycle-still-showing-old-cycle/#entry3563468

Share this post


Link to post
Share on other sites

Apologies,

 

error on my part. I didn't delete the folders prior to running the repair function.

 

Now that I followed the procedure correctly (and paid proper attention), the repair ran just fine and all the dates are Jan 2017.

 

However, the "cycle_info" text file is missing.

 

Thank you!

 

 

Steve

Share this post


Link to post
Share on other sites

Ok - I don't know precicely which of the following two actions fixed it - perhaps it was both. 

 

First, I did successfully perform the repair install and as noted above, the only file that had an old date stamp and references to an old cycle was not re-created during the repair. 

 

Second, one thing I didn't know was that the FMC was paying attention to the date in the simulation! I've been using the default, old  included AIRACs for so long that I was just used to seeing the out of date message. I didn't know that the in-sim date needed to be within the AIRAC's cycle date in order to avoid the warning. (*for some reason, I thought the FMC would just look to my computer's actual date instead of the sim's date) 

 

Either way - with the repair done and forcing the sim to use the current date, the out of date warning is also gone for me.

 

Thanks,

-Greg

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
Sign in to follow this