From: Durk T. <d.t...@xs...> - 2006-03-09 21:30:45
|
On Thursday 09 March 2006 17:59, Curtis L. Olson wrote: > I would like to start working agressively towards the next FlightGear > release which will be called v0.9.10 (putting off the v1.0 release for > at least one more cycle.) We have quite a few important features and > aircraft added since the last release so I think it would be good to get > a new release out the door. > > I don't have a specific schedule worked out yet, but I think my target > will be the end of March or first week in April. That will give us a > week to panic and discuss and lob heated accusations at each other, :-) > then a week or two to test and bug fix, and then we can do the official > release. > Sounds good to me. It might be interesting to know that David Luff has been mentioning a release of Taxidraw at around the same time. In addition, together with a lot of help from Innis Cunningham and others, I'm working toward releasing a major set of AI Aircraft (in various repaints), which I also hope to have available around early April. Unfortunately, I don't think, I'll have a working traffic editor by then. I still have the following issues on my TODO list: - Catch the bogus lon/lat FATAL ERROR in the tile loader thread following a failed AIModel load. Note that this error occurs only when a non existing model is attemted to be loaded before any tiles are loaded. - Investigate whether commenting out all entries in data/Traffic results in an unknown error exception - Prevent non-existing aircraft models from being loaded in the traffic manager at all. - Allow users to enable the traffic manager through the command line - Allow dynamic runtime enabling/disabling of the traffic manager - Investigate whether the time-related command line options are still working properly Cheers, Durk |