This is just too good of an aircraft to let it go into mothballs. I followed pemigris' instructions on pg 2, (mostly) and believe I have a simpler solution (if you have P3Dv4) on getting it installed into P3Dv5. (You should already have it installed in P3Dv4) It works great, but one concern is the instrument panel (in v5) is a bit blurry, (mip or nomip selected). I haven't tested it, but even if you don't have P3Dv4, there might be a way to get it to work for you also, (see below).
THANK YOU Pemigris for the instructions on pg 2! I had everything except for the entry in the dll.xml file.
Instead of copying the Vertx DA62 folder from v4 into v5, I simply created Vertx DA62 folder in the P3Dv5 Add-Ons and then created a "add-on.xml" file that simply pointed to the existing DA62 folder in P3Dv4 Add-Ons. This way, I can make changes to the DA62 using the config program and it will carry over into P3Dv5. Also, your not eating up disk space duplicating the aircraft twice.
my "add-on.xml" file looks like: (of course, substitute my name for yours...)
<SimBase.Document Type="AddOnXml" version="4,0" id="add-on">
<AddOn.Name>Vertx DA62</AddOn.Name>
<AddOn.Description>Vertx DA62</AddOn.Description>
<AddOn.Component>
<Category>SimObjects</Category>
<Path>D:\Terry\Documents\Prepar3D v4 Add-ons\Vertx DA62\SimObjects\Airplanes</Path>
</AddOn.Component>
<AddOn.Component>
<Category>D:\Terry\Documents\Prepar3D v4 Add-ons\Vertx DA62\Effects</Category>
<Path>Effects</Path>
</AddOn.Component>
<AddOn.Component>
<Category>D:\Terry\Documents\Prepar3D v4 Add-ons\Vertx DA62\Fonts</Category>
<Path>Fonts</Path>
</AddOn.Component>
<AddOn.Component>
<Category>D:\Terry\Documents\Prepar3D v4 Add-ons\Vertx DA62\Scripts</Category>
<Path>Scripts</Path>
</AddOn.Component>
</SimBase.Document>
In experimenting, I was able to "install" the aircraft into any folder of my choice. For those without v4, First create a blank Prepar3D v4 folder. Thensimply run the install program and choose that folder to install to. Then follow Pemigris's instructions on pg 2 of this thread. MAKE SURE YOU EDIT THE "add-on.xml" FILE APPROPRIATELY!
