20,741
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
→Objective
| Line 9: | Line 9: | ||
* FlightGear always expects a fully interactive GUI session to be running, see [[FlightGear Headless]] | * FlightGear always expects a fully interactive GUI session to be running, see [[FlightGear Headless]] | ||
* Many settings are runtime-configurable and can be changed through the property tree (or fgcommands) while running FlightGear, some others still require a [[Reset & re-init|full simulator reset]] - this applies in particular to [[FlightGear Run Levels|non-optional subsystems]] but also a bunch of rendering related settings | * Many settings are runtime-configurable and can be changed through the property tree (or fgcommands) while running FlightGear, some others still require a [[Reset & re-init|full simulator reset]] - this applies in particular to [[FlightGear Run Levels|non-optional subsystems]] but also a bunch of rendering related settings | ||
* The Nasal scripting interpreter is initialized pretty late because it has some hard-coded assumptions regarding available subsystem, OTOH it could be doing useful work if it was available earlier, i.e. to help with simulator-reinitialization, see [[Initializing Nasal early]] | |||
Our hope is that we'll be able to come up with a simple benchmark suite to help users provide better troubleshooting reports, but also allow developers to do largely automated regression tests, i.e. through benchmarks or scripted flights. | Our hope is that we'll be able to come up with a simple benchmark suite to help users provide better troubleshooting reports, but also allow developers to do largely automated regression tests, i.e. through benchmarks or scripted flights. | ||