4,400
edits
Troubleshooting problems: Difference between revisions
Jump to navigation
Jump to search
m
Robot: Cosmetic changes
m (Bot: Automated text replacement (-flighgear +FlightGear)) |
m (Robot: Cosmetic changes) |
||
| Line 28: | Line 28: | ||
(before you need to enable log in info mode, | (before you need to enable log in info mode, | ||
FlightGear launcher (fgrun.exe) -->button "advanced" in the third window --> | FlightGear launcher (fgrun.exe) -->button "advanced" in the third window --> | ||
tab "debuuging", select info for "log level" --> click button OK ) | tab "debuuging", select info for "log level" --> click button OK ) | ||
Finished command line arguments | Finished command line arguments | ||
| Line 41: | Line 41: | ||
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 | ||
c) Optimize FlightGear [[ settings for slower graphics cards]] | c) Optimize FlightGear [[settings for slower graphics cards]] | ||
== Slow Framerate with Graphic Card with Nvidia chip == | == Slow Framerate with Graphic Card with Nvidia chip == | ||
| Line 50: | Line 50: | ||
(before you need to enable log in info mode, | (before you need to enable log in info mode, | ||
FlightGear launcher (fgrun.exe) -->button "advanced" in the third window --> | FlightGear launcher (fgrun.exe) -->button "advanced" in the third window --> | ||
tab "debuuging", select info for "log level" --> click button OK ) | tab "debuuging", select info for "log level" --> click button OK ) | ||
Finished command line arguments | Finished command line arguments | ||
| Line 82: | Line 82: | ||
== Corrupt Textures on ATi Cards == | == Corrupt Textures on ATi Cards == | ||
Several users have reported corrupted textures running FlightGear on ATi graphics 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: | ||
Start FG in the normal way. | Start FG in the normal way. | ||
| Line 89: | Line 89: | ||
Uncheck 'Use Point Sprites for Runway Lights' (fourth check-box) | Uncheck 'Use Point Sprites for Runway Lights' (fourth check-box) | ||
When you come to quit FG, do so by menu: | When you come to quit FG, do so by menu: File...Exit, rather than closing the window to save this setting. | ||
If you can't read the Menu titles (because of corrupted graphics) you can manually edit the config files $FG_HOME/autosave.xml and/or $FG_ROOT/preferences.xml before even starting FlightGear. The file autosave.xml is created the first time FlightGear is closed and settings in it override the defaults in $FG_ROOT/preferences.xml. Use your operating system's search facilities to find the files if you don't know where to look for them. Close Flightgear and change the line | If you can't read the Menu titles (because of corrupted graphics) you can manually edit the config files $FG_HOME/autosave.xml and/or $FG_ROOT/preferences.xml before even starting FlightGear. The file autosave.xml is created the first time FlightGear is closed and settings in it override the defaults in $FG_ROOT/preferences.xml. Use your operating system's search facilities to find the files if you don't know where to look for them. Close Flightgear and change the line | ||
| Line 99: | Line 99: | ||
Examples of corrupted graphics with an ATI card: | Examples of corrupted graphics with an ATI card: | ||
[[ | [[File:ATI_point-sprites_corrupted_1.jpg]] [[File:ATI_point-sprites_corrupted_2.jpg]] | ||
| Line 126: | Line 126: | ||
== USB Joystick exhibits permanent offset / requires repeated recalibration == | == USB Joystick exhibits permanent offset / requires repeated recalibration == | ||
USB Joystick drivers should automatically zero and calibrate the joystick on plugin. | 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. | 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 == | ||
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. | ||
| Line 151: | Line 151: | ||
First of all: if [0] doesn't work, check if toggling num-lock solves the issue. | First of all: if [0] doesn't work, check if toggling num-lock solves the issue. | ||
Open file ''[[$ | 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 | ## uncomment this line to get keycode reports printed to the terminal window | ||
#setlistener("devices/status/keyboard/event", func(n) debug.dump(n.getValues())); | #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 "#".< | 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!).< | 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 FlightGear 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: | When FlightGear 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: 1 } | ||
| Line 190: | Line 190: | ||
==Related== | == Related == | ||
* [[About graphic drivers]] | * [[About graphic drivers]] | ||
* [[Howto: Get rid of common errors]] | * [[Howto: Get rid of common errors]] | ||