Changelog 2016.4: Difference between revisions

Jump to navigation Jump to search
3,613 bytes removed ,  20 November 2016
Cleanup
(→‎Misc/Uncategorized: Add references regarding the reintroduction of ATC chatter)
(Cleanup)
Line 1: Line 1:
{{Changelog Draft|version=2016.4}}
{{Changelog Draft|version=2016.4}}


<!--
The FlightGear development team is delighted to announce the v2016.4 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include C++11 Support, support for airport data files within scenery folders, a highly-detailed Space Shuttle model and much more.
The FlightGear development team is delighted to announce the v2016.4 release of FlightGear, the free, open-source flight simulator. This new version contains many exciting new features, enhancements and bugfixes. Highlights in this release include C++11 Support, support for airport data files within scenery folders, high fidelity Space Shuttle model and much more.


Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.
Founded in 1997, FlightGear is developed by a worldwide group of volunteers, brought together by a shared ambition to create the most realistic flight simulator possible that is free to use, modify and distribute. FlightGear is used all over the world by desktop flight simulator enthusiasts, for research in universities and for interactive exhibits in museums.
Line 11: Line 10:


FlightGear - Fly Free!
FlightGear - Fly Free!
-->


== Major enhancements in this release ==
== Major enhancements in this release ==
=== Core ===
=== Core ===
 
* FlightGear is migrating to C++11. Those of you who compile FlightGear yourself might find nasty compilation errors. In any case, ask on our mailing list!
* '''The migration to C++11'''
FlightGear is migrating to C++11. Those of you who compile FlightGear yourself might find nasty compilation errors. In any case, Ask on our mailing list!


=== Aircraft Modeling ===
=== Aircraft Modeling ===
Line 24: Line 20:


=== Atmospheric Light Scattering ===
=== Atmospheric Light Scattering ===
* the [https://forum.flightgear.org/viewtopic.php?f=47&amp;t=28201&amp;p=271916#p271916 automated moonlight and moon position code] has been pushed and will be a part of the 2016.4.1 release.<ref>{{cite web
* Moonlight and moon positioning code under [[ALS]] has been improved.<ref>{{cite web
  |url    = https://forum.flightgear.org/viewtopic.php?p=298343#p298343  
|url    = https://forum.flightgear.org/viewtopic.php?p=298343#p298343
  |title  = <nowiki> Re: Implementing moonlight (or not) </nowiki>
|title  = Re: Implementing moonlight (or not)
  |author = <nowiki> bugman </nowiki>
|author = bugman
  |date  = Nov 8th, 2016  
|date  = Nov 8th, 2016
  |added  = Nov 8th, 2016  
|added  = Nov 8th, 2016
  |script_version = 0.40  
|script_version = 0.40
  }}</ref>, this only works for those ALS shaders that Thorsten added /environment/moonlight ambient lighting support for.  There is no automated full-scene lighting, and nothing visible under the default or Rembrandt renderers.  But if you have ALS on, you should see realistic moon-phase based lighting for a lot of the scene.<ref>{{cite web
}}</ref>
  |url    =  https://forum.flightgear.org/viewtopic.php?p=298365#p298365
  |title  =  <nowiki> Re: Implementing moonlight (or not) </nowiki>
  |author =  <nowiki> bugman </nowiki>
  |date  =  Nov 8th, 2016
  |added  =  Nov 8th, 2016
  |script_version = 0.40
  }}</ref>


=== Environment Rendering ===
=== Environment Rendering ===
Line 45: Line 34:


=== Misc/Uncategorized ===
=== Misc/Uncategorized ===
* [[FGRun]] is removed from the Windows release ({{fgmeta commit|131377}}).
* [[FGRun]] has been removed from the Windows release ({{fgmeta commit|131377|t=commit}}).
* ''TODO: Remote Canvas display via Phi''
* ATC Chatter has been re-introduced.<ref>{{cite web
* ATC Chatter has been re-introduced.<ref>{{cite web
  |url    = https://sourceforge.net/p/flightgear/mailman/message/35388063/
|url    = https://sourceforge.net/p/flightgear/mailman/message/35388063/
  |title  = <nowiki> [Flightgear-devel] ATC Chatter revived </nowiki>  
|title  = <nowiki>[Flightgear-devel] ATC Chatter revived</nowiki>
  |author = <nowiki> Torsten Dreyer </nowiki>
|author = Torsten Dreyer
  |date  = Sept 23, 2016
|date  = Sept 23, 2016
  }}</ref> See [https://sourceforge.net/p/flightgear/fgaddon/HEAD/tree/trunk/Addons/ATCChatter/ Addons/ATCChatter/README] in [[FGAddon]] for instructions explaining how to enable it.
}}</ref>. See {{fgaddon source|Addons/ATCChatter/README|t=here}} for instructions.


=== Usability ===
=== Usability ===
Line 59: Line 47:


=== Scenery ===
=== Scenery ===
* '''new [[File_Formats#.2A.stg_files|STG verbs]] '''<ref>https://forum.flightgear.org/viewtopic.php?f=5&t=22809&p=295366#p295342</ref>
* New [[File Formats#.2A.stg files|STG verbs]] added<ref>{{cite web
* '''Support for apt.dat files inside scenery folders''' For years, FlightGear has been reading a large file called apt.dat.gz and located in [[$FG_ROOT]]/Airports. This file, which is maintained in collaboration with the X-Plane developers and users<ref>Via [[WorldEditor]] and the [https://gateway.x-plane.com/ X-Plane Scenery Gateway].</ref>, contains a lot of information about airports (names and geometry of runways, taxiways, aprons, surface type, position of runway thresholds, light beacons, position of Control Tower, communication frequencies... even startup locations, though FlightGear reads parking positions from other files called ''airportID''.groundnet.xml). Data from this file is used to create the scenery files for airports (.btg.gz), to display airports in the FlightGear built-in map, as well as to let the simulator know how to place your aircraft when starting on a runway—among others.
|url    = https://forum.flightgear.org/viewtopic.php?p=295342#p295342
 
|title  = Re: osm2city.py development
: Despite the possibility to have FlightGear read portions of the scenery from various folders (cf. [[$FG_SCENERY]]), this data was only read so far from this one file, [[$FG_ROOT]]/Airports/apt.dat.gz. As a consequence, custom sceneries could not bring new or updated airport layouts without FlightGear having part or all of the information wrong concerning these airports, since it was read from a file that is maintained independently from said custom sceneries—and tied to FlightGear's current World Scenery, and therefore frozen in FlightGear since 2013.
|author = stuart
 
|date  = Sep 23rd, 2016
: This problem is solved in FlightGear 2016.4,<ref>{{cite web
}}</ref>
  |url    = https://sourceforge.net/p/flightgear/mailman/message/35424973/
* Support for apt.dat files inside scenery folders.<ref>{{cite web
  |title  = <nowiki> Re: [Flightgear-devel] Reading apt.dat files from scenery paths
|url    = https://forum.flightgear.org/viewtopic.php?p=296919#p296919
[was: apt.dat - add local version ?] </nowiki>
|title  = apt.dat - local version(s)
  |author = <nowiki> Florent Rougon </nowiki>
|author = Alant
  |date  = Oct 13th, 2016
|date  = Oct 18th, 2016
  |added  =  Oct 13th, 2016  
}}</ref> See [[FlightGear Newsletter October 2016#Local apt.dat versions support|here]].
  |script_version = 0.40
  }}</ref> which reads files following the pattern NavData/apt/*.dat or NavData/apt/*.dat.gz inside each scenery path, when they exist. These files, collectively called ''apt.dat files'', should have the same syntax as [[$FG_ROOT]]/Airports/apt.dat.gz, and are the natural output of [[WorldEditor]], the recommended tool to create or update airport layouts. With this change, each custom scenery can now embed its own apt.dat files that describe the airports shipped in the custom scenery; FlightGear 2016.4 and later will read them.
 
: The precedence order for these files is the same as for [[$FG_SCENERY]]: if the same airport appears in several apt.dat files, only the first definition found in $FG_SCENERY order is used.<ref>And for apt.dat files belonging to the same component of [[$FG_SCENERY]], the first file in lexicographic order takes precedence, although in practice this rule shouldn't be needed (why ship several definitions for the same airport inside a given [[$FG_SCENERY]] component?).</ref> Finally, for compatibility with existing scenery and as a fallback measure, the traditional [[$FG_ROOT]]/Airports/apt.dat.gz file is still read by FlightGear, with lowest precedence.


=== Canvas System ===
=== Canvas System ===


=== Nasal Scripting ===
=== Nasal Scripting ===
<code>--allow-nasal-read</code> option added


=== Documentation ===
=== Documentation ===


=== Highlighted new and improved aircraft ===
=== Highlighted new and improved aircraft ===
* '''Milestone 7 of the Space Shuttle'''
* Milestone 7 of the Space Shuttle has been released, with more impressive detail than ever before. Download it from [[FGAddon]]. Read more in the [[FlightGear Newsletter November 2016#Milestone 7 of the Space Shuttle|Newsletter]].
The Space Shuttle is now complete with more impressive detail than before. Download it in FGAddon.
 
Read more in the [[FlightGear Newsletter November 2016#Milestone 7 of the Space Shuttle|Newsletter]].


=== Other ===
=== Other ===
* Support for GoFlight EFIS and TQ6
* Support for GoFlight EFIS and TQ6 added


=== Bug fixes ===
=== Bug fixes ===
* See [https://sourceforge.net/p/flightgear/codetickets/search/?q=status%3AFixed+AND+created_date%3A%5B2016-09-08T08%3A05%3A07Z+TO+*%5D our bugtracker] for a list, albeit incomplete, of the bugs fixed in this release.
* See [https://sourceforge.net/p/flightgear/codetickets/search/?q=status%3AFixed+AND+created_date%3A%5B2016-09-08T08%3A05%3A07Z+TO+2016-11-17T18%3A27%3A17Z%5D our bugtracker] for a list, albeit incomplete, of the bugs fixed in this release.


== References ==
== References ==

Navigation menu