27 minutes ago, steve40 said:

Only if they are GLOBAL. The ones in the example were WORLD and needed to be declared correctly.

We agree then, if you don't declare them otherwise they will be treated as GLOBAL.

14 hours ago, steve40 said:

I've just gotten around to testing PrecipitFX in P3D v4. PrecipitFX has supposedly been updated recently to support v4 (it now recognizes v4 in the settings panel), but lo and behold, it will only update the aircraft in the main SimObjects folder and does not search for aircraft add-ons in your "Documents\Prepar3d v4 Add-ons" folder or in the add-ons.cfg files. I've emailed a support request to the folks at Old Prop about this.

Hi Steve,

next version of P4AO will have an option to temporary export a complete SimObjects.cfg file, just like it does for scenery.cfg. If it reads that config file, their setup app should be able to find all the aircraft.

Best regards

 

Although I like the addon method - the lack of compatiblity with some 3rd party apps is enough of an issue for me to continue using the 'old way" for the moment.

One of those apps 'Aivlasoft EFB' has come up with a partial workaround

https://forum.aivlasoft.com/index.php?/topic/2531-p3d-v3v4-scenery-located-at-add-onscfg-scenery_add-onsxml/&

42 minutes ago, TonyD said:

Although I like the addon method - the lack of compatiblity with some 3rd party apps is enough of an issue for me to continue using the 'old way" for the moment.

One of those apps 'Aivlasoft EFB' has come up with a partial workaround

https://forum.aivlasoft.com/index.php?/topic/2531-p3d-v3v4-scenery-located-at-add-onscfg-scenery_add-onsxml/&

My Addon Organizer has an option to temporarily create a complete scenery.cfg with the correct layering for the external tool to use.

Next version will do the same for simobjectscfg too.

Best regards

51 minutes ago, Lorby_SI said:

My Addon Organizer has an option to temporarily create a complete scenery.cfg with the correct layering for the external tool to use.

Next version will do the same for simobjectscfg too.

Best regards

Addon Organizer is coming along nicely, I just upgraded from 0.91 to 0.94. The one thing that caught me off guard is that I assumed that the delete button would simply delete the entries from add-on.xml and not delete the actual addon folders! I found out the hard way that that was not the case. Also, the files are permanently deleted rather than put in the recycle bin. Perhaps you would consider adding a button that only removes the addon entry rather than deleting the files, or alternatively, delete them to the recycle bin so nitwits like myself won't have to reinstall the addon if we make a mistake :) Cheers.

34 minutes ago, steve40 said:

Addon Organizer is coming along nicely, I just upgraded from 0.91 to 0.94. The one thing that caught me off guard is that I assumed that the delete button would simply delete the entries from add-on.xml and not delete the actual addon folders! I found out the hard way that that was not the case. Also, the files are permanently deleted rather than put in the recycle bin. Perhaps you would consider adding a button that only removes the addon entry rather than deleting the files, or alternatively, delete them to the recycle bin so nitwits like myself won't have to reinstall the addon if we make a mistake :) Cheers.

Hello Steve,

sorry about that. This should only be possible if add-on.xml and the addon content itself are both in the same subfolder. That is a bit of a vicious circle, because of the auto discovery function of P3D. If I leave the add-on.xml intact, then P3D will just rediscover them, and they are back.

Maybe it would be the best option to always delete the add-on.xml but not the folder (unless it is empty). 

Best regards

 

Hello Oliver

i need an info about one thing

i ve installed the last update ENGM from aerosoft outside v4 directory and with your software i created an addon xml but in simobject i have 3 other folder, should i add these 3 folders too

so i have simobjects -------------->avatars

                                           ---->groundvehicules

                                           ----->misc

thanks

1 hour ago, grandfred29 said:

Hello Oliver

i need an info about one thing

i ve installed the last update ENGM from aerosoft outside v4 directory and with your software i created an addon xml but in simobject i have 3 other folder, should i add these 3 folders too

so i have simobjects -------------->avatars

                                           ---->groundvehicules

                                           ----->misc

thanks

Hello Frédéric,

unfortunately I don't have that addon (well, I have it, but no time to install...).

I would think that you need the simbojects too, yes. Go to the "Other addons" tab, press "Add component". With the drop down at the top choose the addon.xml that you already have for this airport. Then select Category "SimObjects", and "Set Path" to the folders that you have listed above, one after the other. Do the same with any "Effects" or "Sound" folder, if there are those - remember to select the proper category.

After saving, all you content related to ENGM should be in the same add-on.xml - you can check that on the "Packages" view.

Best regards

4 hours ago, Lorby_SI said:

That is a bit of a vicious circle, because of the auto discovery function of P3D. If I leave the add-on.xml intact, then P3D will just rediscover them, and they are back.

For reasons I have already forgot, I had an add-on.xml with one set of components that I wanted to disable.  Being a very old novice programmer I did what I've always done to temporarily remove code: I 'remmed' it out by framing the components inside a <comment> ..</comment> and although P3D still picks up the add-on.xml there is nothing in there to add and there is no error.

Oliver, thank you for your continued dedication to this subject - you are pushing out new versions faster than I can download them.  I really appreciate the v3.+ option in 0.95.

 

Interesting note on autodiscover...

I went back and re-read the SDK notes and I can see how I got confused, but I didn't realize that for the autodiscover feature to work, your "add-on.xml" can be only one directory deep in the "Prepar3D v4 Add-Ons" location.

This line works with autodiscover...

..\My Documents\Prepar3D v4 Add-Ons\KPVD\add-on.xml

This line does not work with autodiscover...

..\My Documents\Prepar3D v4 Add-Ons\Airport Scenery\KPVD\add-on.xml

But - if you manually add the XML addon as a package in the %AppData% scenery.cfg file, you can have the add-on.xml file anywhere you want. In the file..

C:\Users\Greg\AppData\Roaming\Lockheed Martin\Prepar3D v4\add-ons.cfg

(Manually add the entry...)

[Package.0]
Path=C:\Users\Greg\Documents\Prepar3D v4 Add-ons\Airport Scenery\KPVD
Active=TRUE
Required=FALSE

I know this might be understood by a few of you, but I thought writing it down would A.) Help me remember, and B.)Maybe help someone else!

Now that I understand this nuance, I'm going to be able to start working on my scenery structure.

Cheers,
Greg

On 14/06/2017 at 1:18 AM, steve40 said:

I've just gotten around to testing PrecipitFX in P3D v4. PrecipitFX has supposedly been updated recently to support v4 (it now recognizes v4 in the settings panel), but lo and behold, it will only update the aircraft in the main SimObjects folder and does not search for aircraft add-ons in your "Documents\Prepar3d v4 Add-ons" folder or in the add-ons.cfg files. I've emailed a support request to the folks at Old Prop about this.

Good news, I've just received a positive response from Michaël Villeneuve-Normand of OldProp:

Quote

Hi Steve,

Yes we are working to update PrecipitFX that will do that and much more improvement.

 

20 hours ago, Lorby_SI said:

Hello Frédéric,

unfortunately I don't have that addon (well, I have it, but no time to install...).

I would think that you need the simbojects too, yes. Go to the "Other addons" tab, press "Add component". With the drop down at the top choose the addon.xml that you already have for this airport. Then select Category "SimObjects", and "Set Path" to the folders that you have listed above, one after the other. Do the same with any "Effects" or "Sound" folder, if there are those - remember to select the proper category.

After saving, all you content related to ENGM should be in the same add-on.xml - you can check that on the "Packages" view.

Best regards

Yes, the individual SimObjects folders should be added. Setting the path to the root SimObject folder doesn't seem to work.

  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>SimObjects\Avatars</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>SimObjects\GroundVehicles</Path>
  </AddOn.Component>
  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>SimObjects\Misc</Path>
  </AddOn.Component>

Also, I recommend leaving the <Name></Name> field for SimObject blank. In one of my add-ons I added SimObjects\Aircraft and put the name "Aircraft", but when starting P3D I received the error "failed to initialize aircraft...". Simply removing the <Name>Aircraft</Name> entry fixed this error. I'm not sure why that was a problem, maybe a duplicate name in another add-on or something?

4 hours ago, steve40 said:

Simply removing the <Name>Aircraft</Name> entry fixed this error. I'm not sure why that was a problem, maybe a duplicate name in another add-on or something?

The SDK indicates the name property is used only by scenery, and it does have to be a unique name.  Interesting that it doesn't ignore the name property when improperly applied.

5 hours ago, downscc said:

The SDK indicates the name property is used only by scenery, and it does have to be a unique name.  Interesting that it doesn't ignore the name property when improperly applied.

Ah, thanks for that. The Addon Organizer automatically fills the Name field when adding any category, not just Sceneries. I just encountered a problem last night where some global textures wouldn't load, and again I traced it to the Texture category having a <Name>texture</Name> entry. Removing the name fixed the issue, so now I make sure to leave the name field blank. Yeah, it's odd that it causes the category not to load.