573
edits
Graphics drivers configuration: Difference between revisions
moved info on checking drivers from Troubleshooting performance issues
m (+ cat) |
(moved info on checking drivers from Troubleshooting performance issues) |
||
| Line 2: | Line 2: | ||
The absence of OpenGL support (by the card or the drivers) is often the cause of pathologically low framerate (i.e. less than 1-2 FPS.) | The absence of OpenGL support (by the card or the drivers) is often the cause of pathologically low framerate (i.e. less than 1-2 FPS.) | ||
''If you need to check if the correct drivers are being used, [[#Check if the drivers are working|see below]].'' | |||
== Microsoft Windows == | == Microsoft Windows == | ||
| Line 53: | Line 55: | ||
=== A note on free drivers === | === A note on free drivers === | ||
When using free and open source drivers, support is generally better with AMD graphics cards than with nVidia products, because of differences in the [[wikipedia:Graphics hardware and FOSS|manufacturers' policies]] towards providing documentation for their hardware. As progress on the free drivers has been significant in recent months, try to stay as up to date as possible to get the best results. That means use most recent distribution versions instead of long term supported ones. | When using free and open source drivers, support is generally better with AMD graphics cards than with nVidia products, because of differences in the [[wikipedia:Graphics hardware and FOSS|manufacturers' policies]] towards providing documentation for their hardware. As progress on the free drivers has been significant in recent months, try to stay as up to date as possible to get the best results. That means use most recent distribution versions instead of long term supported ones. | ||
== Check if the drivers are working == | |||
When you're done with the installation, you can verify that in-sim, in the ''About > FlightGear'' dialog. | |||
However you might have graphics issues preventing you to do so. A sure way to check that all went as it should is the following: | |||
:# Set log level to "info": [[FGRun|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! | |||
== Caveat == | == Caveat == | ||
* See [[Problematic | * See [[Problematic Video Cards]]. | ||
* Some video cards only support Direct3D, which is not compatible with FlightGear. | * Some video cards only support Direct3D, which is not compatible with FlightGear. | ||
* Some 3D cards can't function if you set the display resolution too large or the pixel depth to something that card won't support. Some OpenGL drivers silently drop back to software-only rendering under those circumstances. | * Some 3D cards can't function if you set the display resolution too large or the pixel depth to something that card won't support. Some OpenGL drivers silently drop back to software-only rendering under those circumstances. | ||