February 2, 20179 yr 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
February 2, 20179 yr 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
February 2, 20179 yr Commercial Member 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 Kyle Rodgers
February 2, 20179 yr 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 Ryzen 9 9950X3D @ 5.6Ghz + Corsair Nautilus Water Cooler - 64Gb Corsair Vengeance DDR5 6000Mhz - ASUS RTX 5070Ti 16Gb - Samsung G9 Odyssey 49 inch 5120x1440 Monitor - ASUS Crosshair X870E - Win 11 Pro - MSFS 2020 - 3 x NVMe M.2 1Tb - Fractal North XL Case "Tertia Optio, Latebra Factum" Steve Summers
February 3, 20179 yr 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
Archived
This topic is now archived and is closed to further replies.