20,741
edits
FlightGear Newsletter September 2012: Difference between revisions
Jump to navigation
Jump to search
FlightGear Newsletter September 2012 (view source)
Revision as of 11:56, 19 September 2012
, 19 September 2012→Project Rembrandt: navcache: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38330.html
(→Project Rembrandt: navcache: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38330.html) |
|||
| Line 13: | Line 13: | ||
This was a side-effect of the way in which the buildings were created during tile loading. Stuart has now completely changed the way in which random buildings are generated and displayed to reduce the memory occupancy by using a shader-based scheme similar to random trees. You should now see significantly lower memory occupancy (500 - 2GB less depending on area and density) when running with random buildings enabled. | This was a side-effect of the way in which the buildings were created during tile loading. Stuart has now completely changed the way in which random buildings are generated and displayed to reduce the memory occupancy by using a shader-based scheme similar to random trees. You should now see significantly lower memory occupancy (500 - 2GB less depending on area and density) when running with random buildings enabled. | ||
=== NavCache === | |||
James has pushed a large change to next, which adds a binary cache of most of the navigation data. The cache is stored in FG_HOME/navdata.cache, and rebuilt if the timestamps on any of the data files change (apt.dat, nav.data, fix.dat and so on). When the cache needs to be rebuilt, startup will take a bit longer than before, but when the cache is valid, startup is /much/ faster, especially for debug builds. | |||
Memory consumption is also lower, since we don't keep airports / fixes / taxiways / runways in memory until they're needed. | |||
This is a fairly large change, so please look out for any bugs related to navaids / startup position / GPS / route-manager searches and lookups either getting different results or failing. I've tested here locally and things seem | |||
sane, and have had positive feedback from various testers on IRC and email, but I still expect to find some edge cases which need further work. | |||
There's future work to move even more data into the cache - eg parking positions - which will further help performance for FMS / map systems since we won't need to parse lots of XML data repeatedly. I'm going to let this change settle down before adding more cached data, however. | |||
=== Project Rembrandt === | === Project Rembrandt === | ||
=== Canvas System === | === Canvas System === | ||
<!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --> | <!--additions should also be added to:http://wiki.flightgear.org/Changelog_3.0.0#Some_of_the_major_changes_include: --> | ||