The "Esellerate" ( which is only the sale provider, btw ) doesn't have anything to do with the interaction between the Migration tool or the fact an installer recognize P3D V2.
Since you are posting this in the Cloud9 area, I guess you are asking about Cloud9 products. FSDT product don't obviously need to do anything special, they just work in P3D2, provided you use their latest installer.
As with ANY (not just FSDT-specific) product that HAS a proper P3D installer, you must disable the Migration tool. This also doesn't have anything to do with the protection but, rather the fact the migration tool tries to fool installers and software they are running under FSX, which obviously confuse proper P3D products that check for P3D explicitly.
So, your issues are just Cloud9, and right now, Cloud9 installers are not updated for P3D2, and we don't plan to update them, not at least those that don't have an FSDT installer already.
However, you should be able to run them in P3D V2 doing the following:
- Install them in FSX, if you still have it installed. Or, use the Migration tool, but JUST for the installation.
- After all the sceneries are installed, download and install the current Stand-Alone Addon Manager for FSX/P3D, which supports P3D2 and will update whatever is needed to be updated. Keep the Migration tool DISABLED in this case.
So, basically, the rule is very simple:
- If you are installing a product that knows about P3D (everything from FSDT right now), DISABLE the Migration tool
- If you are installing a product that doesn't know about P3D, INSTALL with the Migration tool enabled.
After you installed AND updated the Stand-Alone Addon Manager as the last thing you do, which is not needed if you install something from FSDT AFTER Cloud9, you should keep the Migration tool DISABLED, at least the Legacy mode, which changes the executable file version, and this prevents our stuff to run, because we need to identify precisely the simulator main .exe so, a faked .exe (P3D.EXE with FSX version info) won't work.