Hi, even though it seems that almost all software for P3d v5 is installed via xml, there does not seem to be a consistency by developers on where to place source files, and more importantly those source files that are installed into P3d root are the ones I wish to move. For example Fly Tampa. Their most recent installers place the source files correctly in the Prepar3d Add Ons Folder In My Documents. THIS is where I have been placing all my software when the installer allows it or when I install manually using Lorby’s marvelous and gracious tool. 
 

My need for instructions comes from my attempt today using the Lorby Tool to DELETE three Fly Tampa packages installed by Fly Tampa into the root folder of my P3d v5 install (F:\Prepar3d\FlyTampa\package1, package2, etc) and ADD them back to my preferred location of Prepar5 Add-Ons in My Documents.

what I did today was:

Ran Lorby’s amazing tool, chose the Dubai scenery package installed in Fly Tampa in the root of my P3d folder and told Lorby to DELETE.  It asked for confirmation. I agreed, it did it and I got red save.  I saved and cleared index. At that point I tried to reinstall the package to the my documents Prepar3d v5 Add Ons folder, but Lorby would error out saying that name is already in use. Clearly I was doing something wrong, can someone tell me step by step how to do what you described be above?

Finally, the goal of this entire exercise is to move ALL Add Ons Software PHYSICAL MEDIA to a singular location in the Prepar3d V5 Add On Folder in My Documents

TIA,

-Braun

 

I have not seen that this tool can move folders, only modify xml files.

I would physically move the scenery folders, using file explorer and then use the tool to update the linkages, as you have been doing.

Edited June 2, 20215 yr by Bert Pieke

Hi Bert, yes you are absolutely correct and that is what i want to do.  I want to physically move by Windows File Explorer the Physical Packages and use the tool to point the xml's to the new location.  Problem is when I did that physical move and then used the tool for the virtual move of the xml files I got the error about name already in use and I could not seem to get it to take another name.

This much I have already figured out.  There are two addon.cfg files at play; one in AppData and one in ProgramData.  My stumble is in moving the xml reference from the AppData one to the ProgramDataone.

Make sense?

 

9 hours ago, btacon said:

My need for instructions comes from my attempt today using the Lorby Tool to DELETE three Fly Tampa packages installed by Fly Tampa into the root folder of my P3d v5 install (F:\Prepar3d\FlyTampa\package1, package2, etc) and ADD them back to my preferred location of Prepar5 Add-Ons in My Documents.

If you just physically move files around, that spells trouble. At the very least the uninstaller of the addon will break, and if there is an updater process of some kind, that will stop working too.

When addons are added to the sim via an installer, that is the way to go. Uninstall them properly, then run P3D and P4AO once so they can clean up, then reinstall in the new location.

If they don't have an installer, first move them away from their old location, but not into the autodiscovery path just yet. Run P3D and P4AO so they can clean up. Then move the addon into the autodiscovery path and run either P3D or P4AO again.

Also bear in mind that Packages may reference their Components with absolute paths. So when you move it, those paths become invalid and the addon will not work anymore.

Also check if the addon installer added a new Discovery Path to avoid creating duplicate Package references.

 

Edited June 3, 20215 yr by Lorby_SI

9 hours ago, btacon said:

and told Lorby to DELETE

Delete what? The Package? Or the scenery?

...why would you do that? "Delete" means "Destroy". Make sure that the package = add-on.xml is still intact! If it is empty now, as it should be, there is a backup copy right next to it.

Edited June 3, 20215 yr by Lorby_SI

9 hours ago, btacon said:

the goal of this entire exercise is to move

P4AO is not moving anything anywhere.

 

7 hours ago, btacon said:

This much I have already figured out.  There are two addon.cfg files at play; one in AppData and one in ProgramData.  My stumble is in moving the xml reference from the AppData one to the ProgramDataone.

The AppData add-ons.cfg is for those addons that P3D (and P4AO) are discovering automatically. When a package is moved into the autodiscovery paths, no further action is neccessary, neither in P4AO nor in P3D.

The ProgramData add-ons.cfg is the reference for those addons that are not in the autodiscovery paths (=where the add-on.xml is anywhere on your PC but in "\Documents\P3D addons..." or any DiscoveryPath added by third parties).

 

8 hours ago, Lorby_SI said:

P4AO is not moving anything anywhere.

 

The AppData add-ons.cfg is for those addons that P3D (and P4AO) are discovering automatically. When a package is moved into the autodiscovery paths, no further action is neccessary, neither in P4AO nor in P3D.

The ProgramData add-ons.cfg is the reference for those addons that are not in the autodiscovery paths (=where the add-on.xml is anywhere on your PC but in "\Documents\P3D addons..." or any DiscoveryPath added by third parties).

 

Hi, and thanks for all the good feedback and direction. So how does one clean up the ProgramData paths, use the uninstaller first as you recommended?  That said, once I uninstall via the applications installer I should run P3d and P4AO again to make sure everything cleans up properly?  After that, drop those same sceneries/packages into the auto discover folder?

Am I on the right track and thanks!
-btacon

1 hour ago, btacon said:

So how does one clean up the ProgramData paths,

That depends entirely on the addon. When the installer/uninstaller program works as it should, then the add-ons.cfg file should be cleaned up by it. P3D has a command line interface (CLI) for that, described in the "Learning Center -> Software Development Kit -> Add-ons -> Add-on Configuration Files -> Configuration via Command Line", which the installers are supposed to use. If it doesn't work like that, you can try the CLI yourself. Or you move away the package manually and use P4AO to clean up the references.

When you start P4AO after moving away the package (=not to a discovery path, that could cause a conflict! It must be moved to a neutral location first. Or you could rename the add-on.xml to .-off for the time being), the app should notify you of the missing package with the message "invalid or broken packages..:" after which you click "Ignore" and then "Save". Double check the Package view if it is really gone.

Shut down the app and proceed with either a reinstall or by moving the addon to the new location. Be mindful that discovery paths have rules, you must adhere to the expected folder structure so the add-on.xml can be discovered. (\Documents\Prepar3d Vx Add-ons\IndividualAddonFolder\add-on.xml)

 

Edited June 3, 20215 yr by Lorby_SI

Howdy!  I followed your excellent instructions and using your magnificent tool I was able to accomplish everything I desired. Physical media cleanly moved, virtual pathing rebuilt and working as expected. 

All things nominal!

Thanks

-btacon