Lorby_SI

Prepar3D Addon Organizer 1.00 released

Recommended Posts

Hello @ll,

I have just uploaded version 1.00 of the AddonOrganizer to the Lorby-SI website (http://lorby-si.weebly.com/downloads).

I still consider it to be in beta status. Frequent backups of your config files are recommended.

Change log:
- Fixed serveral null-pointer exceptions when adding / editing scenery
- Accelerated the refresh of the main tree view, so the "up/down" buttons make more sense
- Added the option to activate/deactivate individual addon components in an external add-on.xml

That last part works, but it causes entries in the content error log of P3D. That cannot be avoided for now, so it is up to you if you use it or stick to the official method - which is to disable the complete addon package containing the component (and all others with it).

Best regards

  • Upvote 1

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

Thanks Oliver, very nice from you, great application.

Are there any special instructions on how to do the update to v1.00?.

Cheers, Ed

Share this post


Link to post
Share on other sites

Oliver,

You're most certainly one of the guys who embody the spirit of flight sim that we had in the old days, when many people with your type of talent gave freely to the community and produced some incredible scenery, aircraft, graphics and utilities - and shared them with the community.

A huge THANK YOU, and tremendous respect for giving of your time and talent so freely!

 

  • Upvote 3

Share this post


Link to post
Share on other sites

  Thank-You, for this Oliver. It is very much appreciated.

Cheers

Share this post


Link to post
Share on other sites
10 hours ago, edpatino said:

Thanks Oliver, very nice from you, great application.

Are there any special instructions on how to do the update to v1.00?.

Cheers, Ed

Hello Ed,

no, it should be enough to just run the installer. It will overwrite the existing exe - and there are no other files.

The app was built to assume that every time you start it is the first time - it doesn't keep any data of its own, instead it reads everything fresh from the disk.

Best regards

Share this post


Link to post
Share on other sites

Many thanks Oliver, can only echo what Dave said above.

Share this post


Link to post
Share on other sites
10 hours ago, Lorby_SI said:

Hello Ed,

no, it should be enough to just run the installer. It will overwrite the existing exe - and there are no other files.

The app was built to assume that every time you start it is the first time - it doesn't keep any data of its own, instead it reads everything fresh from the disk.

Best regards

Good!. Thanks.

Cheers, Ed

Share this post


Link to post
Share on other sites

Hello @ll,

many thanks for your kind words!

Best regards

Share this post


Link to post
Share on other sites

Hello Oliver,

 

do you plan do includ the capability to create groups? That means that I can attach group designateors to sceneries so that I can activate certain aeras of the world (e.g. Germany only, or Western Europe, or Scandinavia, or US west coast). So I can attach certain group names to a scenery and only the sceneries belonging to a certain scenery are activated and the rest not. This speeds up loading times significantly.

Danke

Christian

Share this post


Link to post
Share on other sites
9 hours ago, Shasta62 said:

Hello Oliver,

 

do you plan do includ the capability to create groups? That means that I can attach group designateors to sceneries so that I can activate certain aeras of the world (e.g. Germany only, or Western Europe, or Scandinavia, or US west coast). So I can attach certain group names to a scenery and only the sceneries belonging to a certain scenery are activated and the rest not. This speeds up loading times significantly.

Danke

Christian

Hallo Christan,

no, I don't have any plans to do that. This would mean that the app has to keep a local database, matching the groups to the sceneries. While this is not a problem technically, it is not what the app was designed for.

But using the xml addon definition files you can do that without an additional app. There is no rule that is saying that you can't have the same scenery configured more than once, it only cannot be active in more than one package. So you could construct add-on.xml configuration files that represent your different scenery preferences (for example by continent or country or scenery type...etc), and then turn them (=their addon package definition) on and off as desired. For example, I am doing this to switch between photoreal and normal scenery.

Viele Grüße

Share this post


Link to post
Share on other sites

That's a great idea, Oliver! So I'll create more than one add-ones.xml and since I already start P3D with a batch file to select the Autogen I want (FranceVFR or FTX) I just use it to activate a certain xml file.

Danke für die Idee

Christian

Share this post


Link to post
Share on other sites

Autogen can be an addon component in the xml files too. And aircraft, shaders, sound, tools, textures, ... every type of content really.

You could build entirely different simulator setups and "look&feel" with these addon xmls.

Maybe I should add an option to the P4AO that lets you duplicate an existing add-on.xml, and not only move but copy addon components from one package to the other?

Best regards

Share this post


Link to post
Share on other sites

Hi Lorby,

would it be possible to implement an option to choose where a new addon's xml will be created, so that it must not be in the user/documents folder. I think at the moment that's the only location where your tool places new xml's? And of course if we could choose a destination folder it would be useful if your tool then also would make an package entry in the add-ons.cfg with the desired path.

Reason i ask is because yesterday i reinstalled my A2A aircraft and their new (again) updated V4 installers let you now choose a preferred installation folder anywhere you like and then also the package and path was added to the add-ons.cfg in C:\ProgramData\Lockheed Martin\Prepar3D v4.

For example i installed to E:\Addons\Aircraft\A2A where the corresponding xml also is now.

I then installed my RealAir Legacy the same way, of course manually, with adding an xml directly to the RealAir Legacy folder and adding an package entry to the add-ons.cfg under C:\ProgramData\Lockheed Martin\Prepar3D v4.

I personally would like to have my addons together with their corresponding xml's all in my E:\Addons\Aircraft\... and E:\Addons\scenery\... structure. And therefore an option in your tool would be very handy.

Or are there any drawbacks in doing it this way??

 

Thanks!

 

 

 

 

Share this post


Link to post
Share on other sites
10 hours ago, tremor595 said:

Hi Lorby,

would it be possible to implement an option to choose where a new addon's xml will be created, so that it must not be in the user/documents folder. I think at the moment that's the only location where your tool places new xml's? And of course if we could choose a destination folder it would be useful if your tool then also would make an package entry in the add-ons.cfg with the desired path.

Reason i ask is because yesterday i reinstalled my A2A aircraft and their new (again) updated V4 installers let you now choose a preferred installation folder anywhere you like and then also the package and path was added to the add-ons.cfg in C:\ProgramData\Lockheed Martin\Prepar3D v4.

For example i installed to E:\Addons\Aircraft\A2A where the corresponding xml also is now.

I then installed my RealAir Legacy the same way, of course manually, with adding an xml directly to the RealAir Legacy folder and adding an package entry to the add-ons.cfg under C:\ProgramData\Lockheed Martin\Prepar3D v4.

I personally would like to have my addons together with their corresponding xml's all in my E:\Addons\Aircraft\... and E:\Addons\scenery\... structure. And therefore an option in your tool would be very handy.

Or are there any drawbacks in doing it this way??

 

Thanks!

 

 

 

 

Hi,

Currently the Addon Organizer uses the "auto-discover" method of P3D, so your addons will be rediscovered in case that you decide to completely uninstall the sim, including its various config files in "Program Data" and "AppData\Roaming". (the add-ons.cfg for that is in "AppData\Roaming"). So the drawback would be, that should you decide to do the full uninstall, or should the one single add-ons.cfg config file in "ProgramData" get screwed up, you have no reference to the addons that don't have their add-on.xml in "\Documents\...".

Giving the user a choice in which add-ons.cfg he wants to place his addon package is possible, but it is a major rework in quite a few areas. For example, should you decide to "hard code" your add-on.xml like you describe, then it cannot be in "\Documents\Prepar3d V4 Add-ons", otherwise the simulator would discover it twice. So the app has to be made aware of where the add-on.xml actually is in relation to the config file that it was added to, including error message windows etc.
I have evaluated this feature a while back, but decided against it. Still, should I have some time on my hands, I will look into it again.

Best regards

Share this post


Link to post
Share on other sites

Hi Oliver,

I've updated to v1.01 and also have MakeRwys v4.8.2.0. All my FSDT and FB airports are correctly recognised by Addon Organiser.

When I run MakeRwys it creates MakeRwys_scenery.cfg and this does contain all the FSDT and FB airports. But crucially each of the paths in those entries includes \scenery.

This means external programs such as Electronic Flight Bag won't find those airports unless \scenery is removed from the path.

I know this isn't a Addon Organiser problem but I'm trying to work out the best way of excluding \scenery from each of the 11 entries I have. Can each add-on.xml be edited to remove \scenery or will that mess up their loading in P3D?

I'll also ask Pete Dowson about MakeRwys but he's away for a week so thought I'd start here. I've also posted the question in the sticky topic in the P3D forum.

Share this post


Link to post
Share on other sites

Is the updated version working?  The last time I used this P3D would not start it would just CTD.  Had to remove all addons as it kept saying there was no valid scenery.cfg file.  After about 2 hours of removing core files and repairing its working again.

Share this post


Link to post
Share on other sites
1 hour ago, Ray Proudfoot said:

Hi Oliver,

I've updated to v1.01 and also have MakeRwys v4.8.2.0. All my FSDT and FB airports are correctly recognised by Addon Organiser.

When I run MakeRwys it creates MakeRwys_scenery.cfg and this does contain all the FSDT and FB airports. But crucially each of the paths in those entries includes \scenery.

This means external programs such as Electronic Flight Bag won't find those airports unless \scenery is removed from the path.

I know this isn't a Addon Organiser problem but I'm trying to work out the best way of excluding \scenery from each of the 11 entries I have. Can each add-on.xml be edited to remove \scenery or will that mess up their loading in P3D?

I'll also ask Pete Dowson about MakeRwys but he's away for a week so thought I'd start here. I've also posted the question in the sticky topic in the P3D forum.

There appears to be some change affecting discovery from v0.99 where the FSDT/FB scenery's are discovered.

Installed v1.02 and these scenerys are not listed, reverting to 0.99 ( the last install I have available ) all is ok.

I had already removed the extended /scenery path previously from the FSDT/FB entries

Share this post


Link to post
Share on other sites
4 minutes ago, srcooke said:

There appears to be some change affecting discovery from v0.99 where the FSDT/FB scenery's are discovered.

Installed v1.02 and these scenerys are not listed, reverting to 0.99 ( the last install I have available ) all is ok.

Hello Stephen,

not listed where? What simulator?

I have just installed FSDTs Geneva on P3D V3, and I can't detect any issues anywhere with the addon organizer (on 1.02).

- The scenery is visible in the main list
- When exporting the scenery library, this entry doesn't have the \Scenery part.

Right this moment I can't reproduce any of the issues - ??

Best regards

Share this post


Link to post
Share on other sites
11 minutes ago, srcooke said:

There appears to be some change affecting discovery from v0.99 where the FSDT/FB scenery's are discovered.

Installed v1.02 and these scenerys are not listed, reverting to 0.99 ( the last install I have available ) all is ok.

I had already removed the extended /scenery path previously from the FSDT/FB entries

Hi Stephen,

No problems here with 1.02 and my FSDT and FB airports. All correctly identified and included in the exported scenery.cfg although it does contain the \scenery element.

What version of P3D are you running? v3.4 here.

Share this post


Link to post
Share on other sites

My mistake Oliver in not running Makerwys twice after updating AddonManager to v1.02

Even with the additional \scenery path v1.02 with makerwys v4.82 produces the correct output.

Share this post


Link to post
Share on other sites
1 hour ago, sgreen91 said:

Is the updated version working?  The last time I used this P3D would not start it would just CTD.  Had to remove all addons as it kept saying there was no valid scenery.cfg file.  After about 2 hours of removing core files and repairing its working again.

Why didn't you contact me?

Even if you forgot to run the backup process, P4AO automatically makes a backup copy of your original scenery.cfg (and all the other files that it touches) right next to it. So if anything goes wrong, you just delete the broken scenery.cfg and revert back to the original by renaming the "scenery.cfg.orig" back to "scenery.cfg".

Best regards

Share this post


Link to post
Share on other sites
6 hours ago, Lorby_SI said:

Hi,

Currently the Addon Organizer uses the "auto-discover" method of P3D, so your addons will be rediscovered in case that you decide to completely uninstall the sim, including its various config files in "Program Data" and "AppData\Roaming". (the add-ons.cfg for that is in "AppData\Roaming"). So the drawback would be, that should you decide to do the full uninstall, or should the one single add-ons.cfg config file in "ProgramData" get screwed up, you have no reference to the addons that don't have their add-on.xml in "\Documents\...".

Giving the user a choice in which add-ons.cfg he wants to place his addon package is possible, but it is a major rework in quite a few areas. For example, should you decide to "hard code" your add-on.xml like you describe, then it cannot be in "\Documents\Prepar3d V4 Add-ons", otherwise the simulator would discover it twice. So the app has to be made aware of where the add-on.xml actually is in relation to the config file that it was added to, including error message windows etc.
I have evaluated this feature a while back, but decided against it. Still, should I have some time on my hands, I will look into it again.

Best regards

Thanks for detailed explanation!

So if I sort things the "hard code" way I should regularly backup the add-ons.cfg from ProgramData so I can copy it back after a P3D reinstall and I'll have everything in place again.

I will think about both options again but it seems the hard code way offers less restricted folder order or xml placement.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now