Howto:Improve framerates: Difference between revisions

Jump to navigation Jump to search

Howto:Improve framerates (view source)

Revision as of 11:28, 18 December 2011

196 bytes removed ,  18 December 2011
no edit summary
(Optimus Technology)
No edit summary
Line 16: Line 16:
== Hints for users ==
== Hints for users ==
=== Shaders ===
=== Shaders ===
As of FlightGear 2.0.0, a growing number of [[shaders]] is being implemented into FlightGear. While these do make your flights visually appealing, they tend to have quite an impact on most computers. Luckily you can easily disable shaders in the <tt>View > Rendering Options</tt> dialog. It requires some testing to find out what settings are best for your computer, but it's defenitely worth spending some time on!
As of FlightGear 2.0.0, a growing number of [[shaders]] is being implemented into FlightGear. While these do make your flights visually appealing, they tend to have quite an impact on most computers. Luckily you can easily disable shaders in the <tt>View > Rendering Options</tt> dialog. As of FlightGear 2.6.0 an advanced shader options dialog is available, in which you can adjust every single shader's setting.
 
It requires some testing to find out what settings are best for your computer, but it's defenitely worth spending some time on!


=== Other windows/programs ===
=== Other windows/programs ===
Line 28: Line 30:
Turning off just the computer-generated aircraft (leaving the MP traffic visible), can be done by adding a command to your commandline:
Turning off just the computer-generated aircraft (leaving the MP traffic visible), can be done by adding a command to your commandline:
  --prop:/sim/traffic-manager/enabled=0
  --prop:/sim/traffic-manager/enabled=0
Or via [[FGRun]] through Advanced > Properties, add new property with <tt>/sim/traffic-manager/enabled=0</tt>
Or via [[FGRun]] through Advanced > Properties, add a new property with <tt>/sim/traffic-manager/enabled=0</tt>
 
=== Outside vs. inside views ===
One of the things that can also affect the frame rate is the view. The inside cockpit view is better than the outside views, like Tower View (especially KSFO) and Chase view without Yaw. Once inside, the GPU and/or graphics card does not have to draw scenery. But if the cockpit is 3D and really detailed, performance is about the same.


=== Operating system specific ===
=== Operating system specific ===
Line 40: Line 39:


=== Optimus Technology ===
=== Optimus Technology ===
Most notebooks that run Windows 7 have the so called [http://www.nvidia.com/object/optimus_technology.html Optimus Technology] onboard. This is meant to increase battery life, by automatically switching of the powerfull graphics card when it's not needed. However, FlightGear needs it all the time, even if Optimus says it doesn't. This miscommunication results in low framerates (because your computer will run Flightgear on the weak onboard processor).
Most notebooks that run Windows 7 have the so called [http://www.nvidia.com/object/optimus_technology.html Optimus Technology] (NVidia) or Hybrid Graphics technology (ATI) onboard. This is meant to increase battery life, by automatically switching of the powerfull graphics card when it's not needed. However, FlightGear needs it all the time, even if Optimus says it doesn't! This miscommunication results in low framerates (because your computer will run Flightgear on the weak onboard processor).


To make use of the powerful graphics card, perform the following steps:
To make use of the powerful graphics card, perform the following steps:
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/38075"

Navigation menu