• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v2 Addon EULA

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,699
Country
netherlands
Hi all,

I came across this announcement by Leborsim:

https://m.facebook.com/story.php?story_fbid=638388479547316&id=182534921799343&refid=17

This makes me wonder, are other developers changing their EULA for the products they make? Many fsx addons are for entertainment use only. Do you extend the EULA to also allow professional usage in P3D v2 or do you still only allow entertainment usage?

And please keep this thread about the license of your addon, there are enough discussions already about the P3D licence and whether we can use it as a game.
 
Arno,
I will only do a refer to the simulator licence. This seems to be at least save for European based software.
Something similar in the process to 9002 certification.
 
If we can't discuss the EULA for P3D here then it makes sense to me that we should not do the same for products trying to "make it legit in P3D" for them. I'm taking bets on the side for how many replies get made before this one locks up.
 
My EULA has stayed pretty much the same, but it has never been an 'entertainment' license, just a 'single-user, non-commercial' license. Nothing has change with P3D.

Commercial users have always been able to purchase a suitable license, and they still are expected to with P3D. However I get to decide the criteria for this, based on each case. So an aero club which runs P3D or FSX as a training aid may be able to get a suitable license at no additional cost, but a flight school might require a different license, allowing them to have as many installations as they require, plus relevant support, but at an additional cost.

It's my belief that the Universe wants us to have a great sim experience, Lockheed Martin want that too, and I certainly want that.

I look at 'armchair law' as a hobby similar to simming, and there are people who have both these hobbies, but they shouldn't try and combine them:)
 
I'm not certain I agree with the views expressed in the link. However, we are discussing licences and any developer is surely entitled to include whatever terms it wishes in its EULA.

Insurers might perceive an increased risk if an add-on is used commercially rather than by consumers. I can't speak for other countries, but in the UK practically all businesses take out public liability insurance and many will also take out product liability indemnity insurance. Premiums may changes iuf a product is sold for business as well as consumer use.
 
Milviz makes no declaration one way or another. "Usage" is not restricted nor is it defined in any fashion whatever. For example:
End User License Agreement

By purchasing the MilViz B737-200 you are consenting to be bound by and agree to the following:

DOCUMENTATION: Full documentation for the B737-200 is included in the aircraft folder's ..\Manuals subfolder. Please read the manuals before asking for support.

COPYRIGHT
Copyright (c) 2013 Military Visualizations (MilViz). MilViz retains FULL copyright on the entire B737-200 package.

DISTRIBUTION
You may NOT redistributed the MilViz B737-200 in whole or in part. Any such distribution is strictly prohibited.

GRANT OF LICENSE
You are granted a limited license to use the MilViz B737-200. This does NOT give you the license to modify in anyway part or whole based on the designers original work except for your own personal use. You MAY of course use the Paintkit provided to create new liveries for public distribution, provided no *charge* is made for them!

----------------------------------------------------------------------------------------
NOTE: This aircraft requires Windows XP, Vista, or Win7 OS with DirectX 9.0C/DX10.0, and FSX/SP2 or FSX/Acceleration or Prepar3Dv1.4
----------------------------------------------------------------------------------------

DISCLAIMER
MilViz and all associates shall NOT be held responsible for any damages arising from the use of the B737-200 product.

Copyright © 2013 Military Visualizations, All Rights Reserved.

The only "restriction" is really just a "Standard Disclaimer" for the GPS units provided which states:
This manual is intended for use in FSX or Prepar3D ONLY and may NOT be used in any Real World Aviation application. The authors are not responsible for errors or omissions.

I simply cannot fathom why some are insistent on making a mountain out of a molehill... :rolleyes:
 
May be my question in not directly to the issue of P3D V2 but it is related to EULA.

Do you have a standard EULA that I can follow? Since I'm not an English speaking person and EULA is quite a legal language.

Moreover, if you have a settle with this issue, it would be nice if you can have a standard EULA that fits to EULA of P3D V2.
 
An EULA really depends on what you want it to achieve. Different people have different requirements, and different laws apply.

It has to be a bit of a compromise, too complicated and people will not even bother to read it (I suspect that about 90% of users don't read it at all.)

It can be used to limit your liability, but this depends on where you live -- here in New Zealand, certain liability can't be limited by agreement (mainly consumer rights), but then again you are not going to be sued because someone did something stupid with your product. You won't find people suing MacDonalds when they spill their own coffee, for instance.

I just make a list of things I don't want people to do with my scenery. The main goal is to stop the sort of unscrupulous behaviour which some people think is ok, such as packaging something up and selling it as your own, just because you think you can get around the EULA, or the EULA isn't that clear.

People will take advantage of anything, if you are not careful. I once gave a free license to a commercial simulator company, with the agreement that they promote my scenery to some extent. They promptly sold the business and charged the new owners a monthly fee for my scenery. At some stage they were making more money from my scenery per month than I was.
 
The key, to avoid getting into an argument about what is, what isn't, who can, who can't is quite simple.

Either the product is licensed for commercial use, or it is licensed for personal use. By choosing those directions, one doesn't have to get into 'training', 'learning', 'playing' etc.
 
The key, to avoid getting into an argument about what is, what isn't, who can, who can't is quite simple.

Either the product is licensed for commercial use, or it is licensed for personal use. By choosing those directions, one doesn't have to get into 'training', 'learning', 'playing' etc.

If only it were that simple. The complexities of various licenses available that are recognized in various countries makes that a "complicated to achieve" statement. Not that I dont agree with you, on the contrary, however it is a dreamworld scenario.
The EULA only encompasses what the creator/owner wishes to be conveyed. Licensing on top of the EULA makes it complicated. P3D for example has an EULA that has licensing to back up what they allow and dont allow. What other developers have applied to their products is really protected by the associated license, not just the EULA.
 
Last edited:
Back
Top