Troubleshooting problems: Difference between revisions

Jump to navigation Jump to search
added [Enter]-key-does-not-work-for-rudder-problem solution :P
(USB Joystick hardware problem possible fix)
(added [Enter]-key-does-not-work-for-rudder-problem solution :P)
Line 12: Line 12:


If you are facing issues while interacting with the community, please see: http://catb.org/~esr/faqs/smart-questions.html
If you are facing issues while interacting with the community, please see: http://catb.org/~esr/faqs/smart-questions.html


= Making proper issue reports =
= 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 ==
== OpenGL related ==
Line 30: Line 32:


For Linux, there's now an OpenGL benchmarking test suite available [http://www.phoronix-test-suite.com/ here] ([http://www.phoronix-test-suite.com/download.php?file=phoronix-test-suite-1.4.0 download]) that provides useful information about your system's degree of OpenGL support, if you are unsure about your system's OpenGL support and if you are experiencing performance issues in FlightGear, you may want to try running this test suite first in order to ensure that OpenGL is properly set up on your system.
For Linux, there's now an OpenGL benchmarking test suite available [http://www.phoronix-test-suite.com/ here] ([http://www.phoronix-test-suite.com/download.php?file=phoronix-test-suite-1.4.0 download]) that provides useful information about your system's degree of OpenGL support, if you are unsure about your system's OpenGL support and if you are experiencing performance issues in FlightGear, you may want to try running this test suite first in order to ensure that OpenGL is properly set up on your system.


== General Hardware Info ==
== General Hardware Info ==
Line 40: Line 43:
** Type/Model
** Type/Model
** texture memory size
** texture memory size


== Software Specs ==
== Software Specs ==
Line 56: Line 60:
* YOKE
* YOKE
* PEDALS
* PEDALS


== FlightGear related Info ==
== FlightGear related Info ==
Line 72: Line 77:
* whether the same machine/OS (unmodified) 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


=== Sound Issues ===
=== Sound Issues ===
Line 80: Line 86:
* under Linux:if you are able to use other OpenAL programs
* under Linux:if you are able to use other OpenAL programs
* whether any other audio software might be running on your system  
* whether any other audio software might be running on your system  


=== In Flight Issues ===
=== In Flight Issues ===
Line 103: Line 110:
* the value of /sim/rendering/draw-otw using the property browser (needs to be true)
* the value of /sim/rendering/draw-otw using the property browser (needs to be true)
* any screenshots depicting the problem
* any screenshots depicting the problem


=== Input Hardware related Issues ===
=== Input Hardware related Issues ===
Line 116: Line 124:


TODO: we need to evaluate the forum and mailing discussions of the last 2-3 months in order to determine which issues were the most frequently reported ones (i.e. FreeGLUT, RenderTexture,3D Clouds,non calibrated hardware etc), so that we can summarize these issues here, and possibly even directly provide solutions later on.
TODO: we need to evaluate the forum and mailing discussions of the last 2-3 months in order to determine which issues were the most frequently reported ones (i.e. FreeGLUT, RenderTexture,3D Clouds,non calibrated hardware etc), so that we can summarize these issues here, and possibly even directly provide solutions later on.


== Troubleshooting Segmentation Faults ==
== Troubleshooting Segmentation Faults ==
Line 125: Line 134:


This sort of info will help to determine whether the problem is actually caused by FlightGear (or one of its dependencies) or by local, system-specific issues.
This sort of info will help to determine whether the problem is actually caused by FlightGear (or one of its dependencies) or by local, system-specific issues.


= Solutions =
= Solutions =
Line 130: Line 140:
==Common errors and solution==
==Common errors and solution==
{{main article|Howto: Get rid of common errors}}
{{main article|Howto: Get rid of common errors}}
== Slow Framerate with OpenGL Card ==
== Slow Framerate with OpenGL Card ==


Line 154: Line 166:
Warning! If you see anything like "ForceSW" or "Software Emulation", it was a bad thing for you because you do not have HARDWARE OpenGL support, or your drivers are not configured properly. If you have SOFTWARE OpenGL support, your CPU work a lot to display the graphics.
Warning! If you see anything like "ForceSW" or "Software Emulation", it was a bad thing for you because you do not have HARDWARE OpenGL support, or your drivers are not configured properly. If you have SOFTWARE OpenGL support, your CPU work a lot to display the graphics.
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 ==
== Slow Framerate with Graphic Card with Nvidia chip ==
Line 190: Line 203:
I made tests with Flightgear 0.9.10 and 1.0.0, I have only 1 fps with these 2 drivers and 2 flighgear versions.
I made tests with Flightgear 0.9.10 and 1.0.0, I have only 1 fps with these 2 drivers and 2 flighgear versions.
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 ==
== Corrupt Textures on ATi Cards ==
Line 211: Line 225:


[[Image:ATI_point-sprites_corrupted_1.jpg]] [[Image:ATI_point-sprites_corrupted_2.jpg]]
[[Image:ATI_point-sprites_corrupted_1.jpg]] [[Image:ATI_point-sprites_corrupted_2.jpg]]


== USB Joystick Fails to Work ==
== USB Joystick Fails to Work ==
Line 232: Line 247:
* a configuration file matching the name of your stick exists
* a configuration file matching the name of your stick exists
* 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


== USB Joystick exhibits permanent offset / requires repeated recalibration ==
== USB Joystick exhibits permanent offset / requires repeated recalibration ==
Line 238: Line 254:


In some cases this may be caused by improper connector seating or other loose connections within the joystick.  This can sometimes be remedied by unscrewing the base or other case element to access the circuit board and then reseating the connectors.  Also check for faulty solder joints and discrete components bent over onto the circuit board.  Before attempting any repair unplug the device and remove any batteries.
In some cases this may be caused by improper connector seating or other loose connections within the joystick.  This can sometimes be remedied by unscrewing the base or other case element to access the circuit board and then reseating the connectors.  Also check for faulty solder joints and discrete components bent over onto the circuit board.  Before attempting any repair unplug the device and remove any batteries.


== Configuring CH Products Under Windows Vista==
== Configuring CH Products Under Windows Vista==
Line 253: Line 270:
   <js n="1" include="Input/Joysticks/CH/pro-pedals-usb.xml"/>
   <js n="1" include="Input/Joysticks/CH/pro-pedals-usb.xml"/>
</code>
</code>
== [Enter] does not work for rudder control ==
First of all: if [0] doesn't work, check if toggling num-lock solves the issue.
Open file ''[[$FG_ROOT]]/keyboard.xml'' with your preferred Editor. and search for those lines (it's close to the top, around line 40):
      ## uncomment this line to get keycode reports printed to the terminal window
      #setlistener("devices/status/keyboard/event", func(n) debug.dump(n.getValues()));
Read the first one and uncomment the second one. To uncomment it remove the leading "#".<BR>
Save the file and run FlightGear as usual but with the log-level set to "alarm" (no need to do anything if it wasn't used/changed before!).<BR>
When FlighGear is running press [Enter] and immediately after this, without doing anyting on the keyboard, ''click'' on FlightGears log window and you'll see something like this in the last two lines of the log:
{ key: 13, modifier: { meta: 0, shift: 0, alt: 0, super: 0, ctrl: 0, hyper: 0 }, pressed: 1 }
{ key: 13, modifier: { meta: 0, shift: 0, alt: 0, super: 0, ctrl: 0, hyper: 0 }, pressed: 0 }
The first line is for pressing the [Enter]-Key, the second for releasing it. Keep the first number, named "key", in this exaple shown as "13", in mind.
Open file $FG_ROOT/keyboard.xml again and search for "enter". You should find following:
<key n="10">
  <name>Enter</name>
  <desc>Move rudder right</desc>
Now replace the value of ''key n='' with the one you had to keep in mind earlier. Save file and run FlightGear to test it.
If the [Enter] key doesn't work at all for some reason one solution would be to assign the key right hand next to (not the num-block-)[0], if it is not already assigned to something else. Procedure is the same as shown with the [Enter] key.
Last thing to do, in any case, disbable the keycode reports by replacing the "#" which we removed earlier.


= Possible pitfalls when modifying base package files =
= Possible pitfalls when modifying base package files =
Line 270: Line 313:


If you do encounter problems getting your modifications to work for you, you may want to run FlightGear with an increased log/warning level, so that you get to see more completely which parts of FlightGear could be successfully completed and which ones failed, this can be achieved by using the --log-level=bulk parameter
If you do encounter problems getting your modifications to work for you, you may want to run FlightGear with an increased log/warning level, so that you get to see more completely which parts of FlightGear could be successfully completed and which ones failed, this can be achieved by using the --log-level=bulk parameter


==Related==
==Related==
*[[About graphic drivers]]
*[[About graphic drivers]]
* [[Howto: Get rid of common errors]]
* [[Howto: Get rid of common errors]]
392

edits

Navigation menu