Hi there!
I just got your mail informing me that Airac 2604 rev 1 is out, so I started the FMS manager to update my products from 2603 rev 1 to 2604 rev 1. Of all my 7 products, 3 don’t seem to update. It downloads the data, but the product stays on 2603. These products are the following:
Active Sky P3D (for v4/v5)
Aerosoft Airbus A318/319/320/321/330 Professional
Ifly Jets Advanced Series - 737 MAX
This is literally the first time ever i encountered a problem with the FMS Datamanager in many years! Could you please shine a light onto this problem? Thank you very much!
I am running Prepar3D V5.4 on Windows 11 Professional.
Best regards,
Leo van Beusekom
Voorschoten, The Netherlands
Hi Leo,
Thanks for contacting us, and thanks for your report. Unfortunately, I can´t reproduce it - I have just tried to update my addons via the FMS Data Manager, including one of your example iFly 737 for P35.
Here is my FDM during the updates:
What happened when you select only one addon and press the “Update” button? Is the download starting? After that, the installation procedure? Or what happened exactly …
Cheers,
Richard
Hi Richard,
I understand your confusion, I’ll tell you what’s happening with those 3 products:
If I press “update” and hover my mouse over the rotating wheel, I first see a download, then the backup of the old version, then… nothing.
What I did next surprised me a bit. First, I looked in “Addon Mappings” to see the exact path the program uses. Then, I looked inside that map and saw the (old) Airac data. I checked this by looking into the “cycle_info.txt” file, where it said “2603”.
Then I copied the complete contents of that map to another disk and made sure that the original Airac map was empty.
Then I did another update. First the download, then no backup (because no data), followed by an install! Result: 2604 is now in place!
I repeated my new-found procedure at the other two products: OK as well! Here is the proof:
Maybe something was corrupted in those maps? I don’t really know. Bottom line is that all is well (what ends well).
Thanks a lot for your effort in this, you may close the item if you want.
Best regards,
Leo van Beusekom
Voorschoten, The Netherlands.
Hi Leo,
First of all, well done for this great report/feedback. It happens not so often that someone shares his thoughts, his tasks, in so much detail as you have done. Much appreciated - it is much easier for us to identify the issues and/or what happened, without digging into every single step. Great - well done! This is really a teaching example of how a posting can be handled very well …
Short about the content:
The FMS Data Manager also looks in status files, which are typically located in the addons data path. In this status files (xml) there is the revision number included. These files are necessary to identify which add-ons are updated and which are not.
When you copy files from old/outdated cycles or from newer cycles, you may end up producing such “hicks” in the FMS Data Manager, and the FDM does not exactly show what is updated and what is not, even when you have the newest files in the addon folder.
The recommended approach is to update the lines again (which are not updated). This should place all files into the correct folder and update the status files, too. This can also be done, even when the FDM shows the newest cycle, but you see an older one in your addon. Update it again, and all should be fine …
Anyway, solved … great! Happy flying and have a nice evening Leo
Richard
