FlightGear wiki - User contributions [en]

Howto:Creating FlightGear Promo Videos

2013-02-26T18:28:51Z

Trez: /* Video Recording Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k

== Examples ==
{{#ev:youtube|Cmhy9zjRBGs}}
{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the latest [[changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac | only captures the full screen
* VLC (free, multi-platform)
* Fraps (paid) - Windows | works great if configured right
* recordmydesktop - Linux

MAGIX is a set of Applications that handles video and audio editing, it also has a recording software.

To install record my desktop on Ubuntu(and it's variations), Linux Mint and Debian open the terminal and type:
'''sudo apt-get install gtk-recordmydesktop'''

== Video Editing Software ==
Programs to edit your video:

* VirtualDub (free) - Windows
* IMovie (free) - Mac | IMovie comes with every mac for free it costs 15 dollars to upgrade to the latest version though
* Adobe Premiere Pro (paid) - Mac & Windows
* Sony Vegas Pro (paid) - Windows
* Kdenlive (Free) - Linux,Mac |Great editor with many functions

== Finally ==
Everything else is up to the editor... ;)

Howto:Creating FlightGear Promo Videos

2013-02-26T18:07:29Z

Trez: /* Video Editing Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k

== Examples ==
{{#ev:youtube|Cmhy9zjRBGs}}
{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the latest [[changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac | only captures the full screen
* VLC (free, multi-platform)
* Fraps (paid) - Windows | works great if configured right

MAGIX is a set of Applications that handles video and audio editing, it also has a recording software.

== Video Editing Software ==
Programs to edit your video:

* VirtualDub (free) - Windows
* IMovie (free) - Mac | IMovie comes with every mac for free it costs 15 dollars to upgrade to the latest version though
* Adobe Premiere Pro (paid) - Mac & Windows
* Sony Vegas Pro (paid) - Windows
* Kdenlive (Free) - Linux,Mac |Great editor with many functions

== Finally ==
Everything else is up to the editor... ;)

Howto:Creating FlightGear Promo Videos

2013-02-26T18:04:56Z

Trez: /* Video Recording Software */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k

== Examples ==
{{#ev:youtube|Cmhy9zjRBGs}}
{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the latest [[changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac | only captures the full screen
* VLC (free, multi-platform)
* Fraps (paid) - Windows | works great if configured right

MAGIX is a set of Applications that handles video and audio editing, it also has a recording software.

== Video Editing Software ==
Programs to edit your video:

* VirtualDub (free) - Windows
* iMovie (free, I think) - Mac (IMovie comes with every mac for free it costs 15 dollars to upgrade to the latest version though, For our linux friends kdenlive is a great editor)
* Adobe Premiere Pro (paid) - Mac & Windows
* Sony Vegas Pro (paid) - Windows

== Finally ==
Everything else is up to the editor... ;)

Howto:Creating FlightGear Promo Videos

2013-02-26T17:59:06Z

Trez: /* Performance */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k

== Examples ==
{{#ev:youtube|Cmhy9zjRBGs}}
{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the latest [[changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

A good way to get better framerate is to slow the video down in the flightgear replay and speeding it up in the editor.

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac
* VLC (free, multi-platform)
Also I use Fraps for recording. If you configure it the right way, it works fantastically!

A friend uses MAGIX and he quite enjoys it, but I'm not sure of its quality.

== Video Editing Software ==
Programs to edit your video:

* VirtualDub (free) - Windows
* iMovie (free, I think) - Mac (IMovie comes with every mac for free it costs 15 dollars to upgrade to the latest version though, For our linux friends kdenlive is a great editor)
* Adobe Premiere Pro (paid) - Mac & Windows
* Sony Vegas Pro (paid) - Windows

== Finally ==
Everything else is up to the editor... ;)

Howto:Creating FlightGear Promo Videos

2013-02-26T17:51:56Z

Trez: /* Audio / Background Music */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k

== Examples ==
{{#ev:youtube|Cmhy9zjRBGs}}
{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the latest [[changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

Using the aircraft sounds also showcases FlightGear well.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac
* VLC (free, multi-platform)
Also I use Fraps for recording. If you configure it the right way, it works fantastically!

A friend uses MAGIX and he quite enjoys it, but I'm not sure of its quality.

== Video Editing Software ==
Programs to edit your video:

* VirtualDub (free) - Windows
* iMovie (free, I think) - Mac (IMovie comes with every mac for free it costs 15 dollars to upgrade to the latest version though, For our linux friends kdenlive is a great editor)
* Adobe Premiere Pro (paid) - Mac & Windows
* Sony Vegas Pro (paid) - Windows

== Finally ==
Everything else is up to the editor... ;)

Howto:Creating FlightGear Promo Videos

2013-02-26T17:50:12Z

Trez: /* Audio / Background Music */

Contributors: LukeaFG, Osjcag, Trez, connect, sa7k

== Examples ==
{{#ev:youtube|Cmhy9zjRBGs}}
{{#ev:youtube|MZVCmHgAX6Y}}

== Content ==
Use the latest [[changelog]] for the list of changes or updates to include in the video. Probably, promo videos should focus on feaures to be found in the release, not on optional aircraft, addons etc. (see screenshot guidelines).

== Style / Appearance and Branding ==
Place the FlightGear logo in some corner of the video and a link to the official website, i.e. flightgear.org

I would probably make sure to add links (or even watermarks) to each video, so that "flightgear.org" is made very prominent - to make it more difficult for scammers to reuse such promos for their own purposes ... For the same reasons, we may want to use the terms "free" and "open source" to ensure that people cannot easily reuse the promo videos to sell rebranded versions of FG. And maybe each review you should have a date added, so that people know just how recent the promo video really is ? A semi transparent FlightGear logo in the corner of the video might help

== Audio / Background Music ==
Use royalty free audio or ask for full permission, FlightGear is opensource your video should follow that as much as possible. Look up royalty free on google, there are many websites that feature royalty free music. [https://machinimasound.com/ MachinimaSound] is a great site for royalty free music and it's made for content that features gaming.

== Localization ==
We may still want to provide an option to localize/translate videos (I understand that's made possible for YT videos), to give even wider exposure to FG. I think YT videos can have text comments and audio translated for different audiences. Also, using the changelog to create a promo is definitely a very good idea!
You can create an interactive transcript for YouTube in a .txt file in a different language which would be helpful.

== Performance ==
Only record video if FlightGear's framerate is high (this prevents jerky motions... Example of what I mean here: http://www.youtube.com/watch?v=JW7ZrGpSCbk)

== Format & Codecs ==
* Container: mp4
* Codec: h264 (for optimal quality)
* Resolution : 720p or 1080p (progressive)
* Framerate: 24 - 30FPS (30 is the maximum YouTube supports)
* Aspect ratio: 16 ; 9 (any other ratios will have unwanted back bars in your video)

You should also consider encoding with webm, which is google's royalty free codec if you are just planning to upload to youtube.

== Video Recording Software ==
Programs to record your video:
* CamStudio (free) - Windows
* Quicktime (free) - Mac
* VLC (free, multi-platform)
Also I use Fraps for recording. If you configure it the right way, it works fantastically!

A friend uses MAGIX and he quite enjoys it, but I'm not sure of its quality.

== Video Editing Software ==
Programs to edit your video:

* VirtualDub (free) - Windows
* iMovie (free, I think) - Mac (IMovie comes with every mac for free it costs 15 dollars to upgrade to the latest version though, For our linux friends kdenlive is a great editor)
* Adobe Premiere Pro (paid) - Mac & Windows
* Sony Vegas Pro (paid) - Windows

== Finally ==
Everything else is up to the editor... ;)

File:Styler.png

2012-04-08T17:20:51Z

Trez: flightgear gui styler

flightgear gui styler

Howto:Create a custom GUI style

2012-04-08T17:18:18Z

Trez:

== What is a GUI? ==
A GUI (graphical user interface) is is a type of user interface that allows users to interact with electronic devices with images/buttons rather than text commands.
As of version 2.6 there are two diferent gui types:
[[File:menubar1.jpg]]
[[File:menubar2.jpg]]
== Creating your custom gui style ==
Creating a gui style is fairly easy. and there are infact 2 diferent ways of making one. Eather way uses the the RGB color system and alpha to add transparancy.
=== Gui styler ===
The first and easier way is using the gui styler just turn the knobs until you get the color you want it's fairly easy and quick your gui can be finished in less than ten minutes.

the styler is included as of 2.7 GIT but you can get it here[http://flightgear.org/forums/viewtopic.php?f=18&t=15611#p152423]

Howto:Create a custom GUI style

2012-04-08T15:48:45Z

Trez: Created page with "== What is a GUI? == A GUI (graphical user interface) is is a type of user interface that allows users to interact with electronic devices with images/buttons rather than text co..."

FlightGear Newsletter January 2012

2012-01-11T20:19:22Z

Trez: /* FlightGear on youtube */

{{newsletter}}
{{TOC_right|limit=2}}

''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. So if you know about any FlightGear related news or projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''

== Development news ==

=== 2.6.0 release preparations ===
On January 17, the release branches were created from our [[Git]] repositories. From then on, no new features (and aircraft) shall be pushed. Only bug fixes are accepted.

FlightGear 2.6.0 will be released on February 17!

=== Experiment: A new bounty system ===
If somebody would like a specific feature implemented, it will be posted in the wiki (because there is no forum). Then if somebody wants to take on the development, they can start it and if they feel they have fulfilled the requirements, they submit the project to the person who is offering the bounty.

If it is a feature that many people want, quite often more people are adding to the bounty and then each person decides individually if the result fits their ideas and if they want to pay the bounty.

A bounty is a specific amount of money for completing a specific task which can be claimed by an individual or group which completed that task.

Read on at [[Bounty (Overview)]].

== Interview with a contributor (Durk Talsma) ==
''In each edition we have an interview with a contributor. Suggestions for possible questions are available on [[interview questions]], you are invited to come up with new questions and interview ideas obviously! Anyone is free to write an interview (with him-/herself or others) for next month's newsletter! If you'd like to help interview a contributor or get interviewed, please do consider adding yourself to the [[list of interview volunteers]]! To keep this going and less awkward, we are currently trying to come up with the convention that former interviewees become next month's interviewers.''

* '''What is your forum nickname?'''
Hehe, guess once. ☺

* '''How long have you been involved in FlightGear?'''
Almost since the beginning, actually. I first heard about the project in 1997, when I got an email from Curt Olson, in response to a posting on the usenet newsgroup rec.aviation.simulators.

* '''What are your major interests in FlightGear?'''
I like the open nature of the project and the possibility to contribute at various levels.

* '''What projects are you working on right now?'''
I am actually doing several different things for FlightGear. My main project is developing a fully integrated AI air traffic system that contains autonomous vehicles, an ATC system that interacts with both AI controlled aircraft and with the user controlled aircraft. In addition to that, I am one of the editors of the main website, editor of the FlightGear facebook page, involved in the release process, code committer, and organizer of the annual FlightGear booth at FSWeekend in Lelystad (EHLE). In addition, I have recently taken over the administrator role for taxidraw.

* '''What do you plan on doing in the future?'''
I don’t expect the AI system ever to be finished, so I’m fully concentrating my coding efforts on this project.

* '''Why is it that you are interested in flight simulation or aviation in general?'''
As a kid I was fascinated by space travel, the Apollo missions to the moon, etc, watching every program on TV, and reading every book I could lay my hands on. As a six-year old, I visited Schiphol (EHAM) airport for the first time, and that sparked my fascination for the big jet airliners. Kind of like every kid at one stage, I wanted to become a pilot. My real interest in aviation didn’t start until I was nearly 20 though, after visiting an airshow at Leeuwarden airforce base (EHLE). This was around the same time as when I got my first PC, a second hand 286DX, which I bought from a relative living in Germany, with a 40 Mb hard disk and 1 Mb of ram. It had a German version of Microsoft Flight Simulator 4.0 preinstalled. So, in addition to learning to “fly” I learned the German word for “crash” as well.

* '''Are you happy with the way the FlightGear project is going?'''
Yes absolutely. We are currently in the process of further improving our infrastructure, by setting up things like the release plan, formalizing the rules for commit access, aircraft maintenance, and we’re brainstorming about feature requirements for the long term. Firm ideas are present for modularization of the FlightGear code, and some ideas for an integrated launcher GUI have recently been coined in a very informal setting. It will certainly take quite some time before these plans are all realized, but I think that the project is more vital and alive as ever. I’m also just amazed at some of the recent developments, such as Frederic Bouvier’s project Rembrandt, Thorsten Renk’s, local weather system, or Martin Spott’s ongoing efforts to build a unified infrastructure for scenery generation.

* '''What do you enjoy most about contributing to FlightGear?'''
I think there are a number of aspects that I really enjoy. One of them is the collaboration with other people. Being part of the development team, we’re all pretty much equals, and regardless of one’s age, background, occupation, political or religious conviction, we all share something we like and like to collaborate on. That is really enjoyable. It may also happen that somebody just jumps in and finds a solution in no time for a problem that has been cracking my brain for ages. For example, Adrian Musceac, recent work on generating AI traffic patterns was really something amazing. Likewise, I enjoy the interaction with many other talented people, such as Brett Harrison, who’s just so amazing at making convincing liveries. Obviously there are many other talented people around whom I really enjoy working with and it’s a shame I can’t name them all. Secondly, I also really enjoy having the privilege of being the first to experience a new feature for the first time. I was the first person ever to see the sun and moon appear in a desktop Flight Simulator, and that is a little bit special.

* '''Are there any "hidden features" you have worked on in FlightGear that new users may miss?'''
Yes, my original contribution to FlightGear was some code to calculate the position of the Sun, Moon, and even the planets. Both the sun and moon are pretty much taken for granted now, but back then (in 1997) FlightGear was the first PC based simulator that actually had a physical rendering of the sun and moon! Nobody will probably even see the planets, but I got the code almost for free, once I figured out how to calculate the solar and lunar positions, so their a little bit of an Easter egg. After finishing the celestial code, and before starting the AI traffic system, I initiated many projects that I subsequently handed over to others. As such, I have extended the time calculation code to deal with local time, and to allow the user control over the time of day, and implemented the original graphical user interface (GUI) system, and the original 2D cloud layers.

* '''What advice can you give to new contributors who want to get started on their first aircraft/new feature/Nasal script?'''
Be optimistic, be naïve, be realistic, and start modestly. Set yourself an attainable goal! I should probably explain what I mean by this. When we started out, back in 1996-1997, we were what I would now describe as incredibly optimistic in the sense that we believed that we could pull this off, but we were also somewhat naïve in the sense that we really didn’t have any firm idea about the challenges that lay ahead. But, we were able to pull it off, so this shows that we were right after all. But, if you want to contribute don’t start with your magnum opus. Before starting out, take some time to familiarize yourself with the project, get to know the code base, data structure or workflow. In addition, making a good first impression helps. Over the years we’ve seen a tremendous amount of grand ideas and not many of them have materialized, so we’re naturally a little apprehensive you may not find an immediate warm welcome, but if you do come up with a well thought-out idea, you may convince the development team, especially if you can substantiate your ideas with some working code to back it up.

* '''Have you previously used other flight simulators or simulation software in general?'''
Well, as mentioned before, I started out with FS4, and have pretty much had every version since then, until FS2004. The latter version got me interested in the AI system. When I started playing with the FS2004 equivalent of the ATC system I and began to notice its programming flaws. Determined that I could do this better, I started drawing out my own plans, and since than, I haven’t really touched any other simulator.

* '''How does FlightGear compare in your opinion?'''
I like FlightGear better because it’s a platform that is constantly moving. I almost exclusively run the cutting edge development version, so occasionally you’re in for a little surprise. Be it positive or negative. But that keeps things a little exciting to me.

* '''Do you remember what first got you interested in FlightGear? How did you learn about FlightGear? In other words, why did you actually download and try FG?'''
Yeah, that’s a long story. I was reading the usenet rec.aviation.simulators quite frequently at the time, had been exploring Linux for a few years, and finished my C++ programming course at university. This was around 1997, so the Linux distros weren’t as advanced as they are these days, and you still had to do quite a lot yourselves. One particular afternoon, I came across a usenet posting, which read “OPEN LETTER TO ALL FLIGHTSIMULATOR DEVELOPERS”. This was around the time that Microsoft FS97 was the latest version, and many users were dissatisfied. The original poster wanted to write a letter, on behalf of every dissatisfied user, to ask for a better version, asking the big game companies to incorporate their wish list. I responded to the thread, stating that if we really wanted a sim of our own, we should probably do it ourselves. I remember being a little anxious, because I wasn’t sure whether I would actually be able to substantiate that claim, if we were to follow it up. So, a few days later, I was actually a little apprehensive when I opened up my mailbox and found an email from a guy named Curt Olson, inviting me to have a look at, what would eventually become the flightgear.org website. Well, the rest is history I guess...

* '''What was your first impression about FlightGear?'''
That’s a really interesting question, because there was no FlightGear so to speak of. When I joined, Curt had hacked together a few proof-of-principle demos; the one I downloaded was called linux-demo-0.0.7.tar.gz, if I recall correctly, and it consisted of a small sample of elevation data from a chuck of terrain near Arizona, source code of a primitve (by today’s standards) OpenGL based viewer, a copy of Bruce Jackson’s larcsim FDM, and a simple keyboard interface. But it was exciting to get it to compile, and run!

* '''Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?'''
It’s scalability, open architecture, and the fact that it can be a great test bed for ideas, as well as the fact that there is no need for third party add-ons. By bringing every suitable user contribution into a single repository, we essentially create our own add-ons, and in the long run that should remove the burden from the end user to search for extensions.

* '''Do you think it is necessary to know how to program in order to contribute to FlightGear?'''
No way. In fact it never really has been a requirement, even in the old days when there was a lot more emphasis on C++ development, we already had a need for non-coding developers. Think about documentation writers, etc. These days, the balance is actually really shifting away from programming to artwork. The FlightGear world is essentially still largely an empty place, so we really have a need for high-quality buildings. Many of the exciting developments going on right now are in the development of new scenery textures, 3D modeling, and livery painting. These are actually skills that I essentially lack, so I have a lot of respect for the people working in these areas.

* '''Have you ever used FlightGear professionally or for educational purposes?'''
I once tried in my previous job, but the computer we bought for the project had serious overheating issues, so the project never really came off the ground. In the mean time, I found a different job, so the project was shelved.

* '''What about FlightGear as a "game", do you think it can be used as such?'''
Probably, I like to use FlightGear purely for fun, so usually I just make up my own challenges, such as performing a bad weather landing, taking off and landing on an aircraft carrier, or playing with my latest AI/ATC code. Once finished, the ATC code will add a little bit of a game element, because it will expect you to fly specific routes, arrive at specific locations at a specific time, so as not to clash with other traffic etc etc. The system isn’t finished yet, but with some hacking I did quite recently manage to complete a traffic circuit under guidance of the ATC system, and it’s quite tricky to do right. So, there are some “gamey” aspects of FlightGear that are quite realistic and hopefully challenging. Having said that, I see absolutely no need for any formal gaming rules, or game like features such as setting off explosives and the like. Like many of the other developers, I like to keep FlightGear civil(ized). I don’t object to simulating military aviation though, as long as it doesn’t serve the purpose of glorifying death and destruction.

* '''On average, how much time do you spend working with/contributing to FlightGear?'''
Hard to say, it varies quite a bit with my day job requirements, but I think on average maybe one or two hours a day.

* '''Which of the more recent FlightGear developments do you consider most interesting/appealing?'''
There are quite a few. Of the individual projects, I really think that project Rembrandt (Frederic Bouvier’s shadow rendering code) is really exciting. But so is the new effort to unify all the shaders, the atmospheric haze and scattering, and Thorsten Renk’s local weather. I’m also quite happy with the progress we made with the AI traffic/ATC system, even though it’s not finished yet. But, what I think is perhaps even more exciting are some of the long-term infrastructural changes we have recently discussed. I can’t say too much about that yet, because many of the ideas haven’t been formalized yet, but making FlightGear more modularized by making use of HLA technology, and perhaps a more integrated GUI and launcher program are some of the exciting developments that I can see happening in a few years from now.

* '''Is there some feature that you'd truly like to see in FlightGear one day?'''
Yeah, there are some. Obviously, I’d like to see my own project come to it’s full potential, but in addition to that, I would like to see full scenery development of the polar regions of our planet. One year ago I visited Antarctica in real life, and this is just a very exciting area for flying. I’d also like to see the possibility of lower earth orbital space flight, more seamless terrain textures.

* '''What do you think could be done to attract even more new users and contributors to FlightGear?'''
Establish a good balance between developing new stuff and doing some public relations work. For the project the key question for survival is not to attract many users, but to attract potential contributors. Obviously, the way to do this is to attract many users, and to hope that there will be a few potential contributors among them.

* '''What about interacting with the FlightGear community? Any tips/experiences you'd like to share?'''
Nothing really special; just use your everyday courtesy, and keep realizing that we’re all volunteers. I’m usually not that active on the forum or mailing list, but I can tell from 15 years of experience that an intelligent and reasonable response is far more likely to create some momentum than a hurried response that is written in a spur of emotion. Also, I have observed that there is hardly any relation between action and words on either the mailing list or the forum. So when your new to the community, just hang around, get to know the characters and try to establish whom you can trust to be a knowledgeable source of information and who just raises a lot of dust.

* '''Have you ever recommended FlightGear to other users, friends/family?'''
Not really, my friends and family aren’t really into flight simulation.

* '''Is there anything else you'd like to share with us?'''
Yeah, have a lot of fun, and if you can try to contribute something to the project.

Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX

== Snapshot releases ==
Every now and then, easy-to-install development snapshots are created (usually, twice montlhy). These snapshots depict a recent state of the development version of FlightGear. By using them users can test out features that will be included in the upcoming release. Testers are encouraged to file bugs at [http://code.google.com/p/flightgear-bugs/ the issue tracker].

The snapshot can be download via the links at the bottom of this page: http://www.flightgear.org/download/. Updates and feedback can be found [http://flightgear.org/forums/viewtopic.php?f=28&t=10488&p=144233&hilit=snapshot#p144233 at the forum].

== Nasal for newbies ==

== New software tools and projects ==

== FlightGear addons and mods ==

== In the hangar ==

All the way back in May 2011, we addopted a new status-rating system for aircraft. So far, only a few have actually been rated, as can be seen in the list 'hockenberry' set up at [https://docs.google.com/spreadsheet/ccc?key=0ApzphjA4w05ndF94Y2F0bzJTbHQ5QTJXZXJRcUVRbWc&hl=en_US Google Docs]. If you're an aircraft developer and your aircraft is/are not on the list, please consider rating their status. All you'll need to know/do is described at [[Formalizing Aircraft Status]]. If you'd just like to get started contributing to FlightGear, this would also seem like an excellent way to get started.

=== New aircraft ===

=== Updated aircraft ===

=== Liveries ===

== Scenery corner ==
=== Dutch windturbines ===
[[File:Prinses_Amaliawindpark_overview.png|thumb|270px|Overviewing the 60 wind turbines of Prinsess Amaliawindpark, 20km west of the Netherlands.]]
The Netherlands have slightly less than 1900 windturbines at the moment. Since this month, 757 of them are in FlightGear!

Adding them is relatively easy. Since we have a generic windturbine model available (<tt>Models/Power/windturbine.xml</tt>), it's just a matter of finding the GPS coordinates. Some of the larger windparks list locations on their websites. Other windturbines can be positioned based on the FlightGear scenery (with [[CORINE]] data, for more accuracy), or via satellite imagery. Some countries even have a site similar to [http://www.w-i-n-d.nl this website] from the Dutch government, that has a map that shows the locations of all windturbine(park)s.

Locations for windturbines and other shared objects can be easily submitted via [http://scenemodels.flightgear.org/submission/shared/ the new submission form], that we mentioned in last month's newsletter.

For the offshore Prinses Amaliawindpark, a custom windturbine model has been made. Resembling the Vestas V80-2.0 MW edition. [http://scenemodels.flightgear.org/modeledit.php?id=2418 The model] can be easily re-used on other offshore windparks, via the method described above.

=== Airports ===
==== Congonhas - Brazil ====
[[File:Grupofgbrsmall.png|right]]
The Airport of Congonhas is currently being modeled, completely from scratch, by the [http://www.grupofgbr.com.br Grupo FG BR]. Download our logo and link us, please.
{{#ev:youtube|tUQCMTmQ-5Y}}

== 360 degrees motion simulator ==
''Contributed by Samuel DeRose''

Several years ago during a trip to Washington DC, my family got tickets to a flight simulator ride at the Air and Space Museum. All of us were amazed at the innovation of the Smithsonian's interactive simulator ride, having grown accustom to the common, mediocre, hydraulic-platform simulators often seen at carnivals and amusement parks. These simulators could roll 360 degrees, continuously, and could tilt about 30 degrees along the pitch axis.

Inspired by that experience, our group ("Team Viper") is attempting to create an even better version. Like the one at the Air and Space Musuem, ours will roll 360 degrees. In addition we also intend to allow 360 degrees of motion along the pitch axis. Since our family are huge Battlestar Glactica fans we thought it would be fun to theme the interior of the simulator as a Viper fighter from the show.

One big challenge for us is the physical construction of the simulator, but an even greater feat lies in the software to control the motion platform. In order for the game to feel real (and also to avoid motion sickness), the visuals that will be displayed across three 22" monitors need to be fully synced to what the rider feels in his inner ear and his stomach. Thankfully we found FlightGear, which allows us to easily read the plane's flight dynamics from the sim so we can calculate the angles to orient the motion platform.

== Aircraft of the month ==

== Airport of the month ==

== Screenshot of the month ==
[[File:C172p-SanFrancisco.png|800px]]

Cessna c172p near San Francisco flying over the ocean.

== Suggested flights ==
===Khorog, Tajikistan===

[[File:Fw190HinduKush.jpeg|right|thumb|Approaching a bank of snow-covered mountains in the south of the Hindu Kush]]
Surrounded by spectacular mountains and nestled in the end of a valley, Khorog Airfield (UT1C) makes an interesting place to land. It can only be approached by flying down the curved valley that snakes in from the North. Flying from here to OPCH (Chitral, Pakistan) at around 500ft AGL all the way is a wonderful way to explore the Hindu Kush mountains.

If you bring a piston engined aircraft, be prepared to adjust the mixture as you climb - at the highest point in the flight, you will be at around 22000ft. Also, don't forget to carry plenty of fuel - there are very few airfields in the Hindu Kush that exist in FlightGear. This is a scenery bug that will hopefully be fixed in the future.

More amazing places to visit can be found at [[Suggested Flights]].

== Aircraft reviews ==

== Wiki updates ==
===New articles===
<DynamicArticleList>
type=new
count=10
</DynamicArticleList>
===New aircraft articles===
<DynamicArticleList>
type=new
count=10
categoryRoot=Aircraft
</DynamicArticleList>
===Most popular newsletters===
<DynamicArticleList>
type=hot
count=5
categoryRoot=FlightGear Newsletter
</DynamicArticleList>

== Community news ==
=== FlightGear on youtube ===
12 Days of Flight Tips - by [http://www.youtube.com/user/osjcag oscar]

{| class="vatop" valign="top"
! align="left" |
! align="left" |
|valign="top"|
*[http://www.youtube.com/watch?v=RbB5Sn_ag-A Day 1 - FG 2.4 Map]
*[http://www.youtube.com/watch?v=hLB7jui1U5c Day 2 - Useful Keys]
*[http://www.youtube.com/watch?v=L1aNBV7JBIs Day 3 - Animated Jetways]
*[http://www.youtube.com/watch?v=hz1c8nuY62U Day 4 - Approach & Landing tips!]
*[http://www.youtube.com/watch?v=CeFpvAR6sqg Day 5 - Wiki & Newsletter]
*[http://www.youtube.com/watch?v=0HjkFHatYMI Day 6 - Rendering Options]
|valign="top"|
*[http://www.youtube.com/watch?v=_LcZ93Q33D4 Day 7 - Cockpit Instruments]
*[http://www.youtube.com/watch?v=rITkJyTb5-Q Day 8 - Brake After Landing]
*[http://www.youtube.com/watch?v=CLCXwuWvDGQ Day 9 - Virtual Airlines]
*[http://www.youtube.com/watch?v=HdVCVH0XMXM Day 10 - Manual Flight Tips]
*[http://www.youtube.com/watch?v=NeDMwBMg6Gs Day 11 - Multiplayer ATC]
*[http://www.youtube.com/watch?v=9FSdbw_c9qA Day 12 - Crosswind Landing Tips]
|}(Or watch all the episodes in [http://www.youtube.com/watch?v=RbB5Sn_ag-A&list=PL569D227E5E767F3D a playlist])

[http://www.youtube.com/user/FlyTristarairlines?feature=watch Trez] started a new video series Final Approach:
[http://www.youtube.com/watch?v=Au6eS6Y6sYY&list=PL60A11F004175486E&index=1&feature=plcp episode 1]

=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===

== Useful links ==
== 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]].

=== Call for volunteers ===
* The [[OpenRadar]] project is looking for a new maintainer.
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer.

=== Did you know ===

[[Category:FlightGear Newsletter|2012 01]]

Virtual airlines

2011-12-24T01:58:18Z

Trez:

A '''virtual airline''' (VA) is a dedicated hobby organization that uses flight simulation to model the operations of an airline. Virtual airlines generally have a presence on the internet, similar to a real airline. There are over 100 virtual airlines of significance currently active in the internet (supporting a number of flightsims), with thousands of participants involved at any one time each using different simulator platforms.

== A note ==
There has been a rapidly expanding number of VAs in Flightgear, and there is not enough people to support this bugeoning explosion of VAs. So think twice about creating a VA, because we're running out of pilots.

On the other hand, if you really want it and are confident, go ahead and create! This is flightgear, Fly Free! You're FREE to do what you want.

== Purpose ==
Virtual airlines were started to give a sense of purpose to activities conducted within a flight simulator. This basic premise has evolved over time, along with available technology, to provide increasing levels of immersion but always with the same core purpose. When combined with increasingly powerful personal computers, advancing flight simulation software, and communications networks, virtual airlines are often able to provide compelling, realistic, experiences similar to operations inside a real airline. Virtual airlines also provide an avenue for members to gain access to additional content, such as aircraft and scenery, for use with their simulator. The appeal varies; for younger members, virtual airlines provide a sandbox environment where they can experience the corporate environment of commercial business in the airline industry, without the risk of financial loss. These organizations also provide an outlet for those who are interested in aviation but unable to fly themselves in real life due to financial, health, or other reasons.
Most of all, its one step closer to enthusiasts feeling more involved in an airline environment and share their interests with others.
Virtual Airlines also benefit the flight simulator community by providing valuable services such as ATC, events, and general help and knowledge.

== Common elements ==
There are several elements that are common across many virtual airlines:
* A website as the focal point of the community
* Internet forum where discussion and social interaction can occur
* Customized livery that users can download together with aircraft and install in their flight simulator
* Route schedules for members to fly in their simulators
* Multiplayer events, often on a game network such as VATSIM or IVAO
* Less common elements include:
* An Online database for recording and reporting flights and membership statistics
* Dedicated game server hosting to provide private areas for members to complete flights
* Award, rank and recognition systems
* Voice over Internet Protocol servers for members to communicate freely by voice

== Current Flightgear Virtual Airlines ==
Currently, some number of virtual airlines exist, with airlines made of various experiences, fleets and operations. Here is a list of some of the known virtual airlines to have existed:

* [[Air Royale Virtual Airlines]] << Now renamed to "Dravian Virtual Airlines"
* [[Atlas Virtual Airlines]]
* [[BRT Virtual Airlines]]
* [[Flighter Airlines]]
* [[GOL & VARIG Virtual]]
* [[merlion Virtual Airlines]]
* [[Star Alliance]]
* [http://transgear.treborlogic.com TransGear Airways]
* [http://tsavirtual.fr.nf/index.php/ TSA - Tristar Airlines]

=== Current Alliances ===
Alliances point to groups of airlines working with each other in joint operations. Currently, the following are active:
* [[Star Alliance]]
* Transgear Airways and Atlas (considered "sister VA's" and work in symbiosis)
* [[Virtual Star Alliance]]
* [[OneWorld Brasil]]

=== Current Flightgear Flying Clubs ===
* [http://flightgearfans.wordpress.com/ FlightGear Flying Club] (Defunct

== Former Virtual Airlines ==
Before the merger of most virtual airlines into Atlas and gradual declines of airlines following that event, several independent virtual airlines were active. These airlines, as well as airlines proposed but never actually created include the following:
[[File:virtualairlines.jpg|thumb|430px|Logo of most virtual airlines as of February 2010.]]

=== Airlines Merged into merlion Virtual ===
* Seasonal Airlines - This branch now operates Oceania as 'Aerosuperb'
* Dot Airways - This branch now operaties in the US as 'Cloud9'

Both Cloud9 and Aerosuperb are subsidiaries of merlion.

=== Airlines Merged into Atlas Virtual ===
* [[Japan Pacific Airlines]]
* Skynet International Airlines

=== Defunct Airlines ===
* AirLink
* Air San Francisco
* Americair
* Coastal Air Systems
* Detra Virtual Airlines
* Euroair (Aurelen Virtual)
* [http://equipe-flightgear.forumactif.com/f3-europa-airlines Europa Airlines] (->French virtual airline)
* [[Europe Airlines]]
* Gisi Airlines
* [[Cresder Nixrof Airways]]

=== Proposed Airlines ===
* Sandy Oceania Airlines
* Triangle Airlines

== Controversies ==
=== Copyright Issues ===
When a virtual airline is created in the image of a real world airline legal issues can arise out of copyright violations. In 2003, a real world airline, Qantas Airways Ltd., announced a new low-cost carrier by the name of Jetstar Airways. However, a virtual airline named Jetstar International Airlines already existed, complete with a web site. As part of their startup promotion, Qantas sold 100,000 airline tickets at a discount price, and the virtual airline's web site was swamped with would-be customers, job-seekers, and prospective vendors. The virtual airline sued Qantas, claiming that Qantas stole the virtual airline's livery and trademark.
If you wish to create a virtual airline- Which Flightgear would be eager for you to do, Please do not base it on real life airlines to save copyright issues!

=== Misuse ===
Claims have been made of the use of both flight simulators and virtual airlines as training devices for criminal activities, although to date no conclusive link has ever been provided to indicate a situation where a virtual airline has provided flight simulation training to anyone involved in a terrorist activity.
Jermaine Lindsay, one of the four 7 July 2005 London bombings, may have used flight simulators to practice flying an airliner, with an accusation that he was registered with a virtual airline. A person of the same name listed his nearest major airport as Heathrow and clocked up 30 hours in two months with SimAirline.net. The website later denied the member's linking with the bombing, and indicated it was working with the Metropolitan Police to establish whether its former member was the bomber. The website stated that it provides information about airlines and free add-on software for Microsoft Flight Simulator and does not provide flight instruction to its members.
The 9/11 Commission in the US concluded in 2004 that those responsible for flying the planes into World Trade Center and Pentagon had used PC-based flight simulators for training. Despite the initial concerns of the involvement of virtual airlines in these terrorist activities, largely little has come from these claims to date and no changes have been noted as occurring in their operation as a result.

[[Category:Virtual airlines|Virtual airlines]]

FlightGear Newsletter November 2011

2011-11-27T13:39:52Z

Trez: /* TSA - Tristar Airlines */

FlightGear Newsletter November 2011

2011-11-27T13:38:34Z

Trez:

FlightGear Newsletter November 2011

2011-11-27T13:31:26Z

Trez: /* TSA - Tristar Airlines */

File:TSA1.png

2011-11-27T13:28:25Z

Trez: used in nov11 newsletter

used in nov11 newsletter

FlightGear Newsletter November 2011

2011-11-27T13:25:53Z

Trez: /* Virtual airlines */