186
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 | Anything below about 15 frames per second (fps) is close to unplayable, or at least, will not be enjoyable. Additionally, the more the framerate decreases, the more other features of the simulation will suffer. The current FG software architecture is such that long rendering time (slow framerates) will 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, among others: | FlightGear's framerate is influenced by various factors, among others: | ||
| Line 5: | Line 5: | ||
* scenery complexity | * scenery complexity | ||
* cockpit complexity (2D vs. 3D) | * cockpit complexity (2D vs. 3D) | ||
* environmental options ( | * environmental options (eg. visibility) | ||
* FDM update interval | * FDM update interval | ||
* AI scenarios | * AI scenarios | ||
| Line 11: | Line 11: | ||
You can | You can disable most features that often adversely affect framerate. Here is a collection of settings that you may improve your framerate. Please note that some of these options will only take effect if they're specified at startup and cannot be changed after the simulation has started: | ||
TODO: | TODO: | ||
| Line 23: | Line 23: | ||
Contrary to what many people believe, the | Contrary to what many people believe, the impact of high vertex-count models on framerate is fairly minimal. For graphic artists, the key things that should be avoided are: | ||
* high resolution textures | * high resolution textures | ||