20,741
edits
Howto:Improve framerates: Difference between revisions
Jump to navigation
Jump to search
m
→Analyzing lag properly (frame spacing and worst case latency)
mNo edit summary |
|||
| Line 16: | Line 16: | ||
== Analyzing lag properly (frame spacing and worst case latency) == | == Analyzing lag properly (frame spacing and worst case latency) == | ||
In FlightGear => 2.60, use the menu option Debug => Monitor System Performance to analyze stutters. | |||
In a perfect world, min/max/mean values should be almost identical for every subsystem - and standard deviation should be almost 0. Larger differences / high standard deviations result in a sloppy simulation and stuttering movements, though they'll hardly influence the frames-per-second value at all. | In a perfect world, min/max/mean values should be almost identical for every subsystem - and standard deviation should be almost 0. Larger differences / high standard deviations result in a sloppy simulation and stuttering movements, though they'll hardly influence the frames-per-second value at all. | ||