Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G


Jump to: navigation, search

Building FlightGear with osgEarth Integration

133 bytes added, 16:13, 9 December 2016
related content
{{forum|81|OsgEarth support in FlightGear}}
{{Note|This article contains outdated instructions still referring to the 2.12 Development of FlightGear osgEarth integration branchestakes place in separate repositories. Meanwhile, those  Updated branches have been updated for FG 2016.2.0: '''2016.2.0-OsgEarth'''
The repositories for simgear- and flightgear- osgEarth are on:
The corresponding fgdata is at:
* https://bitbucket.org/simperative/fgdata/
I noticed some run-time issues, see below: [[#Run-time issues / missing features]]<br/>
Main FG Scenery development seems to go in other directions, also see below: [[#Related content]]
{{ out of date }}
{{ WIP }}
{{Note|This article contains outdated instructions still referring to the 2.12 integration branches. Meanwhile, those branches have been updated for 3.x - and developers are exploring the possibility to get this committed into mainline for the upcoming release.
These should be the public links to the flightgear / osgEarth repositories (note that latest development is found in OsgEarthNext branch)
* {{gitorious source|cmd=git clone|opt=-v -b OsgEarthNext|proj=fg|repo=simgear-osgearth|type=git|post=simgear|full=1}}
* {{gitorious source|cmd=git clone|opt=-v -b OsgEarthNext|proj=fg|repo=flightgear-osgearth|type=git|post=flightgear|full=1}}
* {{gitorious source|cmd=git clone|opt=-v -b OsgEarthNext|proj=fg|repo=fgdata-osgearth|type=git|post=fgdata|full=1}}
* {{gitorious source|cmd=git clone|opt=-v -b OsgEarthNext|proj=fg|repo=fgrun-osgearth|type=git|post=fgrun|full=1}}
Use this version of osgEarth:
* git clone -v -b OsgEarthNext https://github.com/poweroftwo/osgearth.git osgearth
|This is yet another auto-builder for Flightgear and for the time being specific to '''Windows 64bit ONLY'''. It is particularly geared toward building FG with the latest incarnation of the osgEarth integration. The simple minded script attempts to download all needed and hopefully manages conflicts with your user/system environment variables properly. Also, a minimal sized fgdata is downloaded as a starting point.<br/>
== Objective ==
{{FGCquote|people definitely need to understand what they are doing, I would not suggest to actually try this unless people really understand how to patch/build different versions out of SG/FG - people blindly following instructions by copying &amp; pasting shell commands into a terminal window is begging for trouble - as matter of fact, that is why I always encourage folks to set up dedicated "fgfs" accounts to be on the safe side.|{{cite web |url = https://forum.flightgear.org/viewtopic.php?p=300144#p300144 |title = <nowiki> Re: OSGEarth integrate in Linux Ubuntu </nowiki> |author = <nowiki> Hooray </nowiki> |date = Nov 29th, 2016 |added = Nov 29th, 2016 |script_version category= 0.39 }}section}}
|I believe that the OsgEarthNext branch can be built in Linux but seems to require some gyrations to accomplish the setup. see above conversations[.The fgmindata is simply a minimal set of fgdata necessary to run Flightgear, particularly with the osgEarth build without having to download all of the fgdata repository. It contains only a handful of aircraft. I would not recommend dumping the contents on top of an existing fgdata data set unless you are careful about the merging. There are probably only about a dozen or so files that need to be added/merged to the existing fgdata set.]If you have the fgdata git repository cloned already, you might consider adding a remote pointing to the fgdata-osgearth repository. That would allow you to cleanly manage as a separate branch. |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=228114#p228114
|title=<nowiki>Re: Initial FlightGear / </nowiki>
== Background ==
|1= 3.4 is required, based on looking at this: https://gitlab.com/poweroftwo/flightgear-osgearth/commits/OsgEarth-FG3.4-Kdis
However, most SG/FG related changes that would conflict with a merge are relatively trivial, i.e. could be resolved by manual edits pretty easily - I don't think that there's lots of scenery related code that got updated recently, i.e. anything affecting the osgEarth patch - simply because FG/osgEarth overrides much of the standard scenery engine anyway.
I *assume* that merge conflicts should be relatively straightforward to fix up - but it would make sense to look at the latest release branch in that case.
But even that, people would still need to build the whole shebang
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=276886#p276886
| title = <nowiki>Re: 3.2 osgearth or other integrated real time satellite dat</nowiki>
| author = <nowiki>Hooray</nowiki>
| date = Feb 20th, 2016
| added = Feb 20th, 2016
| script_version = 0.25
== Status ==
|1= It is what it is, and being what it is (a set of external patches), it has a certain barrier to entry, and learning curve, associated with it.
People with a working build environment should have no problems getting this to work - the main caveat being currently that some recent sg/fg developments would not be integrated yet.
But otherwise, all the documentation that you can find on the wiki about building FlightGear from source, using git, will be applicable - the main difference is that once you have everything set up and working to build stock fgfs, you would add poweroftwo's gitlab branches as git remotes, and then build an older version of SimGear/FlightGear which contains the corresponding patches.
|2= {{cite web
| url = http://forum.flightgear.org/viewtopic.php?p=276880#p276880
|That's basically the whole idea behind osgEarth. It can do satellite/orthoimagery (that's what you see<br/>advertised the most), but it can also load shapefiles, DEM etc. And it even comes with built-in LOD<br/>algorithms. See their Google+ page for some recent screenshots and videos<br/><br/>: https://plus.google.com/+OsgearthOrg/posts<br/><br/>Jeff has done/is doing excellent working integrating it to FlightGear. I'd definitely encourage anyone<br/>interested in generating scenery on the fly to look into that before anything else. |{{cite web |url=http://sourceforge.net/p/flightgear/mailman/message/33596851/
|title=<nowiki>Re: [Flightgear-devel] Google Code closing down</nowiki>
|author=<nowiki>Gijs de Rooy</nowiki>
== Assumptions Building on Linux (Arch Linux) ==* You already have working branches ''Updated as of SG/FG and FGData, you only need to add the simperative branches as remote tracking branches* $SG_SRC, $FG_SRC and $FG_ROOT must be clean checkouts, commit/stash any unsaved work and check out next/master first.2016-12-09''
== Building While I am using Arch Linux the osgEarth plugin ==* clone the repository:{{#tag:syntaxhighlight|{{gitorious source|cmd=git clone|opt=-v -b 2.12-OsgEarthIntegration|proj=fg|repo=flightgear-osgearth|type=git|post=flightgear|full=1}}| lang = "sh"}}* create a separate build directory* configure via CMake, set '''-DCMAKE_INSTALL_PREFIX''' matching your OSGinstructions should also be applicable on other GNU/SG/FG installation path (not needed if you installed OSG/SG system-wide)* run "make install" (to run a parallel build, pass '''-j x''', where is x the number of cores available/to be used)* next, build SimGearLinux distributions.
== SimGear == Switch into your cloned SimGear repository, make sure Note however that it is in a clean state (commit/stash any changes, switch to next){{#tag:syntaxhighlight|## add a new remote alias {{gitorious source|cmd=git remote add|opt=simperative|proj=fg|repo=simgear-osgearth|type=git|full=1}}this feature should still be considered experimental. The build process can be tedious and things may not work as expected.
## fetch all branchesgit fetch simperativeIn case you never build FG from source you may try to build the regular version first. Understanding what you're doing should greatly help in getting this to work.
## check out a remote tracking branch named topics/osgearth{{FGCquote|git checkout people definitely need to understand what they are doing, I would not suggest to actually try this unless people really understand how to patch/build different versions of SG/FG -people blindly following instructions by copying &amp; pasting shell commands into a terminal window is begging for trouble -track -b topicsas matter of fact, that is why I always encourage folks to set up dedicated "fgfs" accounts to be on the safe side.|{{cite web |url = https:/osgearth simperative/2forum.12-OsgEarthIntegrationflightgear.org/viewtopic.php?p=300144#p300144 | lang title = "sh" <nowiki> Re: OSGEarth integrate in Linux Ubuntu </nowiki> |author = <nowiki> Hooray </nowiki> |date = Nov 29th, 2016 |added = Nov 29th, 2016 |script_version = 0.39 }}
* run '''make -j4 install'''* switch to your FG_SRC directory=== Prerequisites ===
== FlightGear ==Switch into your cloned FlightGear repository, make sure All that it is in a clean state (commit/stash any changes, switch needed to next){{#tag:syntaxhighlight|{{gitorious build regular FlightGear from source|cmd=git remote add|opt=simperative|proj=fg|repo=flightgear-osgearth|type=git|full=1}}git fetch simperative git checkout --track -b topics/osgearth simperative/2.12-OsgEarthIntegration | lang = "sh"}}
== FGData ==See e.g.:
{{* http://wiki.flightgear.org/Building_FlightGear_-_Linux* http://wiki.flightgear.org/Building_FlightGear_-_Debian I used OpenSceneGraph 3.4.0, installed via package manager. Additionally: * gdal* curl* proj* evtl. more ?? (check the configure outputs) Below instructions will use a directory inside the user's home. So it does not conflict with system-wide installed packages. Create a directory for the build process inside your home: <pre>$ mkdir FG-osgE$ mkdir FG-osgE/local #(install dir)$ cd FG-osgE</pre> === osgEarth === Due to a change not yet adapted in simgear-osgearth, the master branch cannot be used currently. Sticking to a specific version would be useful anyway, so I used the tag<code>osgearth-2.8</code>. For this to work, in turn, a commit in simgear-osgearth has to be reverted in the next step. (This situation is not optimal and should be improved.) <pre>$ git clone https:syntaxhighlight|//github.com/gwaldron/osgearth.git{{gitorious source|cmd=$ cd osgearth/$ git remote add|optcheckout -b osgearth-2.8 osgearth-2.8 $ mkdir ../osgearth-build$ cd ../osgearth-build$ cmake ../osgearth -DCMAKE_INSTALL_PREFIX=simperative|proj&quot;$HOME/FG-osgE/local&quot;$ make -jN$ make install$ cd ..</pre>With N being the number of CPU's you want to use, e.g.: <pre>$ make -j3</pre>=fg|repo=fgdata= simgear-osgearth|type=== <pre>$ git|fullclone https://gitlab.com/poweroftwo/simgear-osgearth.git$ cd simgear-osgearth$ git checkout 2016.2.0-OsgEarth</pre>Branch is at commit: <code>0f2bc916f3d4739adc3efe961c9e313ce4b388e7</code><br />Since we use osgEarth-2.8 we need to revert an API change commit. <pre>$ git revert 8777ad51e2ebc3ba5b55112e391e99504bb5d079 (Save the log.) $ mkdir ../simgear-osgearth-build$ cd ../simgear-osgearth-build$ cmake ../simgear-osgearth -DCMAKE_INSTALL_PREFIX=1}}&quot;$HOME/FG-osgE/local&quot;$ make -jN$ make install$ cd ..</pre> === flightgear-osgearth === <pre>$ git fetch simperativeclone https://gitlab.com/poweroftwo/flightgear-osgearth.git$ cd flightgear-osgearth$ git checkout 2016.2.0-OsgEarth$ mkdir ../flightgear-track osgearth-b topicsbuild$ cd ../flightgear-osgearth -build$ SIMGEAR_DIR=&quot;$HOME/FG-osgE/local&quot; cmake ../flightgear-osgearth -DCMAKE_INSTALL_PREFIX=&quot;$HOME/FG-osgE/local&quot;$ make install$ cd ..</pre>I had to correct the gdal includes in <code>src/Viewer/OsgEarthHeightField.cxx</code> and add <code>-DCMAKE_EXE_LINKER_FLAGS=&quot;-lgdal&quot;</code> to the cmake command, but that might be an Arch specific problem.<ref>I found this solution on a french forum: http://fr.flightgear.org/forums/viewtopic.php?id=3383&p=3</ref> Though I cannot find gdal in the CMakeLists.txt so it would evtl. be good/necessary to add it there (probably not that easy). === fgdata-osgearth === Clone or download from https://bitbucket.org/simperative/fgdata. <pre>$ git clone https://bitbucket.org/simperative/fgdata.git$ cd fgdata$ git fetch &amp;&amp; git checkout 2016.2.120-OsgEarthIntegration OsgEarth</pre> | lang = "sh"== Launch ===}}Commands or a script, e.g.: <pre>#!/bin/bash##export LD_LIBRARY_PATH=&quot;$HOME/FG-osgE/local/lib64&quot;export FG_ROOT=&quot;$HOME/FG-osgE/fgdata&quot;export FG_HOME=&quot;$HOME/.fgfs-osgE&quot; local/bin/fgfs</pre> Activate osgEarth via the menu ''View --> Rendering Options --> osgEarth''. === Run-time issues / missing features === * landing lights are misplaced (in the air) on KSFO (others?)* metar data not available (probably easy to fix, maybe something like a wrong url?)* terrain is always lit up (though brightness can be set manually)* aircraft may sink into ground when switching to osgEarth == Related content == Main FG Scenery development seems to go in other directions. It might take some time till the next release though. * [[TerraGear_roadmap]]* https://forum.flightgear.org/viewtopic.php?f=5&t=29693 Next-generation scenery generating? Also there is interesting OSM (openstreetmap) stuff going on, you may want to check out. * [[OpenStreetMap]] == References == <references />
[[Category:Building from source]]
[[Category:Core development projects]]

Navigation menu