20,741
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
→Purpose
| Line 53: | Line 53: | ||
* Several people mentioned that they would like to have some form of "benchmark" to run FlightGear on various different platforms to see how it performs.I think the idea is not that bad, and that this might actually help troubleshoot some issues. Also, I do think that such a benchmark could probably be implemented directly in FlightGear, just by using Nasal scripting and some custom XML files. This would be pretty much related to the idea of "feature scaling" which was discussed in the other thread. [http://flightgear.org/forums/viewtopic.php?f=6&t=7806#p75962] | * Several people mentioned that they would like to have some form of "benchmark" to run FlightGear on various different platforms to see how it performs.I think the idea is not that bad, and that this might actually help troubleshoot some issues. Also, I do think that such a benchmark could probably be implemented directly in FlightGear, just by using Nasal scripting and some custom XML files. This would be pretty much related to the idea of "feature scaling" which was discussed in the other thread. [http://flightgear.org/forums/viewtopic.php?f=6&t=7806#p75962] | ||
* having a number of benchmarks available could probably provide useful metrics to get FlightGear to run. For example, even the very simple file that I posted can already be used for troubleshooting: if a user is not able to run this with more than 100 fps, he is unlikely to be able to run FlightGear with default settings. | * having a number of benchmarks available could probably provide useful metrics to get FlightGear to run. For example, even the very simple file that I posted can already be used for troubleshooting: if a user is not able to run this with more than 100 fps, he is unlikely to be able to run FlightGear with default settings. | ||
=== Regression Tests === | |||
Troubleshooting bug reports is often extremely tedious, because we need to replicate lots of settings: | |||
* "What's the highest shader level, at which random buildings still work? Or the lowest at which they fail?" [http://flightgear.org/forums/viewtopic.php?f=68&t=18924&hilit=recorder#p175577] | |||
* we should add a menu item to dump the current position and all rendering/environment settings to an XML file, so that we can more easily reproduce such things, just by loading a config from a file. [http://flightgear.org/forums/viewtopic.php?f=68&t=18924&hilit=recorder&start=15#p176017] | |||
* hat's a super idea! It wouldn't surprise me if some of these glitches are peculiar to specific hardware configurations, either, so perhaps that might be part of the report as well. I'll paste XML into forum posts all day if it helps the devs fix bugs. [http://flightgear.org/forums/viewtopic.php?f=68&t=18924&hilit=recorder&start=15#p176023] | |||
* even just knowing that certain issues only occur with some GPUs would be VERY good to know. But obviously we would need a sane way to easily reproduce a certain configuration, including all startup settings, but also the runtime rendering settings. [http://flightgear.org/forums/viewtopic.php?f=68&t=18924&hilit=recorder&start=30#p176025] | |||
* After all, having an easy way to reproduce a certain configuration, could save us tons of time and question asking - so having such a feature would be really invaluable in my opinion. We could add a dialog so that people could even describe the problem - so that the XML files would become self-contained and could be easily checked by different people without having to ask tons of tedious questions... Thinking about it, the simplest option would seem to be using existing stuff. After all, this is just about recording and replaying properties. And that's exactly what the new flight recorder (replay tapes) system does. So we could simply abuse it a little to also provide a configuration to sample the various rendering properties (see rendering dialog), which should give us a way to reproduce settings fairly well. [http://flightgear.org/forums/viewtopic.php?f=68&t=18924&hilit=recorder&start=30#p176025] | |||
=== Aircraft-set.xml based benchmarks === | === Aircraft-set.xml based benchmarks === | ||