FlightGear Newsletter December 2011
- 1 2011 annual
- 2 Development news
- 3 Development notifications
- 4 Logo & banner contest
- 5 Interview with a contributor (Olivier Jacq)
- 6 Snapshot releases
- 7 In the hangar
- 8 Scenery corner
- 9 Airport of the month
- 10 Screenshot of the month
- 11 Suggested flights
- 12 Wiki updates
- 13 Community news
- 14 And finally ...
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.
We'd like to wish everyone a happy 2012! A new year with lots of exciting FlightGear developments in sight. Looking back at 2011, we can list a few events that deserve to be highlighted.
2011 was the year in which:
- FlightGear 2.4.0 was released
- a release plan had been set up; leading to more frequent releases
- the FlightGear website was changed into a CMS, allowing more frequent updates
- the wiki saw its 10.000.000th pageview
- and much more. Check out the newsletter archive for all highlights!
2.6.0 release preparations
See Release plan for the main article about this subject.
On January 17, release branches will be created from our Git repository. That's basically the birth of a new release. From then on, no new features (and aircraft) can be pushed. Only bug fixes are accepted.
Thanks to the branching, development for the next-next release (2.8.0?) can start right away; even before 2.6.0 is released.
Until the release branches are created, changes to aircraft may still be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Aircraft defined as part of the base package (e.g. the c172p) are already in the frozen state and shall not undergo major changes in this period.
Keep in mind that the people that are able to commit your stuff are just as busy finishing their own work as you are! Therefore it is important that you create merge requests for everything that you'd like to see included in the upcoming release, as soon as possible. This includes new aircraft and large updates to existing aircraft.
Don't let it wait for tomorrow, do it today!
Some bug fixes and improvements require aircraft to be adapted/fixed to remain airworthy, to be working correctly, or to be taking full advantage of latest FlightGear version. This is why some developers now went ahead and created a check list including guide lines on maintaining aircraft, please see aircraft maintenance for more info.
FlightGear development over time
Ohloh is an online service that provides repository statistics. FlightGear's repositories are all tracked:
As you can see, development has been quite variable over time (generally a lot of development in the northern hemisphere winter), but core development (FlightGear is made up of the separate SimGear and FlightGear codebases) has been fairly constant since the start of the project. Another interesting observation is the massive increase in aircraft over the last couple of years, as shown by the amount of change to FGdata.
Flightgear goes to space!
As part of the ongoing work developing a haze and fog shader and improving the sky appearance, rendering of the high altitude environment is much improved. With the development version of the terrain-haze and skydome shaders and the visibility model in altitude provided by Local Weather, a seamless transition from low altitude to a near space environment up at 100 km altitude can be achieved.
This allows for spectacular views from planes like the X-15 - here an X-15 has just completed the ballistic climb to 270.000 ft and falls back to Earth with stunning high-altitude views of Nevada and California.
Despite some claims to the contrary, the existing rendering engine is well up to the job, providing framerates above 20 fps at the top of the arc. However, naturally the Flightgear scenery model is not optimal for rendering orbital views, and photo-texturing of Earth with satellite imagery as done in orbital simulations becomes increasingly superior with altitude. 
Shader development continues at a breakneck pace! We now have a nice wet runway effect:
We have already combined all our model shader effects into one: light map, bump map and reflect map, and now we have added to ability to add a dirt effect over time (dirt map?). We call this the uber-shader.
It also gives us the ability to have a good glass reflection with a scratched appearance, although this last effect needs a bit of fine tuning.
At the same time, we've enhanced the shader controls. Users can now control (almost) every single shader through sliders. The Performance vs Quality slider in the View > Rendering Options dialog provides basic control. It does act slightly different than before, setting it all the way to the left (Performance) will disable all shaders. At the right most position, all shaders will be shown at maximum quality. Most shaders are simple on/off, but some of the more demanding shaders have intermediate steps.
Powerfull graphics cards have no problem with the maximum quality setting, but most cards (even modern ones) need a finetuned setting to maintain reasonable framerates. You can change individual shader's settings in the Shader Options dialog, which can be reached via the button in the Rendering Options dialog.
This is all in fgdata in Gitorious now - use --materials-file=materials-dds.xml and enjoy. A nVidia 8400 or its ATI equivalent should be sufficient to run these shaders with a recent driver. No update to source code is required.
New terrain textures
Some new terrain textures have been created, mostly based on USGS aerial imagery. The textures have a warmer, summer theme which fits better with some parts of the scenery. The material mappings are best used for Corine-enabled scenery, and the materials file works only for recent Git snapshots. However, the textures can be used with any materials file. All textures are GPLv2 so they can be freely distributed within the Flightgear repository. More info and screenshots in this forum thread. This is still work in progress, of course.
Improvements to the radio code
The FlightGear radio code has been recently overhauled, for more info please see Radio propagation.
Improving random trees & buildings
Some core developers have been thinking about ways to improve our random scenery, in particular buildings and vegetation. For more details see .
Marketting of 2.6.0 via FS Break podcast
The idea was raised to market FlightGear using the FS Break podcast, for more details please check: 
More performance out of the 3D clouds
Sound support for AI traffic
Erik has been working on implementing an FGFX class for AIModels and is pretty much done, a first stab at the sound code has been committed now. For more info see .
A contest has been set up to create new banners and logos depicting the latest developments of FlightGear 2.4+ (these new banners and logos are specifically meant to demonstrate new capabilities of FlightGear 2.6.0). Everybody is invited to participate. See the forum thread for the latest submissions and send in your own ideas.
Interview with a contributor (Olivier Jacq)
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.
- How long have you been involved in FlightGear?
I've been following FG closely since FlightGear 0.9.8. So, checking on the Wiki, this already dates back to... 2005!
- What are your major interests in FlightGear?
At first, I was using FG as a "casual" user, mainly contributing positions in my local area (Brittany) and especially the Brest area (cause I'm not that good at 3D modelling!). So I would say my major interest is in definitely in the scenery side of FG - and HHS choppers!
- What project are you working on right now?
This is HIGHLY confidential! But because Christmas is coming soon, I'll give you a small written preview on this early present! Still under development, I'm working on automated scripts to add/delete/update shared or static scenery objects/positions within FG, in order to ease the actual submission process, both for the user and the scenery maintainers. The tool to add unitary positions is now in production (see below)!
- What do you plan on doing in the future?
I have at least a few months before all scripts are finished and under production, so I think when they're all done, I'll take some time to use them and add more objects positions into FG myself!
- Are you happy with the way the FlightGear project is going?
I am especially happy to see the latest developments in FG, as the release plan and the many works going to make the scenery better: shaders, weather, and especially scenery which needs to be regenerated and enhance (have a look at the apt.dat 8.50 work in the forums, it's awesome!). FG is really becoming better and very much comparable to other sims.
- What do you enjoy most about developing for FlightGear?
FG is relying on so many exciting parts: GIS, 3D modelling, database, web, network... and there are so many advanced technologies to implement (eg radio propagation early support)... it's amazing and there is no other software where all this is needed but flight sims. A real concentrate of technology!
- Are there any "hidden features" you have worked on in FlightGear that new users may miss?
I was at the origin of the photorealistic scenery for Brest. To be precise, I had the idea and asked for the permission to use the data (as it is CC-BY-SA). Then Nels and others have been working on the patch for SG, etc.
- What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?
Well, they have to check that noone is already working on it, or to get in contact with him. Most of all, I would advise them to start on small projects first. For instance, a LOT of cockpits need enhancement. So try to make existing aircrafts better, rather than try to build yet another one from scratch. Keep this for later and focus on what needs to be enhanced now. FG will then look so much better to our fellow downloaders.
- Have you previously used other flight simulators or simulation software in general?
I remember having a flight simulator called "ILS" on my TRS-80... and next I moved, as a lot of people, on Microsoft Simulator when I was 7 or 8 on 10 Mb hard drives ;-)
- 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?
FG was the only free and open source advanced flight simulator I found under GNU/Linux, so when I decided to moved my computer fully to GNU/Linux, the choice was quite easy. Its success and improved quality over the years confirmed this choice was good!
- Compared to other flight simulation software, what are FlightGear's major benefits in your opinion?
Apart from the fact that it is free and opensource, I would say that its central scenery database and mapserver is one of its major features, compared to other flight sims where you have to download here, download there, add patches, etc... what a mess it becomes on your hard drive after a few years of addons!
- Do you think it is necessary to know how to program in order to contribute to FlightGear?
Not at all, contributing to scenery object positions is for instance very easy (it'll be even easier after my script goes in production ;-). So everyone should be able to contribute to FG (in a proper manner), that's the way to success!
- Have you ever used FlightGear professionally or for educational purposes?
I've been talking about it in my job, so show its quality, even sometimes compared to professional ones I have seen there. I would definitely recommand a stronger relationship between FG and professional/educational worlds.
- On average, how much time do you spend working with/contributing to FlightGear?
For a few weeks, I've been working for around 3 to 4 hours per week developing scripts. It's been a while since I haven't been having a flight in FG!
- Which of the more recent FlightGear developments do you consider most interesting/appealing?
I would definitely vote for the work on fgfs-contruct and 8.50 data format support. The anaglyph support is amazing too.
- Is there some feature that you'd truly like to see in FlightGear one day?
I hope sometimes we'll be able to add GPL-photorealistic pictures on top of actual layers. Looking forward to OSM-based roads scenery release too and multi-core support.
- What do you think could be done to attract even more new users and contributors to FlightGear?
The fact that FG software is not localized into other languages can be a real drawback for some users and is often shown as such when magazines or forums talk about FG. If this support is added back, I will definitely work on the French translation!!
- What about interacting with the FlightGear community? Any tips/experiences you'd like to share?
As many others, I regret the way some people ask for features like: "do this aircraft, I NEED it", or don't even have a look at the Wiki or forums archives to get an answer to their questions. Ask politely, try to understand the way FG community is organised, search for archives, don't pollute threads and everything will be better!
- Is there anything else you'd like to share with us?
The future of FG belongs to you: each of you can make it better, whatever your skills or interests are. So don't say: this is missing, try to add it or ask the community what you can do for help!
Stay tuned for month's interview, featuring FlightGear core developer Durk Talsma.
Every now and then, easy-to-install development snapshots are created. These snapshos 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 the issue tracker.
In the hangar
CASA C-101 Aviojet
The Spain-Latinamerica's community Vive FlightGear! recently introduced the CASA C-101 Aviojet to FlightGear hangars. The Aviojet is a two-seat military turbofan trainer, designed and built in Spain, where it's used for jet training and aerobatics in the "Patrulla Aguila" team. It's also used in other countries like Chile, Honduras and Jordan, where it can enforce a light ground-attack role.
This beta release has 3 versions (EB, BB & CC), each one with different engines and subtle differences. While BB and CC version can use a 30mm cannon, the EB version is capable to dust smoke for aerobatic shows.
The Learjet 35-A has received another major update. She is not a sweet beast any more, she will bite when the pilot mistreats it. The sound configuration is completely different. The FDM is as real as the real thing according to the literature I could find. Even the fuel consumption is close to real as long as it flies. She has a new HUD only showing the controls so the pilot can focus on flying and the instruments. She has an accurate display for N1 and ITT. She is prepared for version 2.6.0., including the flight recorder. She is ready now for a though review.
Custom Poland scenery
Have you got your Christmas present yet? If not the Polish Team has made custom scenery of most Poland territory. Major contributor is SP-MMA who generated terrain and created some objects. Feel free to download it (download soon on forum) and take your favorite plane. There are some really nice areas just perfect for long VFR routes!
Southwest Colorado Scenery - beta 4
New custom built scenery has been made available for the region of Southwest Colorado, for more info please see: the mailinglist.
EBAW (Antwerpen - Deurne)
Belgium got a complete full modeled and textured airport: Happy holidays at EBAW :)
This scenery, is sadly enough, not yet available with terrasync. You can download it from the Belgian scenery Git repo.
Tip: If you want to make some EBAW-EHAM flight, copy the Objects/e000n50/e004n51 and Terrain/e000n50/e004n51 into the terrasync folder.
Added on December 2011, 15th, a useful webtool to ease the insertion of shared models positions within the FlightGear scenery database. We hope this will make the number of positions increase!
The steps are very easy to follow :
- Place the object within FlightGear.
- Take the data and copy/paste it within the form (please double check the content of what you're inserting!).
- Add a small kind comment for Martin, telling him what you're doing.
- Give the captcha what it wants (sorry for this, but it's to avoid unwanted automated robots).
- Click submit and the request is done!
The data is inserted in the database as soon as the reviewer has checked it. It may take a few days to see it appear through Terrasync.
More improvements (mass import, edit, delete) are to come, so follow the forum thread if you're interested.
Airport of the month
December, cold, dark, snow. But also skiing, gluhwein and Santa Claus.
It's time to go to Austria and visit Innsbruck Airport. Take along your skis. You will find amazing scenery here, made by Mother Nature and by the volunteers that have re-created the area.
Read more about the current state of the development at the forum.
Screenshot of the month
La Patrouille de France (PAF) wish you a joyeux noel (French for Merry Christmas) from their home base Grenoble Aerodrome (LFLG)!
For this VFR trip we need a strong machine since we will go up from 4000 to about 10,000 feet and since we are in Africa, Tanzania, what better choice is there as the Cessna 208 Caravan, on wheels. We will take off from HTLM, Lake Manyara, runway 12 (124.5 deg), that has an elevation of 4150 feet. Hit Shift-B so we don't drop off the runway.
We will have to change some settings before we take off. There is no snow where we are so: View=> Rendering Options=> Snow line=> Set to max. (5000M). We need a reasonable clear sky since there are quite a few bumps we could hit: Environment=> Global weather=> METAR source=> Fair weather.
Give full throttle and take off. Bank left and make a full circle so we gain some altitude and make a mental note of the airstrip, since this is the only one nearby. Look at the road West towards the airfield. You will notice that the airstrip is at the edge of a mountain ridge, the lake to the East is quite a lot lower.
We pass over the airstrip towards lake Manyara and turn left keeping the mountains close to our left side, on an initial course of about 30 deg. We keep the mountains to our left and follow our path, our heading will slowly go from 30 to North and takes about 15 mins. During our path we should slowly gain altitude.
On the image we see two distinct mountains. The nearest is Mt.Kerimasi, a fun place for hang-gliders, and North Mt.Ol Doinyo Lengai, an active volcano. We are heading straight towards Mt.Ol Doinyo Lengai. Just before we would collide we take a sharp left turn heading 225. You will see why we need the altitude now.
The mountain ahead, Mt.Embagai, we see does not appear to be anything spectacular. Aim towards it since we have to go over it. Coming nearer, if you are high enough, 9000 feet, you will see why this mountain is well worth a visit. It is a crater with a lake inside, lake Embagai (Empakaai). Enter the crater and look around, careful not to loose any height since we'll have to get out again, we need about 10 000 feet. Mesmerized we grab our compass and take a course of 225 again. To get out we might skim against a cloud, be careful. If you don't see a way out take a turn again to wait for the clouds to move out of sight.
After you managed to get out of the crater keep on the course of 225 while descending slowly for about 9 mins. There are some bumps to avoid, like Mt.Olmoti we keep to the right and Mt.Losirua on the left.
After a small hill we enter one of the most amazing places in Africa, the Ngorngoro Crater, the second biggest crater in the world. A micro climate and amazing wildlife. Examine the crater and you will notice two lakes, head towards the biggest lake, lake Magadi. When you are above it take a course of 123 to get out of the crater.
After leaving the crater it takes some time before we are near the airstrip again. After about 5 mins we will see a river (left) and a road (right). Follow the road since it will lead us to the airstrip again.
Don't scare the wildebeast!
- Fair weather, no snow
- HTLM RW 12 4150 feet
- Course 30 to 0 deg 15 mins, mountains close left
- Head towards /\volcano
- Sharp left turn course 225 deg altitude 9000 feet
- Volcano, lake, 10 000 feet
- Course 225 deg, slow descend 9 min
- Large lake, course 123 deg 5 mins
- River left, road right. Follow road
- Landing 124.5 deg 4150 feet.
More amazing flights can be found at Suggested Flights.
- Learjet 35-A is updated matching the true aircraft flight manual (with FlightGear limitations). On the wiki it is one of the best described aircraft.
- Unique Features now contains a massive list of what makes FlightGear unique.
- The German Flughöhe article is close to complete matching the English version.
FlightGear on Google+
Following up on last month's launch, the FlightGear page on Google+ welcomed its 100th follower! If you haven't done so already, please add us to your circle and stay up to date on the latest FlightGear news, cool screenshots and release info.
FlightGear on YouTube
The headers on the forum have been replaced by some snow/christmas ones to give you the right winter feeling. Did you spot Santa already?
And finally ...
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
- You can turn on anti-aliasing in FlightGear?