COMPLETE UNINSTALL OF LORBY INCLUDING ALL LINKED FILES

[shermank]

Greetings,

First a compliment....this is an excellent tool and I have used it for years.

Recently, however, I came into a situation where I needed to delete files in bulk. Not being much of a techie, I could only see how to do this file by file, much to cumbersome.

So, I uninstalled then reinstalled The AOM, but the same entries were still showing. 

MY question, how can I uninstall the AOM, so that I am presented with a clean slate, as if this were the first time I have used it. I want to completely rebuild the scenery data base within the program. Thanks for any help.

Sherm

[Lorby_SI]

10 hours ago, shermank said:

MY question, how can I uninstall the AOM, so that I am presented with a clean slate, as if this were the first time I have used it. I want to completely rebuild the scenery data base within the program. Thanks for any help.

That is not how this tool works. The P4AO addon manager doesn't keep its own data, there are no "linked" files. What you are seeing in the tool is the actual state of the simulator config files. Or in other words, what you see in P4AO is what the simulator sees too.

The question is what you were trying to delete and how you did that. What "files" are you talking about exactly, what simulator asset are you trying to remove?

Edited June 7, 2024 by Lorby_SI

[shermank]

Thanks for reading and offering help. I have had problems reinstalling scenery files for Return to Misty Mooring and Tongass Fjord.

The first thing I want to do is a clean start, as if I have not used AOM ever.

Here is a  photo of what I am seeing...all my RTMM files are in pink, which means AOM is reading them from a wrong path. To change each file individually to the correct path would require editing scores of scenery files...seems a waste of time and much too tedious. Thus my problem.

 

 

 

Edited June 7, 2024 by shermank

[Lorby_SI]

2 hours ago, shermank said:

which means AOM is reading them from a wrong path.

No, it is not. This has nothing whatsoever to do with the app. The simulator references the sceneries using an incorrect path.
Again: the P4AO tool is only reading what is in the simulators' config files. Nothing more. After reading the scenery information, it tries to access the path that the config files point to (add-on.xml in this case). When P4AO cannot access that path (for whatever reason), then the entry will be shown in violet color. This means that either the path doesn't exist, isn't actually a scenery, or that P4AO is not allowed to access it.

There are several files responsible for pointing the simulator at addons (all addons, not only sceneries):

1. C:\ProgramData\Lockheed Martin\Prepar3D v5\add-ons.cfg
2. C:\ProgramData\Lockheed Martin\Prepar3D v5\scenery.cfg
3. C:\Users\...\AppData\Roaming\Lockheed Martin\Prepar3D v5\add-ons.cfg

File 1 is static, if you delete it, the addons that it references are no longer seen by the sim. This file will not be rebuilt automatically, when it is gone, it is gone.

File 2 is the good old scenery.cfg, same as it has always been since the beginning of MS flightsims.

File 3 is dynamic, you can delete it whenever you want. Prepar3D synchronizes this file automatically every time you start the sim with what it sees in the addon directory: C:\Users\...\Documents\Prepar3D v5 Add-ons

Files 1 and 3 do not point at scenery folders, instead they point at add-on.xml files, which then in turn point at the scenery. That is how addons are ultimately linked to the sim. 

That is all there is to it. The P4AO tool is just showing you the contents of these files and that it is unable to acess the scenery folders. Since the entries are shown in dark violet color, it is the chain starting in file 1, something is wrong with the add-on.xml files that file 1 is pointing at.

Be mindful that when you change anything in P4AO, this changes the actual config files of your simulator! There is no safeguard and no going back. So, if your sceneries work correctly in the sim, uninstall P4AO and just forget about it.

Edited June 7, 2024 by Lorby_SI

[Lorby_SI]

By the way - your screenshot shows an old version of the P4AO app. The current one is 1.60 b02 and it includes P3D V6.

[shermank]

Your help and advice is greatly appreciated. Since my last post, I used the nuclear option to delete generated files. Then I used ORBX Central to reinstall all my ORBX products, which were not part of my problem.

i then rebooted AOM, only to find my RTMM files are now bright red. There was a time when I was able to manage files and installations without difficulty. I sense that age is getting the better of me and I am not as nimble a thinker than I was in past years.

i will carefully reread your two most recent answers and see if I can get my files straightened out, now that I am assured the issue is not your software.

i will take my RTMM issue to their forum for more help.

again thanks for your time and knowledge. I hope it doesn’t go to waste because of any shortcomings on my end.

 

sherm