Troubleshooting problems: Difference between revisions

Jump to navigation Jump to search
→‎Corrupt Textures on ATi Cards: Clarified the autosave.xml / preference.xml editing.
(→‎Corrupt Textures on ATi Cards: Clarified the autosave.xml / preference.xml editing.)
Line 191: Line 191:
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.


If you can't read the Menu titles (because of corrupted graphics) you can manually edit autosave.xml file before even starting FlightGear. Close Flightgear, change the line <point-sprites type="bool">true</point-sprites> to <point-sprites type="bool">false</point-sprites>, and start FlighGear again. This is the same as changing the above mentioned option but does not require FlightGear running.
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
<point-sprites type="bool">true</point-sprites>
to
<point-sprites type="bool">false</point-sprites>
in both files (if you don't have an autosave.xml it is sufficient to make the change in preferences.xml) and start FlighGear again. This is the same as changing the above mentioned option in the rendering dialog but does not require FlightGear running.


Examples of corrupted graphics with an ATI card:
Examples of corrupted graphics with an ATI card:
829

edits

Navigation menu