Hello fellow flight simmers. I have FS2004 and I have been trying to take a shot at designing airport sceneries. I have done aircraft repaints for several years and thought it was time for me to try something different. i understand the format is totally different. In reading these forums I found out it is a more complicated task as there are more programs available for designing sceneries. There is so much to learn. I recently purchased the EZ-Scenery program by Abacus software. I found it works as great as it is advertised, and thought this was the answer to what I wanted to do. The only thing is that I can only work with the objects that are available in its library. For now, that is OK, however, my question is, does the scenery I "created" using EZ-Scenery works only in my computer, or can I actually build a file of that scenery and share that airport with other fellow simmers?Thanks for any input I can get from all of you experts. :(

Hello fellow flight simmers. I have FS2004 and I have been trying to take a shot at designing airport sceneries. I have done aircraft repaints for several years and thought it was time for me to try something different. i understand the format is totally different. In reading these forums I found out it is a more complicated task as there are more programs available for designing sceneries. There is so much to learn. I recently purchased the EZ-Scenery program by Abacus software. I found it works as great as it is advertised, and thought this was the answer to what I wanted to do. The only thing is that I can only work with the objects that are available in its library. For now, that is OK, however, my question is, does the scenery I "created" using EZ-Scenery works only in my computer, or can I actually build a file of that scenery and share that airport with other fellow simmers?Thanks for any input I can get from all of you experts. :(

The files will work for anyone provided that they have the object libraries and textures that you used

Hello fellow flight simmers. I have FS2004 and I have been trying to take a shot at designing airport sceneries. I have done aircraft repaints for several years and thought it was time for me to try something different. i understand the format is totally different. In reading these forums I found out it is a more complicated task as there are more programs available for designing sceneries. There is so much to learn. I recently purchased the EZ-Scenery program by Abacus software. I found it works as great as it is advertised, and thought this was the answer to what I wanted to do. The only thing is that I can only work with the objects that are available in its library. For now, that is OK, however, my question is, does the scenery I "created" using EZ-Scenery works only in my computer, or can I actually build a file of that scenery and share that airport with other fellow simmers?Thanks for any input I can get from all of you experts. :(

You sir can build sceneries using EZ-Scenery using all the default objects in FS2004 and any and all other scenery objects that are in your addon scenery library. When you compile a scenery, ie save the objects you have placed into a file, the program creates a "bgl" file that is sharable. And yes if you share the compiled bgl with other users they will see the objects, since they have the objects already included in their installation.Basically the bgl file just points to the objects and does not actually contain the objects. You do not need to provide objects to other users if you are using only default objects. Generally you can use objects from freeware sceneries where there is no issue with doing so, usually indicated by the author of the scenery, or you can contact and author, say by email, to verify that it is OK to use their "custom" objects in their freeware scenery. A few payware sceneries allow you to use their objects but you can't actually put the objects into your scenery package for sharing. Your bgl will point to those objects but the other user will have to have purchased the payware scenery and therefore will have the objects in their installation. You may have to provide objects along with the bgl where you have used objects from sceneries other than the default fs as long as you have permission to do so. There are hundreds/thousands of freeware objects available for download at this site or other sites beyond those in the default program. Most users have added these to their scenery libraries and have them already. When you distribute a scenery it is useful to provide a list of which objects your scenery bgl calls upon so that the user will know if they need to go and get those objects.

Thanks for your replies. :(

One thing you might consider when creating sceneries you intend to share is to include the scenery BGL's and texture files in your upload instead of pointing new users to where they can download the additional libraries they will need. When I first started downloading and installing sceneries created by others I found it "intimidating" to have to download a scenery and install it and then download a library or libraries and install them as well. I've uploaded two sceneries to AVSIM and included everything that was needed in the uploads...sort of a "one stop shop"...to make it easier to install. There is a drawback to this, however. If you use the same object...let's say a file called "car.bgl"...in several sceneries the end user will have several copies of "car.bgl" in their file system when they really only need one. If you decide to simply refer people to the necessary libraries at least include a weblink "pointer" they can click on in your readme file so future end users don't have to search for the required libraries. Just a courtesy your "clients" will appreciate. Randy

Hi Randy, To include all the libraries is not really a good advice. If users end up installing the same library mulitple times in their FS that can give a number of problems. First it can take a lot of harddisk space, secondly it will result in multiple objects with the same GUID. This can lead to issues, since you don't know from which library the object is actually taken. If the developer decides to update the library later it will also be a nightmare to do so. So the common practise for scenery developers is to point the users where to get the libraries, but don't include them in the distribution.

...I've uploaded two sceneries to AVSIM and included everything that was needed in the uploads...sort of a "one stop shop"...to make it easier to install. There is a drawback to this, however. If you use the same object...let's say a file called "car.bgl"...in several sceneries the end user will have several copies of "car.bgl" in their file system when they really only need one...

Arno, I kinda did make reference to what you say in the second paragraph. And I agree, to a certain extent. When I was working on my first AVSIM upload one of the AVSIM Forum Moderators suggested I make the upload all-inclusive so people who download need not go elsewhere for other downloads. I have multiple EZ-Scenery libraries and Runway12 libraries also on my system and one of the first things I noticed was when I would download someone else's scenery that used those libraries...and the objects/textures were include in the download...that my libraries soon showed two, three, or even five of the same objects in the objects list. Took me forever to weed them out so my objects list was manageable. Now when I download a scenery I always check and if I already have an object I remove it from the download before installing. But, the point still remains, some users just don't do well installing sceneries that require multiple downloads and installs of libraries, textures, AFCADs, etc in various locations, so I opted for the easy install instructions. Unzip, move or copy to addon scenery and activate. Guess it all goes back to my Air Force Effective Writing days. If your target audience is at various skill levels then you use language, syntax, grammar, etc that makes sure the lowest level understands, even at the risk of offending the higher levels. But, in the final analysis, you are right. It is not the correct way to contribute to the AVSIM Library. Cheers... Randy

Randy, If people can't figure out how to download and install a/some object libraries, how are they ever going to figure out how to install your addon? I have seen it time and time again, helped more simmers than I can count who had object display issues caused by people who included object libraries in their scenery addons. In my opinion you should not include anything in packages you upload that you did not create. regards,Joe

Joe, And I agree with you. Which begs the question, "If I agree then why did I upload a One Stop Shop single download type scenery to the library?" When I first discovered the world of addon sceneries that made my airports look the way they were supposed to I was enthralled. Some were simple, jetways added to a default terminal in FS9. Many were complex, new runways, new taxiways, photoreal terminals that look like the real thing, moving jetways, opening hangars, etc. In those early days of my "addiction" the complex installs were terrifying, especially the caveat that was always included, "I accept no responsibility for damage to your system" found at the bottom of the readme file. In those early days I loved "Unzip, Copy to Addon Scenery, Activate, Restart". Simple and direct, no fear, no qualms. Later on as I gained experience I realized the "harm" I was doing and ended up having to correct my libraries to make them useable. Now it's:

Download file A Search for Files B, C, D, E, and F which are required for my scenery to work Install C first, but remove folder X from your system. Create a new folder in Z and place F there, being careful not to overwrite anything (or "yes" to overwrite) Now install A, but remove any related AFCADs (Where would they be if I have "related" AFCADs?) Now install D, B, and E in that order, making sure E is a higher priority than B, but lower than A Plus each file comes with it's own readme that may or may not conflict with the readme that comes with A (File A readme says put file D's objects in a new folder in Addon Scenery, but file D says put them in a new folder in C:\Program Files.

I realize this is somewhat of an exaggeration, but I still have downloads in a folder I named "Pending Installs" simply because I cannot understand the instructions, or they are in such a maze of entanglements that the chances of correctly installing the scenery are slim at best. I think the answer is not in what you have inside your zip file for download, but the Main Readme Install Instructions. For "One Stop Shop" type downloads, warn users that if they have EZ Fuel Tanks objects already on their system they do not need to install that BGL. For complex downloads put in a pointer or link to the files/objects you want the user to download so they don't have to hunt for a library. Put in a very detailed readme. First do this, next do this. The instructions for this will say do that, but do this instead. Think about your targeted user. Is he/she an inexperienced simmer who wants to get more from this fantastic hobby or simmer/designer/builder who knows what and where each little file goes and more importantly what it does? We have to target the former, because they don't know what to do. The latter does. But, and I can't say this enough, you are absolutely correct. Requiring a second or third download and install (without including the required files in your download) to make a scenery work is probably the proper way to contribute. But, in doing that, how many future designers/simmers are we leaving behind because all they want to do right now in their progress is "Load and Go"? How many of those left behind could end up being a valuable contributor to this awesome hobby later on in their "career"? It's a double-edged sword...damned if you do, damned if you don't. Randy