20,741
edits
FlightGear Newsletter March 2014: Difference between revisions
Jump to navigation
Jump to search
m
→Development news: http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/3973F5C2-F2DE-418D-8E39-22498E041C39%40mac.com/#msg32064386
m (→Development news: http://sourceforge.net/p/flightgear/mailman/flightgear-devel/thread/3973F5C2-F2DE-418D-8E39-22498E041C39%40mac.com/#msg32064386) |
|||
| Line 7: | Line 7: | ||
Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]]. | Note to all contributors: Please also copy your newsletter additions to the changelog for the upcoming release: [[Next Changelog]]. | ||
=== Reset & Reinit === | |||
Over the next few days James is going to start switching over the reset system to use the new code. The following changes will happen, in order: | |||
* places that only need to re-position will use the new ‘reposition' command, which is a simplified version of the current reset (and will become even simpler over time, but for now the goal is maximum compatibility). This means the 'select airport' and 'position in air' dialogs, principally. | |||
* the reset command will be switched to use the new logic, which is slightly slower than the current logic, but much more complete. It's very close to shutting down the simulator and re-starting; in particular Nasal is restarted, and it should be possible in the near future to toggle between Rembrandt and the classic renderer. (The only UI-path that triggers a reset its the actual menu command / key-shortcut - If anyone knows of some strange way we trigger a reset, please do let me know) | |||
* the "save / restore initial state" logic in globals will be removed, since it will no longer ever be used | |||
* Many properties which are flagged as 'preserved' or 'userarchive' need to be audited for correctness in the new system. This will be an iterative process, but James will try to address issues as quickly as possible. Unfortunately each time a fix in preferences.xml is made, testers will need to delete their auto-save file. This is the price of living on the bleeding edge :) | |||
James is not expecting any build failures since the code is already in Git, but I would ask that any bug-reports are only made /after/ wiping your autosave XML file. | |||
Continue reading at [[Reset & re-init]]... | |||
=== Random Buildings === | === Random Buildings === | ||