573
edits
Troubleshooting performance issues: Difference between revisions
Jump to navigation
Jump to search
→Performance factors: pfew, done.
m ("auto" save (almost there...)) |
(→Performance factors: pfew, done.) |
||
| Line 24: | Line 24: | ||
== Performance factors == | == Performance factors == | ||
=== Operating system and driver setup === | === Operating system and driver setup === | ||
*'''Problematic video cards''': There is a list of [[problematic video cards]]. Check that yours is not there. | |||
*'''Background programs''': Check that your operating system is not cluttered by unnecessary programs running in the background. Have as little programs running as possible. | *'''Background programs''': Check that your operating system is not cluttered by unnecessary programs running in the background. Have as little programs running as possible. | ||
* '''Maximize power performance settings''': If you're running a laptop, chances are your system defaults to a power-saving mode, even with the laptop plugged in. Adjust these settings to maximal power while running FlightGear. | * '''Maximize power performance settings''': If you're running a laptop, chances are your system defaults to a power-saving mode, even with the laptop plugged in. Adjust these settings to maximal power while running FlightGear. | ||
| Line 47: | Line 48: | ||
* '''Graphics drivers settings''': Disable Anti-Aliasing and Anisotropic Filtering or at least set them to their lowest settings. Decreasing the setting for Mip-Mapping to its lowest setting can also help. | * '''Graphics drivers settings''': Disable Anti-Aliasing and Anisotropic Filtering or at least set them to their lowest settings. Decreasing the setting for Mip-Mapping to its lowest setting can also help. | ||
=== FlightGear | === FlightGear configuration === | ||
From FlightGear Launcher (some options appear also during the simulation, so better to check them there too): | From FlightGear Launcher (some options appear also during the simulation, so better to check them there too): | ||
* '''Rembrandt''': If you enabled the [[Project Rembrandt|Rembrandt renderer]], well, you knew that's experimental. First of all, try to change shadows settings, and consider disabling them. If it's not enough, disable Rembrandt altogether. To check if it's enabled: last tab, ''Advanced > Rendering >'' uncheck ''Rembrandt''. | * '''Rembrandt''': If you enabled the [[Project Rembrandt|Rembrandt renderer]], well, you knew that's experimental. First of all, try to change shadows settings, and consider disabling them. If it's not enough, disable Rembrandt altogether. To check if it's enabled: last tab, ''Advanced > Rendering >'' uncheck ''Rembrandt''. | ||
| Line 57: | Line 58: | ||
* '''Everything else''': Both ''Advanced > features'' and ''Advanced > rendering'' have few settings that you can try out. | * '''Everything else''': Both ''Advanced > features'' and ''Advanced > rendering'' have few settings that you can try out. | ||
* '''Texture compression''': If you're experiencing stuttering when turning left/right or when loading new tiles, it is possible that texture compression is not handled correctly. Disable it by adding the property <tt>/sim/rendering/texture-compression=off</tt> in FGrun: ''Advanced > Properties''. This can be tried for nVidia, ATI cards and for Intel integrated chips with MesaGL, that suffer from bugs with texture compression and FlightGear. | * '''Texture compression''': If you're experiencing stuttering when turning left/right or when loading new tiles, it is possible that texture compression is not handled correctly. Disable it by adding the property <tt>/sim/rendering/texture-compression=off</tt> in FGrun: ''Advanced > Properties''. This can be tried for nVidia, ATI cards and for Intel integrated chips with MesaGL, that suffer from bugs with texture compression and FlightGear. | ||
*'''Multithreading''': '''''WARNING!''''' If you know what you're doing, in Preferences.xml enable <tt><multithreading-mode></tt>. If your framerate is lower with this setting enabled, and both you and your computer survived, disable it again. | |||
During the simulation: | During the simulation: | ||
| Line 72: | Line 74: | ||
* '''2D panels''': Although 3D cockpits look very tempting, simple 2D panels are much easier on the framerate. | * '''2D panels''': Although 3D cockpits look very tempting, simple 2D panels are much easier on the framerate. | ||
* '''AI traffic''': [[Interactive Traffic|AI-traffic]] is computer controlled traffic, which includes traffic over the [[Howto: Multiplayer|Multiplayer network]]. By turning off this function you're not able to see other aircraft. Most stuttering, or lag, is caused by the need to load the models for these aircraft while they appear. It can range from a minor annoyance to a crash. Turning off just the computer-generated aircraft (leaving the MP traffic visible), can be done by adding the property <tt>/sim/traffic-manager/enabled=0</tt> to [[FGRun]], through ''Advanced > Properties''. | * '''AI traffic''': [[Interactive Traffic|AI-traffic]] is computer controlled traffic, which includes traffic over the [[Howto: Multiplayer|Multiplayer network]]. By turning off this function you're not able to see other aircraft. Most stuttering, or lag, is caused by the need to load the models for these aircraft while they appear. It can range from a minor annoyance to a crash. Turning off just the computer-generated aircraft (leaving the MP traffic visible), can be done by adding the property <tt>/sim/traffic-manager/enabled=0</tt> to [[FGRun]], through ''Advanced > Properties''. | ||
=== Nothing worked. Now what? === | |||
It is unlikely, so this must be more than a simple performance issue. Try [[Troubleshooting graphics artifacts]]. | |||
== For the geeks out there == | == For the geeks out there == | ||