Talk:FlightGear and old hardware

feature scaling vs. run-levels

We could support different run-levels, where certain features need to be available in order for the run-level to be initialized, and lack of certain features would mean that certain run-levels/operating modes would be n/a (this may comprise a single-threaded vs. multi-threaded mode for better debugging/troubleshooting, where SGThread-based components would be registered as a conventional SGSubsystem running inside the main loop). For example:

1. NavDB Cache (registered early-on, to be available for CLI processing, i.e. all the navaid/airport handling logic could be delegated to Nasal space)
2. scripting (via Nasal)
3. headless/console only (i.e. for processing CLI arguments, XML parsing, config files etc)
4. networking
   1. telnet
   2. httpd
   3. generic protocol
   4. multiplayer
5. FDM
   1. Autopilot
   2. Route Manager
6. Sound (requires OpenAL)
   1. Sound Effects
   2. AI sounds
   3. Scenery sounds
7. GUI
   1. Canvas
   2. multiple windows
8. Scenery
   1. FDM (terrain/tile manager)
9. Effects & Shaders (requires GLSL)
10. input (keyboard/mouse, joystick, gaming hardware)