General Category > General Discussion
Addon Manager installation locations
virtuali:
--- Quote from: BuddyDog on August 16, 2017, 02:13:15 pm ---This is the entry I was referring to in my question
--- End quote ---
Ok, what I didn't understood was your reference to an ".xml addon manager" in the C:\Program Files (x86) folder, which seemed strange, since you are not supposed to have any .xml file there (which should be under Documents\Prepar3d v4 Addons" instead).
In any case, you should never delete anything manually.
The C:\Program Files (x86)\Addon Manager folder is a perfectly fine location, which is why is default so, the only reason why you wouldn't want to use it, is if you know you won't have enough space on the C: drive to hold all the FSDT sceneries.
In that case, the proper procedure to "move" to another folder, if you changed your mind and want to use a different folder, is as follows:
- Uninstall ALL products (both from FSDT and Flightbeam) using the Addon Manager from the Windows Control Panel.
- Reply YES to the question "Do you want to remove the Addon Manager ?". THIS will clear the folder preference, allowing to select a new folder in the next installation, which will be then shared between all products using the Addon Manager.
- Reinstall everything, using only the current installers. Don't mix old and new installers.
BuddyDog:
Thank you Umberto, I will just leave it where it is, then.
CaptGreg:
--- Quote from: borisvp on August 10, 2017, 08:29:41 pm ---Good Day,
I have recently downloaded the latest Addon Manager and installed it, because the old one in my FSX installation was broken. I have FSX and P3D3 on 2 different hard disks. The installation went well and everything seems to be working again, but I noticed that it installed a couple of folders in c:\program files (X86)\Addon Manager which used to be in the respective sim folder:
* Effects (seems to be just a backup)
* Flightbeam (with my FB sceneries in it)
* Fs DreamTeam (as above)
* Simobjects/Misc
--- End quote ---
I've came across just the same issue :-[
A path to a root folder of my FSX instance is:
X:\FSX
there are subfolders where FSDT add-ons where installed initially:
X:\FSX\fsdreamteam\
X:\FSX\fsdreamteam\couatl\
X:\FSX\fsdreamteam\CYVR\
X:\FSX\fsdreamteam\KLAS\
I put the path to the root folder of my FSX instance - when the installation wizard asks.
But the installer creates a subfolder X:\FSX\Addon Manager\ - and moves there those folders described by borisvp.
Well, Ok. I removed scenery and addon manager and Next time I made sure that there was no subfolder to create with the installation wizard.
But after the installation process had been complete folders of other FSDT and Flightbeam sceneries where moved somewhere else. As a result a have corrupted FSX instance.
What else do I have to do - to have my sceneries installed correctly?
What is the right way to install these addons?
As I said even If I specify the root folder of my FSX instance - the installer ignores the existing path to the couatl subfolder and sceneries subfolders.
virtuali:
--- Quote from: CaptGreg on September 07, 2017, 03:19:31 am ---I put the path to the root folder of my FSX instance - when the installation wizard asks.
--- End quote ---
The installer is NOT asking for the location of FSX!!!! If the installer were looking for FSX, there wouldn't be any need to ask you, since it knows very well where it's located, from the registry.
What the installer is asking at start, is the location for the FSDT product you are installing and that one, as with any Windows program out there, defaults to C:\Program Files (x86)\Addon Manager.
Of course, like any other Windows program out there, the installer is also giving you the freedom to change the suggested installation path because so many users asked for the ability to install OUTSIDE the FSX. In fact, installing outside FSX, is probably the best choice so, you only had to ACCEPT the suggested default path under C:\Program Files (x86)\Addon Manager.
Not that installing *inside* FSX, like you did, would cause "problems" but, it's not usually the best idea, since you are now given a choice.
--- Quote ---But the installer creates a subfolder X:\FSX\Addon Manager\ - and moves there those folders described by borisvp.
--- End quote ---
That's precisely what the installer should do, when if finds FSDT sceneries installed using the "old" method. To SAVE you the hassle of requiring you to Uninstall them all, redownload them all and reinstall them all, it just "moves" them to the folder YOU chose when installing and updates their path in the scenery.cfg so, they will continue to work from the new location.
--- Quote ---Well, Ok. I removed scenery and addon manager
--- End quote ---
Why you did that ? And how ?
--- Quote ---and Next time I made sure that there was no subfolder to create with the installation wizard.
--- End quote ---
Again, why ?
--- Quote ---But after the installation process had been complete folders of other FSDT and Flightbeam sceneries where moved somewhere else
--- End quote ---
They haven't been moved "somewhere else", they should have been moved to the new installation folder YOU chose.
--- Quote ---As a result a have corrupted FSX instance.
--- End quote ---
No, you don't. You probably have a problem in your scenery.cfg, resulted from the mistake you did by assuming the installer did something "wrong" (it hasn't) and moved or removed things on your own.
--- Quote ---What else do I have to do - to have my sceneries installed correctly?
--- End quote ---
You will probably have to do what we tried to save you from, if you just trusted the installer and didn't move things around:
- Uninstall all the FSDT/Flightbeam sceneries
- Download the current installers for all of them
- Reinstall all of them.
--- Quote ---What is the right way to install these addons?
--- End quote ---
Accept the suggested folder, which is of course the most sensible choice, and DO NOT TOUCH ANYTHING afterwards.
--- Quote ---As I said even If I specify the root folder of my FSX instance - the installer ignores the existing path to the couatl subfolder and sceneries subfolders
--- End quote ---
First, as I've said, you are not supposed to specify the FSX folder. And, even if you are now the complete freedom to choose the installation folder, our sceneries must still stay together. That's why, in order to prevent you for making the mistake of installing a scenery in a folder, and another one in a different one, you are allowed to choose the installation folder only the FIRST time you run the installer. Then, the preference is saved, and subsequent installations will automatically go under the folder you chose initially.
In order to clear up your choice, when Uninstalling, you must reply YES to the question "Do you want to remove the Addon Manager ?". This will clear your initial choice, allowing to choose the initial folder again.
It's enough to do this only for one Uninstall, but be sure you Uninstall ALL the sceneries now. And, be absolutely sure you reinstall them using only the updated installers, if you use an old installer after having used the new one, you will have to start from scratch again, Uninstalling everything and reinstalling everything.
CaptGreg:
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---
--- Quote from: CaptGreg on September 07, 2017, 03:19:31 am ---I put the path to the root folder of my FSX instance - when the installation wizard asks.
--- End quote ---
Of course, like any other Windows program out there, the installer is also giving you the freedom to change the suggested installation path because so many users asked for the ability to install OUTSIDE the FSX.
--- End quote ---
I understand. To tell the truth I don't see a significant profit of the approach because FSDT (and FlightBeam) sceneries are very well-optimized and don't need as much disk space as a global photoscenery or a global mesh. But if many users ask for it - then this is a good Idea.
--- Quote from: virtuali on September 07, 2017, 10:22:33 am --- In fact, installing outside FSX, is probably the best choice so, you only had to ACCEPT the suggested default path under C:\Program Files (x86)\Addon Manager.
--- End quote ---
this is not a good idea - install addons on the system volume. In my humble opinion of course.
--- Quote from: virtuali on September 07, 2017, 10:22:33 am --- you are now given a choice.
--- End quote ---
ok, I understand. This is, without any doubt, a good approach
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---
That's precisely what the installer should do, when if finds FSDT sceneries installed using the "old" method. To SAVE you the hassle of requiring you to Uninstall them all, redownload them all and reinstall them all, it just "moves" them to the folder YOU chose when installing and updates their path in the scenery.cfg so, they will continue to work from the new location.
--- End quote ---
that is the root of the issue that I've faced: when I started my FSX after I've had installed a new scenery (with a new version of the addon manager), I got warning messages.
My apologizes for the Cyrillic. These are standard warning messages. They say that an error occurred in the scenery.cfg: the scenery folder for the Area.xxx isn't found:
[spoiler]
[/spoiler]
--- Quote ---But after the installation process had been complete folders of other FSDT and Flightbeam sceneries where moved somewhere else
--- End quote ---
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---They haven't been moved "somewhere else", they should have been moved to the new installation folder YOU chose.
--- End quote ---
I understand. However I didn't found them installed in the folder that I chose. But I as to this aspect I agree with You: this is my own problem. I just was trying to troubleshoot the issue and at a moment It seemed to me that I found a good way out, but further I made some mistake apparently.
--- Quote ---As a result a have corrupted FSX instance.
--- End quote ---
--- Quote from: virtuali on September 07, 2017, 10:22:33 am --- No, you don't.
--- End quote ---
Yes I did. At first time, after I've had installed FSDT scenery I didn't change anything manually. I just stared my FSX and got a number of warning messages.
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---
You probably have a problem in your scenery.cfg, resulted from the mistake you did by assuming the installer did something "wrong" (it hasn't) and moved or removed things on your own.
--- End quote ---
Negative. As I said I didn't touch anything on my own after I've had installed a new FSDT scenery that I purchased (KDWF, If I remember correctly) in addition to those that were purchased and installed previously. But further instead of the new scenery I've got warning messages.
--- Quote ---What else do I have to do - to have my sceneries installed correctly?
--- End quote ---
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---
You will probably have to do what we tried to save you from, if you just trusted the installer and didn't move things around:
--- End quote ---
Maybe this was my Karma and a bad day but somehow you made me to perform a troubleshooting.
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---
- Uninstall all the FSDT/Flightbeam sceneries
- Download the current installers for all of them
- Reinstall all of them.
--- End quote ---
I'm affraid there is one additional step that I have to do: revert to a backup.
--- Quote ---What is the right way to install these addons?
--- End quote ---
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---
Accept the suggested folder, which is of course the most sensible choice, and DO NOT TOUCH ANYTHING afterwards.
--- End quote ---
Of course you have your own reasons for that approach. However this is not a good Idea - to install any scenery addon on a system volume (where C:\Program Files (x86)\ is located).
--- Quote from: virtuali on September 07, 2017, 10:22:33 am ---
Uninstalling everything and reinstalling everything.
--- End quote ---
ok. tnx.
Just to make sure to avoid any further posts here: should I set the checkbox during a new installation process?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version