FlightGear Newsletter January 2014: Difference between revisions

Jump to navigation Jump to search

FlightGear Newsletter January 2014 (view source)

Revision as of 17:19, 2 February 2014

3,514 bytes removed ,  2 February 2014
prep
(prep)
Line 5: Line 5:


== Development news ==
== Development news ==
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]].
=== FlightGear 3.0 release candidates ===
February 17 is our scheduled v3.0 release date! If any of you are a bit adventurous and want to test out the "release candidates", you can find the latest FlightGear-3.0 builds here: http://fgfs.goneabitbursar.com/releases/
Please double check the dates, these are not official 3.0 releases yet and are subject to change as we close in on the official release date.
 
Feedback is welcomed in our dedicated forum http://forum.flightgear.org/viewforum.php?f=68


=== Soaring instrumentation SDK ===
=== Soaring instrumentation SDK ===


Galvedro has started documenting the new soaring instrumentation Software Development Kit (SDK). The soaring instrumentation toolkit is a small library of Nasal objects that you can use for adding specialised soaring gauges to your glider. The library is comprised of several building blocks that you can connect together in different ways in order to get the desired functionality.
Galvedro has started documenting the new soaring instrumentation Software Development Kit (SDK). The soaring instrumentation toolkit is a small library of [[Nasal]] objects that you can use for adding specialised soaring gauges to your glider. The library is comprised of several building blocks that you can connect together in different ways in order to get the desired functionality.


In order to use the library, you will need to write a Nasal script that will be loaded together with your aircraft. You do so by referencing this script in the <Nasal> section of your aircraft definition XML file. But don´t be scared, the scripts will be very simple. Lets see some examples.
In order to use the library, you will need to write a Nasal script that will be loaded together with your aircraft. You do so by referencing this script in the <Nasal> section of your aircraft definition XML file. But don´t be scared, the scripts will be very simple. Lets see some examples.
Line 31: Line 35:


Continue reading at [[Soaring instrumentation sdk]]...
Continue reading at [[Soaring instrumentation sdk]]...
=== Creating a custom ATC/RADAR Layer in 10 minutes ===
=== Creating a custom ATC/RADAR Layer in 10 minutes ===
Philosopher and Hooray have added a new tutorial that demonstrates how to create new [[MapStructure]]-based Canvas displays. People already having some Nasal experience (property tree, OOP), should be able to complete this in less than 15-20 minutes. So, to learn how to create a simple ATC/RADAR display, continue reading at [[Canvas Radar]]...
Philosopher and Hooray have added a new tutorial that demonstrates how to create new [[MapStructure]]-based Canvas displays. People already having some Nasal experience (property tree, OOP), should be able to complete this in less than 15-20 minutes. So, to learn how to create a simple ATC/RADAR display, continue reading at [[Canvas Radar]]...
Line 56: Line 61:


=== Using OpenStreetMap Data in FlightGear ===
=== Using OpenStreetMap Data in FlightGear ===
In 2013, we've seen quite a bit of progress on procedural scenery generation using OSM data, including buildings & cities (radi, Soitanen/osm2fg), roads, rivers - even railways (vivian) and procedural bridge generation (radi), but also procedural power lines (vanosten).  
In 2013, we've seen quite a bit of progress on procedural scenery generation using [[OpenStreetMap]] (OSM) data, including buildings & cities (radi, Soitanen/osm2fg), roads, rivers - even railways (vivian) and procedural bridge generation (radi), but also procedural power lines (vanosten).  


In other words, there's now some serious -and unprecedented manpower, including quite a few folks who are able to build from source and able to write C++ code. So this deserves being coordinated among all interested parties. And it would clearly make sense not to just expose things to the Canvas system, but to expose the corresponding APIs so that other subsystems and users can access these and use these for the purposes outlined above.
In other words, there's now some serious -and unprecedented manpower, including quite a few folks who are able to build from source and able to write C++ code. So this deserves being coordinated among all interested parties. And it would clearly make sense not to just expose things to the Canvas system, but to expose the corresponding APIs so that other subsystems and users can access these and use these for the purposes outlined above.


Which is why we have created a summary of the main OSM related efforts we've seen in the last 18  months, continue reading at [[Using OSM Vector Data in FlightGear]]...
Which is why we have created a summary of the main OSM related efforts we've seen in the last 18  months, continue reading at [[Using OSM Vector Data in FlightGear]]...
=== Project Rembrandt ===
A number of Mac users have been reporting issues related to running [[Project Rembrandt]] (deferred rendering/shadows) on Mac OSX with ATI/AMD GPUS, we are now looking for Mac users to provide feedback on running Rembrandt on Mac OSX, required information includes errors and warnings shown during startup/runtime, but also screen shots showing any issues. Please see: [[Project Rembrandt#Mac Issues]].
=== Canvas System ===
=== High Level Architecture ===
=== Usability Improvements ===
=== Getting involved as a programmer ===
Unfortunately, most of the active FG developers are currently very overstretched in terms of the areas that they have ownership of, which is affecting how much can actually be done.  Fundamentally we need more core devs.
If you are interested in contributing as a core developer, please see [[Howto:Start core development]].
== Release ChangeLog ==
This section lists changes committed this month that will be available in the next release, these will be copied to the release changelog shortly before a release (for each month), so that we hopefully get a comprehensive list of new features.
== Interview with a contributor (NAME) ==
''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?
* What are your major interests in FlightGear?
* What project are you working on right now?
* What do you plan on doing in the future?
* Are you happy with the way the FlightGear project is going?
* What do you enjoy most about developing for FlightGear?
* Are there any "hidden features" you have worked on in FlightGear that new users may miss?
* What advice can you give to new developers who want to get started on their first aircraft/new feature/Nasal script?
More questions are being collected here: [[Interview questions]].
Stay tuned for next month's interview, featuring FlightGear contributor XXXXXXXX
== Nasal for newbies ==
== New software tools and projects ==


== FlightGear addons and mods ==
== FlightGear addons and mods ==


===Bombable add-on updated to Version 4.5b===
===Bombable add-on updated to Version 4.5b===
Flightgear add-on Bombable, which turns Flightgear into a full-featured combat flight simulator, was updated to version 4.5b on January 9th.
FlightGear add-on [[Bombable]], which turns FlightGear into a full-featured combat flight simulator, was updated to version 4.5b on January 9th.


Highlights of the new version: [[File:A-10 Warthog in Bombable.png|thumb|A-10 Warthogs in an AI Scenario running with the Bombable add-on.]]
Highlights of the new version: [[File:A-10 Warthog in Bombable.png|thumb|A-10 Warthogs in an AI Scenario running with the Bombable add-on.]]
Line 111: Line 80:
* '''Improvements to AI aircraft realism''', bug fixes.
* '''Improvements to AI aircraft realism''', bug fixes.


[http://forum.flightgear.org/viewtopic.php?f=6&t=5742 Read more about Bombable or download the add-on here.]
Read more about Bombable or download the add-on from [http://forum.flightgear.org/viewtopic.php?f=6&t=5742 the forum topic]


{{#ev:youtube|PirnWJHZtcg|400}}
{{#ev:youtube|PirnWJHZtcg|400}}


This very well explained video made by Jetman shows how to do a short flight mission from San Francisco (KSFO) intercepting an [[A-10 Warthog]] air patrol near Sausalito in a [[F-14_Tomcat]] running in FlightGear Bombable.
This very well explained video made by Jetman shows how to do a short flight mission from San Francisco (KSFO) intercepting an [[A-10 Warthog]] air patrol near Sausalito in a [[F-14 Tomcat]] running in FlightGear Bombable.


== In the hangar ==
== In the hangar ==
=== New aircraft ===
=== Updated aircraft ===
=== Updated aircraft ===
==== '''DC-10-30 Getting a Flightdeck Refit''' ====
==== DC-10-30 Getting a Flightdeck Refit ====


'''David Waggoner, “DrDavid”'''
'''David Waggoner, “DrDavid”'''


[[File:DC-10-30ER_Over_Mt_Everest.jpg]]
[[File:DC-10-30ER_Over_Mt_Everest.jpg|thumb|350px|DC-10-30ER over Mt. Everest]]
 
'''DC-10-30ER over Mt. Everest'''
 


'''A New Front Office for a Great Widebody Airliner '''
'''A New Front Office for a Great Widebody Airliner '''
Line 136: Line 99:


The DC-10-30 makes a great platform for this kind of revision because of its sophisticated flight dynamics, autopilot and it is Rembrandt enabled. Rembrandt provides superior lighting capabilities both outside and inside the aircraft, but not all FG instruments are Rembrandt-compatible.  Therefore, a new avionics package had to be functional in that environment.
The DC-10-30 makes a great platform for this kind of revision because of its sophisticated flight dynamics, autopilot and it is Rembrandt enabled. Rembrandt provides superior lighting capabilities both outside and inside the aircraft, but not all FG instruments are Rembrandt-compatible.  Therefore, a new avionics package had to be functional in that environment.
[[File:DC-10-30_Flightdeck_Day_Screenshot.jpg]]


'''State of the Project'''
'''State of the Project'''


Fortunately, the CRJ-700 Family Series (also by Ryan Miller) has a glass cockpit set up for Rembrandt.  The PFD, MFD, EICAS, CDU, Radio Stack, Upper Light Switch Panel, and Side Panels were transferred from the CRJ700 to the DC-10-30.  After much tweaking and trial and error, many, but not all of the CRJ’s screens are functional.  In addition, a set of standby instruments have been added to support the three glass screens.  Note there is cleanup work to be done on the panel—this is a work in development. The choice of instruments and layout are designed to meet my preferences, but that is expected to continue to progress.
Fortunately, the CRJ-700 Family Series (also by Ryan Miller) has a glass cockpit set up for Rembrandt.  The PFD, MFD, EICAS, CDU, Radio Stack, Upper Light Switch Panel, and Side Panels were transferred from the CRJ700 to the DC-10-30.  After much tweaking and trial and error, many, but not all of the CRJ’s screens are functional.  In addition, a set of standby instruments have been added to support the three glass screens.  Note there is cleanup work to be done on the panel—this is a work in development. The choice of instruments and layout are designed to meet my preferences, but that is expected to continue to progress.
The two screenshots illustrate the great effectiveness of having Rembrandt.
The two screenshots below illustrate the great effectiveness of having Rembrandt.
 
 
[[File:DC-10-30_Flightdeck_Night_Screenshot.jpg]]
 


'''Rembrandt and Now the Canvas-Ready NavDisplay'''
'''Rembrandt and Now the Canvas-Ready NavDisplay'''


A brilliant opportunity has popped up, in the mean time.  The release of the new Canvas-ready NavDisplay screens, which will be developed by FlightGear over time to match specific aircraft, is now available.  I am in the process of installing the ND in the DC-10’s MFD.  Once a stable MFD is achieved, the aircraft will be uploaded into Git for the FlightGear Community to take a look at.  I have a long TODO list for other improvements to the model, and will welcome other collaborators—I suspect you might have some ideas I haven’t even thought of that would be great to include.  There is also the opportunity to create more liveries for the airplane.
A brilliant opportunity has popped up, in the mean time.  The release of the new Canvas-ready NavDisplay screens, which will be developed by FlightGear over time to match specific aircraft, is now available.  I am in the process of installing the ND in the DC-10’s MFD.  Once a stable MFD is achieved, the aircraft will be uploaded into Git for the FlightGear Community to take a look at.  I have a long TODO list for other improvements to the model, and will welcome other collaborators—I suspect you might have some ideas I haven’t even thought of that would be great to include.  There is also the opportunity to create more liveries for the airplane.
<gallery mode=Packed widths=300px heights=300px>
DC-10-30_Flightdeck_Day_Screenshot.jpg|
DC-10-30_Flightdeck_Night_Screenshot.jpg|
</gallery>


==== McDonnell Douglas MD 902 Explorer ====
==== McDonnell Douglas MD 902 Explorer ====
Line 164: Line 124:
====Updated JSBSim FDM for Sopwith Camel with historical features====
====Updated JSBSim FDM for Sopwith Camel with historical features====


A new JSBSim Flight Dynamics Model for the Sopwith Camel was [https://www.youtube.com/playlist?list=PLttk_Y2c7I-c4_SH4zvqJXx1WMt9U1CUF Aircraft of the Month] in May 2013. The FDM attempts to incorporate all known performance characteristics of the Camel documented in various historical accounts by pilots as well as published technical documents.  Many of these documents and interesting historical accounts of the Camel can by found in the Docs directory of the release.
A new [[JSBSim]] Flight Dynamics Model for the Sopwith Camel was [https://www.youtube.com/playlist?list=PLttk_Y2c7I-c4_SH4zvqJXx1WMt9U1CUF Aircraft of the Month] in May 2013. The FDM attempts to incorporate all known performance characteristics of the Camel documented in various historical accounts by pilots as well as published technical documents.  Many of these documents and interesting historical accounts of the Camel can by found in the Docs directory of the release.


Now version 1.8 of the JSBSim FDM for the Camel has been released, taking into consideration feedback from users and making various improvements.
Now version 1.8 of the JSBSim FDM for the Camel has been released, taking into consideration feedback from users and making various improvements.


[http://forum.flightgear.org/viewtopic.php?f=4&t=19584 Find out more or download the Sopwith Camel here]
Find out more or download the Sopwith Camel from [http://forum.flightgear.org/viewtopic.php?f=4&t=19584 the forum topic]


<gallery mode=packed widths=350px heights=350px>
<gallery mode=packed widths=300px heights=300px>
Sopwith Camels battle in Bombable 02.png|Sopwith Camels in an AI Scenario running with the Bombable add-on.
Sopwith Camels battle in Bombable 02.png|Sopwith Camels in an AI Scenario running with the Bombable add-on.
Sopwith Camels battle in Bombable 01.png|Sopwith Camels in an AI Scenario running with the Bombable add-on.
Sopwith Camels battle in Bombable 01.png|Sopwith Camels in an AI Scenario running with the Bombable add-on.
</gallery>
</gallery>
=== Liveries ===


== Scenery corner ==
== Scenery corner ==
=== Airports ===
=== Airports ===
==== Václav Havel Airport Prague ====
Works have been added to Václav Havel Airport Prague (LKPR) with a lot of hangars, terminals and other buildings. More information can be found on the dedicated wiki page: [[Václav Havel Airport Prague]].


Works have been added to '''Václav Havel Airport Prague - LKPR''' with a lot of hangars, terminals and other buildings. More informations you can find on this FG wiki page: [[Václav_Havel_Airport_Prague|Václav Havel Airport Prague]]
TerraSync has it all! You don't need to download a custom scenery.
 
''TerraSync has it all! You don't need to download a custom scenery.''
<gallery mode=Packed-overlay widths=300px heights=300px>
<gallery mode=Packed-overlay widths=300px heights=300px>
LKPR North Apron.jpg|The north apron of LKPR
LKPR North Apron.jpg|The north apron of LKPR
LKPR East Apron.jpg|The east apron of LKPR
LKPR East Apron.jpg|The east apron of LKPR
</gallery>
</gallery>


=== Regional textures ===
=== Regional textures ===
Regional texture definitions for Iceland have been updated on GIT to match the newly available CORINE based version of Iceland in our World Scenery 2.0. Check it out - the place looks gorgeous now!
Regional texture definitions for Iceland have been updated on GIT to match the newly available CORINE based version of Iceland in our World Scenery 2.0. Check it out - the place looks gorgeous now!


Line 203: Line 159:
[[File:SouthAfrica03.jpg|260px|Near Franshoek, ZA  in World Scenery 2.0]]
[[File:SouthAfrica03.jpg|260px|Near Franshoek, ZA  in World Scenery 2.0]]


== Aircraft of the month ==
== Airport of the month ==
== Screenshot of the month ==
== Screenshot of the month ==
 
FlightGear goes back to space!  
Flightgear goes back to space!  


Arc top of a ballistic trajectory with the X-15 - 330.000 ft above Iceland, 600 km visibility range!
Arc top of a ballistic trajectory with the X-15 - 330.000 ft above Iceland, 600 km visibility range!
Line 217: Line 170:
[[File:X-15-iceland05.jpg|600px|The X-15 on the falling leg of a high-altitude ballistic trajectory above Iceland]]
[[File:X-15-iceland05.jpg|600px|The X-15 on the falling leg of a high-altitude ballistic trajectory above Iceland]]


== Suggested flights ==
== Aircraft reviews ==
== Wiki updates ==
=== Translators required ===
{|
|[[File:en.gif]]
|The FlightGear Wiki still needs help for translating it into various languages. If you are interested in making the FlightGear Wiki multi-language then start at [[Help:Translate]].
|-
|[[File:de.gif]]
|Das FlightGear Wiki benötigt immer noch Hilfe bei der Übersetzung in verschiedene Sprachen. Wenn Du Interesse daran hast, das FlightGear Wiki Mehrsprachig zu machen, dann fang doch mit [[:de:Help:Übersetzen|Help:Übersetzen]] an.
|-
|[[File:nl.gif]]
|De FlightGear Wiki kan nog steed hulp gebruiken bij het vertalen van artikelen. Als je interesse hebt om de wiki meertalig te maken, raden we je aan om een kijkje te nemen bij [[:nl:Help:Vertalen|Help:Vertalen]].
|-
|[[File:es.gif]]
|La FlightGear wiki todavía necesita ayuda para traducirla a varios lenguajes. Si estás interesado en hacer la FlightGear wiki multilingüe, entonces comienza en [[:es:Help:Traducir|Help:Traducir]].
|}
== Community news ==
=== FlightGear on YouTube ===
=== New tutorials and screencasts ===
=== Forum news ===
=== Multiplayer ===
=== Virtual airlines ===
=== FlightGear events ===
== Useful links ==
== And finally ... ==
== And finally ... ==
=== Contributing ===
=== Contributing ===
Line 255: Line 179:


=== YASim looking for a new maintainer ===
=== YASim looking for a new maintainer ===
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.
{{cquote|There are some pending merge requests to add some Yasim features, but we have an issue that since none of the current C++ developers own, or are experts in Yasim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.


Line 276: Line 198:


<references/>
<references/>
=== Call for volunteers ===
* The [[Target4Today]] team is looking for volunteers to help improving FlightGear's combat support
=== Did you know ===


[[Category:FlightGear Newsletter|2014 01]]
[[Category:FlightGear Newsletter|2014 01]]
[[Category:Changes after 2.12]]
[[Category:Changes after 2.12]]
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/67133"

Navigation menu