20,741
edits
Troubleshooting crashes: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
'''Targeted FlightGear versions: 2.6, 2.8, 2.10, 2.12+ ''' | '''Targeted FlightGear versions: 2.6, 2.8, 2.10, 2.12+ ''' | ||
== Motivation == | |||
This 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 in 2.11+) in FG 2.10 in particular, 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. | This 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 in 2.11+) in FG 2.10 in particular, 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. | ||
In other words, any and all help is appreciated, so please feel free to get involved and contribute to the article by adding your own findings, suggestions and techniques. Your help is really appreciated! | In other words, any and all help is appreciated, so please feel free to get involved and contribute to the article by adding your own findings, suggestions and techniques. Your help is really appreciated! | ||
If you should find yourself having to disable additional settings in order to further maximize FlightGear performance, please do add your findings to this article, so that others can benefit. | |||
Our hope is that we can come up with a fairly safe subset of FlightGear settings that should work for 99% of our users, even on moderately old hardware. This would enable us to change the FlightGear defaults accordingly, and use these settings as a safe fallback alternative - so that FlightGear should no longer just crash for people without certain hardware/features. | |||
There's a trend to expose more and more information via the property tree, to make the simulator increasinly runtime-configurable, and to allow subsystems to be re-initialized at runtime, so being able to start up FlightGear in some form of "safe" mode is generally a good thing and useful for anybody helping with troubleshooting on the forums, because it helps us exclude many potential problems. In the long run, such a profile could also be used as the foundation for a [[FlightGear Benchmark]] or some scripted regression suite to run FlightGear in a [[FlightGear Headless|headless]] mode to help with release preparations. | |||
== The Issue with 2.10 == | |||
<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> | ||
== Crashes in general == | |||
If FlightGear crashes (or looks/performs very badly/slowly), it's possible that this is due a number of reasons, such as limited hardware resources (CPU, GPU, RAM etc) or insufficient driver support - so crashes are not necessarily due to a faulty program. Also see [[FlightGear Benchmark]]. | If FlightGear crashes (or looks/performs very badly/slowly), it's possible that this is due a number of reasons, such as limited hardware resources (CPU, GPU, RAM etc) or insufficient driver support - so crashes are not necessarily due to a faulty program. Also see [[FlightGear Benchmark]]. | ||