8,564
edits
Howto:Improve framerates: Difference between revisions
Jump to navigation
Jump to search
m
Log level is also important
m (moved Howto: Improve Framerates to Howto: Improve framerates) |
m (Log level is also important) |
||
| Line 10: | Line 10: | ||
* [[aircraft]] speed (scenery paging) | * [[aircraft]] speed (scenery paging) | ||
* rendering options | * rendering options | ||
* debugging level | |||
You can disable most features that often adversely affect framerate. Here is a collection of settings that you may change to improve your framerate. Please note that some of these will only take effect if they're specified at startup and cannot be changed after the simulation has started. | You can disable most features that often adversely affect framerate. Here is a collection of settings that you may change to improve your framerate. Please note that some of these will only take effect if they're specified at startup and cannot be changed after the simulation has started. | ||
| Line 34: | Line 35: | ||
=== Operating system specific === | === Operating system specific === | ||
Many newer Linux distributions, like openSUSE 11.2, come with KDE4 as a desktop environment. While it allows some fancy desktop effects, it is known to consume enough computing power from the CPU and the graphics card to slow FlightGear down by 10 frames per second or even more. Choosing another window manager from the login screen, like xfce results in higher FlightGear performance. Setting "Compositing" to "off" in KDE4 might also help. | Many newer Linux distributions, like openSUSE 11.2, come with KDE4 as a desktop environment. While it allows some fancy desktop effects, it is known to consume enough computing power from the CPU and the graphics card to slow FlightGear down by 10 frames per second or even more. Choosing another window manager from the login screen, like xfce results in higher FlightGear performance. Setting "Compositing" to "off" in KDE4 might also help. | ||
=== Debugging/log level === | |||
The more FlightGear has to write out to the log, the more framerates will be sacrificed. On normal usage, one is best of with the highest log level, which is ''alert''. In FGRun this can be set via <tt>Advanced > Debugging</tt>, on a commandline you'll use <tt>--log-level=alert</tt> (or simply remove an existing --log-level command, as alert is the default). | |||
== Hints for developers == | == Hints for developers == | ||