Troubleshooting performance issues: Difference between revisions

Troubleshooting performance issues (view source)

703 bytes removed , 24 May 2014

573

edits

@@ Line 45: / Line 45: @@
 === Graphics drivers setup ===
-*'''Graphics card drivers''': Ensure that the manufacturer's graphics card drivers are installed. You may be able to download and install drivers specific to your card from the manufacturer's site. See [[Graphics drivers configuration]]. If you think you're done, a sure way to check is the following:
+*'''Graphics card drivers''': Ensure that the manufacturer's graphics card drivers are installed. You may be able to download and install drivers specific to your card from the manufacturer's site. See [[Graphics drivers configuration]].
-:# Set log level to "info": FlightGear launcher (fgrun.exe), in the last window button ''advanced > debugging'', set ''Log level'' to ''info'' and click OK.
-:# Launch FlightGear and find in the console window the line reporting your graphics card:
- Finished command line arguments
- Initializing splash screen
- GeForce4 MX 440 with AGP8X/AGP/SSE2/forceSW
- Max texture size = 2048
-: That "forceSW" indicates that the hardware acceleration is software emulated, so the OpenGL drivers are not configured, or worse you simply lack hardware support for OpenGL. '''Remember to set back to "alert" the log level!!''' Logging affects performance!
 * '''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.