Hello,
I updated the Client and Content to p3d v4.2. Unfortunately this has removed the airplanes from the simulator although the addon folder outside of the prepar3d folder is still present. Thus, I suspect that a link has gone missing somehow. Any advice on how to re-activate the aircrafts? I tried to remove them completely and do a fresh installation but it did not bring them back in the simulator.
This is what I see in the cfg file:
[Package.0]
PATH=F:\Prepar3D v4 Add-ons\A2A\
TITLE=A2A P3D Add-Ons
ACTIVE=true
REQUIRED=false
whereas in the addon folder I have the attached structure including also a sub A2A folder:
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
<AddOn.Name>A2A</AddOn.Name>
<AddOn.Description>Aircraft by A2A Simulations Inc.</AddOn.Description>
<AddOn.Component>
<Category>Effects</Category>
<Path>Effects</Path>
</AddOn.Component>
<AddOn.Component>
<Category>Fonts</Category>
<Path>Fonts</Path>
</AddOn.Component>
<AddOn.Component>
<Category>Gauges</Category>
<Path>Gauges</Path>
</AddOn.Component>
<AddOn.Component>
<Category>Scripts</Category>
<Path>Scripts</Path>
</AddOn.Component>
<AddOn.Component>
<Category>SimObjects</Category>
<Path>SimObjects\Airplanes</Path>
</AddOn.Component>
</SimBase.Document>
Kind regards
Brian
P3D v4.2 all A2A aircrafts don't show after update
Re: P3D v4.2 all A2A aircrafts don't show after update
Hi Brian,
You can check this thread here:
http://a2asimulations.com/forum/viewtop ... 9d#p480924
I believe the solution is to remove the \ after A2A here - PATH=F:\Prepar3D v4 Add-ons\A2A\
Cheerz,
Will
You can check this thread here:
http://a2asimulations.com/forum/viewtop ... 9d#p480924
I believe the solution is to remove the \ after A2A here - PATH=F:\Prepar3D v4 Add-ons\A2A\
Cheerz,
Will
Bonanza, Skylane, Skyhawk, Cherokee, Cub, Texan, Mustang, Warhawk, Spitfire, Flying Fortress
- Nick - A2A
- A2A Captain
- Posts: 13734
- Joined: 06 Jun 2014, 13:06
- Location: UK
Re: P3D v4.2 all A2A aircrafts don't show after update
Yes, it does seem like a manual edit to the relevant "add-ons.cfg" in the "ProgramData" directory is required. Sounds like Brian is all sorted, and once I've done a bit more testing (and hopefully heard from L-M) I'll post more details of the workaround.
Thanks,
Nick
Thanks,
Nick
Who is online
Users browsing this forum: No registered users and 12 guests