Talk:FlightGear and old hardware
Jump to navigation
Jump to search
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:
- 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)
- scripting (via Nasal)
- headless/console only (i.e. for processing CLI arguments, XML parsing, config files etc)
- networking
- telnet
- httpd
- generic protocol
- multiplayer
- FDM
- Autopilot
- Route Manager
- Sound (requires OpenAL)
- Sound Effects
- AI sounds
- Scenery sounds
- GUI
- Canvas
- multiple windows
- Scenery
- FDM (terrain/tile manager)
- Effects & Shaders (requires GLSL)
- input (keyboard/mouse, joystick, gaming hardware)