Flightgear Scenery USA downloaden install#
Flightgear Scenery USA downloaden manual#
Flightgear Scenery USA downloaden simulator#
Flightgear Scenery USA downloaden download#

Flightgear Scenery USA downloaden install#

Most README, INSTALL and “manual” writers assume that every reader is as skilled as they are themselves in the field of compilation, debugging and installation. From those examples i could have been able to deduct the necceasary information myself. One of the main reason that frustrated me, was the serious lack of EXACT documentation and real life EXAMPLES. I have tried several time to recompile, make and make install the OpenVrml Packege, but i kept crashing into “lack of real detailed documentation”. This error was caused by the missing OpenVrml (package,plugin) as a part of the OpenSceneGraph package. Only the package crashed, because it gave an error message like this: “… can not find plugin to load model data.” “starting… Loading scenery data… etc etc”.

Flightgear Scenery USA downloaden simulator#

I have gotten to the point the FlightGear simulator started with a black square screen, and a text line below that mentioned:.

Here a “progress report” on my Flightgear installation quest: Or better still look at the spec and see if you can tweak it from the src.rpm.Īlso naughty naughty it is generally a bad idea to do make and. This may actually be better but you may need to tweak the config if it is using /usr/local or it may install here which won’t completely matter.

Flightgear Scenery USA downloaden download#

Having had a look at the spec it looks like /usr/something I suspect /usr/share/FlightGear… If you really want to know download the rpm and look at the structure… Index of /repositories/games/openSUSE_11.1Īlso rather than using make install look at checkinstall. One other thing look at terrasync for the scenery. It will generate the commandline and you can see it before processing(And it has a nice gui). So as some of the first few flags, you can pass it with commandline flags… but… you have fgrun use this to start with. (beta) soo many I couldn’t post it here without getting told too many chars…

$FG_HOME/Scenery:$FG_ROOT/Scenery:$FG_ROOT/WorldSceneryĪs for the where well that can be kind of up to you there is nothing stopping you running it from you home environment.(May take a some configs at configure though)Īs for the rest Flightgear has more command flags than I’ve ever met… Setenv FG_ROOT=/usr/local/share/FlightGear/data Setenv FG_HOME=/usr/local/share/FlightGear usr/local/share/FlightGear/lib:$LD_LIBRARY_PATH LD_LIBRARY_PATH=/usr/local/share/FlightGear/lib:$LD_LIBRARY_PATHįG_SCENERY=$FG_ROOT/Scenery:$FG_ROOT/WorldScenery *To add these in the Bourne shell (and compatibles):

Flightgear Scenery USA downloaden manual#

This is what the manual vaguely writes about it: In which FILE at which LOCATION must i add these settings?

Where and how do i need to add the FlightGear environment Variables?.

“/path/to/data”…(which directory of the data? which files must in in that directory?)īut no-one tells EXACTLY to which directory and which files those “paths to…” must point! (like /usr/share/flightgear/ exeutable).

“/path/to/FlightGear”…(what? directory? executable file?).

On the FlightGear website i encounter “stupid vague descriptions” like: Which commandline options to i need to add to fgfs of fgrun, so that everything works correctly and Flightgear starts up. Question (if you have FlightGear already up-and-running on your system):Ĭan you tell me where all your Plib,OpenSceneGraph, Simgear, FlightGear and FlightGear_datafiles have been installed on your machine? Trying to put all compiled pieces into the right place, directory configure without any prefixes or options!įinished all the making, building and compiling of all packages root/download/flightgear/openscenegraph/OpenSceneGraph/… root/download/flightgear/Simgear/Simgear-1.9.1/… root/download/flightgear/flightgear_program/FlightGear-1.9.1 I’ve untarred all packages in their own directories like:

I am busy installing FlightGear completely “from sourcecode” by manually downloading all tar-balls.