20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
http://flightgear.org/forums/viewtopic.php?f=3&t=20424&p=187595#p187595
mNo edit summary |
m (http://flightgear.org/forums/viewtopic.php?f=3&t=20424&p=187595#p187595) |
||
| Line 1: | Line 1: | ||
'''Targeted FlightGear versions: 2.6, 2.8, 2.10, 2.12+ ''' | |||
Thi article should be suitable for pretty much any OSG-based version beyond 2.6/2.8 - the 2.10 reference/disclaimer below is just about a specific GLSL issue that got introduced (and now fixed), the point of the whole write-up is to provide a dedicated place for people to go with these sorts of problems, and to reduce the workload on our part obviously - and provide some guidance to end-users facing such issues, allowing them to experiment a little and provide more specific feedback. The idea is to keep it up-to-date for upcoming FG versions, too - including 2.12 and beyond. | |||
<font color="red">'''Note:''' FlightGear 2.10 users seeing crashes during simulator startup (without seeing the actual aircraft/scenery) with very old graphics cards that lack GLSL (shader) support should know that there used to be a bug in 2.10 that broke support for graphics cards without any shader support. In other words, if you are able to run other OpenGL software, but cannot even display the about dialog in FG 2.10 using the minimal startup profile detailed below, it is almost certainly your graphics card's lack of shader support causing the issue, because FlightGear 2.10 tries to copy graphics card information to the property tree for debugging purposes, to allow end-users to provide better troubleshooting reports - ironically, this very feature introduced crashes for all 2.10 users without any GLSL support. This issue has been fixed in FlightGear 2.11+ </font> | <font color="red">'''Note:''' FlightGear 2.10 users seeing crashes during simulator startup (without seeing the actual aircraft/scenery) with very old graphics cards that lack GLSL (shader) support should know that there used to be a bug in 2.10 that broke support for graphics cards without any shader support. In other words, if you are able to run other OpenGL software, but cannot even display the about dialog in FG 2.10 using the minimal startup profile detailed below, it is almost certainly your graphics card's lack of shader support causing the issue, because FlightGear 2.10 tries to copy graphics card information to the property tree for debugging purposes, to allow end-users to provide better troubleshooting reports - ironically, this very feature introduced crashes for all 2.10 users without any GLSL support. This issue has been fixed in FlightGear 2.11+ </font> | ||