FlightGear wiki - User contributions [en]

User talk:Quadunit404

2011-01-24T19:41:13Z

Quadunit404:

Thank you very much, Quadunit404, for your fixes in 735 page ;)

Welcome. I noticed it needed a bit of improvement here and there (namely, the English, but that's understandable) so I fixed it where necessary. --[[User:Quadunit404|QU404]] 14:41, 24 January 2011 (EST)

Boeing 737-500

2011-01-23T20:21:45Z

Quadunit404:

{{infobox Aircraft
|image =737-500.png
|alt =Boeing 737-300 in Lufthansa livery
|name =Boeing 737-500
|type =Airliner
|livery =LH Retro 1986, RioSul, Nordeste, AirFrance
|authors =George Luiz, Isaias V. Prestes
|fdm =JSBSim
|status =Alpha
|fgname =737-500
|download = http://www.mediafire.com/?4in58197fe6o9pbb
}}

The Boeing 737 is a short-to medium-range, twin-engine narrow-body jet airliner. Originally developed as a shorter, lower-cost twin-engine airliner derived from Boeing´s [[Boeing 707|707]] and [[Boeing 727|727]] .

The 737-500 for FlightGear 2.0 is a resized (to real dimensions and characteristics) and FDM adjusted version of the [[Boeing 737-300]] done by David Culp, Innis Cunningham, Heiko Schulz, Brett Harrison and Emmanuel Baranger.

=== Liveries ===
The liveries from 1.9.1 and 2.0 don't fit on the 737-500, but with some work the 2.0 liveries can be made compatible.
So thanks to David Culp, Innis Cunningham, Heiko Schulz, Brett Harrison and Emmanuel Barranger for the great 737-300.

== Features in 2.0.0 ==
* new built fuselage based on free datas from Boeing and free available scale drawings matching now the real dimensions and proportions
* wings done by Innis Cunningham scaled and textured
* vstab done by Innis Cunningham scaled and textured
* better texture mapping and paintkit
* contrails done with particles based on a script by Zan
* new wheels done by helijah
* added thrust reserver by Bertrand Coconnier
* using generic tyre smoke
* added pushback
* added some more contactpoints to the fdm
* start of an 3d-cockpit
* fdm refined: pointmasses and locations based on a real 733 Balance and Trim sheet
* autopilot stable now in all altitudes, every weight and on glideslope until approx. 25-0ft

[[File:737-500lufthansa.png|thumb|270px|Lufthansa colors on a 737-500]]

As the aircraft is still in developement:

== Development status/Issues/Todo (FGFS 2.0.0) ==
'''Outside:'''
* wings need still some refinement and UVmapping
* wheel well area still missing

'''3d Cockpit:'''
* 3d-mainpanel added- needs still a lot of work like adding all instruments, and make them all work correctly (!)

'''Interior'''
* better interior needed

'''General:'''
* engine sound in cockpit does not differ from outside engine sound
* engines can't be turned off

= Reference =
* [http://en.wikipedia.org/wiki/Boeing_737 Wikipedia Boeing 737]

== External links ==
* [http://en.wikipedia.org/wiki/Boeing_737 Wikipedia Boeing 737 article]
* [http://www.b737.org.uk The Boeing 737 technical site]

== Related content ==
* [[Table of models]]
=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

{{Boeing}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:GPL model]]

User:Quadunit404

2010-12-27T06:41:44Z

Quadunit404:

I'll make this page better, eventually.

User:Quadunit404

2010-12-27T06:41:26Z

Quadunit404:

Hello! I have been flying around in FlightGear for about a year.

Stuff I do for the FlightGear project:

Contribute to the newsletter
Give guidance on developing aircraft based on knowledge
Develop aircraft (...eventually)

User:Quadunit404

2010-12-27T06:40:50Z

Quadunit404:

Hello! I have been flying around in FlightGear for about a year.

Stuff I do for the FlightGear project:

- Contribute to the newsletter
- Give guidance on developing aircraft based on knowledge
- Develop aircraft (...eventually)

FlightGear Newsletter August 2010

2010-08-27T03:30:05Z

Quadunit404: /* How do I commit changes to Git on Windows? */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome.''

==Development news==
===More realistic textures on mountains===
Shader-artist Gral picked up a new project, after his forest and grassland improvements. This time he impoves the look of our mountains a lot, thanks to some "elevation and slope detecting" shaders. They replace the vegetation with rocks above a certain elevation or on steep faces. Transition between the different terraintypes are extremely smooth, especially when compared to the usual landcover-transition (eg. between land and ocean) in FlightGear.

[http://www.flightgear.org/forums/viewtopic.php?f=5&t=9183 The forum] provides you with more information, screenshots and updates.

==In the hangar==
Several [[aircraft]] that have been around in FlightGear for many years got updates this month. There is a huge number of aircraft in the FlightGear hangar (over 300!), and while new aircraft are always welcome, there are many existing aircraft that would benefit from some spit-and-polish. Creating a completely new aircraft to a high standard represents a monumental amount of work. Those wanting to contribute, but without the time available to create a truly world-class aircraft from scratch might want to consider improving a favourite aircraft from the hangar instead. The effects are more immediate, and you can improve it one piece at a time.

===Douglas A-4F Skyhawk===
On a smaller scale to Hal's improvements to the Mustang, Stuart Buchanan has been making a number of changes to the venerable [[Douglas A-4 Skyhawk|A4-F Skyhawk]], or "Scooter". Rather than change the existing A-4F Blue Angels model, Stuart has instead modelled a normal Navy A-4F with dual drop-tanks. As well as some minor [[FDM]] tweaking, improvements include a completely new exterior and 3D [[cockpit]], and some more accurate flight control systems including auto-deploying spoilers. The A-4F is an interesting [[Aircraft carrier|carrier]]-based light attack aircraft, designed on the principle of simplicity and lightness by Edward Heinmann. In particular, by making the wings short, they didn't need to be folded for storage on carriers, which meant they didn't need complex wing folds, and hence were lighter and stronger.

===Fokker 100===
Another aircraft that has been updated recently is the [[Fokker 100]]. It now has a 3D cockpit and a rudimentary equipment failure control system, as well as a much-improved FDM and Autopilot. At the moment, the Equipment Failure System can only cause engine fires and flap failure. Several new liveries have been made as well. Authors who contributed to this latest phase in development include (in no particular order) Erik Hofman, Thomas Ito-Haigh, Gary Neely, and Skyop.

===North American P-51D Mustang===
Hal V. Engel has made some massive improvements to the [[P-51D Mustang|P51-D]]. Using NACA (the pre-cursor to NASA) published data, he's produced a very impressive [[JSBSim]] FDM. He's also made a number of improvements to the 3D cockpit and the engine systems. Those who enjoy their WWII warbirds will be very interested indeed. Your correspondent has still to manage a take-off from the runway without at least one bounce, but can report that the landing characteristics, while not benign, are at least manageable. This is an aircraft that will really repay some effort on the part of the pilot to get to know, and almost certainly represents the most accurate warbird FDM we have available.

===AC-130===

== Scenery corner ==
===Las Vegas McCarran International Airport===
[[File:KLAS.jpg|thumb|right|270px|A Southwest Airlines [[Boeing 737-300]] parked at Concourse B; Concourse C is visible in the background.]]
[[User:Skyop|Skyop]] has modeled Concourse A, Concourse B, Concourse C, and the Charter International Terminal at Las Vegas McCarran International Airport (KLAS). Unfortunately, the new Concourse D could not be modeled as there was no [[GPL]]-compatible satellite imagery available. You can obtain the new terminals via [[TerraSync]].

===Animated jetways finalized===
An exciting new feature comes to FlightGear with the completion of [[User:Skyop|Skyop's]] [[Howto: Animated jetways|animated jetway system]]. The first airport to implement it is none other than KLAS. [[Howto: Animated jetways#Usage|A slight fix]] is required to see the jetways.

To use the system, taxi to an animated jetway and park your aircraft with your nosegear on the "T" at the end of the marking line. Click the jetway, and if your aircraft has the appropriate values in its <tt>-set.xml</tt> file, the jetway will extend and raise/lower itself to your door! Updated <tt>-set.xml</tt> files for the [[Boeing 737-300]], [[Boeing 747-400]], and [[Boeing 777-200ER]] can be downloaded from [http://www.flightgear.org/forums/viewtopic.php?t=8728&start=90#p91826 this post] of the development thread.

Unfortunately, there are still a few unresolved issues with the jetways. The biggest being that they currently cannot operate independently.

== Community news ==
=== FlightGear on YouTube ===
* A [http://www.youtube.com/watch?v=-1pI8bIOxYA wonderful example] of the possibilities and power of FlightGear, in which FlightGear is connected to some avionics equipment (including flight displays and EICAS).
* Chances are big that you never saw anything like what is done in [http://www.youtube.com/watch?v=ISiia1syhTM this video], before. These people connected a radio controller vehicle to their computer and visualized its movements with FlightGear's [[jeep]].
* Our home-director, Oscar, uploaded a [http://www.youtube.com/watch?v=a-40ocTyVGY nice video] summarising the KLM fleet in FlightGear.
* In case you have missed it, a [http://www.dailymotion.com/video/x5i0i0_brest_videogames video showing photorealistic scenery] in Brest.
* Despite the bad graphics (clouds and smoke), this [http://www.youtube.com/watch?v=t90qRgczJ-o Red Bull Air Race video] shows once again what an enormous range of different things one can do in FlightGear. A [http://www.youtube.com/watch?v=oQQDL7jaScQ second video] was uploaded as well.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

=== Wiki updates ===
====Nasal articles====
In the aftermath of a [http://www.flightgear.org/forums/viewtopic.php?f=30&t=8995 forum topic], work has been started on expanding the number of [[Nasal]] related articles at the wiki. These articles should help (new) developers to understand the scripting language and eventually write their own scripts.

All Nasal articles are collected in a [[:Category:Nasal|special category]]. More articles are welcome, as always, so feel free to share your Nasal knowledge!

====How do I commit changes to Git on Windows?====
Three months after our big move to [[Git]], there finally is a tutorial on how to commit changes to Git on a Windows based computer! This allows every FlightGear user/developer to get their edits up in the official FlightGear repository. Let's hope that this will stimulate more people to start developing and sharing their work with the rest of the world.

Read the article at [[FlightGear Git on Windows#Commiting changes]].

=== Update on FlightProSim ===
Thanks in part to ''jackmermod'', the FlightGear community now has [http://flightgear.org/forums/viewtopic.php?f=3&t=8225&start=45#p90830 access] to the source code of the much-discussed [[FlightProSim]], which will allow for a better and more thorough investigation of the simulator. Browsing through the source directory structure has so far given promising results, but compiling the program itself has been problematic.

=== Relaunch of TransGear Airways ===
This month saw the first event of the resurrected TransGear Airways. The event was planned by Lukosius and Redneck. Redneck and Jomo provided Air Traffic Control services. The event was well received and attended by registered TGA pilots and other unregistered pilots as well. Details are available on the [http://transgear.treborlogic.com official site]. The September event will be the first event scheduled using Yourgod's scheduling software which will allow pilots to plan their own routes within the event.

==And finally==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

[[Category:FlightGear Newsletter|2010 08]]

FlightGear Newsletter August 2010

2010-08-27T03:29:39Z

Quadunit404: /* How to commit changes to Git on Windows? */

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome.''

==Development news==
===More realistic textures on mountains===
Shader-artist Gral picked up a new project, after his forest and grassland improvements. This time he impoves the look of our mountains a lot, thanks to some "elevation and slope detecting" shaders. They replace the vegetation with rocks above a certain elevation or on steep faces. Transition between the different terraintypes are extremely smooth, especially when compared to the usual landcover-transition (eg. between land and ocean) in FlightGear.

[http://www.flightgear.org/forums/viewtopic.php?f=5&t=9183 The forum] provides you with more information, screenshots and updates.

==In the hangar==
Several [[aircraft]] that have been around in FlightGear for many years got updates this month. There is a huge number of aircraft in the FlightGear hangar (over 300!), and while new aircraft are always welcome, there are many existing aircraft that would benefit from some spit-and-polish. Creating a completely new aircraft to a high standard represents a monumental amount of work. Those wanting to contribute, but without the time available to create a truly world-class aircraft from scratch might want to consider improving a favourite aircraft from the hangar instead. The effects are more immediate, and you can improve it one piece at a time.

===Douglas A-4F Skyhawk===
On a smaller scale to Hal's improvements to the Mustang, Stuart Buchanan has been making a number of changes to the venerable [[Douglas A-4 Skyhawk|A4-F Skyhawk]], or "Scooter". Rather than change the existing A-4F Blue Angels model, Stuart has instead modelled a normal Navy A-4F with dual drop-tanks. As well as some minor [[FDM]] tweaking, improvements include a completely new exterior and 3D [[cockpit]], and some more accurate flight control systems including auto-deploying spoilers. The A-4F is an interesting [[Aircraft carrier|carrier]]-based light attack aircraft, designed on the principle of simplicity and lightness by Edward Heinmann. In particular, by making the wings short, they didn't need to be folded for storage on carriers, which meant they didn't need complex wing folds, and hence were lighter and stronger.

===Fokker 100===
Another aircraft that has been updated recently is the [[Fokker 100]]. It now has a 3D cockpit and a rudimentary equipment failure control system, as well as a much-improved FDM and Autopilot. At the moment, the Equipment Failure System can only cause engine fires and flap failure. Several new liveries have been made as well. Authors who contributed to this latest phase in development include (in no particular order) Erik Hofman, Thomas Ito-Haigh, Gary Neely, and Skyop.

===North American P-51D Mustang===
Hal V. Engel has made some massive improvements to the [[P-51D Mustang|P51-D]]. Using NACA (the pre-cursor to NASA) published data, he's produced a very impressive [[JSBSim]] FDM. He's also made a number of improvements to the 3D cockpit and the engine systems. Those who enjoy their WWII warbirds will be very interested indeed. Your correspondent has still to manage a take-off from the runway without at least one bounce, but can report that the landing characteristics, while not benign, are at least manageable. This is an aircraft that will really repay some effort on the part of the pilot to get to know, and almost certainly represents the most accurate warbird FDM we have available.

===AC-130===

== Scenery corner ==
===Las Vegas McCarran International Airport===
[[File:KLAS.jpg|thumb|right|270px|A Southwest Airlines [[Boeing 737-300]] parked at Concourse B; Concourse C is visible in the background.]]
[[User:Skyop|Skyop]] has modeled Concourse A, Concourse B, Concourse C, and the Charter International Terminal at Las Vegas McCarran International Airport (KLAS). Unfortunately, the new Concourse D could not be modeled as there was no [[GPL]]-compatible satellite imagery available. You can obtain the new terminals via [[TerraSync]].

===Animated jetways finalized===
An exciting new feature comes to FlightGear with the completion of [[User:Skyop|Skyop's]] [[Howto: Animated jetways|animated jetway system]]. The first airport to implement it is none other than KLAS. [[Howto: Animated jetways#Usage|A slight fix]] is required to see the jetways.

To use the system, taxi to an animated jetway and park your aircraft with your nosegear on the "T" at the end of the marking line. Click the jetway, and if your aircraft has the appropriate values in its <tt>-set.xml</tt> file, the jetway will extend and raise/lower itself to your door! Updated <tt>-set.xml</tt> files for the [[Boeing 737-300]], [[Boeing 747-400]], and [[Boeing 777-200ER]] can be downloaded from [http://www.flightgear.org/forums/viewtopic.php?t=8728&start=90#p91826 this post] of the development thread.

Unfortunately, there are still a few unresolved issues with the jetways. The biggest being that they currently cannot operate independently.

== Community news ==
=== FlightGear on YouTube ===
* A [http://www.youtube.com/watch?v=-1pI8bIOxYA wonderful example] of the possibilities and power of FlightGear, in which FlightGear is connected to some avionics equipment (including flight displays and EICAS).
* Chances are big that you never saw anything like what is done in [http://www.youtube.com/watch?v=ISiia1syhTM this video], before. These people connected a radio controller vehicle to their computer and visualized its movements with FlightGear's [[jeep]].
* Our home-director, Oscar, uploaded a [http://www.youtube.com/watch?v=a-40ocTyVGY nice video] summarising the KLM fleet in FlightGear.
* In case you have missed it, a [http://www.dailymotion.com/video/x5i0i0_brest_videogames video showing photorealistic scenery] in Brest.
* Despite the bad graphics (clouds and smoke), this [http://www.youtube.com/watch?v=t90qRgczJ-o Red Bull Air Race video] shows once again what an enormous range of different things one can do in FlightGear. A [http://www.youtube.com/watch?v=oQQDL7jaScQ second video] was uploaded as well.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

=== Wiki updates ===
====Nasal articles====
In the aftermath of a [http://www.flightgear.org/forums/viewtopic.php?f=30&t=8995 forum topic], work has been started on expanding the number of [[Nasal]] related articles at the wiki. These articles should help (new) developers to understand the scripting language and eventually write their own scripts.

All Nasal articles are collected in a [[:Category:Nasal|special category]]. More articles are welcome, as always, so feel free to share your Nasal knowledge!

====How do I commit changes to Git on Windows?====
Three months after our big move to [[Git]], there finally is a tutorial on how to commit changes to Git, on a Windows based computer! This allows every FlightGear-user/developer to get their edits up in the official FlightGear repository. Let's hope that this will stimulate more people to start developing and sharing their work with the rest of the world.

Read the article at [[FlightGear Git on Windows#Commiting changes]].

=== Update on FlightProSim ===
Thanks in part to ''jackmermod'', the FlightGear community now has [http://flightgear.org/forums/viewtopic.php?f=3&t=8225&start=45#p90830 access] to the source code of the much-discussed [[FlightProSim]], which will allow for a better and more thorough investigation of the simulator. Browsing through the source directory structure has so far given promising results, but compiling the program itself has been problematic.

=== Relaunch of TransGear Airways ===
This month saw the first event of the resurrected TransGear Airways. The event was planned by Lukosius and Redneck. Redneck and Jomo provided Air Traffic Control services. The event was well received and attended by registered TGA pilots and other unregistered pilots as well. Details are available on the [http://transgear.treborlogic.com official site]. The September event will be the first event scheduled using Yourgod's scheduling software which will allow pilots to plan their own routes within the event.

==And finally==
=== Contributing ===
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time". Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

For ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

=== Reminder: Google's Summer of Code 2011 ===
We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011. However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person. It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

[[Category:FlightGear Newsletter|2010 08]]

FlightGear Newsletter August 2010

2010-08-17T03:45:41Z

Quadunit404:

{{newsletter}}
{{TOC_right}}
''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone with a wiki account (free to register) can edit the newsletter and every contribution is welcome.''

== FlightGear events ==
== Development news ==
== Contributing ==
One of the regular thoughts expressed on the FlightGear forums is "I'd like to contribute but I don't know how to program, and I don't have the time".

Unfortunately, there is a common mis-conception that contributing requires programming and lots of free time. In fact, there are a huge range of ways to contribute to the project without needing to write code or spending days working on something.

Some ideas:
* writing articles for the [[Next newsletter|next issue of this newletter]]
* sending corrections/updates to the FlightGear Manual
* helping new users on the forums/IRC
* writing a wiki page
* organising fly-outs

One of the easiest ways to help is to improve the scenery in your local area by placing buildings/structures using the UFO and submitting them to the [http://scenemodels.flightgear.org/contribute.php FlightGear Scenery Object Database]. It's easy, and best of all requires little time to have a real impact. Instructions on how to do this can be found in the wiki, [[Placing 3D Objects with the UFO]].

For other ideas on starting to contribute to FlightGear, you may want to check out: [[Volunteer]].

== Reminder: Google's Summer of Code 2011 ==

We would like to remind all readers that the FlightGear project is planning to participate in [[GSoC]] 2011.
However, doing that really requires a fair amount of work, planning and organizing. This is not something that can be done by a single person.
It really needs a coordinated team effort, or otherwise FlightGear won't be able to apply/participate at all.

So all users are invited to help us progress further with our preparations for GSoC 2011.
Some easy ways for contributing right now would be:

* suggest new project ideas
* browse the forums or mailing list archives and look for viable candidate projects
* help refine and improve existing project proposals
* help finalize the application template that we are preparing
* help us find suitable students who might be interested in participating in 2011
* help us find mentors
* summarize all related discussions, and document them here in the wiki

If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].

== Nasal for newbies ==
== New software tools ==
== FlightGear addons and mods ==
== In the hangar ==
Two aircraft that have been around in FG for many years got updates this month - the North American P-51D Mustang and the Douglas A-4F Skyhawk. There are a huge number of aircraft in the FG hangar (over 300), and while new aircraft are always welcome, there are many existing aircraft that would benefit from some spit-and-polish. Creating a completely new aircraft to a high standard represents a monumental amount of work. Those wanting to contribute, but without the time available to create a truly world-class aircraft from scratch might want to consider improving a favourite aircraft from the hangar instead. The effects are more immediate, and you can improve it one piece at a time.

===North American P-51D Mustang===
Hal V. Engel has made some massive improvements to the P51-D. Using NACA (the pre-cursor to NASA) published data, he's produced a very impressive JSBSim FDM. He's also made a number of improvements to the 3D cockpit and the engine systems. Those who enjoy their WWII warbirds will be very interested indeed. Your correspondent has still to manage a take-off from the runway without at least one bounce, but can report that the landing characteristics, while not benign, are at least manageable. This is an aircraft that will really repay some effort on the part of the pilot to get to know, and almost certainly represents the most accurate warbird FDM we have available.

===Douglas A-4F Skyhawk===
On a smaller scale to Hal's improvements to the Mustang, Stuart Buchanan has been making a number of changes to the venerable A4-F Skyhawk, or "Scooter". Rather than change the existing A-4F Blue Angels model, Stuart has instead modelled a normal Navy A-4F with dual drop-tanks. As well as some minor FDM tweaking, improvements include a completely new exterior and 3D cockpit, and some more accurate flight control systems including auto-deploying spoilers. The A-4F is an interesting carrier-based light attack aircraft, designed on the principle of simplicity and lightness by Edward Heinmann. In particular, by making the wings short, they didn't need to be folded for storage on carriers, which meant they didn't need complex wing folds, and hence were lighter and stronger.

== Liveries ==
== Scenery corner ==
== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==
== Suggested flights ==
== Aircraft reviews ==

== Community news ==
=== FlightGear on YouTube ===
* A [http://www.youtube.com/watch?v=-1pI8bIOxYA wonderful example] of the possibilities and power of FlightGear, in which FlightGear is connected to some avionics equipment (including flight displays and EICAS).
* Chances are big that you never saw anything like what is done in [http://www.youtube.com/watch?v=ISiia1syhTM this video], before. These people connected a radio controller vehicle to their computer and visualized its movements with FlightGear's [[jeep]].
* Our home-director, Oscar, uploaded a [http://www.youtube.com/watch?v=a-40ocTyVGY nice video] summarising the KLM fleet in FlightGear.

[http://www.youtube.com/watch?v=XkeApfVUnVk&feature=PlayList&p=3B31CCD15245D0AA&playnext_from=PL&index=0&playnext=1 Watch the FlightGear PlayList] for a collection of all (somewhat) quality FlightGear videos ever uploaded to YouTube.

=== Forum news ===

=== Wiki updates ===
====Nasal articles====
In the aftermath of a [http://www.flightgear.org/forums/viewtopic.php?f=30&t=8995 forum topic], work has been started on expansing the number of [[Nasal]] related articles at the wiki. These articles should help (new) developers to understand the scripting language and eventually write their own scripts.

All Nasal articles are collected in a [[:Category:Nasal|special category]]. More articles are welcome, as always, so feel free to share your Nasal knowledge!

=== Multiplayer ===
=== Virtual airlines ===
== Update on FlightProSim ==
Thanks in part to ''jackmermod'', the FlightGear community now has [http://flightgear.org/forums/viewtopic.php?f=3&t=8225&start=45#p90830 access] to the source code of the much-discussed [[FlightProSim]], which will allow for a better and more thorough investigation of the simulator. Browsing through the source directory structure has so far given promising results, but compiling the program itself has been problematic.
== Useful links ==
== And finally ... ==
=== Did you know ===

[[Category:FlightGear Newsletter|2010 08]]

FlightGear Newsletter August 2010

2010-08-13T19:32:06Z

Quadunit404: /* FlightGear on YouTube */

User:Quadunit404

2010-08-08T07:50:17Z

Quadunit404:

Hello! I have been flying around in FlightGear for about a year. I'm about to begin development of my first plane, the DHC-7-150. It should begin at any opportunity I get.

FlightGear Newsletter August 2010

2010-08-03T20:20:01Z

Quadunit404: /* Community news */

FlightGear Newsletter July 2010

2010-07-08T04:20:14Z

Quadunit404: /* In the hangar */

{{newsletter}}
{{TOC_right}}

''We would like to emphasize that the monthly newsletter can not live without the contributions of FlightGear users and developers. Everyone (with a wiki account, free to register) can edit the newsletter and every contribution is welcome.''

'''This month's newsletter marks a year since [[FlightGear Newsletter July 2009|the first issue]] was written!'''

==Development news==

==In the hangar==
===Bell P59 Airacomet and Bell 222 X===
''helijah'' created and pushed both P59 and Bell 222X onto Git. The Bell 222X FDM is still in development. More information and download at [http://helijah.free.fr/flightgear/hangar.htm ''helijah's'' Hangar].

===SpaceShipOne and White Knight===
''helijah'' has made some changes to the SpaceShipOne model including the [[FDM]], adding fuselage reflection effect and separating the SpaceShipOne and White Knight objects. The next step is to improve the SpaceShipOne model by adding wheels and moving parts. After that he will try to separate the two aircraft when in flight.

===De Havilland Canada DHC-7-150 Dash 7===
''Quadunit404'' has announced [http://www.flightgear.org/forums/viewtopic.php?f=4&t=8805 intentions] to produce his first aircraft, the De Havilland Canada DHC-7-150 Dash 7, adding yet another member of the De Havilland Canada family to to FlightGear fleet after active development begins. Currently he is learning how to model using [[Blender]] and will be studying the FDMs of other turboprop regional airliners already in FlightGear to get an idea of how to write the FDM.

==Scenery corner==

===Animated Jetways===

[[File:Movable_Jetway.jpg|thumb|right|skyop's movable jetways]]
''skyop'' and ''Gijs'' are currently working on animated jetways for FlightGear that can be activated with a click of the mouse. At the moment they are very primitive and only fit [[Boeing 737|737s]]. Planned features include automatic attachment to your airplane's door and even multiple jetways for wide-body airliners and [[Airbus A380|A380s]]. See [http://www.flightgear.org/forums/viewtopic.php?t=8728 this thread] for more information.

===Night Flying at London Gatwick===
The new version of [[London Gatwick Airport]] (EGKK) is available and has improved textures and features. It claims to be one of the few ''(two?)'' major international airports in [[FlightGear]] suitable for night flying with full lighting textures on all buildings, hazard lights and approximately one hundred lighting masts. The tower even has lit instrumentation visible in the control room. Images are shown at [http://www.flightgear.org/forums/viewtopic.php?f=5&t=8363 the forum topic].

The taxiways at night are complex but made easier if the official charts are downloaded from [http://www.nats-uk.ead-it.com]. Many taxiway and runway signs have been included to help you on your way. Additional [[AI]] ground network and AI traffic have made this into a very busy airport and a single gate at each pier has been thoughtfully reserved so you can find a parking space when you land here (see the readme file for details).

In daytime the airport is fully modelled with detailed textures and even the roofs of buildings having accurate features. Stock model jetways, cargoes and ground vehicles have been added in quantity to give an authentic look to the airport. Large areas of open air car parks are distributed around the perimeter with novel layering of textures to enhance the 3D effect of the parked cars. Similarly, woods and trees have been added in surrounding areas to add more to the overall feel of the airport.

London Gatwick EGKK may be downloaded from [http://www.mediafire.com/?t2ml5ezmgwv MediaFire].

==Aircraft review==
'''This Month: (name of aircraft here)'''

==From the community==

==And finally...==

===Did you know?===

[[Category:FlightGear Newsletter|2010 06]]

Talk:Building FlightGear - Windows

2010-07-03T02:15:48Z

Quadunit404:

When I followed the instructions most things went smoothly, but I did encounter a few wrinkles:

SimGear -------------

When I attempted to build SimGear, I got a bunch of errors. After flailing around quite a bit, I tried checking out the version of SimGear that was active at the time the instructions were written, and the errors were pretty much gone (more on the pretty much below).

To do this, you'll need to do an update-by-date, probably from the command line (I could not figure out how to do it within Eclipse, which is what I generally use for my repository interaction):
cvs -d :pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3 update -D"2009-08-23"
This will replace the Head version that you checked out with the version from 8/23.

This is likely to be an ongoing problem, since I think SimGear is *not* generally developed in Windows, so any Windows-compatibility is likely to be rather sporadic.

That still left a minor linking problem; I may have messed up the set-up a bit, but for some reason SimGear couldn't find jerror.h or jpeglib.h. I substituted the full path in the #include, since I really just wanted to get the darned thing to compile - and that did the trick.

FlightGear ------------

After various struggling, I wound up checking out the older date-based version (8/23/09) for this as well. I know that's not much help for people who truly need the latest and greatest . . . but I couldn't get the latest and greatest to work.

With the version from 8/23, things worked beautifully without a bunch of mucking around - just just a couple exceptions.

I had a few path problems with "boost". I got an extra layer of stuff when I unzipped boost_1_39_0; I had to take the nested boost directory and move it up a level before things were happy. Depending on the way you read the instructions this might be implied, but I completely missed the step.

It couldn't find sg.lib; I had to add ;..\..\..\..\plib to the end of the "Additional Library Directories" in the linker section of the FlightGear project properties.

And the compiled version of plib that I had downloaded ([http://www.oflebbe.de/FlightGear/plib-2007-04-16.zip]) did not seem to be quite up-to-date enough - I got a bunch of linking problems. The other pre-compiled link supplied no longer had any pre-compiled goodies on the other end, so I had to follow the directions for retrieving and compiling plib - but those directions worked beautifully first try :)

Once I got that fixed, everything was happy.

Below are some of my notes from when I was trying to do the most up-to-date version. Some of them might also be handy for problems with the 8/23 version (since some of those changes may have actually impacted my reverted versino).

''Many of the projects couldn't find plib. I just added the plib directory to the end of the include list of all my projects (right-click the project, go to properties, select C/C++, and add ;..\..\..\..\plib to the end of the "Additional Include Directories" field.''

''Some things also complained about the absence of GL/glut.h (get from [http://www.xmission.com/~nate/glut.html]; download, extract to your base FlightGear directory with everything else, rename GL).''

--

''Erg. I was stepping through the various FlightGear issues, but now they are turning into the weird/hard-to-resolve sorts of things that I was getting with SimGear. I went ahead and switched my FlightGear download to be from 8/23 as well''

------------------------
With those few caveats, the instructions worked beautifully - thank you for putting them together! Considering how long things took even so, I hate to think how long I would have been at it without them.

-- Annaka

==Updating the article==
Due to the migration to Git, shouldn't the article be updated a bit? I already updated section CVS to reflect the current host for FlightGear's source code, so why not everything else that refers to CVS, excluding the header as that was already updated to reflect that? --[[User:Quadunit404|Quadunit404]] 02:15, 3 July 2010 (UTC)

Building FlightGear - Windows

2010-07-03T02:13:20Z

Quadunit404: /* Git */

{{Main article|Building Flightgear}}

'''NOTE: Some parts of these instructions do not work correctly at this time, due to changes in the underlying software libraries. This page is a work in progress. The instructions should now be usable for all but building jpeglib and installing FlightGear'''

This section describes how to build [[FlightGear]] on Windows using Visual C++ 2008 Express Edition (the "free" for personal use version). These procedures will be very similar if you have the full Visual Studio 2008 and mostly similar if you're using older versions of Visual C++.

Keep in mind that FlightGear is a large project with external dependencies and compiling it is not a task for novice users. If you just want to fly, we recommend you get the binary distribution and have fun. If you intend to get hip deep in the code, please proceed...

'''Due to a hardware failure, the CVS servers of the FlightGear source and data repository are currently down. As a result, many links on this or other pages describing the built of FlightGear from CVS are obsolete.
Some highly skilled people are currently working on a substitute for the CVS system and it is already complete. Repository at: [http://www.gitorious.org/fg Gitorious.org]'''

== Requirements ==
Before you can compile FlightGear, you need to have the following installed on your computer:

===C++ compiler===
You may [http://www.microsoft.com/express/download/#webInstall download] the Express ("free" for personal use) version of Visual C++ 2008 from Microsoft. C++ Builder and Turbo C++ Explorer (by CodeGear, formerly by Borland) should work as well with some effort. We have not tried this.

Please note that when using MSVC++ Express, you'll probably want to download the full '''offline''' installation image file (iso) which -unlike the web installation- doesn't require any complicated and long-winded registration process. The direct link to the latest version (as of 11/2008) is [http://download.microsoft.com/download/E/8/E/E8EEB394-7F42-4963-A2D8-29559B738298/VS2008ExpressWithSP1ENUX1504728.iso] - after having downloaded the iso image, you'll either have to burn it or simply mount it in order to execute the installation.

You will also need the Platform SDK (Software Developer's Kit).

You can download the PSDK from http://www.microsoft.com/downloads/details.aspx?FamilyId=F26B1AA4-741A-433A-9BE5-FA919850BDBF&displaylang=en or http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm

Detailed installation instructions are available [http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=1995837&SiteID=1 here] (and [http://forums.microsoft.com/Forums/ShowPost.aspx?PostID=2888051&SiteID=1]).

===Git===
FlightGear uses [[FlightGear Git on Windows|Git]] for hosting the source code. You will need a Git client if you want to download the latest (development) source code for both FlightGear and SimGear. Traditionally, these are command line tools, but msysGit provides a graphic interface for Windows users. Download the installer for the latest stable version of [http://code.google.com/p/msysgit/downloads/list msysGit], run the installer, using all of its default settings (the installation destination folder is up to you).

===SVN===
OpenSceneGraph (OSG) uses Subversion (SVN) for version control. You will need an SVN client if you want to use the latest (development) source code for OpenSceneGraph. TortoiseSVN provides a graphic interface for Windows users. Download the installer for the latest stable version of [http://tortoisesvn.net/downloads TortoiseSVN], run the installer, using all of its default settings (the installation destination folder is up to you).

== Dependencies ==

FlightGear is dependent on quite a number of external libraries. You do not need to compile all of them yourself, but you will at least need to have their development version installed.

* [http://www.boost.org/users/news/version_1_39_0 Boost 1.39.0]
* [http://connect.creativelabs.com/openal/Downloads/Forms/AllItems.aspx?RootFolder=%2fopenal%2fDownloads%2fALUT ALut (OpenAL Utility Toolkit)]
* [http://connect.creativelabs.com/openal/Downloads/Forms/AllItems.aspx OpenAL CoreSDK]
* [http://sourceware.org/pthreads-win32/ pthreads]
** The latter 3 are available as one single package by a FlightGear project member
* [http://www.zlib.net/ zlib]
* [http://gnuwin32.sourceforge.net/packages/jpeg.htm GnuWin's JpegLib]
* [[Plib]] - portability libraries and scene graph
* [http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=8100 Subversion Headers and Libraries] - To get [[TerraSync]] compiled using svn for synchronizing scenery data. Make sure to pick actual "development libraries"
* [[OpenSceneGraph]]
* [[SimGear]] - Simulation support libraries that are developed mainly by the same people who develop FlightGear, though it can be and is used for other purposes. If you are building FlightGear from CVS, you need the CVS version of SimGear. If you have strange FlightGear build errors, check that you have an up-to-date version of SimGear built and installed

The dependencies are introduced in the steps below in roughly the order that you will need to get them.

== Directory Structure ==

As noted above, FlightGear depends on several other software packages. The Visual C++ project files that are maintained in CVS for both SimGear and FlightGear assume that these dependencies can be found within a very specific directory structure. In these examples, the root of the FlightGear related directories is '''C:\FlightGear\'''. This part is actually up to you; you could choose a completely different name and drive location.

All other directories shown under this project root must follow the directory structure shown below:

C:\FlightGear\boost_1_39_0\
C:\FlightGear\simgear\
C:\FlightGear\simgear\simgear\
C:\FlightGear\install\msvc90\OpenSceneGraph\include\
C:\FlightGear\3rdParty\include\
C:\FlightGear\plib
C:\FlightGear\flightgear

If you continue to follow the instructions in this wiki, you will end with the proper directory structure that is shown above.

== Getting '''Boost 1.39.0''' ==

* '''Step 1''' - Download Boost packaged release Version 1.39.0 (about 188 MB) from
http://sourceforge.net/projects/boost/files/boost/1.39.0/boost_1_39_0.zip/download (direct link) or from the project releases page at http://www.boost.org/users/download/#releases

* '''Step 2''' - Extract the contents of the boost archive in your '''\FlightGear''' directory. This will create a subdirectory named '''boost_1_39_0''' where the boost libraries and include files reside.

== Getting "3rdParty" ALut, OpenAL and pthreads ==

Olaf Flebbe has provided an archive containing the following FlightGear dependencies:

ALut
OpenAL
pthreads

Download the archive from http://www.oflebbe.de/FlightGear/3rdParty-2008-01-30.zip

Extract the archive in your FlightGear project root directory, '''C:\FlightGear\''' in these instructions. This will create the directory '''3rdParty''' under your project root directory.

== Getting zlib ==

* '''Step 1''' - Download the latest zlib binary package here http://sourceforge.net/projects/gnuwin32/files/zlib/1.2.3/zlib-1.2.3-lib.zip/download (direct link) or view the release page here http://sourceforge.net/projects/gnuwin32/files/zlib/1.2.3/

* '''Step 2''' - Extract the archive you downloaded in Step 1 in the "3rdParty" directory under your FlightGear project root directory.

* '''Step 3''' - As of zlib version 1.2.3, you must edit line 287 of the file "3rdParty\include\zconf.h" from "#if 1" to "#if 0" to avoid compiler errors when compiling SimGear against zlib.

== Getting jpeglib ==

* '''Step 1''' - Download the latest jpeglib source package here http://www.ijg.org/

* '''Step 2''' - This is a simple way to compile that should work with all versions of MSVC.
Open a command prompt and navigate to the folder where you have extracted the sources.
Type the following commands:
<pre>
copy jconfig.vc jconfig.h
copy makefile.vc makefile
</pre>
(this will copy the preconfigured Visual C configuration and makefile).

Then on the same command prompt type the following command to build the library:
<pre>
nmake nodebug=1
</pre>

Make sure that other projects will find your new files: Either copy '''jerror.h, jmorecfg.h''' and '''jpeglib.h''' to an include folder which is already defined (e.g. 3rdparty/include) or modify the individual project settings by adding the directory where you unpacked the jpeglib sources. The latter method is not advised.

Finally if you get the error:
<pre>
makefile(11) : fatal error U1052: file 'win32.mak' not found
Stop.
</pre>

then you need to add the switch '''/f <path>''' to point to the file Win32.Mak which resides in the above mentioned Platform SDK directory\Include. Make sure to enclose this path into double quotes if the path contains spaces. Or you may just want to copy win32.mak to the folder and run nmake.

If you get cl.exe not recognized, you will need to go to your VC/Bin folder and run vcvars32.bat to set the environment settings.

== Getting plib ==

You may download a prebuilt version of plib from http://www.oflebbe.de/FlightGear/plib-2007-04-16.zip (direct link) or visit Olafe's Compiling FlightGear page at http://www.oflebbe.de/FlightGear/index.html If you use this prebuilt, just extract the archive file's contents in your FlightGear project root directory. This will create the subdirectory '''plib'''.

The above plib package does not include debug libaries, only release. There have also been some bug fixes and changes to since that package was created, so you may wish to use the latest development version from SVN which you may download here http://plib.svn.sourceforge.net/viewvc/plib/trunk.tar.gz One annoying bug that was fixed caused joystick models to not be recognized automatically on Windows XP, Vista and 7.

Going this route means that you must compile plib yourself by following the instructions below:

* '''Step 1''' - Download the latest plib source tarball from http://plib.svn.sourceforge.net/viewvc/plib/trunk.tar.gz and extract it in some location that is NOT in your FlightGear project root directory. This will create a subdirectory named '''trunk''' which you may wish to rename to '''plib-svn'''. The remaining instructions assume that you did name it '''plib-svn'''

* '''Step 2''' - Double-click the file '''plib-svn\plib.dsw'''. This should launch Visual C++ which will ask if you want to convert the project file; answer "Yes to all" at the convert prompt.

* '''Step 3''' - Build the debug version of the plib libraries first by setting the VC++ Solution Configuration for Debug and hitting the F7 key.

Build the release version of the plib libraries next by setting the VC++ Solution Configuration for Release and hitting the F7 key.

NOTE: as of this writing, 5 compile errors in 4 files will occur. In each case, a typecast of '''(char*)''' must be added in order to compile without error using VC++ 2008 (VC90).

* '''Step 4''' - Create the subdirectory '''plib''' in your FlightGear project root directory.

Example:
C:\FlightGear\plib

* '''Step 5''' - Copy all of the files in your '''plib-svn'' directory that have the extensions "h", "lib" and "pdb" to the new plib directory under your FlightGear project root directory.

== Getting SVN headers ==

[[TerraSync]] is a convenient method to get actual scenery data without the need for download many megabytes of data before flying by synchronizing in [http://en.wikipedia.org/wiki/Apache_Subversion SVN manner]. TerraSync is part of the FlightGear sources and will be compiled by default with the other FlightGear binaries. To get TerraSync compiled properly you need to get the above mentioned "SVN developer library files". Extract the library and header files into your 3rdparty folder to the corresponding subfolders.

== Getting OpenSceneGraph (OSG)==

* '''Intro'''
To build SimGear and FlightGear from CVS head, you'll usually need the latest version of OSG. OSG from SVN head might be the best choice.

* '''Fetching "cutting edge" sources from SVN head'''
Use [http://tortoisesvn.net/ Tortoise SVN] to fetch the lastest source of OSG. The URL for the project archive is http://www.openscenegraph.org/svn/osg/OpenSceneGraph/tags/OpenSceneGraph-2.9.6. The destination folder should be '''OpenSceneGraph''' under your FlightGear project root directory. All other options can be left alone and are good to go as default. Wait until all files are downloaded from SVN.

* '''Dependencies''' 
OSG depends on some external libraries from the GnuWin project 
- [http://gnuwin32.sourceforge.net/packages/jpeg.htm Jpeg] 
- [http://gnuwin32.sourceforge.net/packages/libpng.htm Png] 
- [http://www.zlib.net/ ZLib] 
Download these packages and unzip them (including the folder structure) to your FG project folder\3rdparty. If you do not intend to create debug versions of OSG you can remove all links to debug files and *-bcc.lib in ...\3rdparty\lib.
A ready-to-use 3rd party archive, a detailed list of single dependencies and an explanation of the different dependencies can be found [http://www.openscenegraph.org/projects/osg/wiki/Downloads/Dependencies here].

* '''Preparing sources with CMake (generating project and solution files)'''
Get [http://www.cmake.org/cmake/resources/software.html CMake for Windows]. Extract all files from the archive to a folder of your choice (e.g. C:\DEV\CMake). Go to C:\DEV\CMake\bin and start '''cmake-gui.exe'''. Browse for the OSG source code (e.g. FlightGear project root\OpenSceneGraph) and enter this to the first line. Below this you'll find the path '''where to build the binaries'''. After entering the path to the souce code you'll find the same path here. Just add '''\build''' to this and you are now good to press '''Configure'''. If it did not happen before you'll now receive an information that your buld-folder was not found and cmake-gui asks you if it should be ceated for you. Press '''yes''' to do so.
Next specify you installed compiler (e.g. '''Visual Studio 9 2008'''). Set '''Use default native compiler''' and press '''Finish'''.

cmake-gui is now configuring everything so that you can use VC9 with OSG sources. But before you can go on you'll need to tweak cmake a little bit. After pressing Configure the first time, many red lines will appear in the middle window which points you to settings where you can customise your build. Chnage the view from '''Simple view''' to '''Advanced view''' to achieve more detailed settings. Some settings must be reviewed (e.g. ACTUAL_3RDPARTY_DIR, CMAKE_INSTALL_PREFIX, etc.).

In permission-restricted environments (like Vista or Windows 7) do '''not''' set CMAKE_INSTALL_PREFIX to a restricted folder like c:\program files as this will not work and lead to many '''permission denied''' messages as cmake can't elevate your rights. Use a permission free folder instead.

If you are satisfied with your cmake-options press configure 2, 3 or 4 times until '''Generate''' becomes active. Press it and wait until cmake-gui has finished to creat all neccesary folders/files for proceeding in Visual Studio (VC).

* '''Building in VC9'''
Switch to the folder '''Where to build binaries''' named before in cmake-gui and open the file '''OpenSceneGraph.sln''' with VC. Select your desired build type (Debug, Release, RelWithDebugInfo, MinSizeRel) and press '''F7''' to build the project. It's time for some coffee as this process will take some time. After all is done (hopefully) without errors right click the INSTALL project and build it. This will copy your compiled files to their correct locations (CMAKE_INSTALL_PREFIX). Before you do that all files reside in your build folder and it's not recommende to use them from there.

* '''Some additional words'''
The first compile run will take certain long time. After you finished the first build all further builds will work much faster. So updating SVN and recompiling the sources will not take too much time in the future. Just make sure: '''ALWAYS BUILD THE INSTALL PROJECT''' as this is part of the complete process. Without this your newly built files will stay in your build but not in your install folder.

* '''Stable releases'''
You can however try and follow the building instructions from above to bet "cutting edge" with OSG.
Or you can download the latest Windows binaries from this page: [http://www.openscenegraph.org/downloads/stable_releases/OpenSceneGraph-2.8.1/binaries/Windows/VisualStudio9/]

Get the archive(s) named "openscenegraph-all[...]". Get both the Release and Debug versions if you expect to do any debug builds of FlightGear. Otherwise, just the Release version should be fine.

* '''Step 2''' - Create a the following directure structure under your FlightGear project root directory: "install\msvc90\"

Example:

C:\FlightGear\install\msvc90\

I have no idea why that directory structure was chosen, but that's what the MS VC++ project file(s) in FG CVS expect.

* '''Step 3''' - Extract the OSG archive(s) you downloaded in Step 1 in the directory you created in Step 2.
* '''Step 4''' - Rename the resulting "OpenSceneGraph-[version]" directory to simply "OpenSceneGraph".

This method is much more simple but the stable releases are far behind the actual development.

== Getting and compiling SimGear ==

* '''Step 1''' - Navigate to the base folder for your FlightGear stuff; In this example, we've chosen "C:\FlightGear"

In Windows Explorer, select the "C:\FlightGear" folder and right-click on it. From the resulting pop-up menu, choose "CVS Checkout". On the "Module" tab, enter the following in the CVSROOT field:

:pserver:cvsguest@cvs.simgear.org:/var/cvs/SimGear-0.3

At the "Module" section near the bottom of the "Module" tab, click the "Fetch List" button. You will see some brief action and may see an error and a prompt for a password. Enter "guest" for the password (without the quote symbols). From the drop-down "Module" list, select "source" and click the "OK" button to begin the checkout.

* '''Step 2''' - Since all the source code will be downloaded into a directory called '''source''', you will need to rename that directory to '''simgear'''.

Navigate to simgear\projects\VC90 and double-click on the file '''SimGear.vcproj'''. This should launch Visual C++ with the SimGear project loaded.

* '''Step 3''' - Build SimGear, either Release, Debug or both using VC++ 2008 (9.0)

<s>''Note:'' with the default settings, Visual C++ will yield many compiler warnings. Unfortunately, this is normal.</s> 
''Note:'' Fortunately due to the efforts of developing the amount of warnings is getting less and less. Actually (June 2010) not more than 30 warnings should come up during compiling under Windows.

== Getting and compiling FlightGear ==

* '''Step 1'''
Make a base folder for your FlightGear stuff; In this example, we've chosen "C:\FlightGear"

In Windows Explorer, select the "C:\FlightGear" folder and right-click on it. From the resulting pop-up menu, choose "CVS Checkout". On the "Module" tab, enter the following in the CVSROOT field:

:pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9

At the "Module" section near the bottom of the "Module" tab, click the "Fetch List" button. You will see some brief action and may see an error and a prompt for a password. Enter "guest" for the password (without the quote symbols). From the drop-down "Module" list, select "source" and click the "OK" button to begin the checkout.

A directory with the name '''source''' will then be created with all of Flightgear's source code downloaded into it. Rename this directory from '''source''' to '''flightgear'''.

* '''Step 2'''

Build either the Debug or Release version FlightGear as desired.

* '''Step 3'''

TODO: Installation.

==Checking out the FlightGear data==
The binary distribution package contains '''data''' for only a small subset of the existing aircraft and other objects. The instructions below tell you how to obtain the full set of data, in their latest, greatest form.

Make a base folder for your FlightGear stuff; In this example, we've chosen "C:\FlightGear"

In Windows Explorer, select the "C:\FlightGear" folder and right-click on it. From the resulting pop-up menu,
choose "CVS Checkout...". On the "Module" tab, enter the following in the CVSROOT field:

:pserver:cvsguest@cvs.flightgear.org:/var/cvs/FlightGear-0.9

At the "Module" section near the bottom of the "Module" tab, click the "Fetch List" button. You will see some brief action and may see an error and a prompt for a password. Enter "guest" for the password (without the quote symbols). From the drop-down "Module" list, select "data" and click the "OK" button to begin the checkout.

The result of the checkout is a directory called C:\FlightGear\data. To use this data directory with the FlightGear program, you can either (a) move it to C:\Program Files\FlightGear\ directory or (b) direct FlightGear to the actual location of this data directory from the command line or within the fgrun launcher application.

== External links ==
* [http://www.microsoft.com/express/vc/ Microsoft Visual C++ (Express) Download page]
* [http://www.geoffmclane.com/fg/index.htm FlightGear Build Centre]

{{Building}}

FlightProSim

2010-05-24T20:40:46Z

Quadunit404: /* Why did you refuse a money offer from FlightProSim? */

As many people will be aware, there is a new flight simulator product that is being widely and actively marketed at the moment - Flight Pro Sim. As it is almost entirely based on FlightGear, there is some confusion between the two. To help provide some clarity, and answer some common questions, we (the core FlightGear development team) felt it was appropriate to make a statement, and provide a FAQ.

FlightGear is an open-source flight simulator that was started in 1996. It is released under the GNU General Public License v2, and as such, it is free to use, modify and distribute with few restrictions. It has been developed with the collaboration of a large number of individuals over the last 12 years. FlightGear can be downloaded at no cost from http://www.flightgear.org.

Flight Pro Sim is a commercial product very heavily based on FlightGear. Investigation by a number of the FlightGear developers has found no difference between this and the FlightGear v1.9.1 release other than a change of name. Flight Pro Sim is in no way endorsed or supported by the core FlightGear development team. Given the similarities between Flight Pro Sim and FlightGear, we would recommend that prospective buyers download FlightGear for free and satisfy themselves that Flight Pro Sim provides worthwhile value for money before purchasing it.

==I bought FlightProSim, what to do?==
If you have bought FlightProSim, try to get your money back as soon as possible. You can have (almost) the same software for free nevertheless! They guarentee a 60 day money back trial period, so this should be no problem if you react quickly.

The FlightGear developers are interested in the package to see whether the package complies with the GNU GPL terms or not. Therefore we would like to receive a package for inspection. If you own a package and were unable to get your money back, please contact the developers through the [[mailing list]].

==Legal or illegal?==
The [[GNU GPL]] license under which FlightGear is released allows reselling under certain terms. Many FlightGear developers have difficulties with the way FlightProSim is acting and doubt if they are acting legally. If you have any (inter)national law knowledge, please contact the developers at the [[mailing list]], they will welcome any legal support.

==What are the differences between the two?==
As far as we have been able to make out, the only difference between FlightGear v1.9.1 and FlightProSim is a change in name throughout the software, and the fact that you have to pay for it.

==Why did you refuse a money offer from FlightProSim?==
After a lot of negative criticism from the FlightGear developer, FlightProSim offered to fund a competition in which a developer of a nice new feature is rewarded with a sum of money ($250). The FlightGear developers have more or less un-officially decided to not accept the money offer. A couple of the reasons include:
* If the guy behind FPS really is interested in improving a flight sim, he would input his addons/improvements back into the FlightGear community so the software can be further developed.
* Everyone is allowed to sell FlightGear, as long as they comply with the GNU GPL v2 license. FPS did not in the past, and thus we do not trust them any more. Only after lots of requests from our side they changed their website telling the visitors (in a very small message without link) that it is actually an adaption of free software
* FlightProSim also copied all content from our wiki (and initially also our main website). That does not give a positive developer impression, more like a "we-want-money-fast-and-without-much-effort" attitude. Apart from the fact that FPS is actually part of a money making company, rather than a software developing one...

==Why do FlightGear developers allow this?==
The freedom to modify and enhance FlightGear is a core part of the project, and of open-source in general. Restricting the modifications that are allowed and what people can do with the software goes against that ethos.

McDonnell Douglas DC-10-30F

2010-02-02T21:03:28Z

Quadunit404: /* Reference */

{{non-stable}}

{{infobox Aircraft
|image =DC-10-30F.png
|alt =DC-10-30 first fly
|name =McDonnell Douglas DC-10-30F
|type =Airliner
|livery = Fedex, Varig
|fdm =JSBSim
|status =Under development
|authors =Isaias V. Prestes
|fgname =<tt>DC-10-30F</tt>
|download =http://presteshangar.wikidot.com/mcdonnell-douglas-dc-10-30
|3dcockpit =red
|animations =red
|carrier =red
}}

= The DC-10-30 =

The McDonnell Douglas DC-10 is a three-engine medium- to long-range widebody airliner, with two engines mounted on underwing pylons and a third engine at the base of the vertical stabilizer. The most common model, built with General Electric CF6-50 turbofan engines and larger fuel tanks to increase range and fuel efficiency, as well as a set of rear center landing gear to support the increased weight. It was the second long-range model after the -40 and very popular with European flag carriers. Produced from 1972 to 1988, the DC-10-30 was delivered to 38 different customers (163 built).

== Completed/In progress ==

The aircraft development was started at 31/01/2010.

[[File:DC-10-30F_2.png|320px|right|thumb|DC-10-30 at SBPA]]
[[File:DC-10-30F_3.png|320px|right|thumb|DC-10-30 at SBPA]]

=== Completed ===
* Models - 3D models
* Splashs - aircraft specific splash screens
* Engines - various different engines supported by the FDMs
* FDMs - various FDM configs that are supported
* Views - aircraft-specific views
* Animations
* UVmap
* Texture template
* Nasal - aircraft specific Nasal scripts

* Extras

# README
# TODO
# AUTHORS
# CHANGELOG

=== In progress ===
* Liveries - livery-specific textures
* Panels - 3D cockpit panel
* Instruments - aircraft specific instruments
* Systems - electrical system

=== To do ===
* Sounds - aircraft specific sounds
* Docs - aircraft specific documentation

Extras that should be completed:

* HELP
* FEATURES

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

=Authors=
Isaías V. Prestes, isaias at gmail dot com.

=Reference=
[*http://en.wikipedia.org/wiki/McDonnell_Douglas_DC-10 Wikipedia DC-10-30]

{{MDouglas}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:McDonnell Douglas]]

McDonnell Douglas DC-10-30

2010-02-02T21:02:13Z

Quadunit404: /* Reference */

{{non-stable}}

{{infobox Aircraft
|image =DC-10-30.png
|alt =DC-10-30
|name =McDonnell Douglas DC-10-30
|type =Airliner
|livery = Fedex, Varig
|fdm =JSBSim
|status =Under development
|authors =Isaias V. Prestes
|fgname =<tt>DC-10-30</tt>
|download =http://presteshangar.wikidot.com/mcdonnell-douglas-dc-10-30
|3dcockpit =red
|animations =red
|carrier =red
}}

= The DC-10-30 =

The McDonnell Douglas DC-10 is a three-engine medium- to long-range widebody airliner, with two engines mounted on underwing pylons and a third engine at the base of the vertical stabilizer. The most common model, built with General Electric CF6-50 turbofan engines and larger fuel tanks to increase range and fuel efficiency, as well as a set of rear center landing gear to support the increased weight. It was the second long-range model after the -40 and very popular with European flag carriers. Produced from 1972 to 1988, the DC-10-30 was delivered to 38 different customers (163 built).

== Completed/In progress ==

The aircraft development was started at 09/29/2009.

[[File:DC-10-30_2.png|320px|right|thumb|DC-10-30 at SBPA]]
[[File:DC-10-30_3.png|320px|right|thumb|DC-10-30 at SBPA]]

=== Completed ===
* Models - 3D models
* Splashs - aircraft specific splash screens
* Engines - various different engines supported by the FDMs
* FDMs - various FDM configs that are supported
* Views - aircraft-specific views
* Animations
* UVmap
* Texture template
* Nasal - aircraft specific Nasal scripts

* Extras

# README
# TODO
# AUTHORS
# CHANGELOG

=== In progress ===
* Liveries - livery-specific textures
* Panels - 3D cockpit panel
* Instruments - aircraft specific instruments
* Systems - electrical system

=== To do ===
* Sounds - aircraft specific sounds
* Docs - aircraft specific documentation

Extras that should be completed:

* HELP
* FEATURES

=== Related lists ===
* [[Aircraft]]
* [[Aircraft Todo]]

=Authors=
Isaías V. Prestes, isaias at gmail dot com. If anyone can complete any other aspects of the Model PM 'isix' in the Forums or email.

=Reference=
[*http://en.wikipedia.org/wiki/McDonnell_Douglas_DC-10 Wikipedia DC-10-30]

{{MDouglas}}

[[Category:Aircraft]]
[[Category:Aircraft TODO]]
[[Category:Airliners]]
[[Category:Civilian aircraft]]
[[Category:McDonnell Douglas]]

User:Quadunit404

2010-01-15T03:26:15Z

Quadunit404: Created page with 'Hello! I have been playing FlightGear for a little under a year. I enjoy it more than MSFS, although it tends to lag up my computer or absorb 50-80% of my CPU. I wish that pre-re…'

Hello! I have been playing FlightGear for a little under a year. I enjoy it more than MSFS, although it tends to lag up my computer or absorb 50-80% of my CPU. I wish that pre-rendering frames also went towards OpenGL games... stupid NVIDIA...