... with different startup/runtime settings while running a profiler or even just while logging frame rate/frame spacing to disk, while replaying a fgtape file with different rendering/environmental settings. To exclude Nasal from the list of potential culprits, it would also be possible to patch ...

... was sliding with the wind: https://curl.irmp.ucl.ac.be/~chris/upload/spaceshuttle/iceland/fgfs-20201029131530.png I've made a video using the fgtape, and I spotted a few other weird things :-/ iceland.webm -The rear wheels are not really centered on their axis? (see around 1:38). Landing damage? ...

... use a handful of airports/runways and different environmental settings, and then batch-run these in FlightGear while creating a recorded flight (fgtape), possibly using time-warp mode - at that point, dozens or even hundreds of fgtapes could be created automatically, and then post-processed using ...

... take the full path. Instead it forms a path by taking the string specified, prepending the name of the tape directory and appending ".fgtape". [I have some changes in my local tree that omits this prepending and appending if the string already ends with ".fgtape", which ...

... https://i.imgur.com/uGA24QS.jpg Not sure if recording and performance hit from MSAA + overlays work well while flying, but maybe recording an fgtape or 720p/480p would work. 5z1 (Juneau Harbor) is in a good location with forests and access to glacier/icefield (manually tweaking snowline makes ...

Depending on your concrete requirements, there are a handful of primary means: ⋅  creating a custom fgtape: http://wiki.flightgear.org/Instant_Replay ⋅  using the external FDM mechanism: http://wiki.flightgear.org/Property_Tree/Sockets ⋅  feeding ...

... rate, frame spacing, osg stats) I would suggest to start with a really simple aircraft in a location without any scenery, and then record an fgtape that you can easily replay again with different combinations of settings. Once that is in place, you can easily try different draw masks / rendering ...

... of locations/aircraft and draw masks - i.e. would have the basic building blocks to build a simple benchmark using Nasal, just by replaying an fgtape file and toggling settings on/off while watching metrics like frame rate/spacing and number of drawable. CPU vs GPU Bound (split from other topic) ...

... It would actually be a neat little project to create different rendering profiles (say different , save those to an XML and then replay a few fgtape files while sampling performance metrics (frame rate, frame spacing) - this could be done with different draw masks set to enable/disable terrain/scenery ...

... to work out a way to create a suite of benchmarks, i.e. by taking certain aircraft (with different complexity) and fly/replay certain patterns (fgtape) while tinkering with different startup/runtime settings, otherwise conclusive statements simply cannot be made reliably. In a perfect world, ...

In terms of exporting off the top of my head the choices you'd have would be - fgtape mechanism - but thats more for saving flights and viewing them later - export via UDP protocol: http://wiki.flightgear.org/Generic_protocol - for JSBSim aircraft use the dedicated ...

once suitable baseline to start with would be an aircraft's set of bindings/multiplayer properties and flight recorder/fgtape config (instant replay).
This is again something where looking at Emesary (wiki) may pay off quickly, very quickly.

... of things in FlightGear that have to do with serialization/persistence of properties/data structures (think multiplayer, but also instant replay/fgtape). Also, Emesary is transport agnostic, so it would make sense to have a bridge for our existing SGSocket class, or at least the generic protocol ...

... you can use a combination of Linux shell tools to accomplish the same thing. There is also a dedicated logging/instant replay (flight recorder/fgtape) subsystem in FlightGear, it would be fairly simple to adapt that to make it MP/network aware.

... subsystems that mainly deal with properties for their input/output needs. Like I said, this applies to the property tree recorder subsystem (fgtape), but also things like AI traffic - to see how much of an impact these systems have on flightgear at runtime, you can simply disable/remove them ...