Jump to content

olbind

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

1 Neutral

About olbind

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

793 profile views
  1. Hello @ll, from what I could find out, what is happening here is this: Users decide to install the Airbus 330 directly into the default autodiscovery path "C:\Users\...\Documents\Prepar3D Vx Add-ons" The installer will then use the CLI to add the Package to the add-ons.cfg file in "C:\ProgramData\Lockheed Martin\Prepar3D vx" This creates a duplicate dependency, the addon is referenced twice - once by the CLI file, and a second time because the add-on.xml file is at the same time properly located in the default discovery path If the Lorby Addon Organizer is used in this configuration, it will remove the CLI reference and move it into the autodiscovery add-ons.cfg file in "C:\Users\...\AppData\Roaming\Lockheed Martin\Prepar3D vx". It does that, because a few P3D versions back, the sim itself put the autodiscovery packages into the wrong add-ons.cfg (I think that it was P3D V4.4, and the matter had been posted on the P3D forum, ackowledged by Lockheed and resolved in 4.5). But the mechanism to clean this up is still there in the Addon Organizer. The Airbus in turn is accessing the CLI add-ons.cfg file to find out where its assets are. It cannot find the Package entry and throws an Exception. I'm not sure about this practice to be honest, the add-ons.cfg files are managed by the sim. They could theoretically change at any time, with any P3D version. A custom INI or a registry key would be better suited - but really just IMHO. My recommendation would be not to install the Airbus addons into the autodiscovery path. Yes, this works with P3D alone, when you don't use P4AO or any other management tool. But technically it is wrong and only works by accident (because the sim doesn't care if the same package is referenced twice - but that could change with every point release too). Edit: the aforementioned consistency check (legacy of P3D 4.4) has been removed from the Addon Organizer tool -> Version 1.55 b07 and later. Every package reference should now stay where it has been initially installed - even if that is "wrong". Best regards Oliver Binder Lorby-SI
×
×
  • Create New...