by Steve Waite » Sun Nov 26, 2017 8:49 am
...so from the top...
In the add-on.xml:
C:\Users\ptima\Documents\Prepar3D v4 Add-ons\FSLabs\add-on.xml
see the line:
<Path>SimObjects/Airplanes</Path>
must point to the folder with the aircraft
so it should look like this
<Path>SimObjects\Airplanes</Path>
with the backslash becdause it is this folder:
C:\Users\ptima\Documents\Prepar3D v4 Add-ons\FSLabs\SimObjects\Airplanes
as you can see the backslash between SimObjects\Airplanes is how things should look.
then you run P3D and it makes an entry in:
C:\Users\ptima\AppData\Roaming\Lockheed Martin\Prepar3D v4\add-ons.cfg
the entry looks like this, may be a different package number:
[Package.3]
PATH=:\Users\ptima\Documents\Prepar3D v4 Add-ons\FSLabs\SimObjects\Airplanes
ACTIVE=true
REQUIRED=false
If you don't have that then it won't work properly.
It's not straightforward and I see a lot of confusion and errors in installs around this area. I have dozens of aircraft installed like that all work great, like your A2A.
About that foreslash, did the FSLabs installer do that or have you edited that? If it's the installer makes that line then you need to report the problem to FSLabs.
software architect at codelegend.com
equipment: i9-9980Xe 64GB 2xRTX2080ti NVLink 2TB M.2 NVMe,
i9-9900X 64GB RTX2080ti 2TB M.2 NVMe, i7-3960X 32GB GTX680 4TB RAID10,
NAS @7TB RAID10 (16TB)