20,741
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 1: | Line 1: | ||
== Objective == | |||
A long time ago, we once had a FG-specific benchmark suite called "FGBenchmark" - meanwhile, a number of end-users and long-term contributors have been talking about re-introducing a form of scriptable benchmark, directly as part of FlightGear itself, using [[Nasal]] scripting to recreate certain situations (location, aircraft, rendering settings) in order to gather runtime statistics, but also for better regression testing. | |||
FlightGear has drastically evolved since the early days of FGBenchmark, so that many of these things could now be accomplished, even without touching the C++ source code. The technical main restrictions at the moment are: | |||
* 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 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 | |||
== Background == | == Background == | ||