573
edits
FlightGear benchmark: Difference between revisions
Jump to navigation
Jump to search
m
→Objective: link update
No edit summary |
m (→Objective: link update) |
||
| Line 16: | Line 16: | ||
* The Nasal scripting interpreter is initialized pretty late because it has some hard-coded assumptions regarding available subsystem, OTOH it could be doing useful work if a restricted interpreter was available earlier, i.e. to help with simulator-reinitialization, see [[Initializing Nasal early]] | * The Nasal scripting interpreter is initialized pretty late because it has some hard-coded assumptions regarding available subsystem, OTOH it could be doing useful work if a restricted interpreter was available earlier, i.e. to help with simulator-reinitialization, see [[Initializing Nasal early]] | ||
Our hope is that we'll be able to come up with a simple benchmark suite to help users provide better troubleshooting reports, but also allow developers to do largely automated regression tests, i.e. through benchmarks or scripted flights. The recent advances in deferred rendering support ([[Rembrandt]]) also resulted in tons of GPU/GLSL related bug reports that are often hardware-specific and difficult to reproduce. Also see: [[ | Our hope is that we'll be able to come up with a simple benchmark suite to help users provide better troubleshooting reports, but also allow developers to do largely automated regression tests, i.e. through benchmarks or scripted flights. The recent advances in deferred rendering support ([[Rembrandt]]) also resulted in tons of GPU/GLSL related bug reports that are often hardware-specific and difficult to reproduce. Also see: [[Troubleshooting performance issues#A note from the developers]]. | ||
In the long run, the corresponding data could also help us to provide more reliable [[Hardware Recommendations]]. | In the long run, the corresponding data could also help us to provide more reliable [[Hardware Recommendations]]. | ||