Troubleshooting problems: Difference between revisions

** Try [[Requesting Technical Help]], but only after trying the other suggestions on this page first

{{main article|Howto: Get rid of common errors}}

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:

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

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:

* the configuration joystick name matches the name the stick actually reports to your computer

USB Joystick drivers should automatically zero and calibrate the joystick on plugin. Some examples of some types of joystick can be faulty where the fault is exhibited as an offset from the zero position when this process is completed. In Kubuntu this can be fixed for the session by use of the Joystick calibration tool under "Keyboard and Mouse" of "System Settings", or equivalent tools with other distributions, but the problem will recur.

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.

The CH Products Yoke and Pedals are among the most popular flight sim controls.  

FlightGear provides excellent configuration files for both the Yoke and Pedals manufactured by CH. Windows Vista recognizes and configures the USB versions of these products by default. However, it reports them as "Generic Controls." This creates an issue when FlightGear tries to assign the appropriate controller configuration.  

</code>

First of all: if [0] doesn't work, check if toggling num-lock solves the issue.

Last thing to do, in any case, disbable the keycode reports by replacing the "#" which we removed earlier.

At some point, most users will probably want to modify FlightGear in some way or another.  

Many interesting modifications can be done by editing base package resources, such as for example aircraft files, instrumentation files, GUI files, Nasal scripts etc.

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

* [[Graphics drivers configuration]]

* [[Howto: Get rid of common errors]]

[[Category:Troubleshooting]]