Troubleshooting crashes: Difference between revisions

Jump to navigation Jump to search
m
Fix internal wiki links
m (Switch to the {{forum url}} and {{forum link}} templates for all forum links.)
m (Fix internal wiki links)
 
Line 184: Line 184:
If you're able to build from source and don't mind using development looks like the built-in profiler, it would be interesting to see comparison of both builds - ideally using a simple test case with everything else disabled - you could use a pre-recorded flight and/or a flight recorder type to come up with a "test flight". From our standpoint, it would help tremendously if all features that don't seem to have an effect could be completely disabled, including complex aircraft and scenery/locations. In other words, if you can reproduce the problem using "bare" minimum settings, the resulting log file will be much easier to process.
If you're able to build from source and don't mind using development looks like the built-in profiler, it would be interesting to see comparison of both builds - ideally using a simple test case with everything else disabled - you could use a pre-recorded flight and/or a flight recorder type to come up with a "test flight". From our standpoint, it would help tremendously if all features that don't seem to have an effect could be completely disabled, including complex aircraft and scenery/locations. In other words, if you can reproduce the problem using "bare" minimum settings, the resulting log file will be much easier to process.


There's a built-in profiler which you can use to create these profiles: http://wiki.flightgear.org/Built-in_Profiler
There's a built-in profiler which you can use to create these profiles: [[Built-in Profiler]]
You would then want to use two different build directories, where SG/FG build settings would be identical, but using an older version of OSG: http://wiki.flightgear.org/Building_using_CMake#Multiple_build_directories
You would then want to use two different build directories, where SG/FG build settings would be identical, but using an older version of OSG: [[Building using CMake#Multiple build directories]]


For the sake of simplicity there's a so called "minimal startup profile" that you can use: http://wiki.flightgear.org/Howto:Debugging_FlightGear_Crashes#Minimal_startup_profile
For the sake of simplicity there's a so called "minimal startup profile" that you can use: [[Howto:Debugging FlightGear Crashes#Minimal startup profile]]
While unlikely, it would be great if the issue could be reproduced that way - but more likely than not, you'll have to re-add a few features and change a few settings, e.g. by using a different location.
While unlikely, it would be great if the issue could be reproduced that way - but more likely than not, you'll have to re-add a few features and change a few settings, e.g. by using a different location.


Like I said, you could then use the replay system to create an test flight than can be easily reproduced - to get going more quickly, you can also use the built-in route manager to create a simple flight plan and fly the whole thing on autopilot: http://wiki.flightgear.org/Instant_Replay
Like I said, you could then use the replay system to create an test flight than can be easily reproduced - to get going more quickly, you can also use the built-in route manager to create a simple flight plan and fly the whole thing on autopilot: [[Instant Replay]]


You can use time warp mode to speed up simulation time and finish more quickly.
You can use time warp mode to speed up simulation time and finish more quickly.
Line 197: Line 197:
We do have a number of people interested in adding features to support benchmarking/profiling workflows natively:
We do have a number of people interested in adding features to support benchmarking/profiling workflows natively:


http://wiki.flightgear.org/FlightGear_Benchmark
[[FlightGear Benchmark]]
http://wiki.flightgear.org/Testing
[[Testing]]


If that's something you'd like to pursue, feel free to get in touch - it is definitely a worthwhile thing, even regardless of any OSG specific issues, as it will also help with unrelated performance issues.
If that's something you'd like to pursue, feel free to get in touch - it is definitely a worthwhile thing, even regardless of any OSG specific issues, as it will also help with unrelated performance issues.

Navigation menu