by tdammers » Thu Jun 28, 2018 3:29 pm
Define "stopped working". Did the program...
...crash? If so, you may want to try reproducing the problem with a flightgear instance that you started from the command line, this should produce some debug output, and if it crashes with a core dump, you might even be able to load that into a debugger like gdb and get a stack trace (not sure how that stuff works on Windows though).
...freeze? As in, just not respond to input anymore and nothing moves?
...silently exit? So no crash, no backtrace, no nothing, just the program exits?
...keep running, but do something other than what you'd expect? If so, what does it do, and what did you expect?
And then, in order to give people a shot at helping you, you should describe how the problem can be reproduced. Because, you see, for most of us it mostly works just fine; and without reproducing the problem, we can't figure out what goes wrong. So please tell us:
- Which OS you're running on
- Which Flightgear version you're using, where you got it from, and how you installed it
- The exact steps to trigger the problem (which aircraft did you use, where did you spawn, which setting did you use, what did you do in-sim)