June 19, 20205 yr P3D v5 HF1 I get a ND error when loading the the Aerosoft Airbuses and discovered the reason why. Using the latest version 1.55 Lorby's Addon Organizer. Whenever I hit save it will remove any duplicates between the two add-ons.cfg. In this case it removes the following lines from the add-ons.cfg file located in C:\ProgramData\Lockheed Martin\Prepar3D v5. I have a backup add-ons.cfg where I just copy and paste the missing lines. [Package.0] PATH=C:\Users\wrs51\Documents\Prepar3D v5 Add-ons\Aerosoft A318-A319 Pro V5 TITLE=Aerosoft A318-A319 Professional ACTIVE=true REQUIRED=false [Package.1] PATH=C:\Users\wrs51\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5 TITLE=Aerosoft A320-A321 Professional ACTIVE=true REQUIRED=false
June 19, 20205 yr Commercial Member Hi, that doesn't sound right. The known issue with the Aerosoft Airbus products was that P4AO moved the CLI reference in the add-ons.cfg you mention to the other one in AppData - if you installed the product into the default autodiscovery path like you did. This location indeed creates a duplicate reference. P4AO reacted that way, because there was an actual bug in P3D 4.4 where the sim would use the wrong add-ons.cfg - this logic has been removed now. Generally speaking, it would be better to install the Airbus products where they initially say that they want to be installed (or at least not into the default autodiscovery path) Are you sure that you are using the latest version 1.55 b07? The build number is important. There shouldn't be any duplicates either, I can't imagine how they would be created by P4AO or P3D. Would you mind posting/emailing more specifics about what happens exactly? My email address is on the last page of the users manual. IMHO, the core issue is that the Airbus products use the add-ons.cfg file to determine where certain file assets are. Normally actions like this would be implemented using registry keys or an ini file. The add-ons.cfg files are managed by the sim and edited by installers etc. all the time. I wouldn't rely on their consistency with any of my own addons. Best regards Edited June 19, 20205 yr by Lorby_SI LORBY-SI
June 19, 20205 yr Author HI Oliver, @Lorby_SI I have the latest version.1.55b07. I have both P3Dv4.5 as well as P3Dv5HF1. AS Airbus Pro installed in both sims into their respective Addon folders as per the installers default locations. This also includes an Aerosoft folder under Documents that is shared by both sims. No issues with P3Dv4.5 just v5. Removing the 2 Airbus packages from the AppData add-ons.cfg worked to solve the problem. Bill
June 19, 20205 yr Commercial Member 16 minutes ago, BillS511 said: Removing the 2 Airbus packages from the AppData add-ons.cfg worked to solve the problem. I wonder how they ended up being there in the first place. Could that have been an artifact of an earler P4AO version? Did P3D do that? Best regards LORBY-SI
Archived
This topic is now archived and is closed to further replies.