8,564
edits
FlightGear Newsletter April 2011: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 10: | Line 10: | ||
The shader does some simplifications, but basically tries to recreate physical phenomenom, so the look could be easily modified depending on environmental conditions. But since the values are not so easy to figure out, some testing would be needed for creating nice looking sky for misty weather, rainy weather, cold winter etc. After that, proper equations could be written to transform weather values to scattering parameters. | The shader does some simplifications, but basically tries to recreate physical phenomenom, so the look could be easily modified depending on environmental conditions. But since the values are not so easy to figure out, some testing would be needed for creating nice looking sky for misty weather, rainy weather, cold winter etc. After that, proper equations could be written to transform weather values to scattering parameters. | ||
The shader is not production ready | The shader is not production ready; it has some bugs and terrain (especially fog at horizon) does not match the looks of the skydome. This is a work in process, but might take some time, because the terrain shader is much harder than the skydome shader. | ||
== Nasal for newbies == | == Nasal for newbies == | ||
| Line 25: | Line 25: | ||
* Output data can be used locally or sent to network | * Output data can be used locally or sent to network | ||
Recently a FlightGear support was added. At this time it was tested | Recently a FlightGear support was added. At this time it was tested to work with FlightGear versions 1.9.1, 2.0 and from GIT. Instructions on how to run LinuxTrack with FlightGear are available in the README.ltr_pipe file located in the "doc" directory of the project's source tree. Source code is available from svn repository: | ||
to work with FlightGear versions 1.9.1, 2.0 and from GIT. Instructions on how | |||
to run LinuxTrack with FlightGear are available in the README.ltr_pipe file located | |||
in the "doc" directory of the project's source tree. Source code is available from svn repository: | |||
<pre>svn checkout http://linux-track.googlecode.com/svn/trunk/ linux-track-read-only</pre> | <pre>svn checkout http://linux-track.googlecode.com/svn/trunk/ linux-track-read-only</pre> | ||
| Line 71: | Line 68: | ||
[[Image:Bk117cockpitdev.jpg|thumb|BK 117 cockpit in developement (Blender)]] | [[Image:Bk117cockpitdev.jpg|thumb|BK 117 cockpit in developement (Blender)]] | ||
While work on the fdm is mostly finished and only small things on the exterior model has to be done, work on the cockpit of the | While work on the fdm is mostly finished and only small things on the exterior model has to be done, work on the cockpit of the | ||
BK 117 has begun and is in a good progress. The cockpit will be detailed and make use of photorealistic textures and as | [[BK 117]] has begun and is in a good progress. The cockpit will be detailed and make use of photorealistic textures and as | ||
a lot of new instruments and panels will be created, this is mostly a modeling challenge. The b1900d-cockpit is guide for the developement to keep the aircraft framerate-friendly. Because of the complex cockpit an own AI-model will be created to keep MP-Users happy. | a lot of new instruments and panels will be created, this is mostly a modeling challenge. The b1900d-cockpit is guide for the developement to keep the aircraft framerate-friendly. Because of the complex cockpit an own AI-model will be created to keep MP-Users happy. | ||
This developement is also a test for the upcoming [[EC135]]/635-project, which will also have a detailed and accurate cockpit with photorealistic textures. | |||
The images for the textures are taken by the former user and developer heliflyer, who was a emergency doctor on [[Bo105]], BK117 and EC135 in Northern Germany. | |||
=== Doctor Who TARDIS === | === Doctor Who TARDIS === | ||
| Line 81: | Line 79: | ||
Vinura has started work on developing a [http://en.wikipedia.org/wiki/TARDIS#The_Doctor.27s_TARDIS Doctor Who TARDIS] for FlightGear. The exterior model is almost complete in SketchUp. Click [http://www.flightgear.org/forums/viewtopic.php?f=4&t=11738 here] for the development thread. | Vinura has started work on developing a [http://en.wikipedia.org/wiki/TARDIS#The_Doctor.27s_TARDIS Doctor Who TARDIS] for FlightGear. The exterior model is almost complete in SketchUp. Click [http://www.flightgear.org/forums/viewtopic.php?f=4&t=11738 here] for the development thread. | ||
Currently, | Currently, he still needs to get the TARDIS colours right as it is only allowed to use 'Named Colours' from Google SketchUp as they can't claim copyright on colours. | ||
=== Updated aircraft === | === Updated aircraft === | ||
| Line 87: | Line 85: | ||
==== ATR 72-500 ==== | ==== ATR 72-500 ==== | ||
[[File:ATR_72-500-cockpit.jpg|thumb|The 3d cockpit of the ATR 72.]] | [[File:ATR_72-500-cockpit.jpg|thumb|The 3d cockpit of the ATR 72.]] | ||
After a long | After a long five months, [[User:Skyop|Skyop]] has completed the [[ATR 72-500]], which finally features a complete cockpit and aircraft systems. Highlights include an advanced autopilot, hydraulics system, tiller steering system, an interior cabin, and new documentation. The aircraft has been committed to [[FlightGear and Git|Git]] and will hopefully be available in the next release of FlightGear. It is now one of the most advanced turboprops for FlightGear, right behind the [[B1900d]]. | ||
==== A340-600 ==== | ==== A340-600 ==== | ||
| Line 94: | Line 92: | ||
=== Liveries === | === Liveries === | ||
[[Image:Fgfs-screen-089.png|thumb|SriLankan Airlines' Boeing 767]] | [[Image:Fgfs-screen-089.png|thumb|SriLankan Airlines' Boeing 767]] | ||
Some [http://liveries.flightgear.org/airlines.php?id=231 SriLankan Airlines] liveries have been made by Vinura for the [[Boeing 767]] and [[Airbus A320]]. | * Some [http://liveries.flightgear.org/airlines.php?id=231 SriLankan Airlines] liveries have been made by Vinura for the [[Boeing 767]] and [[Airbus A320]]. | ||
* Brett created a lot of nice [http://liveries.flightgear.org/aircraft.php?id=52 Gloster Meteor liveries]. Altough we're slowly getting used to the quality of his liveries, they still amaze lots of users. | |||
* Robert started painting (and remapping) the [[De Havilland Canada DHC-6 Twin Otter|DHC-6]], providing us some [http://liveries.flightgear.org/aircraft.php?id=57 excellent liveries]. | |||
== Scenery corner == | == Scenery corner == | ||
| Line 101: | Line 101: | ||
==== Create the shapefiles by hand ==== | ==== Create the shapefiles by hand ==== | ||
This method has been used for St. Maarten in the World Scenery | {{Main article|Howto: Create custom scenery}} | ||
This method has been used for St. Maarten in the World Scenery and Rio de Janeiro custom scenery. In this way, you download a satellite photo or an aerial photo and create the shapefiles by hand by "drawing" on top of the photo. | |||
==== Create the shapefiles using land cover data ==== | ==== Create the shapefiles using land cover data ==== | ||
| Line 117: | Line 118: | ||
=== New buildings === | === New buildings === | ||
Once again, there are new Eastern Asian buildings | Once again, there are new Eastern Asian buildings added to the scenery database, including: | ||
* Saigon Center - Ho Chi Minh City - Vietnam | * Saigon Center - Ho Chi Minh City - Vietnam | ||
* Ben Thanh market - Ho Chi Minh City - Vietnam | * Ben Thanh market - Ho Chi Minh City - Vietnam | ||
| Line 152: | Line 152: | ||
KSFO was also improved with animated jetways. | KSFO was also improved with animated jetways. | ||
=== | === Chubu Centrair - JAPAN: a new highly detailed airport in FlightGear=== | ||
[[File:RJGG_island.png|200px|thumb|left|Chubu Centrair island and airport]] | [[File:RJGG_island.png|200px|thumb|left|Chubu Centrair island and airport]] | ||
[http://en.wikipedia.org/wiki/Ch%C5%ABbu_Centrair_International_Airport Centrair] is classified as a first class airport and is the main international gateway for the Chūbu ("central") region of Japan, and currently is counted among the Top-10 modern airports of the world. Chubu is an airport on an artificial island in Ise Bay, Tokoname City in Aichi Prefecture, 35 km (22 mi) south of Nagoya in central Japan. | [http://en.wikipedia.org/wiki/Ch%C5%ABbu_Centrair_International_Airport Chubu Centrair] (RJGG) is classified as a first class airport and is the main international gateway for the Chūbu ("central") region of Japan, and currently is counted among the Top-10 modern airports of the world. Chubu is an airport on an artificial island in Ise Bay, Tokoname City in Aichi Prefecture, 35 km (22 mi) south of Nagoya in central Japan. | ||
[[File:RJGG_day01.png|200px|thumb|right|Chubu jetways and hangars]] | [[File:RJGG_day01.png|200px|thumb|right|Chubu jetways and hangars]] | ||
Originally a single runway in the middle of the ocean in default | Originally a single runway in the middle of the ocean in tge default FlightGear terrain, it has now been developed at a high level of details and realism by Horacio, who has modeled the main terminal (shaped like a "T"), the ATC tower and main hangars sorrounding the airport. A second step considers complete the rest of buildings presents on the island. The terminal and main buildings have been animated with night textures, which complemented with lights and default 3D airplane models taken from FG package, give the airport a very realistic and fantastic night impression. | ||
[[File:RJGG_night01.png|200px|thumb|right|Chubu jetways and hangars]] | [[File:RJGG_night01.png|200px|thumb|right|Chubu jetways and hangars]] | ||
| Line 176: | Line 176: | ||
</gallery> | </gallery> | ||
== Screenshot of the month == | == Screenshot of the month == | ||
SriLankan Airlines livery on an Airbus A320 taken at dusk. | SriLankan Airlines livery on an Airbus A320 taken at dusk. | ||
| Line 215: | Line 213: | ||
This has to be one of the best planes that I have ever used in FlightGear! | This has to be one of the best planes that I have ever used in FlightGear! | ||
Thanks for reading! | Thanks for reading! | ||
'''''Review by Vinura''''' | |||
== Community news == | == Community news == | ||
=== FlightGear on youtube === | === FlightGear on youtube === | ||
* Skyop created a lovely video (for the [http://www.flightgear.org/forums/viewtopic.php?f=19&t=11059 Linuxtag video contest], which was held at the forum) showcasing some of the latest and greatest developments in FlightGear. The video was uploaded in two parts: [http://www.youtube.com/watch?v=nTDgtDrabaA part 1], [http://www.youtube.com/watch?v=A-6xyxjom68 part 2]. It will be shown in Berlin, to attract new FlightGear users and developers. | |||
=== FlightGear events === | === FlightGear events === | ||
==== FlightGear at Linuxtag ==== | |||
From 11 till 14 May, FlightGear will be present at [http://www.linuxtag.org/2011/en.html Linuxtag 2011] in Berlin, Germany. A preview of what the FlightGear guys will be showing was posted at [http://www.flightgear.org/forums/viewtopic.php?f=42&t=11881 our forum]. If you are able to drop Berlin a visit, feel welcome to stop over at our booth. | |||
==== FlyingClub Mayday 1 ==== | ==== FlyingClub Mayday 1 ==== | ||
The FGFC '''"Mayday 1: Manitoba Rescue"''' operation was held April 2nd, 2011 at CYAV, Winnipeg/St.Andrews, with seven pilots participating. The scenario stated two of Manitoba's major rivers were flooding, and people were stranded along both, so STOL and helicopter pilots were mustered at CYAV, received assignments from ATC, planned their flights, and notified ATC when they were ready to proceed. A total of twenty missions were assigned, sixteen of which were successfully completed in the space of three hours. | The FGFC '''"Mayday 1: Manitoba Rescue"''' operation was held April 2nd, 2011 at CYAV, Winnipeg/St.Andrews, with seven pilots participating. The scenario stated two of Manitoba's major rivers were flooding, and people were stranded along both, so STOL and helicopter pilots were mustered at CYAV, received assignments from ATC, planned their flights, and notified ATC when they were ready to proceed. A total of twenty missions were assigned, sixteen of which were successfully completed in the space of three hours. | ||