Feature Requests / Proposals / Ideas: Difference between revisions

Jump to navigation Jump to search

Feature Requests / Proposals / Ideas (view source)

Revision as of 00:33, 19 August 2006

1,416 bytes removed ,  19 August 2006
Moved section "Standard Aircraft Folder Structure" from the wish-list to the Aircraft Development page.
(Moved the technical report out of this wish-list.)
(Moved section "Standard Aircraft Folder Structure" from the wish-list to the Aircraft Development page.)
Line 133: Line 133:
* 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 ==


=== Standard Aircraft Folder Structure ===
The majority of cleanly structured aircraft share a common folder layout:
* Models - for 3D models
* Panels  - for 2D/3D cockpit panels (maybe categorized into 2D/3D?)
* 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
* Views - for aircraft-specific views
* Resources - for all sorts of aircraft specific development resources that may be required by other developers to continue development of an aircraft (i.e. data, images, artwork etc) but that isn't officially included in any of the other folders because it isn't yet used. That is, such "resource" folders could/should be automatically excluded from the script that is currently used to create the default base package for distribution.
Additionally, all aircraft should have files such as the following included:
* README
* HELP
* FEATURES
* TODO
* AUTHORS
* CHANGELOG


== General Ideas ==
== General Ideas ==
Ampere
356

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/2783"

Navigation menu