jrhoads

Sorry. EU law doesnt trump US law unless it is international. This thread is not going to anyone any good and personally, it should not be left to stand. This is nothing but a powder keg that no one will win over.

Jeff, right you are. Plus add the fact that if we turn off the activation for the product it is essentially of no use. So those that are entertaining the thought of reselling software, it would be good to keep these things in mind. This business is as a few others noted, small, competitive (in that small space) and long development cycles with generally marginal returns. Add the fact that there is indeed piracy and others that believe if they bought a product once, they have the right to install it or transfer it into any other platform they deem. So, in the EU, this might apply, but as Jeff says.... we don't have to support them. Look deeper into that statment and I think you will find our position.

The product is licensed for use in FSX only. Avsim? this topic should not proceed any further.

Hi Bo, There are some products that will indeed be ported over to P3D, and others that won't. Those that do, are sold through Flight1 Aviation Technologies.That is the company the produces products that lend themselves to a "true" academic or professional environment. So it isnt about being kind, disrespecting any loyalty or anything like that, its about our business model and how we view the P3D licensing requirements. We take those requirements seriously, and at face value. Others may not, but we do. So as noted earlier, some will be available for the P3D platform with respect to training, professional and R&D use. Others will not. And last but not least, we certainly do care and I do care about your concerns. But its not that simple Regards, Jim

The Flight1 Mustang is not licensed or supported for use in P3D.

Answered in the Mustang forum Chris and a personal message to you as well... We will figure it out.

There is a demo version available now: http://flight1.100megabyte.com/instant_object_studio_demo.exe

Sounds like you will have many other options available for that.... Jim

Thanks Jacoba, It wont be less I can assure you.... Regards, Jim

Seeing how we own all the code to the Aeroworx King Air and "Yoda" who was instrumental in the success of the original Aeroworx King Air is co-managing the project with me... I think its safe to say we will surpass "near it" Jim

Your accusations are not only un-true, but postured to make your position and your tool more acceptable than the developers policies and licensing requirements. Very well.. as you wish.

Nice try. But you cannot lay the burden on developers as the issue. the real issue comes down to the intended usage of P3D and the user. Its not my business to tell you what to buy and how to use it, but the P3D academic version is very clear that it is not for entertainment. Whether or not they enforce it again is not my business. But, because I run a business and sell software that can be used on that platform, you better believe I will posture our policy toward respecting the legal terms of the agreement. So lets be very clear... P3D IS NOT a migration of FSX. It may be based off of it, it may run a lot of the same products, but it IS NOT a transition or migration in the same manner as FS2004 was to FSX. It is a new product, a new developer and a new license. The fact that someone wants it to be a migration does not mean it is and it is not at the feet of the developer to do a "wink wink" and act like nothing has changed and allow straight out compatability ports without respecting the terms of the legal agreement. This is not arm chair lawyer vergbage, this is real licensed terms and I will respect those terms. I still contend that this tool opens up the ability to bypass those terms if a person so chooses. And that affects all developers.

Yeah, what do I know...Silly me... :Whistle:

So essentially you are saying that it doesnt matter what the licensing requirments or position of the developer is, you will do what you want. But keep in mind that this is counter-productive. Because the least the developer is respected in thier position, the more they will do to protect thier products from being used outside of the licensing requirements.

Apparently you and a couple of others did not understand the point of my message. I said nothing about a EULA. You did, not me. My point of licensing is with the 3rd party vendor / developer. If the 3rd party vendors / developers product is licensed for FSX and not licensed for P3D, and you install it into P3D via any other means other than an official P3D installer offered by the developer than it is not only not supported, but not licensed either. Agree or not, that is my position.

Nobody slandered anyone. Not in the slightest sense. if you thought so, the post was revised to make it seem less personal and more generic. But my point remains and I stand by it.

Explain to me why anyone would be willing to pay for a new simulator based off off an existing simulator, yet expect to pay nothing to migrate an existing add-on to the simulator they were williing to pay for? And why would anyone be willing to pay for a product that allows them to not pay for a product ? I will rephrase not acceptable. If someone installs an FSX product licensed for FSX into P3D and not licensed for P3D, it is piracy. Clear enough?

Keep in mind that some developers do not approve of FSX to P3D installations without proper licensing to accomplish that. Although a clever concept, it may not be acceptable depending on the product or the developer. In other words, it could be considered a "hack" tool in certain instances. I cannot speak for Lockheed Martin, but I know they are sensitive to 3rd party licensing as noted above and I personally could not see them endorsing this if violations occur as a result.

Yes, a service pack will be out very shortly and addresses things found and "verified" and a couple of other extra things thrown in for good measure. Nothing is ever bug free. Look at Windows. Windows updates come out weekly or sometimes even more so. The idea that every computer, and every configuration and every method of testing arrives at perfection in a release just doesnt happen as perfect as anyone including us want it to be. But we always deliver and that is what makes Flight1 an "always" safe purchase.

One thing of note. Just like the Mustang, our 162 Skycatcher was done in official partnership with Cessna.

You assume too much.Mods? Please lock this as we have stated our position.

We have made our position clear.

And expounding on what Steve says, it really is not reasonable to assume that one product designed and purchased for use in FSX can be installed into a different platform without compensation to the developer / publisher and the incurred support issues as a result of that. Even more so, we take the Prepar3D licensing at face value, and our (Flight1 Software) products are designed / marketed as entertainment based products. Flight1 Aviation Technologies on the other hand fit the role and purpose as well as licensing of Prepar3D and are fully supported as such. Flight1 Softwares products are not. So Bottom line? Flight1 Software does not support the use of our products in Prepar3D.Further more as per our EULA:The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed, not sold.1. GRANT OF LICENSE. This EULA grants you the following rights:- Installation and Use. You may install and use one copy of the SOFTWARE PRODUCT.

Sorry, to burst the bubble, but no food fight here. A simple fact that I can represent myself and prefer too. And just because one dev says it, doesnt mean its necessarily so.I have been doing this as long if not longer than anyone in the business, and have seen a lot over the many years and versions. I see nothing that alarms me or would cause me to take MS to the wood shed.At the end of the day, it's a simulator gents. Nobody has a gun to anyones head and I have learned over the years that if you dont agree or embrace something, you put your hat on and get more clever.