40
edits
(+quote) |
(related content) |
||
(3 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
{{ | {{incomplete}} | ||
{{forum|81|OsgEarth support in FlightGear}} | {{forum|81|OsgEarth support in FlightGear}} | ||
{{Note|Development of FlightGear osgEarth integration takes place in separate repositories. | |||
Updated branches for FG 2016.2.0: '''2016.2.0-OsgEarth''' | |||
* | |||
* | The repositories for simgear- and flightgear- osgEarth are on: | ||
* https://gitlab.com/users/poweroftwo/projects | |||
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]] | |||
}} | |||
<!-- | |||
{{FGCquote | {{FGCquote | ||
|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/> | |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/> | ||
Line 32: | Line 36: | ||
== Objective == | == Objective == | ||
{{ | {{out of date|category=section}} | ||
}} | |||
{{FGCquote | {{FGCquote | ||
Line 63: | Line 57: | ||
{{FGCquote | {{FGCquote | ||
|I believe that the OsgEarthNext branch can be built in Linux but seems to require some gyrations to accomplish the setup. | |I believe that the OsgEarthNext branch can be built in Linux but seems to require some gyrations to accomplish the setup. [...] | ||
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 | |||
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. | |||
|title=<nowiki>Re: Initial FlightGear / </nowiki> | |title=<nowiki>Re: Initial FlightGear / </nowiki> | ||
|author=<nowiki>poweroftwo</nowiki> | |author=<nowiki>poweroftwo</nowiki> | ||
Line 74: | Line 65: | ||
}} | }} | ||
== Status == | == Status == | ||
{{FGCquote | {{FGCquote | ||
|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. | |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. | ||
Line 97: | Line 74: | ||
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. | 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. | 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 | |2= {{cite web | ||
| url = http://forum.flightgear.org/viewtopic.php?p=276880#p276880 | | url = http://forum.flightgear.org/viewtopic.php?p=276880#p276880 | ||
Line 110: | Line 85: | ||
{{FGCquote | {{FGCquote | ||
|That's basically the whole idea behind osgEarth. It can do satellite/orthoimagery (that's what you see | |That's basically the whole idea behind osgEarth. It can do satellite/orthoimagery (that's what you see advertised the most), but it can also load shapefiles, DEM etc. And it even comes with built-in LOD algorithms. See their Google+ page for some recent screenshots and videos: https://plus.google.com/+OsgearthOrg/posts<br/> | ||
advertised the most), but it can also load shapefiles, DEM etc. And it even comes with built-in LOD | Jeff has done/is doing excellent working integrating it to FlightGear. I'd definitely encourage anyone 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/ | ||
algorithms. See their Google+ page for some recent screenshots and videos | |||
https://plus.google.com/+OsgearthOrg/posts | |||
<br/> | |||
Jeff has done/is doing excellent working integrating it to FlightGear. I'd definitely encourage anyone | |||
interested in generating scenery on the fly to look into that before anything else. | |||
|title=<nowiki>Re: [Flightgear-devel] Google Code closing down</nowiki> | |title=<nowiki>Re: [Flightgear-devel] Google Code closing down</nowiki> | ||
|author=<nowiki>Gijs de Rooy</nowiki> | |author=<nowiki>Gijs de Rooy</nowiki> | ||
Line 125: | Line 93: | ||
}} | }} | ||
== | == Building on Linux (Arch Linux) == | ||
''Updated as of 2016-12-09'' | |||
While I am using Arch Linux the build instructions should also be applicable on other GNU/Linux distributions. | |||
{{ | Note however that this feature should still be considered experimental. The build process can be tedious and things may not work as expected. | ||
{{ | |||
In 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. | |||
{{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 of SG/FG - people blindly following instructions by copying & 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 = 0.39 | |||
}} | |||
}} | }} | ||
== | === Prerequisites === | ||
All that is needed to build regular FlightGear from source. | |||
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://github.com/gwaldron/osgearth.git | |||
$ cd osgearth/ | |||
$ git checkout -b osgearth-2.8 osgearth-2.8 | |||
$ mkdir ../osgearth-build | |||
$ cd ../osgearth-build | |||
$ cmake ../osgearth -DCMAKE_INSTALL_PREFIX="$HOME/FG-osgE/local" | |||
$ make -jN | |||
$ make install | |||
$ cd ..</pre> | |||
With N being the number of CPU's you want to use, e.g.: | |||
<pre>$ make -j3</pre> | |||
=== simgear-osgearth === | |||
<pre>$ git clone 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="$HOME/FG-osgE/local" | |||
$ make -jN | |||
$ make install | |||
$ cd ..</pre> | |||
=== flightgear-osgearth === | |||
<pre>$ git clone https://gitlab.com/poweroftwo/flightgear-osgearth.git | |||
$ cd flightgear-osgearth | |||
$ git checkout 2016.2.0-OsgEarth | |||
$ mkdir ../flightgear-osgearth-build | |||
$ cd ../flightgear-osgearth-build | |||
$ SIMGEAR_DIR="$HOME/FG-osgE/local" cmake ../flightgear-osgearth -DCMAKE_INSTALL_PREFIX="$HOME/FG-osgE/local" | |||
$ 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="-lgdal"</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 | |||
git checkout -- | $ cd fgdata | ||
$ git fetch && git checkout 2016.2.0-OsgEarth</pre> | |||
=== Launch === | |||
Commands or a script, e.g.: | |||
<pre>#!/bin/bash | |||
# | |||
# | |||
export LD_LIBRARY_PATH="$HOME/FG-osgE/local/lib64" | |||
export FG_ROOT="$HOME/FG-osgE/fgdata" | |||
export FG_HOME="$HOME/.fgfs-osgE" | |||
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:Building from source]] | ||
[[Category:Core development projects]] | [[Category:Core development projects]] |
edits