20,741
edits
mNo edit summary |
|||
Line 5: | Line 5: | ||
In FlightGear >= 2.6.0, use the menu option '''Debug''' => '''Monitor System Performance''' to analyze stutters. | In FlightGear >= 2.6.0, 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 | In a perfect world, min/max/mean values should be almost identical for every subsystem - and standard deviation should be almost 0. | ||
Also, imagine a system producing 100 frames in 0.5 seconds, then blocking completely for another 0.5 seconds | 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. | ||
Also, imagine a system producing 100 frames in 0.5 seconds, then blocking completely for another 0.5 seconds: | |||
The fps display would still show "100fps", which seems great. But the 0.5 second stutter cause the visual performance to be terrible. | |||
That's why it is preferable to display "(worst-case) frame spacing" instead of fps (View => Display Options => Show frame spacing). The frame spacing for the previous example would show "500ms", while a system producing 100 frames with perfectly even spacing would show "10ms". | |||
So, frame spacing is a much better property to judge visual quality than just watching fps. | So, frame spacing is a much better property to judge visual quality than just watching fps. |