Migration tool for P3D v3 released today

[Bruce (a.k.a. brian747) 142]

It has evidently been a more difficult job to upgrade the Migration Tool than anyone expected. To quote the developer -

"Why is it taking so long?

Because Prepar3D v3 brings frustrating amount of changes to the simulator's existing structure. To bring you an example, since the very first version of Prepar3D, its version numbering scheme has looked like this:

1.3.3078.0

1.4.4747.0

2.0.9448.0

2.1.10201.0

2.2.10437.0

2.3.11345.0

2.5.12945.0

First number marks Prepar3D generation (v1, v2). Second denotes subversion within that generation (v1.4 and v2.5). Third is build number (increased with every change) and fourth unused.

Not only Migration Tool, but several other add-ons determined Prepar3D version by checking the third number, which was increased with each new update to the simulator (incl. hotfixes). This proved an easy and convenient way of knowing which simulator we're precisely dealing with. If we needed something do be done when the simulator is v2.2 or newer, we could've simply read the build number, see if it is equal or larger than 10437, and if it was, do whatever needed to be done.

This numbering scheme has been broken with v3. Build number now stands at fourth position:

3.0.10.14945

This may not look like much, but among other things, I traced FSINN's failure to properly run down to exactly this change. Suddenly, when we read the third version number and check it against 10437 like in previous example, we get an incorrect result that the simulator is NOT newer than v2.2, because number 10 is obviously smaller than 10437. This messes up Migration Tool's small internal engine that intercepts add-ons' version queries and alters them as needed.

To overcome this and many other similiar changes, much of Migration Tool has to be rewritten and expanded to adapt to Prepar3D's ever-changing standards."

Not exactly kind of LM, IMO.

But anyway, the first v3 version has now been released:

"I have uploaded a new build of Migration Tool, with FSInn working under all testing conditions:"

http://www.flightsim.ee/products/migration-tool#download

I wait with interest to hear how effective it is!

Cheers,

B.

[J G 927]

This looks promising!

What might be good is if folks record their successes and failures here to save others a load of time working out if an add-on works with this tool or not.

[wain 879]

No migration tool here, only thing that wont work is Alabeo, I am however waiting for proper installers from ORBX & REX.