20,741
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
m
→Objective
No edit summary |
m (→Objective) |
||
| Line 6: | Line 6: | ||
* the fgfsrs, autosave.xml preferences.xml files are user-specific and cannot currently be overridden by a benchmark, to ensure that a 100% correct setup is replicated | * the fgfsrs, autosave.xml preferences.xml files are user-specific and cannot currently be overridden by a benchmark, to ensure that a 100% correct setup is replicated | ||
* FlightGear expects an aircraft to be selected at startup, so that benchmarks could only be self-contained if they're are provided as a custom set of aircraft-set.xml files for, simply because we cannot yet switch aircraft at runtime | * FlightGear expects an aircraft to be selected at startup, so that benchmarks could only be self-contained if they're are provided as a custom set of aircraft-set.xml files for, simply because [[FlightGear Sessions|we cannot yet switch aircraft at runtime]] | ||
* 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 while running FlightGear, 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 while running FlightGear, 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 | ||
== Background == | == Background == | ||