Where do I file a report? I helped many people with this exact issue.
Here, of course. Where else ?
The installer is placing entries in c:\programdata add-on.cfg AND adding folders to My Documents so the addons are being added 2 times which causes the crashing. Removing the add-on.cfg entries that I said above will resolve it.
Sorry, but this is NOT while the program crashes and the installer is CORRECT doing this. In fact, it's not even "the installer", it's P3D ITSELF which creates those two entries, and this is exactly how it's supposed to work. I believe you are assuming a double entry, but there isn't one, if you use ONLY the FSDT installers. I'll try to explain:
When an add-on use the P3D own facilities ( it should ) to install using the add-on.xml method, the following will happen:
- The add-on.xml will be created, in a folder named like the addon itself, under Documents\Prepar3d V4 Add-ons
- An entry for the add-on will be created in the add-on.cfg. WHICH one, depends on the permission level the installer ran with. If the installer ran with Admin permissions ( all our installer runs like that ), the entry will be created in the add-on.cfg in %PROGRAMDATA%, if it doesn't, the entry will be created in the add-on.cfg in %APPDATA%
This is NOT a "double entry", the add-on.xml in Documents and the add-on.cfg file are two entirely different things, the first *defines* the files used by the add-on, and the other *enables* the add-on. BOTH are required in order for the add-on to be visible so no, it's not a double entry.
If you manage the files manually, or using external utilities, it might be possible to end up with double entries, which are NOT created by our installers. For example, you might have decided to move the entry correctly created by the installer in the add-on.cfg located under %PROGRAMDATA% to %APPDATA%, then you run our installer again, and it *might* create a 2nd entry in %PROGRAMDATA% ( again, it's NOT our installer, it's P3D itself that does it, when called from our installer ), so if you got a double entry, it was because you moved something manually, but it's surely not created when always using our installers, and nothing else.