Changelog 3.4: Difference between revisions
(Firewall exceptions added during setup) |
|||
Line 23: | Line 23: | ||
=== Breaking Changes === | === Breaking Changes === | ||
{{FGCquote | |||
|the rendering logic for AI aircraft has changed recently. If they are drawn depends on the projected size on the screen and not on their distance.<br/> | |||
Please check the properties | |||
* /sim/rendering/static-lod/ai-range-model-pixel (should be true) | |||
* /sim/rendering/static-lod/ai-detailed (should be 30) | |||
With this configuration, AI aircraft bigger than 30pixels on the screen should show up. | |||
There are other factors in OpenSceneGraph that decide if the Paged LOD nodes get rendered. It may sometimes take a couple of minutes or some view panning for the models to pop up. | |||
|{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33271362/ | |||
|title=<nowiki>Re: [Flightgear-devel] Flightgear next (3.5.0) Does not render MP | |||
aircraft</nowiki> | |||
|author=<nowiki>Torsten Dreyer</nowiki> | |||
|date=<nowiki>2015-01-26</nowiki> | |||
}} | |||
}} | |||
=== Major enhancements in this release === | === Major enhancements in this release === |
Revision as of 16:54, 11 February 2015
This changelog is a draft.
This changelog is currently being written for the FlightGear 3.4 release. To see what is being worked on, check out Changelog 3.4.
Feel free to help! If you are aware of any FlightGear related changes, please add them to the changelog.
|
Upcoming FlightGear Changelog
Breaking Changes
the rendering logic for AI aircraft has changed recently. If they are drawn depends on the projected size on the screen and not on their distance. Please check the properties
With this configuration, AI aircraft bigger than 30pixels on the screen should show up. There are other factors in OpenSceneGraph that decide if the Paged LOD nodes get rendered. It may sometimes take a couple of minutes or some view panning for the models to pop up. — Torsten Dreyer (2015-01-26). Re: [Flightgear-devel] Flightgear next (3.5.0) Does not render MP
aircraft.
(powered by Instant-Cquotes) |
Major enhancements in this release
Core
I have just pushed a partial fix for the issue to SimGear. The event now uses property polling instead of attaching listeners to — Torsten Dreyer (2014-08-29). Re: [Flightgear-devel] crash in SGPropertyNode::fireValueChanged.
(powered by Instant-Cquotes) |
As a side effect, I have noticed that the load for the xml-property rule subsystem has decreased on my system — Torsten Dreyer (2014-08-29). Re: [Flightgear-devel] crash in SGPropertyNode::fireValueChanged.
(powered by Instant-Cquotes) |
Aircraft modelling
JSBSim
Graphics
Performance
Usability
Scenery
Canvas system
FlightGear's fully scriptable 2D rendering system now includes improved APIs for creating maps and navigation displays amongst many other improvements. People no longer need to have programming experience to add a working ND to their aircraft, it can now be all done by copying and pasting 30 lines of text and customizing a few properties. The so called MapStructure back-end handles efficient updating of all ND layers transparently. Also, maps can now be mostly customized, including custom styling (colors, fonts, symbols etc).
- Nasal namespace Browser
- MapStructure is being ported to become a native Canvas Widget
- work has begun to port the airport selection dialog to use the MapStructure framework
- Tom has implemented keyboard handling support
- Text/Input field support
- Input dialog
Nasal scripting
Documentation
Highlighted new and improved aircraft
Other
- Firewall exceptions are automatically added during setup on Windows systems
- Aircraft moved to a SVN repository.
Bug fixes
- See our bugtracker for an extensive, yet incomplete, list of the bugs fixed in this release.