Changelog 3.2: Difference between revisions

1,193 bytes added ,  12 October 2014
(remove terrain simplifier stuff)
Line 36: Line 36:
* [[Reset & re-init]] is merged and now enabled
* [[Reset & re-init]] is merged and now enabled
* A segfault related to scripted Nasal fgcommands (like used in joystick and other bindings) has been fixed {{Issue|1397}}
* A segfault related to scripted Nasal fgcommands (like used in joystick and other bindings) has been fixed {{Issue|1397}}
* YASim versioning support for maintenance fixes (TorstenD)
* YASim now has versioning support. The YASim FDM now checks a version tag in it's configuration file to eventually provide backward compatibility.
* FLITE TTS support
* A text-to-speech system based on flite+hts_engine has been implemented.
* ATIS messages, previously hard coded in C++, are now generated based on customizable XML configuration files. Their audio now gets generated by the new text-to-speech system.
* Windows dependencies have been updated
* Windows dependencies have been updated
* The integrated [[Map]] dialog now uses an azimuthal equidistant projection, for better representation in polar regions and across the International Date Line.
* The integrated [[Map]] dialog now uses an azimuthal equidistant projection, for better representation in polar regions and across the International Date Line.
* A new internal web server (aka httpd) based on mongoose httpd has been added. It supports various AJAX requests, a screenshot server, a property tree browser and much more.
* A web browser based moving map has been added using the new AJAX capabilities of FlightGear


'''Aircraft Modeling'''
'''Aircraft Modeling'''
Line 69: Line 72:


'''Performance'''
'''Performance'''
As a side effect of a fixed bug, a huge performance boost with respect to frame rate can be seen on some machines. The implementation of a Uniform-Cache for shader-effects has reduced the CPU workload significantly.




Line 140: Line 144:


'''Bug fixes'''
'''Bug fixes'''
A serious bug has prevented FlightGear version 3.2 being released on time. Identified by the clumsy name "crash in SGPropertyNode::fireValueChanged", this bug clearly was a release blocker and it took a lot of effort to identify the cause for the crash. Finding a solution was even harder but was finally accomplished and presented the nice side-effect of a noticeable performance boost.
* See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D3.2 our bugtracker] for an extensive, yet incomplete, list of the bugs fixed in this release.
* See [http://code.google.com/p/flightgear-bugs/issues/list?can=1&q=Milestone%3D3.2 our bugtracker] for an extensive, yet incomplete, list of the bugs fixed in this release.


[[Category:FlightGear changelogs]]
[[Category:FlightGear changelogs]]