8,574
edits
FlightGear Newsletter March 2016: Difference between revisions
m
Protected "FlightGear Newsletter March 2016": Newsletter ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))
(Template) |
m (Protected "FlightGear Newsletter March 2016": Newsletter ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))) |
||
| (13 intermediate revisions by 8 users not shown) | |||
| Line 1: | Line 1: | ||
{{Newsletter-header|March 2016}} | {{Newsletter-header|March 2016}} | ||
<div style="border-bottom:3px double #BBB;"> | <div style="border-bottom:3px double #BBB;"> | ||
| Line 7: | Line 4: | ||
| valign="top" width="33%" | | | valign="top" width="33%" | | ||
{{Newsletter-cover-header|Development news}}<br> | {{Newsletter-cover-header|Development news}}<br> | ||
[[#ALS procedural lights|ALS procedural lights]]<br> | |||
{{Newsletter-cover-header|In the hangar}}<br> | {{Newsletter-cover-header|In the hangar}}<br> | ||
[[#Space Shuttle|Space Shuttle]]<br> | |||
[[#Extra500 update|Extra500 update]] | |||
| valign="top" width="33%" | | | valign="top" width="33%" | | ||
{{Newsletter-cover-header|Scenery Corner}}<br> | {{Newsletter-cover-header|Scenery Corner}}<br> | ||
[[#Scenery corner|New tower and terminal models]] | |||
| valign="top" width="33%" | | | valign="top" width="33%" | | ||
{{Newsletter-cover-header|Contributing}}<br> | {{Newsletter-cover-header|Contributing}}<br> | ||
[[# | [[#Tips and advice for novices|Tips and advice for novices]]<br> | ||
[[#Screenshot of the Month|Screenshot of the Month]] | |||
|}</div> | |}</div> | ||
== Development news == | == Development news == | ||
=== ALS procedural lights === | |||
[[File:Cessna 182 with procedural lights.jpg|thumb|[[Cessna 182|Cessna 182S]] with procedurally generated position lights.]] | |||
{{usr|Thorsten}} has been working on the implementation of a [[ALS technical notes#ALS procedural lights|new framework for aircraft lights]] for the [[Atmospheric light scattering]] rendering engine. Instead of creating the lights (Beacon, navigation lights, strobes, etc.) via a billboarded emissive texture, these lights are generated procedural. | |||
The big advantage of procedural lights is that they can be directional and change their appearance with changing ambient light, which the traditional lights cannot do. | |||
Note that procedural lights do not work for [[Rembrandt]] and the default rendering engine. | |||
{{-}} | |||
== In the hangar == | == In the hangar == | ||
=== Space Shuttle === | |||
The development version of the [[Space Shuttle]] contains now code to simulate approaching and docking with the International Space Station (ISS). | |||
[[File:Shuttle ISS01.jpg|600px|The Space Shuttle approaching ISS]] | |||
The implementation involves the actual Shuttle avionics displays and requires proper application of state vector management using the sensors (e.g. the ranging radar) - for a [http://wiki.flightgear.org/Flying_the_Shuttle_-_Orbital_Operations#Proximity_operations tutorial] see the wiki. | |||
Currently ISS is represented by a rather coarse, untextured mesh - a textured model with better resolution would (obviously) be a valuable addition. | |||
=== Extra500 update === | |||
[[File:Only 2 greens.png|thumb|Extra500: only two greens]] | |||
The [[Extra EA-500]] recently received a few more features for you to enjoy. | |||
==== Failure manager GUI ==== | |||
The first is a [[Extra EA-500/failure dialog|failure manager with user interface.]] It will let you produce and repair failures in various aircraft systems. For instance, a jammed landing gear leg or a leaking fuel tank. | |||
==== Alternative pitch control ==== | |||
The second one is [[Extra EA-500/pitch control|an alternative pitch control system]]. It is intended for joystick users and is toggled on/off with {{key press|Ctrl|f}}. In this mode the joystick position controls the pilot force on the yoke, not the position. It fixes two issues: | |||
# Too sensitive control due to the large difference in real aircraft yoke travel and joystick travel. | |||
# To be able to (pitch) trim the aircraft for the joystick to be centered and fly straight and level. | |||
==== The icing on the cake ==== | |||
The third feature is [[Extra EA-500/Icing|icing]]. Now your aircraft can ice up with all the bad things accompanying that (so the above statement "to enjoy" is not quite valid here). Your engine might fail or your horizontal tail might stall among other things. So from now on you need to be aware of icing and take the appropriate counter measures. | |||
This latest version is available in FGaddon or alternatively {{gitlab zip file | proj=extra500 | repo=extra500 | branch=FG/2016.1 | text=download}} (for FG version 2016.1 and later). | |||
Have a safe flight! | |||
== Scenery corner == | == Scenery corner == | ||
New tower and terminal models have been added to, amongst others, the following airports: | |||
* Denver (KDEN) | |||
* London Heathrow (EGLL) | |||
* Washington Dulles (KIAD) | |||
You can obtain the models through [[TerraSync]]. | |||
== Contributing == | |||
=== Tips and advice for novices === | |||
Some days ago an user presented a livery for a model of a BK 117 helicopter in the forum. Looked great, really. Unfortunately the author of this helicopter model (and also of this text) decided to remake the 3D model already two years ago. He found more detailed drawings and errors on the 3D model. Due to real life the author didn't manage to finish it yet. But anyway - the uvmapping and with that liveries made for the old model will not work. And the author has already a 3D cockpit in the pipeline.... | |||
What does this teach us? | |||
The common saying "Release early, release often" in developing programs doesn't work all to good on artwork like aircraft models. Even small changes on the 3D model destroys UV-maps and already made textures. It doesn't make sense to publish an aircraft before main things are done. And it doesn't make sense to already work on liveries, textures and other things before fundamental things won't change anymore. A lot of time and energy is wasted due to such things. And of course it is quite disappointing when you notice that your hard work on a livery was useless, as it won't work anymore, because something changed..... | |||
So how to prevent this? | |||
As author you should publish your work when you are sure that it is ready enough for other people to contribute. No problem at all to publish the work on sourceforge.net, github.com etc. - but make clear when things are ready for contributions. | |||
As contributor you should be sure that an aircraft is ready for contributions. Unless it isn't explicitly mentioned you should ask the main author. It is not only polite, it is also very helpful to coordinate workloads. | |||
Usually you will find a ReadMe with all informations to contact the author. If not, the developers mailing-list, or a request in the forum might help. Maybe other users do know how to contact the main author. | |||
But accept that you might need some patience until you get an answer! Unlike developers for commercial sims like MSFS or X-Plane, the authors uses their spare time to create things. That means a whole lot of other stuff comes first: job, family, friends, other hobbies like sport. Or simply vacations. Neither should you think, that in such cases the aircraft is abandoned - the author simply may not have found the time to answer. | |||
And even if the aircraft is lacking things - the author might have it already in work and simply didn't published it - for the mentioned reasons above. | |||
So a better communication between author and contributor can help prevent disappointment and frustration on both sides. Keep the above in mind - it will help a lot! | |||
=== Translators required === | === Translators required === | ||
{| | {| | ||
| Line 59: | Line 116: | ||
==== Screenshot of the Month ==== | ==== Screenshot of the Month ==== | ||
FlightGear's screenshot of March 2016 is ''Departing from Barcelona-El Prat in the wonderful Cessna 182 Skylane'' by {{usr|Dg-505}} | |||
[[File:Cessna 182S at LEBL.jpg|900px|center]] | |||
[[Category:FlightGear Newsletter|2016 03]] | [[Category:FlightGear Newsletter|2016 03]] | ||
[[Category:Changes after 2016.1]] | [[Category:Changes after 2016.1]] | ||
[[de:FlightGear Newsletter März 2016]] | |||