My scenery re-uploaded by another, at another website...

[Shaka 2]

Hi all,I was perusing another flight sim site yesterday, and came across a very large file (377 MB) of Thailand scenery. Since I am an avid Thailand scenery designer, I downloaded it to take a look. Imagine my surprise to discover that the work was my own, as well as some scenery made by Jan Martin.Anyway, I emailed the webmaster, and asked that the file be removed. Keep in mind that this isn't a case where someone simply leeched a file from AVSIM, and re-uploaded it. The "uploader" took the time to take all the scenery and texture files from several exisiting archives, and re-zip them into one package. There are numerous problems with this, but the primary one was that he also removed all of my readme files, and then created his own, giving himself credit.That's the part that really gets me - I did all the work (... and Jan Martin), so I at least deserve to have my name on there somewhere. Anyway, I'm sure the webmaster will remove it.Meanwhile, 285 GB of bandwdith has been lost to this other website (based on 755 downloads). Also, the offender uploaded the scenery as FS2002 scenery, when in fact most of it was specific to FS2004, which leads me to suspect that he never actually used the scenery. He is just a re-packager.Whatever your personal feelings towards EBay selling, or Leech sites are, you have to agree that taking other peoples work and re-uploading it as your own is going too far. I think that this guy thought he was being helpful and wanted to contribute somehow, but this can cause problems for me as a scenery designer. Hopefully, the webmaster will educate his minions through his forum, and all will be well. It behooves us to check other websites occaisionally for this sort of thing.- Martin

[LuisFelizTirado 33]

I have seen it here as well, Martin. In particular, I remember a library of ship objects that is nothing more than a compilation of work by various other people. In this case, the person who put the package together did not hide the names of the original authors, but I doubt whether he got permission from them to do this. The package is still in the library, I believe. And this sort of thing is all too common, though infrequent.Also, some "commercial" scenery designers release packages where they use freeware textures by other authors. What is particularly annoying is that the texture authors specifically mention that these textures are not to be used in commercial scenery (Nova, Jorge Pagano). This has notably appeared in scenery packages for my part of the world, which is why I have noticed it, since generally I do not download other people's scenery.A most regretable practice overall. Flightsim specifically mentions authors' rights in its library section (as does Avsim, that in addition, requests that nothing be placed in the library except by the original author), yet some people deliberately ignore this.Sorry it had to happen to you.Best regards.Luis

[jvile 1]

MartinI also have these same fustrations. I spend a lot of time (past 2 years) updating FS9's default scenery database when real World Airports add a new ILS runway or change runway numbers. AFCAD alone does not add any xml Approach data which has to be written for each new ILS runway. If a scenery designer changes a runway number without updating all the default FS9 database xml Approaches this breaks FS9 and renders the ATC portion partially inoperative. CTD can also occur because the approach data which is owned by the Airport Scenery called the Visual AI Zone is no longer in sync with the new or changed visual runway numbers. The AFCAD xml runway data owns the ILS (user aircraft radio only) and ground movement. One of my most popular fixes is EHAM for the default scenery. I have had some extract out of the zip only the ILS/scenery bgl portion and place in with their uploaded AFCAD file for freeware/payware addon scenery. That even occured here on AVSIM where my original zip files are uploaded. There is still only two Scenery's that fix EHAM properly. My FS9 default scenery and NL2000 which I lended knowledge too. I monitor closely EHAM, KDEN, KMIA, KIAH, KMCO, KPVD, LEBL, EFHK just to name a few that I have fixed for the default FS9 scenery that I produce and upload. If a freeware or payware scenery designer wants my help all they have to do is ask. Shez's did (KCLE) I learned along time ago to finger print any of my AFCAD's that must coincide with my ILS approach data.I also add portions of my copywright distribution statements to the compiled ILS/Scenery bgl's that are identical to the original readme. If someone trys to decompile my bgl's and remove this type info the compilers cannot recompile due to missing model mdl's and other added xml statements embedded that I made. We can't police the entire internet (locks are for honest people) but if I do find some of my files elsewhere or here on AVSIM then it is very convincing to say those are mine and here is why.Same as Luis, Sorry it has happened to you also.

[scott967 62]

If someone disassmbles MS' default AP files, takes some data out of it and modifies or adds their own, is that OK or not? It seems like we are getting on shakey ground if we try to claim too much credit for a mod of another (default or addon) file. I know I have modded many files (default and addon) for my own use. My mods may be useful for someone else. In general I have not uploaded these, concerned about this copyright/credit issue. What is the community position on these mods? I agree that simply aggregating files doesn't provide enough value added to really justify a new upload, but what if there is some value added? I know the readmes provide differing statements on what the authors want/allow. Just the other day was a post from a user complaining about having to d/l VOD textures, or trees and having to keep track of all these things separate from scenery designs that use them.scott s..

[mgh 89]

Good question, given that the FS EULA states:"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."

[Shaka 2]

>If someone disassmbles MS' default AP files, takes some data>out of it and modifies or adds their own, is that OK or not? >It seems like we are getting on shakey ground if we try to>claim too much credit for a mod of another (default or addon)>file. I know I have modded many files (default and addon) for>my own use. My mods may be useful for someone else. In>general I have not uploaded these, concerned about this>copyright/credit issue. What is the community position on>these mods? I agree that simply aggregating files doesn't>provide enough value added to really justify a new upload, but>what if there is some value added? I know the readmes provide>differing statements on what the authors want/allow. Just the>other day was a post from a user complaining about having to>d/l VOD textures, or trees and having to keep track of all>these things separate from scenery designs that use them.>>scott s.>.>>> You have a good point, but common courtesy would require an email to the original author to at least ask his permission. In the past, other people have emailed me asking to use my textures, and objects, and I have always agreed. In every case, I was at least credited with the original work. I agree that there is some grey area to be worked out sometimes.That is not the case this time though. The uploader didn't modify any of the scenery files. He simply re-uploaded them and claimed exclusive credit for the work.- Martin

[jvile 1]

>If someone disassmbles MS' default AP files, >takes some data out of it and modifies or adds their own,>is that OK or not? It seems like we are getting on>shakey ground if we try to claim too much credit for >a mod of another (default or addon) file.If that was true then every single AFCAD airport uploaded including the AFCAD program itself are in some kind of violation. However it is the other way around because MSN incourages us to modify their exsisting airports that are found in the APnnnnnnn.bgl files with our own.The SDK that MSN wrote explains what all these This is the backbone of Lee Swordy's AFCAD program and it copies out most of the default APnnnnnnnnn.bgl so we can modify FS9 airports and use or upload a new bgl which includes our changes.When I write approaches for new runways or change exsisting runway numbers I better follow the SDK to the letter by using the deleteAllApproaches = "TRUE" statement.I go as far as placing my files in the correct folder that MSN says to use, not the Addon Sceneryscenery folder.When you follow the SDK correctly the MSN files (APnnnnnn.bgl) are never modified at the root level.

[jvile 1]

ScottI just re-read my post and it is not entended to be offensive but informative.The APnnnnnnn.bgl is a very powerful bgl and MSN gives us most of the information in the SDK to write a new bgl that will replace their APnnnnnnn.bgl or portions of it.>If someone disassmbles MS' default AP files, >takes some data out of it and modifies or adds their own,>is that OK or not? No, I do not believe that is ok. (see MPH post)That is saying we decompiled a APnnnnnnnn.bgl, changed something and then recompiled it back as a MSN protected file with a backup of the original file.What MSN does allow is to write a new bgl that resembles a APnnnnnnnn.bgl and then place it at a higher priortity level (Generic Scenery folder) so our new xml file replaces or adds to the default root file.The Authors of both decompilers (to view default xml bgl's) state that they are for information purposes only.There is a decompiler/compiler out there that does change the root MSN protected file and that is the utility JABBgl. I stay away from those type utilities because they are in direct violation of tampering with MSN protected files.MSN gives us a correct way of fixing 3rd party scenery that does not have the airport elevation set correctly. That requires a new xml Airport Header compiled by BGLComp and placed into the world scenery folder. Hope this helps and sorry if my post sounded offensive.

[scott967 62]

I did not take your post as offensive in any way. I understand exactly what you are saying. ISTM that modding is an important part of most of the top level games. The problem is what is a fair use of the base file (either default or some one elses). I don't mean that from a legal standpoint, but from the betterment of the hobby standpoint.I think maybe there needs to be something like the GPL. You can use my software in your software as long as you include this license with it and abide by it.Believe me, I have no problems with your files. You have done a lot of good for all of us, helping users as well as providing files.Again, I'm not talking about aggregators, or ebay resellers where no value added occurs, though I could see how a compilation might be a benefit to someone.scott s..

[mgh 89]

"The Authors of both decompilers (to view default xml bgl's) state that they are for information purposes only."The documentation I have states:"BGLXML is an utility which analyzes and decompiles BGL files" "NewBglAnalyze is version 1 of a disassembler for BGL-files" The EULA forbids decompilation and dissambly except as permitted by law. It seems to me that there is an element of double standards here - it's wrong to ignore restictions imposed by add-on developers but OK to ignore Microsoft's

[jvile 1]

MPH Maybe I read too much into these different statements from the decompilers but I read it as a information toolBGLAnalyze says"Disassembling scenery files in some countries might violate legal rights of copyright holders" and"The program can be used by scenery designers or other people interested in the structure of scenery files without restrictions"BGLX180 says"This utility is freeware and open-source,licensed under GNU-GPL to help developersunderstand the new FS2004 BGL structures"My interpretation could differ from others

[mgh 89]

I only have BGLXML and NewBGLAnalyse, so I can't comment on the others you mention. Whatever disclaimers may be included, the fact remains that the applications appear to breach the EULA.I'm quite laid-back about this subject, but do feel slightly uneasy at the regular choruses of disapproval whenever people here complain their rights have been infringed, when many of them seem happy to infinge other's (Microsoft's) rights.

[Shaka 2]

>I only have BGLXML and NewBGLAnalyse, so I can't comment on>the others you mention. Whatever disclaimers may be included,>the fact remains that the applications appear to breach the>EULA.>>I'm quite laid-back about this subject, but do feel slightly>uneasy at the regular choruses of disapproval whenever people>here complain their rights have been infringed, when many of>them seem happy to infinge other's (Microsoft's) rights.And if someone were to actually infringe on Microsoft's rights, I'm sure they would have something to say about it. But that is not the case here. In any event, the only default files which are regularly modded show up as AFCAD files. There really isn't much question as to how MS feels about this - they gave us the tools and detailed instructions of how to create and modify these files. As well, there is a seperate EULA that was distributed with the SDKs which isn't quite as heavy handed as the one that shipped with FS9, and even tells us to include a copyright statement with our application.Even if we take the FS9 EULA literally, and ignore the SDKs and fair-use rules, we still have to accept that it is up the MS to determine whether to enforce it or not. If they choose to allow the distribution of AFCAD files, then that is their perogative. If I choose to complain because someone has taken my entire catologue of work and re-uploaded it as their own, then that is mine.Back on track...The offending file has been removed. An explanation was offered that with so many files being uplaoded, they can't all be thoroughly checked to see whether they actually work or not, never mind whether the uploader stole it or not.- Martin

[mgh 89]

I made no objection to creating new scenery using the information in the SDK to create an XML file and then compiling that with BGLCOMP. That seems to me perfectly permissible under the EULA. What isn't permissible is decompiling Microsoft's files in breach of the EULA and then recompiling new versions. Widening the thread a little, do all add-on aircraft developers create new .air files only by changing the .cfg and then using FSEdit or do they rely on knowledge gained by decompiling Nicrosoft's .air files?

[Shaka 2]

>I made no objection to creating new scenery using the>information in the SDK to create an XML file and then>compiling that with BGLCOMP. That seems to me perfectly>permissible under the EULA. >It is permissible if MS allows it, therefore we have a plethora of AFCAD files in the library.>What isn't permissible is decompiling Microsoft's files in>breach of the EULA and then recompiling new versions. Widening>the thread a little, do all add-on aircraft developers create>new .air files only by changing the .cfg and then using FSEdit>or do they rely on knowledge gained by decompiling Nicrosoft's>.air files?What you are implying is correct - most add-on aircraft designers modify existing .air/.cfg files. Does this violate the EULA? I think not, since MS gave us the tools and instructions specifically to do this. I think that this is exactly what MS expects us to do!Maybe we'll just have to agree to disagree. I don't think the EULA was meant to be construed as narrowly as you suggest, and I'm pretty sure that most scenery designers see the difference. My best support is the numerous files which already exist on this and other websites, and the fact that MS told us how to make and modify those files, and tolerates their existence. - Martin