Hi Oliver,

I'm running AO v1.55 b10 and have an issue with an AIG entry which is impacting on the Save option.

When I launch AO a message appears advising a new Package has been detected - AIGAIM Airports. This is one entry of six in the supplied add-on.xml file by AIG.

The entry is shown in the scenery list in dark green as as addon. I okay the message and press Save which is highlighted in red. A confirmation appears and after pressing OK the save button shows in red. If I exit AO I get a warning message that changes have not been saved.

Any idea why this is happening and how to solve it?

Hello Ray,

hard to tell from here. One possible cause would be the add-ons.cfg files. If the P4AO can't add the package to the add-ons.cfg in appdata\roaming, if there is a conflict with the autodiscovery paths or if the app is not able to recognize the package because of a file system error (like, access privileges or something), then you would get this error.

So the first things to check are the two add-ons.cfg files. There is one in the sim directory in \AppData\Roaming\... and another in C:\ProgramData\. See if that package is already in any of the two before you start P4AO, and if it is, check if there is any obvious reason why P4AO might not be able to see it (syntax error, package sequence error, encoding troubles, etc.). These things can potentially be caused by an automated installer. 

Edited May 21, 20215 yr by Lorby_SI

Hi Oliver,

Thanks for your reply. I have a total of 3 add-on.xml files. The two you list above plus the one in the AIG folder which I pasted the contents of in my post yesterday.

In the Program Data one there is an entry for the main AIG which calls all 6 components.

In the Roaming one there is one which includes an entry for C:\Users\Ray\Documents\Prepar3D v5 Add-ons\AIGAIM Airports

and the third is shown above.

When I opened AO this morning it was fine. But then I launched SimStarterNG and then closed it without launching P3D.

When I then opened AO again the message appeared about a new add-on. It's the same as yesterday - AIGAIM Airports and the red Save button is back. I suspect SimStarterNG is changing the date/time of the Program Data add-on.xml which seem to be triggering AO to detect a new package. But there isn't a new package.

1 hour ago, Ray Proudfoot said:

which seem to be triggering AO to detect a new package

No, P4AO doesn't care about that. It compares the two add-ons.cfg files to the list of add-on.xmls that are visible to the sim. It obviously finds a package on a discovery path that it thinks is not listed in the add-ons.cfg file. And when it tries to add it anyway, the operation fails. The question is why. The way I see it, all AIG components should be in the add-ons.cfg in \ProgramData\... as there is be only one add-on.xml file from AIG.

There are only two active add-ons.cfg files - the one in AppData\Roaming and the one in \ProgramData. Whatever else you find is irrelevant. The one in AppData\Roaming lists all "dynamic" packages (=add-on.xml files) that have been found on the autodiscovery paths (by P3D or P4AO). The one in ProgramData lists all "fixed" addons that have been installed through the Prepar3D command line interface. If an app or installer interferes with these automated processes, there is no telling what will happen. If you think SimStarter is doing "something", observe the two add-ons.cfg files before starting the app and after.

I'm not sure if I can help, but if you want, create a backup with P4AO and send the resulting ZIP file to me by email. Maybe I can see something in it.

Hi Oliver. I've identified and fixed the problem. SimStarterNG allows you to have different add-on configurations. I had two different ones for add-ons as one of my aircraft is installed via an add-on as opposed to the normal installation method. I had disabled it when flying other aircraft.

When I switched from one aircraft to another (I have a separate profile for each aircraft) it was using a different add-on configuration and it was this that was being detected by AO.

I have reverted to a single add-on configuration now and that has resolved the problem. It has to be this because the problem has only existed for a few weeks and it back then I decided on more than one add-on configuration.