8,564
edits
FlightGear Newsletter April 2012: Difference between revisions
Jump to navigation
Jump to search
Cleanup for publishing
(→Wiki updates: Some info about the new portals/main page.) |
(Cleanup for publishing) |
||
| Line 9: | Line 9: | ||
=== Random Buildings === | === Random Buildings === | ||
[[File:Random buildings in San Francisco.jpg|thumb|Random buildings in San Francisco.]] | |||
[[File:Random buildings in San Francisco.jpg|thumb|Random buildings in | |||
In an effort to improve the scenery in cities, towns and villages with minimal impact to framerate, Stuart has been working on automatically generated "random buildings". The idea is to have FG itself generate buildings with randomized size, shape and texture in a very efficient manner, and builds on the work that he and Tim Moore did on random vegetation a couple of years ago. This is now available in git. | In an effort to improve the scenery in cities, towns and villages with minimal impact to framerate, Stuart has been working on automatically generated "random buildings". The idea is to have FG itself generate buildings with randomized size, shape and texture in a very efficient manner, and builds on the work that he and Tim Moore did on random vegetation a couple of years ago. This is now available in git. | ||
Building generation is configurable through materials.xml, and documented in Docs/README.materials. It is designed to be flexible enough that we can have different types of cities in Europe compared with the USA, or Africa. The current texture used for the buildings is a proof of concept, and rather limited by Stuart's artistic abilities. If anyone is interested in creating a better texture, please get in touch with Stuart on the mailing list or forums. | Building generation is configurable through materials.xml, and documented in Docs/README.materials. It is designed to be flexible enough that we can have different types of cities in Europe compared with the USA, or Africa. The current texture used for the buildings is a proof of concept, and rather limited by Stuart's artistic abilities. If anyone is interested in creating a better texture, please get in touch with Stuart on the mailing list or forums. | ||
One of the main aims of this work is to minimize frame-rate impact. If you are running git, and have the time to test the new feature, please fill in | One of the main aims of this work is to minimize frame-rate impact. If you are running git, and have the time to test the new feature, please fill in [http://www.flightgear.org/forums/viewtopic.php?f=5&t=16204 this poll] on the forums so we can gather information on whether it has succeeded. Read more at [[Random Buildings]]. | ||
=== Additional Scripting APIs === | === Additional Scripting APIs === | ||
| Line 22: | Line 20: | ||
There's now an effort to improve this, while keeping the complex, especially aircraft-dependant functionality in Nasal so it can be tailored and extended easily. Work has started on improving the existing Nasal scripting interface such that modern avionics can be more easily modeled in scripting space, for additional information please check out [[Nasal Flightplan]]. | There's now an effort to improve this, while keeping the complex, especially aircraft-dependant functionality in Nasal so it can be tailored and extended easily. Work has started on improving the existing Nasal scripting interface such that modern avionics can be more easily modeled in scripting space, for additional information please check out [[Nasal Flightplan]]. | ||
== Interview with a contributor (Sam Clancy) == | == Interview with a contributor (Sam Clancy) == | ||
''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]]!'' | ''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]]!'' | ||
'''[http://www.flightgear.org/contributors/ Read | '''[http://www.flightgear.org/contributors/ Read previous interviews at our website's archive].''' | ||
* '''How long have you been involved in FlightGear?''' | * '''How long have you been involved in FlightGear?''' | ||
| Line 64: | Line 47: | ||
The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe. | The satisfaction you get when something works! Maybe that's because I'm not the most technically minded, hehe. | ||
'''[http://www.flightgear.org/contributors/ Read | '''[http://www.flightgear.org/contributors/ Read previous interviews at our website's archive].''' | ||
== Snapshot releases == | == Snapshot releases == | ||
| Line 70: | Line 53: | ||
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]. | 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]. | ||
== In the hangar == | == 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. | 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 === | === New aircraft === | ||
==== ATC FS: A new ATC mode for FlightGear ==== | |||
[[File:ATC-FS.png|thumb|270px]] | |||
ATC-FS (ATC, with flightstrips) is an [[air traffic control]] (ATC) aircraft, with the purpose to help an ATC controller keeping track of the aircraft around his airport as well as helping him guide the aircraft on approach and departure and aircraft just passing through his airspace. It can be added to FlightGear just as a regular aircraft and is built with XML and nasal. Read more at [[ATC-FS]]. | |||
==== Embraer 195 ==== | ==== Embraer 195 ==== | ||
A new [[Embraer 195]], developed by the group FGBr for Flightgear version 2.4 and 2.6 can soon be found at at: [http://www.grupofgbr.com.br grupofgbr.com.br]. | A new [[Embraer 195]], developed by the group FGBr for Flightgear version 2.4 and 2.6 can soon be found at at: [http://www.grupofgbr.com.br grupofgbr.com.br]. | ||
| Line 90: | Line 71: | ||
=== Updated aircraft === | === Updated aircraft === | ||
[[File:Cessna_337G_Skymaster.png|thumb| | ==== Cessna 337G Skymaster ==== | ||
The | [[File:Cessna_337G_Skymaster.png|thumb|270px|The Skymaster is now ready for FlightGear 2.6]] | ||
The [[Cessna 337G Skymaster]] received an update, making the plane ready for FlightGear 2.6 and some more nice improvements. The Skymaster now has an autostart function, new autopilot, checklists and "utility" dialogs, new heading indicator, 2 new liveries, new splash screen, new cockpit animations and new shaders, and a complete new [[ELT]] system. Some more? Well, the 337G is now able to crash due for hitting the ground or excesive G loads. | |||
==== MiG-21bis ==== | |||
[[MiG-21]]bis had a major update; 3D model is cleaned and remaped, new texture is added. Cockpit is remodeled and it has new instrument arangement. Aditional weapons are added with full [[Bombable]] support. Small fixes in FDM include more efficient flaps and hardpoint weights. | [[MiG-21]]bis had a major update; 3D model is cleaned and remaped, new texture is added. Cockpit is remodeled and it has new instrument arangement. Aditional weapons are added with full [[Bombable]] support. Small fixes in FDM include more efficient flaps and hardpoint weights. | ||
==== | ==== Zivko Edge ==== | ||
The [[ | The [[Zivko Edge 540|Zivko Edge]] by Torsten Dreyer was already a great airplane, Jentron worked the FDM over and now its quite capable of tumbling and spinning with rough handling. | ||
=== New Instrument === | === New Instrument === | ||
[[File:10huog1.jpg|thumb| | [[File:10huog1.jpg|thumb|270px|A DR400 fitted with GPS-196 instrument.]] | ||
The PAF team is proud to announce the arrival in git of the Garmin 196 GPS instrument. | The PAF team is proud to announce the arrival in git of the Garmin 196 GPS instrument. This GPS fits perfectly into light aircrafts such as the [[Robin DR400]], microlight aircraft or helicopters. The source code is available in the fgdata Gitorious repository. | ||
This GPS fits perfectly into light aircrafts such as the | |||
The source code is available in the fgdata Gitorious repository | |||
=== | To include this GPS in your aircraft, simply follow [https://gitorious.org/fg/fgdata/blobs/master/Aircraft/Instruments-3d/garmin196/README those guidelines]. A full howto is also available [https://gitorious.org/fg/fgdata/blobs/master/Aircraft/Instruments-3d/garmin196/doc/doc-en.htm here], while [http://www.flightgear.org/forums/viewtopic.php?f=14&t=15433&p=151735&hilit=garmin#p151735 a thread on the international forums] has been opened. | ||
== Scenery corner == | == Scenery corner == | ||
=== Birds in | === Birds in FlightGear === | ||
[[File:Sea_Gulls_2.png|thumb|270px|Sea Gulls]] | [[File:Sea_Gulls_2.png|thumb|270px|Sea Gulls]] | ||
Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. | Every so often I get fed up modelling buildings, so I think of other (often silly) things I can model for FlightGear. I have already made several low-poly models which can be used with AI scenarios. This time I have created an animated Seagull. | ||
| Line 140: | Line 120: | ||
=== TerraGear === | === TerraGear === | ||
As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official | As you might be aware there is constant genapts850 development going on, to bring the apt.dat 850 format features (and beyond) to FlightGear. This work has now been merged into the official [[TerraGear]] git repository for general consumption. Work is still ongoing to bring missing features like some special light variants, runway shoulders and different textures in. Some bad bugs have been fixed recently and there are even Windows binaries available from our build server. | ||
=== Scenery Data === | === Scenery Data === | ||
Data with the explicit use of being turned into FlightGear scenery has now been vectorized for almost all of California, western Oregon, parts of the Grand Canyon in Arizona, Las Vegas, Colorado, and northern New Mexico. This product is not yet available in terrain form, but represents good progress toward having nicer United States scenery data. | Data with the explicit use of being turned into FlightGear scenery has now been vectorized for almost all of California, western Oregon, parts of the Grand Canyon in Arizona, Las Vegas, Colorado, and northern New Mexico. This product is not yet available in terrain form, but represents good progress toward having nicer United States scenery data. | ||
== Airport of the month == | == Airport of the month == | ||
"Airport International | "Airport International of Guarulhos (SBGR Sao Paulo)" | ||
[[File:International_Airport_Of_Guarulhos.jpg|800px]] | [[File:International_Airport_Of_Guarulhos.jpg|800px]] | ||
[[File:International Airport Of Guarulhos (1).jpg|423px]][[File:International Airport Of Guarulhos (2).jpg|377px]] | [[File:International Airport Of Guarulhos (1).jpg|423px]][[File:International Airport Of Guarulhos (2).jpg|377px]] | ||
International Airport | International Airport of Guarulhos in Sao Paulo City Brasil | ||
In the site: www.grupofgbr.com.br | In the site: www.grupofgbr.com.br | ||
| Line 162: | Line 140: | ||
== Suggested flights == | == Suggested flights == | ||
=== Central Karakoram range === | === Central Karakoram range === | ||
Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high. | Let's explore one of the highest regions of the planet - the central Karakoram with the densest concentration of mountains of 8000 m and above. We're going to need a good climbing performance for the trip - even the frozen plateau of Baltoro glacier above which K2 and Gasherbrum V and VI loom is more than 13.000 ft high. | ||
| Line 177: | Line 154: | ||
Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures! | Passing a few lakes, you reach finally Baltoro glacier continuing the river valley stretching eastward. Ever climbing, follow the glacier till you reach some kind of T-junction. The glacier arm reaching north leads to K2 (which sadly isn't really there in Flightgear), but just ahead of you are the still rather impressive peaks of Gasherbrum V, VI and I - circle the range and make some pictures! | ||
A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem. | A good way back to Skardu is to go about 10 miles sourth from the Gasherbrum peaks, then head due west. To your west, you can see the long valleys fall away from the high ranges, to your right is the still glacier-covered high Karakoram. On a clear day (really good visibility selected) you can see the distinctive peak of Nanga Parbat appearing straight ahead on the horizon. The valley of Skardu is quite a distinctive feature and finding back VFR should not be a problem. | ||
== Wiki updates == | == Wiki updates == | ||
| Line 197: | Line 170: | ||
Feedback on all of this is extremely appreciated! Feel free to share your thoughts in the (new) [[FlightGear wiki:Village pump|Village Pump]]. | Feedback on all of this is extremely appreciated! Feel free to share your thoughts in the (new) [[FlightGear wiki:Village pump|Village Pump]]. | ||
== Useful link == | |||
== Useful | |||
* [http://www.aircharts.org www.aircharts.org] provides fast, simple access to aerodrome charts. This includes STIDs, STARs, Approach Procedures, IAPs and the ICAO-standard aeordrome chart itself. It also provides en-route charts for the USA and most of Europe. IFR flight planning just became a lot easier! | * [http://www.aircharts.org www.aircharts.org] provides fast, simple access to aerodrome charts. This includes STIDs, STARs, Approach Procedures, IAPs and the ICAO-standard aeordrome chart itself. It also provides en-route charts for the USA and most of Europe. IFR flight planning just became a lot easier! | ||
| Line 236: | Line 182: | ||
* The [[OpenRadar]] project is looking for a new maintainer. | * The [[OpenRadar]] project is looking for a new maintainer. | ||
* The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer. | * The [[FGFSPM]] (FlightGear Package Manager) is looking for a new maintainer. | ||
[[Category:FlightGear Newsletter|2012 04]] | [[Category:FlightGear Newsletter|2012 04]] | ||