@hae5904
OH MY GOD I WILL NEED TO PAY MILLIONS OR I AM GOING TO JAIL!
My joke about the "users" being sued is that, well, I thought there was some debate on the fact that a user (not a consumer?) could buy the a Prepar3d licence and have fun.
Again, just a joke.
As for myself, I have seen the Prepar3d SDK and I am following the path I said: Develop on FSX SDK + eventual Tacpack features, and check for P3Dv2 compatibility. From what I have seen, with my workflow and the features I usually include in my plane, there should be full compatibility. If this is not acceptable by the law (and it may well be) then we (freeware developers) should stop developing immediately and withdraw from download anything we did - and this includes FSX stuff.
This has been enforced in the past by some aircraft vendors in specific freeware and payware cases.
By the way, I fail to grasp why a freeware is legally different than payware in terms of copyright enforcement. The argument that being free I am not making money hence I cannot be sued is IMHO false. By developing, say, a realistic simulation of the T-45C I am chopping the potential customer base of a payware project, which should then create a profit, via licensing, to Boeing. Different story would be if I shared my projects privately - and afaik the Internet is anything but private.
Anyway, I'll (try to) continue doing what I am doing - hopefully lawyers of Boeing (T-45C, along with BAe), Lockheed Martin (F-35 and S-3) or Northop Grumman (F-14) are not reading this...
EDIT - Sorry if my comments sounded harsh. I understand the concerns, and I did not want to sound aggressive. Thing is, having read the SDK, the "new features" are basically tied to the Weapons SDK which only applies to the Professional Plus version, which I have no interest to develop for. So, for me, there is literally no change to what I am doing.