![]() 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.2.4 Reporting incompatible default settings.1.3 Old graphics cards and FlightGear 2.10.1.2 World Scenery 2.0 and 32-bit machines.1.1 Optimus/Hybrid graphics technologies for laptops.It might take some time till the next release though.Īlso there is interesting OSM (openstreetmap) stuff going on, you may want to check out. Main FG Scenery development seems to go in other directions. aircraft may sink into ground when switching to osgEarth.terrain is always lit up (though brightness can be set manually).metar data not available (probably easy to fix, maybe something like a wrong url?).landing lights are misplaced (in the air) on KSFO (others?).$ git fetch & git checkout 2016.2.0-OsgEarth LaunchĮxport LD_LIBRARY_PATH="$HOME/FG-osgE/local/lib64"Īctivate osgEarth via the menu View -> Rendering Options -> osgEarth. be good/necessary to add it there (probably not that easy). Though I cannot find gdal in the CMakeLists.txt so it would evtl. I had to correct the gdal includes in src/Viewer/OsgEarthHeightField.cxx and add -DCMAKE_EXE_LINKER_FLAGS="-lgdal" to the cmake command, but that might be an Arch specific problem. flightgear-osgearth -DCMAKE_INSTALL_PREFIX="$HOME/FG-osgE/local" $ SIMGEAR_DIR="$HOME/FG-osgE/local" cmake. simgear-osgearth -DCMAKE_INSTALL_PREFIX="$HOME/FG-osgE/local" Since we use osgEarth-2.8 we need to revert an API change commit. ![]() With N being the number of CPU's you want to use, e.g.:īranch is at commit: 0f2bc916f3d4739adc3efe961c9e313ce4b388e7 osgearth -DCMAKE_INSTALL_PREFIX="$HOME/FG-osgE/local" $ git checkout -b osgearth-2.8 osgearth-2.8 ![]() (This situation is not optimal and should be improved.) Sticking to a specific version would be useful anyway, so I used the tag osgearth-2.8.įor this to work, in turn, a commit in simgear-osgearth has to be reverted in the next step. So it does not conflict with system-wide installed packages.Ĭreate a directory for the build process inside your home:ĭue to a change not yet adapted in simgear-osgearth, the master branch cannot be used currently. more ? (check the configure outputs)īelow instructions will use a directory inside the user's home. I used OpenSceneGraph 3.4.0, installed via package manager. Īll that is needed to build regular FlightGear from source.
0 Comments
Leave a Reply. |