General Category > General Discussion
Installation into P3D V4
Eziocin:
Hi,
I have downloaded all the updated products and when I try to install them they point at "C:\Program Files (x86)\Addon Manager"....is this OK or should I manually point them at the P3DV4 folder ?
Thanks
Ezio
virtuali:
If you have enough space on the C: drive, then yes, the default choice is correct. The whole main advantage of the new installer, which has been requested by user for years, is that now you can freely select the installation folder as you like, without being forced to install into the sim like it used to be.
In fact, it would be best if you DO NOT install into the sim, so you'll be able (at least on P3D 3 and 4), to reinstall the sim entirely, without having to reinstall all the FSDT sceneries, which is the main advantage of the new installation system, which is the one officially suggested by LM.
lonewulf47:
I have just started to install FSDT airports into P3D V4. I have installed P3D V4 on a separate (D:) drive and would like to install all my addons also on this drive, but outside the sim. I have therefore created a folder "Prepar3D v4 Add-Ons" on this drive D (actually the same name as it was proposed in the "documents" folder after installing P3D V4 (similar to P3D V3).
To install into this mentioned folder I have directed the installer there and had started the install process. So far the install went flawless and after finishing I found a folder "Addon Manager" holding all possible data for the Addon Manager, the installed airports etc. So far so good.
Now what I see further is that NO ENTRY is made in the scenery.cfg. To properly start displaying the airports (and the Addon Manager) there is now some XML code in the "Documents\Prepar3D V4 Add-Ons" folder within a subfolder for each component like Addon Manager, Airports etc.
How can I tell the installer to make the usual entry into the scenery.cfg? I understand how it works without this, but you might have noticed that there are some Add-Ons that actively use the scenery.cfg for other utility works. So - leaving out the entries in the scenery.cfg may not be such a great idea. Any other ideas?
Regards
Oskar
virtuali:
--- Quote from: lonewulf47 on June 01, 2017, 05:08:35 pm ---Now what I see further is that NO ENTRY is made in the scenery.cfg. To properly start displaying the airports (and the Addon Manager) there is now some XML code in the "Documents\Prepar3D V4 Add-Ons" folder within a subfolder for each component like Addon Manager, Airports etc.
--- End quote ---
Please have a look at this post of mine on the LM forum:
http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=124701#p158461
It explains some of the benefit of this new system, and why is so much better for users and developers alike.
--- Quote ---How can I tell the installer to make the usual entry into the scenery.cfg? I understand how it works without this, but you might have noticed that there are some Add-Ons that actively use the scenery.cfg for other utility works. So - leaving out the entries in the scenery.cfg may not be such a great idea. Any other ideas?
--- End quote ---
The one addon we do which requires reading all the scenery areas, regardless where they are, which is of course GSX, fully supports it so, we made our own part.
We can only hope that, having switched entirely to this new method, with all our products, would prompt developers for such utilities to update them to support it.
lonewulf47:
Thank you, Umberto for your descriptive answer. I fully understand the arguments and - so far - even the system, however there is one important question remaining: Why are the entries for all FSDT airports in the Scenery Library non-editable? This seems a bit strange to me - to say the least. See attached picture. It seems that you have missed a parameter from the SDK.
https://dl.dropboxusercontent.com/u/94175055/P3DV4_01.jpg
Edit: After a few trials with the add-ons.xml I am more or less convinced that this system has a major flaw: the entries in the Scenery Manager remain un-editable. While this may be ok for simple scenery within one folder, it is completely unacceptable for complex scenery with multiple entries. I wonder how LM will deal with that. For the moment I don't see any other possibility than to remove the add-on.xml and enter the scenery manually to the Scenery Manager and thus again to the scenery.cfg. Not sure whether this is a real progress in the history of simulation.... ::)
Regards
Oskar
Navigation
[0] Message Index
[#] Next page
Go to full version