FlightGear Newsletter November 2010: Difference between revisions

Jump to navigation Jump to search

FlightGear Newsletter November 2010 (view source)

Revision as of 20:32, 1 December 2010

4,767 bytes removed ,  1 December 2010
m
no edit summary
m (Protected "FlightGear Newsletter November 2010" ([edit=sysop] (indefinite) [move=sysop] (indefinite)))
mNo edit summary
Line 3: Line 3:
''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 projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''
''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 projects such as for example updated scenery or aircraft, please do feel invited to add such news to the newsletter.''


== FlightGear events ==
== Call for volunteers ==
== Call for volunteers ==
The [[OpenRadar]] project is looking for a new maintainer.
The [[OpenRadar]] project is looking for a new maintainer.
Line 15: Line 13:
We use the new definitions in Multi Player Carrier Carl Vinson to move around the Goofer's deck while we are goofing, or to seek a more advantageous view from PriFly, or to inspect the Flight deck as the Flight Deck Officer, as seen in [http://www.youtube.com/watch?v=h9MUT7GfzBs this video].
We use the new definitions in Multi Player Carrier Carl Vinson to move around the Goofer's deck while we are goofing, or to seek a more advantageous view from PriFly, or to inspect the Flight deck as the Flight Deck Officer, as seen in [http://www.youtube.com/watch?v=h9MUT7GfzBs this video].


Meanwhile, in other news, Tim Moore has fixed the condition tag in the Material Animation. We can combine these two facilites to generate some more interesting views - [http://www.youtube.com/watch?v=1YmJN9o6TBc]. Alexis Bory has said that he will see if he can produce some more models with which to populate the hangar. Let's hope he finds something!
Meanwhile, in other news, Tim Moore has fixed the condition tag in the [[Howto: Animate models#Material|material animation]]. We can combine these two facilites to generate some more interesting views - [http://www.youtube.com/watch?v=1YmJN9o6TBc]. Alexis Bory has said that he will see if he can produce some more models with which to populate the hangar. Let's hope he finds something!
 
== Shader requests ==
We have added a new page to the wiki titled [[shader requests]]. This is intended to provide a place for people to post ideas related to new shaders for use in FlightGear. But this is also meant to be place for aspiring shader developers to find interesting ideas for new shaders. In the past, these ideas were often spread over many different places, such as forum or mailing list discussions, and often ended up getting hidden rather quickly. So if you have ideas related to improving existing shaders or creating completely new ones, please add your ideas to the [[Shader requests]] page. And if you are aware of any ongoing shader development efforts, please also add those there. Consequently, if you want to get started creating shaders for FlightGear, please make sure to check out this page.


== Known problems ==
== Known problems ==
Line 28: Line 23:
* Otherwise please stick with manual weather configuration and wait for the next FlightGear release (won't be too long).
* Otherwise please stick with manual weather configuration and wait for the next FlightGear release (won't be too long).


== Nasal for newbies ==
== New software tools and projects ==
== FlightGear addons and mods ==
== In the hangar ==
== In the hangar ==
=== New aircraft ===
=== New aircraft ===
==== DC-8-63 ====
[[File:Fgfs-screen-178.png|thumb|The DC-8-63 in KLM colours.]]
Isix and Armchair Ace have recently unveiled a DC-8-63. You can follow the progress on the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=10228 development thread]. 


====Boeing 737NG Series====
==== Boeing 737NG Series ====
 
Three out of four models from Innis Cunningham's Boeing 737NG series have been included in FlightGear's GIT repository. Despite being an initial release, the models are characterized by great attention to detail in the 3D cockpit, with some of the more advanced systems such as the autopilot and autobrake systems already fully operational. The models are further characterized by excellent Flight Dynamics Models (FDMs), co-developed and tested by real-life 737 pilot David Culp, and excellent exterior texturing, provided by FlightGear's very own texture master Gooneybird. Included are the 600, 800, and 900 variants. The 737-700 is expected to follow soon.
Three out of four models from Innis Cunningham's Boeing 737NG series have been included in FlightGear's GIT repository. Despite being an initial release, the models are characterized by great attention to detail in the 3D cockpit, with some of the more advanced systems such as the autopilot and autobrake systems already fully operational. The models are further characterized by excellent Flight Dynamics Models (FDMs), co-developed and tested by real-life 737 pilot David Culp, and excellent exterior texturing, provided by FlightGear's very own texture master Gooneybird. Included are the 600, 800, and 900 variants. The 737-700 is expected to follow soon.
====DC-8-63====
Isix and Armchair Ace have recently unveiled a DC-8-63. You can follow the progress on the [http://www.flightgear.org/forums/viewtopic.php?f=4&t=10228 development thread]. 
[[File:Fgfs-screen-178.png|thumb|left|The DC-8-63 in KLM colours.]]


=== Updated aircraft ===
=== Updated aircraft ===
 
[[File:ZF Navy free balloon-2.jpg|thumb|150px|The ZF Navy free balloon with the envelope shader enabled.]]
[[File:ZF_Navy_free_balloon-2.jpg|thumb|The ZF Navy free balloon with the envelope shader enabled.]]
====ZF Navy free balloon====
====ZF Navy free balloon====
The [[ZF Navy free balloon]] has been updated with a custom shader effect that changes the shape of the balloon envelope according to its gas content.
The [[ZF Navy free balloon]] has been updated with a custom shader effect that changes the shape of the balloon envelope according to its gas content.


====IAR 80====
====IAR 80====
The [[IAR_80|IAR 80]] beta has seen some updates, with new features added in the eyecandy department, as well as some refining of the [[Nasal_scripting_language|Nasal]] code and a revamped [[FDM]].
The [[IAR 80]] beta has seen some updates, with new features added in the eyecandy department, as well as some refining of the [[Nasal_scripting_language|Nasal]] code and a revamped [[FDM]].


====Boeing 757 and 717====
====Boeing 757 and 717====
[[User:Skyop|Skyop]] has picked up development of the [[Boeing 757-200]] and the [[Boeing 717]]. New features included generic autostart systems, improved models, new instruments and new [[YASim]] [[FDM]]s. New and improved cockpits and aircraft systems are planned. Skyop is requesting livery makers to start painting their favorite airlines and submitting their textures to the [http://liveries.flightgear.org official FlightGear livery database].
[[User:Skyop|Skyop]] has picked up development of the [[Boeing 757-200]] and the [[Boeing 717]]. New features included generic autostart systems, improved models, new instruments and new [[YASim]] [[FDM]]s. New and improved cockpits and aircraft systems are planned. Skyop is requesting livery makers to start painting their favorite airlines and submitting their textures to the [http://liveries.flightgear.org official FlightGear livery database].


Follow further progress at the [http://flightgear.org/forums/viewtopic.php?t=9944 757-200 development thread] and the [http://flightgear.org/forums/viewtopic.php?t=6145 717 development thread].
Follow further progress at the respective development threads: [http://flightgear.org/forums/viewtopic.php?t=9944 757-200], [http://flightgear.org/forums/viewtopic.php?t=6145 717].
 
[[File:DC8pit.png|thumb|left|The DC-8's cockpit as it was on the 29th of November.]]
====Douglas DC-8-73F====
[[User:Armchair Ace|Armchair Ace]] has been developing the DC-8-73's cockpit, which has also been used in the new DC-8-63.


====Boeing 777-200====
====Boeing 777-200====
The [[Boeing_777-200|777-200ER]] received a cockpit and systems upgrade.
Extensions by Syd Adams and ThorstenB include better [[GPWS]] integration, improvements for cockpit instruments, sounds, textures, key/mouse bindings and many bug fixes.
The upgraded 777-200ER also features brake temperature monitoring.
Pilots are advised to also use spoilers and thrust-reversers for deceleration to avoid overheated brakes - especially when landing a heavily loaded plane.
The new auto spoilers, automatically deploying on touch-down when armed, provide some assistance here.
[[File:B777-200_RTO.jpg|thumb|Smoking brakes after a 777-200ER had to execute a rejected takeoff.
[[File:B777-200_RTO.jpg|thumb|Smoking brakes after a 777-200ER had to execute a rejected takeoff.
The airline declined to comment on the reason for the takeoff problem, but assured no one on board was injured.]]
The airline declined to comment on the reason for the takeoff problem, but assured no one on board was injured.]]


====Douglas DC-8-73F====
The [[Boeing 777-200|777-200ER]] received a cockpit and systems upgrade. Extensions by Syd Adams and ThorstenB include better [[GPWS]] integration, improvements for cockpit instruments, sounds, textures, key/mouse bindings and many bug fixes. The upgrade also contains a FlightGear's first: brake temperature monitoring.
[[File:DC8pit.png|thumb|left|The cockpit as it was on the 29th of November.]]
[[User:Armchair Ace|Armchair Ace]] has been developing the DC-8-73's cockpit, which has also been used in the new DC-8-63.


=== Liveries ===
Pilots are advised to use spoilers and thrust-reversers for deceleration to avoid overheated brakes - especially when landing a heavily loaded plane. The new auto spoilers, automatically deploying on touch-down when armed, provide some assistance here.


==Scenery corner==
==Scenery corner==
Line 89: Line 73:
[[File:mercuryredstone3.png|thumb|Mercury Redstone 3 Rocket ready for launch.]]
[[File:mercuryredstone3.png|thumb|Mercury Redstone 3 Rocket ready for launch.]]
Jack Mermod has released the first of many NASA Interactive Launch Complexes. This first release is based on Launch Complex 5 and the [http://en.wikipedia.org/wiki/Mercury-Redstone_3 Mercury-Redstone 3] launch. The model should be in the official database soon, for now you can download the scenery [http://alphashangar.co.nr/ here].
Jack Mermod has released the first of many NASA Interactive Launch Complexes. This first release is based on Launch Complex 5 and the [http://en.wikipedia.org/wiki/Mercury-Redstone_3 Mercury-Redstone 3] launch. The model should be in the official database soon, for now you can download the scenery [http://alphashangar.co.nr/ here].
=== TerraGear-CS ===
After attempts to provide a new World Scenery build in sync with the 2.0 software release failed miserably (due to software deficiencies), some effort has been expended into investigations, experiments (some of which ended up in filing bug-reports for related software) and large-scale tests for replacing the entire polygon processing in TerraGear by the use of [http://grass.osgeo.org/ GRASS GIS]. Just to give an idea about the term "large scale": The procedure to turn the Europe-wide CORINE CLC2000 vector data set into a topologically consistent coverage is taking several weeks on a 3 GHz Xeon machine.
The "*-decode" commands and old-style work directories are affected by this change as well as all polygon-mangling routines in "construct". The GRASS toolbox provides all the features we need for ''reliable'', topologically correct polygon handling (cleaning, clipping and the like). Those (early) steps of the new toolchain which have proven to be rather stable are available [http://mapserver.flightgear.org/git/?p=terragear-cs;a=tree;f=gisscripts here] (GRASS7 required for certain features).


=== Jet d'Eau in Geneva ===
=== Jet d'Eau in Geneva ===
Line 102: Line 91:
In an effort to improve the cities in FlightGear, Daniel Strawn (aka "Intel-Qube") has modeled a simple "one size fits all" city. Affectionately codenamed "ICEJAW", the city, still in development, features tangible helipads to land on, billboards and snow cover for heavy snow-fall.
In an effort to improve the cities in FlightGear, Daniel Strawn (aka "Intel-Qube") has modeled a simple "one size fits all" city. Affectionately codenamed "ICEJAW", the city, still in development, features tangible helipads to land on, billboards and snow cover for heavy snow-fall.
Follow development in the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10016 forum topic].
Follow development in the [http://www.flightgear.org/forums/viewtopic.php?f=5&t=10016 forum topic].
=== TerraGear-CS ===
After attempts to provide a new World Scenery build in sync with the 2.0 software release failed miserably (due to software deficiencies), some effort has been expended into investigations, experiments (some of which ended up in filing bug-reports for related software) and large-scale tests for replacing the entire polygon processing in TerraGear by the use of [http://grass.osgeo.org/ GRASS GIS]. Just to give an idea about the term "large scale": The procedure to turn the Europe-wide CORINE CLC2000 vector data set into a topologically consistent coverage is taking several weeks on a 3 GHz Xeon machine.
The "*-decode" commands and old-style work directories are affected by this change as well as all polygon-mangling routines in "construct". The GRASS toolbox provides all the features we need for ''reliable'', topologically correct polygon handling (cleaning, clipping and the like). Those (early) steps of the new toolchain which have proven to be rather stable are available [http://mapserver.flightgear.org/git/?p=terragear-cs;a=tree;f=gisscripts here] (GRASS7 required for certain features).
== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==


== Suggested flights ==
== Suggested flights ==
A beautiful flight is from Prince George, ICAO: CYXS, to Calgary Springbank, ICAO: CYBW, under the route created by reed, which can be seen at [http://flightgear.org/forums/viewtopic.php?f=10&t=9772 the forums]
A beautiful flight is from Prince George (CYXS), to Calgary Springbank (CYBW), under the route created by reed, which can be seen at [http://flightgear.org/forums/viewtopic.php?f=10&t=9772 the forum].


== Aircraft review ==
== Aircraft review ==
Line 122: Line 102:


== Wiki updates ==
== Wiki updates ==
===New articles===
=== Shader requests ===
<DynamicArticleList>
We have added a new page to the wiki titled [[shader requests]]. This is intended to provide a place for people to post ideas related to new shaders for use in FlightGear. But this is also meant to be place for aspiring shader developers to find interesting ideas for new shaders. In the past, these ideas were often spread over many different places, such as forum or mailing list discussions, and often ended up getting hidden rather quickly. So if you have ideas related to improving existing shaders or creating completely new ones, please add your ideas to the [[Shader requests]] page. And if you are aware of any ongoing shader development efforts, please also add those there. Consequently, if you want to get started creating shaders for FlightGear, please make sure to check out this page.
  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 ==
== Community news ==
=== FSweekend ===
=== FSweekend ===
As in previous year's FlightGear organized a booth at the annual [[FSweekend]] event in Lelystad, the Netherlands. [[FSweekend 2010|This year's edition of FSweekend]] came and went by before we realized it. Although there was initially skepticism as to whether we would be able to top last year's presentation, we did so, by quite a large margin. Main attractions this year were our Thomas-Krenn sponsored server, driving 10 monitors, and our near continuous use of [[Anaglyph (3D)|anaglyphic 3D]]. Although we had considered it to be a neat gadget, running flightgear in 3D analglyphic mode turned out to be a brilliant move. Not only did it draw a lot of people to our booth who wanted to check it out, handing out 3D glasses also worked as an extremely good vehicle to start a conversation with them.
As in previous year's FlightGear organized a booth at the annual [[FSweekend]] event in Lelystad, the Netherlands. [[FSweekend 2010|This year's edition of FSweekend]] came and went by before we realized it. Although there was initially skepticism as to whether we would be able to top last year's presentation, we did so, by quite a large margin. Main attractions this year were our Thomas-Krenn sponsored server, driving 10 monitors, and our near continuous use of [[Anaglyph (3D)|anaglyphic 3D]]. Although we had considered it to be a neat gadget, running flightgear in 3D analglyphic mode turned out to be a brilliant move. Not only did it draw a lot of people to our booth who wanted to check it out, handing out 3D glasses also worked as an extremely good vehicle to start a conversation with them.


Some assorted highlights include:
Some assorted highlights include:
*Our Thomas-Krenn AG machine has been running for 8 hours straight, on both days, without a single glitch. At one point Torsten ran out of fuel, because he hadn't realized that FlightGear had been running for so long continuously. The machine ran in three 3D mode most of the time, and the way the screens were set up gave the impression that the were just holes in a wall though which you could see a (virtual) reality known as FlightGear. Very nicely done.
* Our Thomas-Krenn AG machine has been running for 8 hours straight, on both days, without a single glitch. At one point Torsten ran out of fuel, because he hadn't realized that FlightGear had been running for so long continuously. The machine ran in three 3D mode most of the time, and the way the screens were set up gave the impression that the were just holes in a wall though which you could see a (virtual) reality known as FlightGear. Very nicely done.
*Very positive comments on the Lockheed Constellation's artwork, particularly because that model is really shining when presented in 3D (probably the best cockpit we have for a 3D demo).
* Very positive comments on the Lockheed Constellation's artwork, particularly because that model is really shining when presented in 3D (probably the best cockpit we have for a 3D demo).
*Also very postive comments on the advance copy of the 737NG (800) that Innis Cunningham sent me. Also in particular due to the fact that the switches on the overhead panel look very real in 3D.
* Also very postive comments on the advance copy of the 737NG (800) that Innis Cunningham sent me. Also in particular due to the fact that the switches on the overhead panel look very real in 3D.
*Booth members Gijs and Jorg trying to outperform each other in terms of their helicopter flying skills (trying to land it on a chimney, once they found the helipad to easy).
* Booth members Gijs and Jorg trying to outperform each other in terms of their helicopter flying skills (trying to land it on a chimney, once they found the helipad to easy).
*A number of people claiming that our booth was the best one at FSWeekend this year.
* A number of people claiming that our booth was the best one at FSWeekend this year.
*Our aerotowing demo involving all of our major demonstration machines (my machine as the glider, Jorg's computer as the tow plane, and our sponsor's machine as a joint (3D) model viewer.
* Our aerotowing demo involving all of our major demonstration machines (my machine as the glider, Jorg's computer as the tow plane, and our sponsor's machine as a joint (3D) model viewer.
*Some people just not believing that a single machine could drive 10 monitors and actively checking where all the monitor cables actually went to.
* Some people just not believing that a single machine could drive 10 monitors and actively checking where all the monitor cables actually went to.
*Another opportunity to meet FlightGear developers (one expected encounter: Geoff McLane, and one totally unexpected meeting with Thorsten Brehm). Thanks guys for showing up!
* Another opportunity to meet FlightGear developers (one expected encounter: Geoff McLane, and one totally unexpected meeting with Thorsten Brehm). Thanks guys for showing up!


And last, but not least, everybody involved in getting this year's booth organized. It's been a lot of fun. Some pictures of the event can be found [http://www.dropbox.com/gallery/7455889/1/FSWeekend2010?h=0e9825 here]
And last, but not least, everybody involved in getting this year's booth organized. It's been a lot of fun. Some pictures of the event can be found [http://www.dropbox.com/gallery/7455889/1/FSWeekend2010?h=0e9825 here]
Line 160: Line 124:
[http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=8726 Sealbhach] has made an [http://www.youtube.com/watch?v=zveiKtooXs0 excellent video] showcasing the great scenery at LOWI.
[http://www.flightgear.org/forums/memberlist.php?mode=viewprofile&u=8726 Sealbhach] has made an [http://www.youtube.com/watch?v=zveiKtooXs0 excellent video] showcasing the great scenery at LOWI.


=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
== Useful links ==
== And finally ... ==
== And finally ... ==
===A christmas present for you===
===A christmas present for you===
Line 180: Line 138:


So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].
So all users are invited to help us progress further with our preparations for GSoC 2011. If you have any questions or other feedback, please use the forum to [http://flightgear.org/forums/viewforum.php?f=38 get in touch].
=== Amateur Built Collimated Display ===
''Contributed by Gene Buckle''
A couple of months ago, my friend Wayne and I embarked on the development of a fully functional collimated display system for our DIY flight simulators. A collimated display has been the holy grail of DIY cockpit builders because of the image it generates. Collimated displays are also known as "infinity" displays. It's described that way because the focus point to your eye becomes "infinity" when you're located at the right spot when viewing the mirror.  The exact details of how they work are beyond this article, but you can learn more at [http://en.wikipedia.org/wiki/Full_flight_simulator Wikipedia]; see the section marked "Collimated Cross-Cockpit Displays".
Building the display successfully is a pretty big deal. Up until we completed the proof-of-concept project, collimated displays were the sole domain of multi-million dollar flight simulators from the likes of CAE, FlightSafety and others. It was declared too complex and too costly by just about everyone that ever approached the problem. Fortunately for us, all the "experts" were wrong. Not only did we build a fully functional collimating display, but we did it with off the shelf materials and very, very little expenditure. Total material costs for the mirror and projection screen is under $100.
The test mirror was built using an 8 foot diameter spherical shape. The framework itself describes a 60 degree wide by 40 degree high "slice" of that shape. The mirror itself is made of a 48" wide, 2mm thickness of Mylar sheet. In order to properly stretch the mirror, a set of "ears" had to be added to the framework. 
This shows the frame prior to the mirror being glued into place:
[[File:mirror_frame.jpg|200px|Collimating Mirror Framework]]
The framework itself is made from 12mm Baltic Birch and is under 36" tall. The arcs defined by the "inside" ribs show where the spherical section mirror will form. In order to form the mirror, vacuum must be applied. This will stretch the mirror into a spherical section shape.
Attaching the Mylar:
[[File:attaching_mylar.jpg|200px|Attaching the Mylar to the framework]]
The Mylar is attached to the oval ring by a high-tack spray on adhesive made by 3M.
In order to test the visual properties of the system, we set it up on a platform I'd built some time ago to use with racing games:
[[File:mirror_test.jpg|200px|Test setup]]
The mirror just reflects what is on the screen above it - the test screen in this case is just a bit less than half the radius of the mirror and is 17" tall. In order to start testing as soon as possible, Wayne skinned the screen with kraft paper. It's very wrinkly, but it did an adequate job of being a screen. It's also what we had handy at the time. :)
Here's the complete test configuration:
[[file:test_config.jpg|200px|Test configuration]]
We used a Fein Turbo III dust collector as our vac source and it pulls the mirror down very well! It's pulling about 5 PSI in order to force the Mylar into the correct shape. Below is a picture of the mirror after being pulled down.
[[file:formed_mirror.jpg|200px|Formed mirror]]
Photographs and video cannot do this justice!  It's just incredible to look at!
Here's a pic of Wayne performing the first test flight:
[[file:test_flight.jpg|200px|Test Flight]]
...and thus was born the world's very first amateur built fully collimated display for DIY flight simulators. I can't stress enough how thankful I am for Wayne and his skills. Were it not for his deep understanding of the math involved, this would have never been built.
Here are a few YouTube videos of the system in operation:
* [http://www.youtube.com/watch?v=y67TAo9Lv5g First draw down of the mirror]
* [http://www.youtube.com/watch?v=8yaDnXYlf8k My badly narrated test flight]
* [http://www.youtube.com/watch?v=zogFny49zrI A walk-around of the setup taken the next day]
The [http://www.diy-cockpits.org/coll/collimated_display.html project site] has more pictures and details on the current state of the project. Work has already begun on a 180 degree version!


=== Did you know ===
=== Did you know ===
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/26035"

Navigation menu