2,561
edits
Troubleshooting problems: Difference between revisions
Jump to navigation
Jump to search
m
restructuring
m (restructuring) |
|||
| Line 1: | Line 1: | ||
= Intro = | |||
Hi, you were probably referred to this page because you are having problems getting FlightGear to work for you. This page is dedicated to helping you address any issues you may face. | Hi, you were probably referred to this page because you are having problems getting FlightGear to work for you. This page is dedicated to helping you address any issues you may face. | ||
| Line 5: | Line 6: | ||
Even if some of the information we ask for is not always necessarily required in order to fix a particular issue, it can tremendously simplify and shorten the troubleshooting process, for example by allowing us to exclude certain problem sources. So, if at all possible please try to comply with our requests, if anything is unclear or you don't know how to obtain certain information please ask for clarification rather than ignoring a particular request. | Even if some of the information we ask for is not always necessarily required in order to fix a particular issue, it can tremendously simplify and shorten the troubleshooting process, for example by allowing us to exclude certain problem sources. So, if at all possible please try to comply with our requests, if anything is unclear or you don't know how to obtain certain information please ask for clarification rather than ignoring a particular request. | ||
= Making proper issue reports = | |||
'''In general, you should always try to provide the following information in your requests/reports:''' | '''In general, you should always try to provide the following information in your requests/reports:''' | ||
== OpenGL related == | |||
* Do you have a non NVIDIA/ATI graphics card (i.e. Intel) | |||
* Are you currently able to run other OpenGL (non-DirectX) 3D-software with your current system configuration using hardware acceleration? | |||
* Have you previously run other OpenGL software on your current system? | |||
On *nix systems: | |||
* the output from running glxgears | |||
* the output from running glxinfo | |||
== General Hardware Info == | |||
* CPU | * CPU | ||
| Line 13: | Line 24: | ||
* SOUND CARD | * SOUND CARD | ||
* GRAPHICS CARD | * GRAPHICS CARD | ||
** Manufacturer | |||
** Type/Model | |||
== Software Specs == | |||
* OS (Version, Kernel, Servicepacks etc) | * OS (Version, Kernel, Servicepacks etc) | ||
| Line 22: | Line 35: | ||
== Input Hardware == | |||
(This is only likely to be required if FlightGear itself seems to be working properly otherwise) | |||
* KEYBOARD (language/country encoding) | * KEYBOARD (language/country encoding) | ||
| Line 32: | Line 46: | ||
== FlightGear related Info == | |||
=== Basic Info === | |||
* version of FlightGear you are trying to get to work for you | * version of FlightGear you are trying to get to work for you | ||
* where you obtained it from | * where you obtained it from (URL) | ||
* in what format you obtained it (executables/binaries vs. source code) | * in what format you obtained it (executables/binaries vs. source code) | ||
* if you built it yourself, how you did do that (compiler,flags etc) | * if you built it yourself, how you did do that (compiler,flags etc) | ||
* how and where you installed FlightGear | * how and where you installed FlightGear (file system location) | ||
* how you are starting FlightGear (GUI frontend vs. shell/console) | * how you are starting FlightGear (GUI frontend vs. shell/console) | ||
* startup parameters you use | * if you have previously only tried starting it via GUI frontend, the output of trying to run it from a console | ||
* startup parameters you use, and information whether using the defaults (i.e. no arguments at all), works for you or not | |||
* runtime settings you use | * runtime settings you use | ||
* any console messages (warnings and errors) you may see | * any console messages (warnings and errors) you may see (preferably the complete redirected output from STDERR) | ||
* whether the same machine/OS has previously been used to run FlightGear successfully, if so what version of FlightGear | * whether the same machine/OS (unmodified) has previously been used to run FlightGear successfully, if so what version of FlightGear | ||
* if FlightGear works properly using the default settings | * if FlightGear works properly using the default settings | ||
=== In Flight Issues === | |||
If you experience any problems during flight, please save the active flight and make the saved file available for further investigation (i.e. in order to post it to a forum or send it to a [[mailing list]]) | If you experience any problems during flight, please save the active flight and make the saved file available for further investigation (i.e. in order to post it to a forum or send it to a [[mailing list]]) | ||
| Line 55: | Line 71: | ||
* whether you can see any scenery (i.e. runways) from non-cockpit views (i.e. outside view: using the v/V key to cycle through all views) | * whether you can see any scenery (i.e. runways) from non-cockpit views (i.e. outside view: using the v/V key to cycle through all views) | ||
* what daytime settings you are using and whether changing this setting has any effect | * what daytime settings you are using and whether changing this setting has any effect | ||
* what environmental settings you are using (clouds, visibility) | |||
* which tiles you downloaded, and from where-including the size of each file or its MD5 sum | * which tiles you downloaded, and from where-including the size of each file or its MD5 sum | ||
* whether you are able to open the downloaded scenery tiles using an archiver such as WinZip, PowerZIP, IzArc | * whether you are able to open the downloaded scenery tiles using an archiver such as WinZip, PowerZIP, IzArc - and if you get to see any warnings or errors | ||
* which areas/airports specifically are causing trouble, and what you are (not) seeing (i.e. water?) | * which areas/airports specifically are causing trouble, and what you are (not) seeing (i.e. terrain/water?) | ||
* how exactly you installed the scenery tiles, did you extract the scenery tiles properly? | * how exactly you installed the scenery tiles, did you extract the scenery tiles properly? | ||
* the location of your FlightGear base package (data) folder | * the location of your FlightGear base package (data) folder | ||
* whether you made any modifications to your base package, if so: if using a fresh copy of the base package results in the same problem | |||
* whether you customized any user-specific FlightGear settings, if so: whether deleting/renaming your fgfs home folder, still results in the same problem | |||
* if you are using the FG_ROOT and FG_SCENERY variables, their contents | * if you are using the FG_ROOT and FG_SCENERY variables, their contents | ||
* the contents of the folder under $FG_ROOT/Terrain | * the contents of the folder under $FG_ROOT/Terrain | ||
| Line 66: | Line 85: | ||
* any screenshots depicting the problem | * any screenshots depicting the problem | ||
=== Input Hardware related Issues === | |||
'''If you are facing problems related to your input hardware, please also try to provide the following information:''' | '''If you are facing problems related to your input hardware, please also try to provide the following information:''' | ||
| Line 80: | Line 99: | ||
= Solutions = | |||
== Slow Framerate with OpenGL Card == | |||
a) | a) | ||
| Line 107: | Line 126: | ||
Source : http://ocw.mit.edu/ans7870/6/6.370/contestants/software.htm#issues | Source : http://ocw.mit.edu/ans7870/6/6.370/contestants/software.htm#issues | ||
== Slow Framerate with Graphic Card with Nvidia chip == | |||
a) First, Identify if your graphic card use software OpenGL support | a) First, Identify if your graphic card use software OpenGL support | ||
| Line 143: | Line 162: | ||
This card is not yet powerful for flightgear and there is no workaround for it. | This card is not yet powerful for flightgear and there is no workaround for it. | ||
== Corrupt Textures on ATi Cards == | |||
Several users have reported corrupted textures running FlightGear on ATi graphics cards. The ATi drivers are the subject of intensive improvement, but can still be problematic for some users. Try this: | Several users have reported corrupted textures running FlightGear on ATi graphics cards. The ATi drivers are the subject of intensive improvement, but can still be problematic for some users. Try this: | ||
| Line 154: | Line 173: | ||
When you come to quit FG, do so by menu: File...Exit, rather than closing the window to save this setting. | When you come to quit FG, do so by menu: File...Exit, rather than closing the window to save this setting. | ||
== USB Joystick Fails to Work == | |||
FlightGear is designed to recognize automatically any USB joystick that it is aware of (has a configuration on file for it). Configuration for USB joysticks is located in the Inputs folder. For example: | FlightGear is designed to recognize automatically any USB joystick that it is aware of (has a configuration on file for it). Configuration for USB joysticks is located in the Inputs folder. For example: | ||
| Line 175: | Line 194: | ||
* the configuration joystick name matches the name the stick actually reports to your computer | * the configuration joystick name matches the name the stick actually reports to your computer | ||
== Configuring CH Products Under Windows Vista== | |||
The CH Products Yoke and Pedals are among the most popular flight sim controls. | The CH Products Yoke and Pedals are among the most popular flight sim controls. | ||