![]() Before proceeding any further, please make sure that you are actually able to run other OpenGL-based software/simulators/games, unrelated to FlightGear! The standard procedure A suggestion for a thorough updating procedure can be found at Graphics drivers configuration. Make sure you've got the newest driver for your video card installed and running without errors. ![]() See Troubleshooting performance issues, Problematic Video Cards and FlightGear Hardware Recommendations for more details. Since version 2.6, FlightGear will assume support for certain features that hardware older than 4-5 years might not give (especially graphics cards), so the default settings need to be customized to disable all unsupported features. It's just as well possible that the FlightGear default settings are not supported with your hardware/drivers. After all, it works "out of the box" for most users, so if something's broken it's often a system-specific issue, and yet again, it could be a system configuration that the developers couldn't test - you can help with that!) 2.11)įlightGear crashes are due to a number of reasons, not necessarily to bugs in its code. The bug was solved immediately later (ver. So, if you're on 2.10 and think your card could be old enough, try the minimal startup configuration below: if it keeps crashing, that's definitely it. This bug would prevent using FG even with shaders off! Ironically, this bug comes from a feature introduced to help troubleshooting bugs. If you're using FlightGear 2.10, you're seeing crashes during simulator startup (without seeing the actual aircraft/scenery), and you're using an old enough graphics card, it is possible that your crash is due to a bug in that FG version and to your card lacking GLSL support. If you're feeling "hackish", you can try the solution reported at Unexpected Crashes with Scenery ver.2. Sadly, the solution is keeping a low visibility, or moving to a 64-bit machine with at least 8GB of RAM, which can provide even 45km of visibility. You can also check memory consumption with the tools provided by your OS. To verify this, reduce your visibility (in-sim with View > Level of Detail adjustment and set Bare to 5000 m) and see if it stops crashing. A 32-bit machine can't use more than that memory, and simply kills FlightGear when it asks for more. ![]() Basically, with 4GB of RAM once you could safely use a visibility of a hundred kilometers with Scenery 2.0, 4GB is barely enough for 10 km. ![]() World Scenery 2.0 (the one with CORINE and OpenStreetMap data) highly raised memory requirements with respect to the previous version. (Note that the problem is treated there because it's mostly cause of low performance.) Aborting.Īnd you happen to have a laptop with Optimus Technology (NVidia) or Hybrid Graphics technology (ATI) onboard, you'll find some help at Troubleshooting performance issues#Operating system and driver setup. If your problem is not listed here, please consider adding it after you have solved it! Others like you will be grateful! Optimus/Hybrid graphics technologies for laptops 7 The original idea and future developmentsīefore diving into the real troubleshooting, first try to see if one of the following is your case.5 Debugging Segfaults & Obtaining Backtraces. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |