I am using the add-on.xml procedure to install my addons outside of P3D v4.1's root directory.  I decided to test with the Alabeo Cessna 207.

 

I put an add-on.xml in the C:\Users\Caleb\Documents\Prepar3D v4 Add-ons\Alabeo folder, and this is what is in it:

 

<?xml version="1.0" encoding="utf-8"?>
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
  <AddOn.Name>Alabeo</AddOn.Name>
  <AddOn.Description>Alabeo Aircraft</AddOn.Description>
  <AddOn.Component>
    <Category>SimObjects</Category>
    <Path>C:\Lockheed Martin\Addons\Alabeo\SimObjects</Path>
    <Name>Sim Obj.</Name>
  </AddOn.Component>
<AddOn.Component>
    <Category>Effects</Category>
    <Path>C:\Lockheed Martin\Addons\Alabeo\Effects</Path>
    <Name>Effects</Name>
  </AddOn.Component>
<AddOn.Component>
    <Category>Fonts</Category>
    <Path>C:\Lockheed Martin\Addons\Alabeo\Fonts</Path>
    <Name>Fonts</Name>
  </AddOn.Component>
<AddOn.Component>
    <Category>Gauges</Category>
    <Path>C:\Lockheed Martin\Addons\Alabeo\Gauges</Path>
    <Name>Gauges</Name>
  </AddOn.Component>
<AddOn.Component>
    <Category>Sound</Category>
    <Path>C:\Lockheed Martin\Addons\Alabeo\Sound</Path>
    <Name>Sound</Name>
  </AddOn.Component>
</SimBase.Document>

 

Is that correct? 

 

This is where I installed the Alabeo C207 to:

 

 

And the C207 does not show up in P3D v4.1's vehicle list.

 

Am I doing something wrong or skipping a step?

 

Thanks in advance.

 

What do you have in the SimObjects folder?  If you have a folder called Airplanes which in turn contains the actual aircraft folder, then the simobjects entry in the addon.xml file has to point to the Airplanes folder (not the Simobjects folder).

That was it.  I was thinking since the category was "SimObjects" then the path would be to the SimObjects folder.

 

Thanks a lot.

1 hour ago, caleb1 said:

That was it.  I was thinking since the category was "SimObjects" then the path would be to the SimObjects folder.

 

Thanks a lot.

Be careful with your Name tags..., review the SDK documentation.  I believe only Scenery category uses name and that name must be unique.  As lzamm pointed out, the path provides P3D a reference to a location that must include the objects not more than one folder or layer down.  This is consistent with paths in scenery.cfg pointing to the folder that contains both scenery and texture subfolders, the process will look down one layer to find the referenced object.

1 hour ago, downscc said:

Be careful with your Name tags..., review the SDK documentation.  I believe only Scenery category uses name and that name must be unique.  As lzamm pointed out, the path provides P3D a reference to a location that must include the objects not more than one folder or layer down.  This is consistent with paths in scenery.cfg pointing to the folder that contains both scenery and texture subfolders, the process will look down one layer to find the referenced object.

Ok.  I will keep that in mind.