Flightgear Boeing 737 800 Download ((TOP))
Mirthe Sinkey
Big thanks and shoutouts to all people who helped developing flightgear and the 787-8 model. I've been truly sitting in this cockpit for hours now to learn about and play with the plane, everything else was forgotten. The combination of visuals, hardware interfacing, ATC audio feed, soundscape of hydraulics/APU/turbines and interaction with this machine captured me completely. I was in there :)
Have you ever done a model for flightgear before? Will you use this in flightgear for personal enjoyment or will you be attempting to upload it officially? I think i was reading couple weeks ago they only remotley even accept models with 5000 triangles. Is that right? I guess if its just for personel reasons and you have a fast enough comp it would be nice to be able to add all the detail and not worry so much about the number of verts.
Anyway the last attempt is much better then your first post.
Keep it up.
>Have really gotten into FGFS, but this is my very first post>about it.>After figuring out how to create a gosh darn SGI format (.RGB>extension) texture-map file for FG on my PC, (solution: get>GIMP opensource paint program [binaries]),Just in case that it took you any significant amount of time to figure that out, it's really a good recommendation to search the mailing list archives at flightgear.org and this sub forum before spending much time trying to figure something out that may be very simple to do by actually looking into previous discussions.On the other hand, it would probably not harm at all if these things were also "officially" mentioned in some specific readme file within $FG_ROOT/Docs, i.e. something like README.textures> I've created my first "reskin" of an FG plane!Congratulations !>Now I want to share it! Is there a way FG'ers do this?Yes, indeed there are some ways to share FlightGear specific files, if you have created genuine work, you would preferably license it under any GPL compatible license, so that your work may optionally even be included into the official FlightGear base package and may become part of future releases.On the other hand, if licensing your work under the GPL may not be an option, for whatever reasons, you may still license your files under your own license and make your files available via a simple download using some simple webspace (in case that you don't have webspace yet, make sure to google for it, as there are numerous hosts offering free webspace).Alternatively, you may consider making your files available via some of the user-run aircraft repositories, in that case you'll probably want to search flightgear.org and its mailing list archives for the different possibilities (repositories, that is).>I know that in the car-sim "Racer" (also open source)>community I'm part of, there are agreed ways of doing this,>including issues of etiquette.>I haven't found anything in the FG forums about aircraft maps!I'm not sure I'm getting you right.What do you mean by "maps", the textures/liveries?In that case, there's no dedicated place to share such things as of now, however usually they will quite well fit into the individual aircraft's folder itself.>Should I upload the texture map, perhaps on this forum?That's probably also not a bad idea at all, simply because any privately hosted files may be subject to removal sooner or later if users cannot afford to maintain the webspace, also given the insignificant size of these plaintext ASCII files, this looks like a very feasible option.>What about the original author(s) of the plane being>reskinned? Indeed, the author(s) of individual aircraft may probably be another potential way to actually "re-lease" your modifications, at least if those people are still around (within the FlightGear community), you may want to search the FlightGear mailing list archives to check whether the corresponding people are still "active" or not, in the latter case, it might also be a good idea to simply consider sending your files/changes (i.e. a diff patch) themselves to the FlightGear Devel mailing list (as long as the files don't exceed a certain size, i.e. 10 kb)>(Come to think of it, what about the photographer over on>Airliners.net who's B737 side view shot I'm mapping onto the>plane?)This may actually be the most criticial issue at all, airliners.net is known to have authors copyright their images, amongst others also for sale. So in that case you are most likely using copyrighted work, which in itself shouldn't be any problem if you are only using that work for your own personal purposes, however as soon as you intend to make these modifications publicly available, this may indeed cause significant problems. Hence, your best bet would probably be to contact the photographer(s) of the images that you used, explain to them what you've done with their images, and what you'd like to be allowed to do. And preferably, they might even consider releasing certain images explicitly under the GPL for FlightGear incorporation.In any case it would probably help tremendously if you provide a short introduction about FlightGear, its purpose, its goals/philosophy (i.e. FREE) and enclose some screenshots of your final work to illustrate to the photographer(s) what you've done.That way, it will be straight forward for them to see what their artwork would be used for.>The author of the Boeing 737 did a nice handpainted United>Airlines livery texture map, but one can adapt photographic>resources to really enhance the realism of the aircraft!I agree, the attached image looks really very cool and I'd personally love to see this officially added to the base package.>Attached pic: (top): original author's handpainted texture>map.>(bottom): my tweaked and massaged and generally adapted map>made from actual photo(s). Friendly feedback welcomed. ;-)Just in case that none of the previous suggestions should turn out not to appeal to the photographer(s), it's still an option to simply package the corresponding definition files, i.e. the XML file, the actual MAP and a link to the image that you used, that way each user could personally re-create the modification without you having to package the actual binary file.
Very nice work!But there is only one thing that you should know because it can save you a lot of time. :)The cvs version of flightgear now supports realtime shadows that are calculated on the fly by using the 3d model data.Shadow maps are no more necessary.