20,741
edits
Howto:Improve framerates: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Anything below about 15 frames per second (fps) is close to unusable, or at least, will not be enjoyable. In fact, you'll probably want to aim for 25-35 fps minimum. Additionally, the more the framerate decreases, the more other features of the simulation will suffer. The current [[FlightGear]] software architecture is such that long rendering times (slow framerates) may prevent other parts of the flight simulator, such as the autopilot, from having sufficient CPU time to respond correctly in the context of the simulation. | Anything below about 15 frames per second (fps) is close to unusable, or at least, will not be enjoyable. In fact, you'll probably want to aim for 25-35 fps minimum, and a maximum frame spacing (latency) of ~50 ms. | ||
Additionally, the more the framerate decreases, the more other features of the simulation will suffer. The current [[FlightGear]] software architecture is such that long rendering times (slow framerates) may prevent other parts of the flight simulator, such as the autopilot, from having sufficient CPU time to respond correctly in the context of the simulation. | |||
FlightGear's framerate is influenced by various factors, including: | FlightGear's framerate is influenced by various factors, including: | ||