FlightGear Newsletter April 2014: Difference between revisions

Jump to navigation Jump to search
m
→‎Development news: http://forum.flightgear.org/viewtopic.php?f=6&t=22598
(→‎YASim Bug Fixes: big announcement, please feel free to edit!)
m (→‎Development news: http://forum.flightgear.org/viewtopic.php?f=6&t=22598)
Line 24: Line 24:
Continue reading at [[TerraGear scenery build server]]...
Continue reading at [[TerraGear scenery build server]]...


=== Helicopter Missions ===
{{WIP}}
{{#ev:youtube|yWEyRVGJks0}}
Continue reading at [http://forum.flightgear.org/viewtopic.php?f=6&t=22598 "Mission" for helicopters]...
=== YASim Bug Fixes ===
=== YASim Bug Fixes ===
As of April 4th, several bug fixes by Colin Howell have been merged into the "next" branch of FlightGear's source. As per issues {{issue|1400|}}, {{issue|1423|}}, and {{issue|1427|}}, these are only small fixes in portions of code, but they still may have noticeable affects on YASim aircraft, including making the solver fail with some aircraft and making other aircraft perform better. Currently these fixes are loaded unconditionally, so there's no opt-in or opt-out system in place, meaning that we need ''you'' to help test as many YASim aircraft as possible. (Please note that these patches are only available with a latest binary, i.e. a nightly from Jenkins or a compilation from source, and a corresponding FGData clone.) Detlef posts, "I have tested the slat patch and the twist patch and found very little problems, in fact most cases I've seen saw an improvment. Of the 15 Aircraft I've tested the twist patch on, only two wouldn't start up at all" [http://forum.flightgear.org/viewtopic.php?f=49&t=22522#p204370]. Having a large number of non-working aircraft in the next release would be undesirable, and would suggest that we need an opt-in system for such fixes, but if most aircraft work well it will be simpler to let the patches load unconditionally.
As of April 4th, several bug fixes by Colin Howell have been merged into the "next" branch of FlightGear's source. As per issues {{issue|1400|}}, {{issue|1423|}}, and {{issue|1427|}}, these are only small fixes in portions of code, but they still may have noticeable affects on YASim aircraft, including making the solver fail with some aircraft and making other aircraft perform better. Currently these fixes are loaded unconditionally, so there's no opt-in or opt-out system in place, meaning that we need ''you'' to help test as many YASim aircraft as possible. (Please note that these patches are only available with a latest binary, i.e. a nightly from Jenkins or a compilation from source, and a corresponding FGData clone.) Detlef posts, "I have tested the slat patch and the twist patch and found very little problems, in fact most cases I've seen saw an improvment. Of the 15 Aircraft I've tested the twist patch on, only two wouldn't start up at all" [http://forum.flightgear.org/viewtopic.php?f=49&t=22522#p204370]. Having a large number of non-working aircraft in the next release would be undesirable, and would suggest that we need an opt-in system for such fixes, but if most aircraft work well it will be simpler to let the patches load unconditionally.

Navigation menu