Feature Requests / Proposals / Ideas: Difference between revisions

Add folder structure proposal
(Add folder structure proposal)
Line 132: Line 132:
* add support for automatically created scenery objects to populate the scenery dynamically at runtime (autogen-like), this could add quite a portion of realism to FlightGear without having to model scenery manually using fgsd, yet one could still use fgsd for areas where people are willing to contribute. All other scenery should by default be populated using autogen buildings and objects (references: http://www.infinitylab.com.au/research/prototypes.htm and http://vterrain.org/Culture/BldCity/procedural.html and http://pcity.sourceforge.net/ )
* add support for automatically created scenery objects to populate the scenery dynamically at runtime (autogen-like), this could add quite a portion of realism to FlightGear without having to model scenery manually using fgsd, yet one could still use fgsd for areas where people are willing to contribute. All other scenery should by default be populated using autogen buildings and objects (references: http://www.infinitylab.com.au/research/prototypes.htm and http://vterrain.org/Culture/BldCity/procedural.html and http://pcity.sourceforge.net/ )


== Proposals Post 1.0 ==  
== Proposals ==  


=== A New Architecture for FlightGear Flight Simulator ===
=== A New Architecture for FlightGear Flight Simulator ===
Line 146: Line 146:
'''Full document''': [http://www.cs.yorku.ca/~cs233144/Flightgear/new_FG_architecture.pdf A New Architecture for FlightGear Flight Simulator]
'''Full document''': [http://www.cs.yorku.ca/~cs233144/Flightgear/new_FG_architecture.pdf A New Architecture for FlightGear Flight Simulator]


=== Standard Aircraft Folder Structre ===
The majority of cleanly structured aircraft share a common folder layout:
* Models - for 3D models
* Panels  - for 2D/3D cockpit panels
* Instruments - for aircraft specific instruments (possibly with its own Textures subfolder)
* Sounds - for aircraft specific sounds
* Splashs - for aircraft specific splash screens
* FDMs - for various FDM configs that are supported
* Engines - for various different engines supported by the FDMs
* Systems  - for systems such as the electrical system
* Nasal - for aircraft specific Nasal scripts
* Docs - for aircraft specific documentation
* Huds - for aircraft specific HUDs
* Textures - for aircraft specific general Textures
* Liveries - for livery-specific textures
Additionally, all aircraft should have files such as the following included:
* README
* HELP
* FEATURES
* TODO
* AUTHORS
* CHANGELOG


== General Ideas ==
== General Ideas ==