20,741
edits
FlightGear 3.0 backlog: Difference between revisions
Jump to navigation
Jump to search
→Items
(→Items) |
|||
| Line 16: | Line 16: | ||
Please only add items that have a corresponding mentoring core developer, or items that have been marked as accepted in the issue tracker: https://code.google.com/p/flightgear-bugs/issues/list?can=2&q=FeatureRequest%20status%3Aaccepted | Please only add items that have a corresponding mentoring core developer, or items that have been marked as accepted in the issue tracker: https://code.google.com/p/flightgear-bugs/issues/list?can=2&q=FeatureRequest%20status%3Aaccepted | ||
=== Weather (Thorsten) === | |||
* lightfields and Rembrandt working together | |||
* lightfields properly supported by Basic Weather | |||
* a redesign of the weather interfaces, basically going to the unified weather | |||
system people have been talking about - some ideas and brainstorming urgently | |||
needed! | |||
Then some fixes for long-standing, not really critical but annoying bugs | |||
* <del>the current rain system still only works for Basic Weather</del> {{Done}} (by Stuart for 2.10) | |||
* turbulence should affect YaSim and JSBSim the same way | |||
Then maybe some cool, but not so important features to make things complete: | |||
* lightning (and thunder?) for thunderstorms | |||
* windsocks moving with ground wind rather than wind at aircraft position | |||
Ideally, making full use of things we already have to present the best possible | |||
scenery | |||
* regionalized random building types | |||
* dedicated texture packs for the main vegetation zones | |||
* exploit the placement mask possibilities fully | |||
And then, ship 3.0 with (finally) the next edition of a world scenery release, | |||
so we can really present much better visuals! So, personally I'd like 3.0 to be | |||
a release that doesn't only have cool features, but also cool features which | |||
work basically everywhere and a release that doesn't have the current snags | |||
like 'this doesn't work with that, and the GUI is counter-intuitive and so on. | |||
Let me be the first to admit that it's much more fun doing my own stuff the way | |||
I like and then just merge it in. But if we can find consensus about any plan | |||
having to do with integration of new features and making it all work together, | |||
then I'm willing to reserve the majority of my coding time for working towards | |||
that goal. Would this be something to aim for in a 3.0 release? | |||
== Related Pages == | == Related Pages == | ||