2,561
edits
Feature Requests / Proposals / Ideas: Difference between revisions
Jump to navigation
Jump to search
m
Feature Requests / Proposals / Ideas (view source)
Revision as of 09:44, 23 January 2008
, 23 January 2008adding random tree reference to related RFE
m (→Interactivity) |
m (adding random tree reference to related RFE) |
||
| Line 206: | Line 206: | ||
* texture cropping support for 2D panels (see mailing list archives for discussions) | * texture cropping support for 2D panels (see mailing list archives for discussions) | ||
* <strike>add support for enhanced water modeling, so that we can start implementing water aircraft with floats etc.</strike>-'''in progress as of 11/2007''' | * <strike>add support for enhanced water modeling, so that we can start implementing water aircraft with floats etc.</strike>-'''in progress as of 11/2007''' | ||
* when aircraft are very low, the terrain/scenery looks only rarely convincing due to the fact that flat textures are applied to surfaces in order to illustrate vegetation, however this works only properly for higher altitudes, so it would be desirable if we could add support for dynamic vegetation modeling, so that grass, trees and other plants are dynamically created within a certain proximity. | * when aircraft are very low, the terrain/scenery looks only rarely convincing due to the fact that flat textures are applied to surfaces in order to illustrate vegetation, however this works only properly for higher altitudes, so it would be desirable if we could add support for dynamic vegetation modeling, so that grass, trees and other plants are dynamically created within a certain proximity. (NOTE: [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15388.html this is currently (01/2008) being tackled]) | ||
* the navdb should eventually become a true SGSubsystem, it needs some serious revamping. | * the navdb should eventually become a true SGSubsystem, it needs some serious revamping. | ||
* basically all subsystems should be fully "suspend-able" and "reinit-able" at runtime, there are currently various subsystems that will consume CPU cycles even though they are not in fact necessarily required, affecting FlightGear's performance negatively. This is particularly the case for non-SGSubsystem based systems. | * basically all subsystems should be fully "suspend-able" and "reinit-able" at runtime, there are currently various subsystems that will consume CPU cycles even though they are not in fact necessarily required, affecting FlightGear's performance negatively. This is particularly the case for non-SGSubsystem based systems. | ||