• 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.

FS2004 FS9 SDK docs -> Wiki

Heretic

Resource contributor
Messages
6,830
Country
germany
Would anyone mind if the documentation for the FS9 SDK ends up in the wiki here?


People, when developing, tend to have their web browser open anyway (for looking at reference pictures/videos/documents) and getting rid of the necessity to have MS/Open/Libre Office open to look at the SDK documentation would improve workflow and computer resource usage.
Also, the formatting would be better (no Times New Roman).


Alternatively, what about converting the documents into .pdf format (with Arial) and putting them up here separately?
 
I think that would be a good idea. I second that.

Also, can we 'perhaps' also make a list of the tons of XML codes; command strings, data strings, etc. So many of these are 'not' in the main SDK. For gauge and custom animations, this would be extremely useful to extremists.



Bill
 
I'm in favor for a general "Useful XML bits" entry, similar to the section on FFDS.
 
Err ....

Microsoftâ Flight Simulator 2004:
A Century of Flight
Software Development Kit

© 2003 Microsoft Corporation. All rights reserved.
 
© 2003 Microsoft Corporation. All rights reserved.

The information contained within the documentation will not be altered, so I really don't see the problem.

It's just like hosting the SDKs themselves here instead of on the MS homepages...
 
Last edited:
Hi,

As long as the documentation is exactly like the sdk, we do not see a problem with putting them on the wiki. So I think providing them as a PDF or so on the wiki would be best, since a normal wiki page could be changed from the version that Microsoft provided.
 
Tried to upload a bunch of the documents (in .pdf format) in a .zip, but the "Add File" page gives me an "upload failed" error.
 
Hi,

Let me check. I think there might be restrictions what you can upload. Else you can email them to me and I will upload them to the server.
 
Well, .zip files are an accepted format for a start.
Size-wise, the docs weren't too much either.

Hmm...a dislike for Opera and/or Linux?
 
*Bump*

I've uploaded the .pdfs to my Drive account, so you can read and download them at will.

-> Link <-


Better late than never, I guess.
Hope someone finds them useful.


Also, no harm intended MS.
Word documents are horribly out of date though...
 
You better contact MS first. This is a copyright work. Even posting on a wiki page verbatim is still controlled by the copyright and permission need be obtained. You can not copy or redistribute their entire document without facing some legal recourse. The generally accepted limit is 23 to 25% of the work before it becomes infringement.

All the information you need to determine what is allowed is in the EULA and the copyright documents.

You can provide links to the documents if its hosted on a MS source, that is legal, but copying the doc's verbatim or altering to post is illegal. You can request permission from MS.

There may be a Fair Use release on the docs since they are aged, but IDK.

EDIT: Currently researching to confirm what can be done with the docs

FOUND: http://www.microsoft.com/en-us/legal/intellectualproperty/Permissions/default.aspx

In the EULA for FS9
"Reservation of Rights. All rights not expressly granted are reserved by Microsoft."

Again, the EULA
IMPORTANT—READ CAREFULLY: This Microsoft End-User License Agreement (“EULA”) is a legal agreement between you (either an individual or a single entity) and Microsoft Corporation for the Microsoft software product identified above, which includes computer software and may include associated media, printed materials, and “online” or electronic documentation (“SOFTWARE PRODUCT”). The SOFTWARE PRODUCT also includes any updates and supplements to the original SOFTWARE PRODUCT provided to you by Microsoft. Any software provided along with the SOFTWARE PRODUCT that is associated with a separate end-user license agreement is licensed to you under the terms of that license agreement. By accessing or otherwise using the SOFTWARE PRODUCT, you agree to be bound by the terms of this EULA. If you do not agree to the terms of this EULA, do not use the SOFTWARE PRODUCT; you may, however, return it to your place of purchase for a full refund.
6. COPYRIGHT. All title and copyrights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, animations, video, audio, music, text, and “applets” incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, and any copies of the SOFTWARE PRODUCT are owned by Microsoft or its suppliers. All title and intellectual property rights in and to the content which may be accessed through use of the SOFTWARE PRODUCT is the property of the respective content owner and may be protected by applicable copyright or other intellectual property laws and treaties. This EULA grants you no rights to use such content. If this SOFTWARE PRODUCT contains documentation which is provided only in electronic form, you may print one copy of such electronic documentation. You may not copy the printed materials accompanying the SOFTWARE PRODUCT.

Now there is a limit, and its displayed in the EULA for each portion of the SDK.

Ohh and another sidewall. EULA for the BGLComp SDK
GRANT OF LICENSE. This EULA grants you the following rights:

· Applications Software. You may install, access and run (“RUN”) the SOFTWARE PRODUCT on an unlimited number of computers, including workstations, terminals or other digital electronic devices ("COMPUTERS") to design, develop, and test software application products that are designed to operate in conjunction with Microsoft Flight Simulator 2004: A Century of Flight and subsequent versions thereof (“Application”).
· Sample Code. You may modify the sample source code located in the SOFTWARE PRODUCT’s “samples” directories (“Sample Code”) to design, develop, and test your Application. You may also reproduce and distribute the Sample Code in object code form along with any modifications you make to the Sample Code, provided that you comply with the Distribution Terms described below. For purposes of this section, “modifications” shall mean enhancements to the functionality of the Sample Code.
· Redistributable Code. You may reproduce and distribute portions of the SOFTWARE PRODUCT designated as “Redistributable Code” identified as the “BGLC.EXE,” “BGLPLACER.EXE,” “BGLCOMP.EXE,” and “TRAFFICINFO.DLL” files and other files which may be identified in the text file LICENSE\REDIST.TXT. You may redistribute the Redistributable Code with your Applications provided that you comply with the Distribution Terms described below.
· Reservation of Rights. All rights not expressly granted are reserved by Microsoft.

2. DISTRIBUTION TERMS. You may reproduce and distribute an unlimited number of copies of the Sample Code and/or Redistributable Code (collectively "REDISTRIBUTABLE COMPONENTS") as described above, provided that (a) you distribute the REDISTRIBUTABLE COMPONENTS only in conjunction with, and as a part of, your Application; (b) your Application adds significant and primary functionality to the REDISTRIBUTABLE COMPONENTS; (c) the REDISTRIBUTABLE COMPONENTS only operate in conjunction with Microsoft Flight Simulator 2004: A Century of Flight and subsequent versions thereof; (d) you distribute your Application containing the REDISTRIBUTABLE COMPONENTS pursuant to an End-User License Agreement (which may be “break-the-seal,” “click-wrap” or signed), with terms no less protective than those contained herein; (e) you do not permit further redistribution of the REDISTRIBUTABLE COMPONENTS by your end-user customers; (f) you do not use Microsoft's name, logo, or trademarks to market your Application; (g) you include a valid copyright notice on your Application; and (h) you agree to indemnify, hold harmless, and defend Microsoft from and against any claims or lawsuits, including attorneys' fees, that arise or result from the use or distribution of your Application.

3. DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS.

· Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, or disassemble the SOFTWARE PRODUCT, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation.
· Rental. You may not rent, lease or lend the SOFTWARE PRODUCT.
· Trademarks. This EULA does not grant you any rights in connection with any trademarks or service marks of Microsoft.
· Software Transfer. You may permanently transfer all of your rights under this EULA, provided you retain no copies, you transfer all of the SOFTWARE PRODUCT (including all component parts, the media and printed materials, any upgrades and this EULA) and the recipient agrees to the terms of this EULA. If the SOFTWARE PRODUCT is an upgrade, any transfer must include all prior versions of the SOFTWARE PRODUCT.
· Termination. Without prejudice to any other rights, Microsoft may terminate this EULA if you fail to comply with the terms and conditions of this EULA. In such event, you must destroy all copies of the SOFTWARE PRODUCT and all of its component parts.

4. COPYRIGHT. All title and intellectual property rights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, animations, video, audio, music, text, and “applets” incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, and any copies of the SOFTWARE PRODUCT are owned by Microsoft or its suppliers. All title and intellectual property rights in and to the content which may be accessed through use of the SOFTWARE PRODUCT is the property of the respective content owner and may be protected by applicable copyright or other intellectual property laws and treaties. This EULA grants you no rights to use such content.

This is clearly written, you can supply sample code, modified sample code, modified code, but not the entire works, meaning according to my interpretation, you can not copy the SDK or provide it without permission from MS.

Im still looking to see if MS has it posted on their servers.
The only way to get the documents it download the SDK and install it (Only legal way). Unless its classified under Fair Use (doubtful) or for a licensed School project, its bound by the copyright.
http://support.microsoft.com/kb/555857

The FSX and ESP below
http://msdn.microsoft.com/en-us/library/cc526948.aspx
http://msdn.microsoft.com/library/ff798293.aspx
http://www.microsoft.com/Products/Games/FSInsider/developers/Pages/default.aspx
 
Last edited:
"Also, can we 'perhaps' also make a list of the tons of XML codes; command strings, data strings, etc. So many of these are 'not' in the main SDK. For gauge and custom animations, this would be extremely useful to extremists.
Bill"


Hello all,

This one would be great for a lot of us.
And "out" of any EULA.




Daniel.
 
Would anyone mind if the documentation for the FS9 SDK ends up in the wiki here?
...what about converting the documents into .pdf format (with Arial) and putting them up here separately?
Microsoft would mind. They hold the copyright.

Also, can we 'perhaps' also make a list of the tons of XML codes; command strings, data strings, etc. So many of these are 'not' in the main SDK. For gauge and custom animations, this would be extremely useful to extremists.
Copying the codes is fine, as samples are permitted. The full SDK docs outside the MS distributed method, not so much.

I'm in favor for a general "Useful XML bits" entry, similar to the section on FFDS.
Useful XML bits would be fine if its from the SDK, as long as its not the entire document.

So, in one year, the copyright should expire and 'then' we can put them up. :)
Not even close to being true. We wish.

The information contained within the documentation will not be altered, so I really don't see the problem.
It's just like hosting the SDKs themselves here instead of on the MS homepages...
It may not look like a problem, but getting the docs requires installing the SDK. They are not available from MS separately. MS EULA does not permit distributing the software separately from the docs. Just because it is not explicitly stated 'You can not do this' doesnt mean its legal. Its their property, and they will protect it. It may be OK to host the SDK, so long as you abide by the terms of distribution and copyright by MS, but it has limits.

Hi,

As long as the documentation is exactly like the sdk, we do not see a problem with putting them on the wiki. So I think providing them as a PDF or so on the wiki would be best, since a normal wiki page could be changed from the version that Microsoft provided.
Actually, hosting it here is violating the EULA and the copyright. I would advise getting permission. Its not hard, and I provided the link in my other post. Whether modifying it or not, its protected.

Hi,

Let me check. I think there might be restrictions what you can upload. Else you can email them to me and I will upload them to the server.
Wouldnt upload separately without getting permission first.

"Also, can we 'perhaps' also make a list of the tons of XML codes; command strings, data strings, etc. So many of these are 'not' in the main SDK. For gauge and custom animations, this would be extremely useful to extremists.
Bill"


Hello all,

This one would be great for a lot of us.
And "out" of any EULA.
Daniel.
This would not be outside the EULA. If its from the SDK documentation, its covered under the EULA and copyrights. If its code samples, its legal. If its verbatim and full, its infringement.

My information is in the SDK EULA, FS EULA and MS copyright information available on their website and in the SDK's.
If I missed something point it out.
 
FYI: IIRC, within the last year MS gave hosting permission to FSDeveloper and AVSIM for all FS SDKs and the accompanying docs. ;)

http://www.fsdeveloper.com/forum/downloads.php?do=cat&id=10



MS also 'overlooked' hosting of some or all of same by fsnordic, simviation and fligtsim.com for many years, sometimes even when there had been (minor) but reasonably accurate renaming of the SDK installers which had been repackaged into ex: ZIP files on those FS web sites for free download access. :p



Although FS2004 word *.DOC format files can easily be converted by the end user to *.PDFs or *.CHMs, most info in both the FS9 and FSX SDKs is included in- and viewed more easily via- the enhanced HTML "ESP" online SDK docs at MSDN:

http://msdn.microsoft.com/en-us/library/cc526948.aspx


Hope this info helps individuals establish a perspective based on how MS has actually dealt with dissemination of the SDKs and the "documentation" for same ...over many years ! :)

GaryGB
 
Last edited:
FYI: IIRC, within the last year MS gave hosting permission to FSDeveloper and AVSIM for all FS SDKs and the accompanying docs. ;)
Well that covers it.

MS also 'overlooked' hosting of some or all of same by fsnordic, simviation and fligtsim.com for many years, sometimes even when there had been (minor) but reasonably accurate renaming of the SDK installers which had been repackaged into ex: ZIP files on those FS web sites for free download access. :p
Just because they overlook it, doesn't make it legal. It still suggest to ask permission.
 
If MS has a problem with me converting and Google hosting a few otherwise unaltered docs, they're free to contact me.
 
Back
Top