Obviously, FlightGear has drastically evolved since the early days of FGBenchmark, so lots of benchmarking metrics can now be gathered, even without touching the C++ source code and without using any external tools or introducing other platform-specific dependencies. Objective Note Based on recent experiments with benchmarking Rembrandt, it would obviously make sense to have access to individual stages (cameras)Ī long time ago, we once had a FG-specific benchmark suite called "FGBenchmark" over time this wasn't updated anylonger and got phased out- 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 etc) in order to gather runtime statistics, but also for better regression testing. 6.5 Extending the replay/flight recorder subsystems.FlightGear would very probably be featured in every Phoronix benchmarking article and those are very frequent. My personal situation will improve in about half a year, but if someone can pull this off before that, we'd not only get better support but also great marketing. If any developer finds some time to implement the missing pieces this could help tremendously. Combined with some static weather input and fixed random seeds (probably supplied on the command line) we'd have all we need for reproducible benchmarks. Using generic file input allows replaying a full flight and the telnet interface allows reading FPS and frame distance numbers. Setting FG_HOME to a temporary directoy ought to be enough to prevent leaking settings from one run to another and allows using specific settings for the benchmark run (e.g. I played around with the existing capabilities last weekend and it looks like we're almost there anyway. ![]() It's possible that this article hasn't been updated in a while, so to catch up with the latest developments, you are advised not to start working on anything directly related to this without first coordinating your ideas with fellow FlightGear contributors using the FlightGear developers mailing list or the FlightGear forums. Mentors: Hooray (get in touch to learn more) PropertyList XML File, Aircraft-set.xml, Property Tree, Nasal scripting, fgcommands, Nasal/Web scripting ![]() So if you'd like to help in one way or another, please get in touch or just help improve the article in the meantime! While this article is based on considerable community feedback, there's nobody working on this currently.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |