Hello @ll,

I have updated the Addon Organizer for P3D V4 to version 0.92

It still has beta status, so I suggest a frequent use of the backup feature.

New functionality:

• It is now possible to edit scenery list entries.
• A Package view has been implemented, so you can see where your addons reside in terms of addon packages and change their loading sequence
• It is possible to import an existing scenery.cfg into an add-on.xml
• You can temporarily export the complete Scenery Library, for example to run yet another external tool that needs to discover all scenery BGLs, but hasn't been updated to P3D V4 specification yet (MakeRunways, flight planners of all kinds, etc.)

As usual, the download is available on the Lorby-SI website.

http://lorby-si.weebly.com/downloads.html

Best regards

 

 

 

Thanks for the update. Will try this.

I just used his for the first time to install UK2000 EGLL from a separate Addons folder. Worked perfectly and now that I have some confidence in what I am doing this is the way I will continue to add things. 

Hi @ll,

another small update to 0.93.

As requested, the option to export the complete library into a scenery.cfg type file is now accessible directly from the command line.

Best regards

Nice! Thanks for the update.

Thanks, very good tool

 

 

Not sure if this is a good way, but I'm creating XML for each Country and adding the scenery to the correct country XML.

A few questions:

1.On the Package tab, what order do they load, or does it matter anymore?

2. On the scenery tab there is already the base scenery etc showing(different color), if you 'import external scenery cfg', can you then delete the entries in the external scenery cfg?

Thanks

1 hour ago, alpha117 said:

Not sure if this is a good way, but I'm creating XML for each Country and adding the scenery to the correct country XML.

A few questions:

1.On the Package tab, what order do they load, or does it matter anymore?

2. On the scenery tab there is already the base scenery etc showing(different color), if you 'import external scenery cfg', can you then delete the entries in the external scenery cfg?

Thanks

Hi Clive,

1. From top to bottom. But this order doesn't matter for scenery when you are using the tool, because it will always add the proper layer tags to all resources. Scenery will always have the layering that you see on the first page, you cannot change it by moving the packages around. I have implemented the movement of packages only because I don't know what else might be coming in the future or if this might be important for a certain type of addon (for example when you are loding DLLs or EXEs through the xml files and they need to be in a certain order, or texture components).

2. What you see on the first page is what your simulator sees at this moment, a combination of all scenery components (scenery.cfg and all add-on.xmls). With the "external" scenery.cfg I meant for example the one that you were using in FSX or P3D V3 = one that P3D V4 cannot "see" anyway. So it doesn't matter what you do with it.

• The imported content does not replace what is already there, it is an addition in a separate package.
• The import is very selective: it will only accept scenery area entries that have an absolute path ("C:\MyScenery\...")
• Relative paths (like "\Scenery\World") are ignored, because they designate a location in your old simulator
• Duplicates of scenery that you already have are ignored as well.
• All the content from the external scenery.cfg is bundled into one single addon package called "Imported Scenery"
• You can rearrange the components in it by either shifting them to another package on the package view (open the package, select a component node and use "Move up"/"Move down") or by editing the components on page 1 and 2.

Best regards

Thanks Oliver

 

 

1 hour ago, alpha117 said:

Not sure if this is a good way, but I'm creating XML for each Country and adding the scenery to the correct country XML.

The only "good way" is what works well for you. There is no limit to what you can do. You can group them by continent, by country, by day/night/season, Photoreal/Landclass based - and then switch between them with the addon dialog in P3D or in P4AO.

Hi Oliver

Hmm, I've just 'reset' the SIM back to original, by deleting V4 folders in APPDATA local/roaming  and Program data.  Good idea I thought!

Now my scenery cfg is back to standard, which is good.  

Now when I run the program, it does not see any of the XMLs in DOC> Prepar3D v4 add-ons.   Before it found the 'fsdreamTeam Addon-manager' XML straight away.

Is there away of getting it to automatically 'see' the already created XML's

Thanks

 

 

 

Oliver, could your tool be used to convert  P3Dv3 scenery installs that are using the "old" scenery.cfg method over to the  V4 xml files system ?

I am currently running V3.2 and I am very interested in having my sceneries separate from the sim to facilitate re installs. especially as I will eventually move over to P3Dv4.x in the future.

Hi Oliver,

Just a couple of questions, what about scenery addons like Fly Tampa, which use a configurator ? and what about effects files ?

 

Also, I just tried adding FT YSSY using your tool, but I had to manually add the correct number and path in the addon config in C:\PrgramData. Have I missed a step ?

Edit: I should have added that FT YSSY was just a copy over from P3DV3.4 to a folder I created called addon sceneries. It was a test whilst learning how to use the tool. P3D crashed on the first attempt, that is when I noticed there was no entry on the addon.cfg  in C:\ProgData.

I just loaded the airport and every thing is fine. I am still curios about just porting over from P3D 3.4, but I have concerns if that will work.

 

Regards

Edited June 11, 20178 yr by Travelling_Wilbury
Spelling mistake

So far It works perfect. It will import from your V3  scenery.cfg  into one XML.  I've used it fine. Use the option 'Import external scenery.cfg.  

What it will not do is move any files from your effects folder and also any 'adjustment'  bgl's from scenery> world> scenery, that might be needed. 

 

The only issue, is what I have posted above. I'm sure Oliver will sort that very quickly

Oliver

If you delete a package or scenery it will delete from the program, but leave the XML in the Doc...etc..etc. 

So if you try and add another scenery with the same description it will CTD

You have to go into the docs folder and manual delete the folder, then all is fine