https://wiki.flightgear.org/w/api.php?action=feedcontributions&feedformat=atom&user=RaazeerFlightGear wiki - User contributions [en]2026-04-03T17:39:04ZUser contributionsMediaWiki 1.39.6https://wiki.flightgear.org/w/index.php?title=FlightGear_Git_for_laymen&diff=62548FlightGear Git for laymen2013-08-30T22:04:11Z<p>Raazeer: No folder creation needed</p>
<hr />
<div>= Git for Laymen =<br />
Git, and its fellow Version Control Systems are a domain of geeks - who are patently incapable of explaining anything in simple terms most of the time. Because of this, many a layman has fled in terror from what is, when all's said and done, easy to use.<br />
<br />
== What is Git? ==<br />
Git is a Version Control System, meaning that it ''tracks changes to files'' - in other words, if you make a change to a file known to Git, or ''commit'' the change as the expert would put it, Git stores what parts of the file have changed between the last version and the current version. That makes it possible to do a lot of great things, the most mind-soothing among them being the ability to get the old version back in case it turns out you've broken something.<br />
<br />
== What does Git do for me? == <br />
Another thing Git does is ''distribute change''. That means, additionally to committing things ''to'' the Git repository, you can also get the changes others made ''from'' the Git repository - thus keeping your local copy of whatever is kept in the repository current. That is the use most laymen will be most interested in. In practical terms, that means you can at any time get all the changes the developers made just by updating your copy from the repository - instead of having to re-download the whole data (or trying to scrape together the changed files manually, a path that leads to insanity without any stop signs or speed limits). With a large repository like Flightgear Base Data for example, the difference is a few kilobytes instead of 15 gigabytes.<br />
<br />
== What do I need to use a Git repository that way? ==<br />
Basicly, all you have to do is install a git client on your machine. For windows users, '''TrotoiseGit''', which is free for download, would be the option of choice, for Linux/Unix users it's just plain '''git''', available from your favorite software repository. Both are rather trivial to set up - the only confusing thing is that they may require you to supply a name and an email adress on install - don't get panicky, it's just a prerequisite Git has for use cases you'll never see unless you decide to come to the geek side of life. Needs to be done, just like you have to klick "I accept" to install most (proprietary) software.<br />
<br />
== How do I use the git repository to update Flightgear stuff? ==<br />
Git has a score of '''very''' confusing options that allow you to do stuff that boggles the mind of even an established geek. To achieve what you, the layman, will want to do, a total of two commands are totally sufficient. <br />
=== Initial cloning ===<br />
The first step to using the Git data for your own purposes is to grab a copy from the repository. Here's how to do that. <br />
<br />
This description uses the linux commandline version of the git commands, but in principle you do the same with TrotoiseGit, only the commands are in the context menu there.<br />
<br />
First, navigate to where you want the checkout to live<br />
<br />
$ cd /home/user/data/git-repos<br />
<br />
Then, you clone the repository. To do that, you have to know the URL of the repository you want to be cloning. Those are found on the [https://gitorious.org/fg Flightgear Gitorious page].For this example, we'll be using the Flightgear Base Data repository '''fgdata''', but the principle is exactly the same for simgear or flightgear source. All that changes is the URL to clone.<br />
<nowiki>$ git clone git://gitorious.org/fg/fgdata.git</nowiki><br />
Note also how you don't have to create a directory for the checkout. A well-setup git repository does that for you with the clone command. <br />
<br />
After you hit enter on that line, it's time to lean back and get a cup of coffee, because that specific repo is really quite ''huge'' - almost 15 GB of data as of writing this. (There is a better method for cloning huge repos like this, it's described on this page: [[FlightGear and Git#Special for fgdata:|FlightGear and Git]],but it's likely that's exactly the page you fled here from.)<br />
<br />
Now, once that operation completes (without errors hopefully), you're done! Try<br />
$ cd fgdata<br />
$ ls<br />
and enjoy.<br />
<br />
=== Keeping it current ===<br />
Up to this point, we haven't done anything we couldn't have achieved with an archive file. That is, we have, but not in a way you, a layman, are in any position to recognize. Now is the time to take advantage of this fact.<br />
<br />
Let's say you've buggered the guys in the IRC channel until finally somebody has fixed the bug in your favorite airplane just to get rid of you. Now how do you personally get that change? If you had been downloading an archive, you'd have to wait for the archive to be rebuilt, download the whole thing again, and iron it on over the old data. Not so with Git - here's what to do. Navigate to the place where your repository lives, in our example like this:<br />
$ cd /home/user/git-repos/fgdata<br />
Note that this time, we're cding ''into'' the directory.<br />
Now get all the changes since you cloned the repository like this:<br />
$ git pull<br />
That's all. Watch the numbers dance - it'll be much quicker this time than the last time, because only the changes in the files need to be transmitted - and once the command returns, you can jump into your now (hopefully) bug-free airplane and take her for a spin<br />
<br />
== A word about troubleshooting ==<br />
This wouldn't be a good article without a word about troubleshooting. The process described above is really rather reliable and will work 99% of the time, but sometimes it '''does''' break down - mostly because you inadvertedly changed a file that somebody else changed in the "official" repository. If Git finds a conflict, e.g. a file having been edited by you AND somebody else since the last pull - it will refuse to just clobber the local changes. <br />
<br />
Now - if you DID change the file actively, it's time you went over to a ''real'' git tutorial and found out about merging changes. If you didn't, you can revert the changes to the baseline of the repository, that is, reset the file(s) to how it was when you last pulled the changes:<br />
$ cd /home/user/git-repos/fgdata<br />
$ git reset<br />
$ git pull<br />
If it works, all is fine. If Git still complains, e.g. about not being able to "fast-forward" the changes, you'll have to tell it to try a little harder (and with less respect to what it might clobber) to reset your working copy:<br />
$ git reset --hard<br />
Sometimes, IT is simple. This command should undo everything you did in your working copy, that is, get the entire working copy back to the state it was when you last pulled. In 99% of the trouble, this is the end of it, and a <br />
$ git pull<br />
will work. If it still doesn't, your local clone has gotten a nasty dent somewhere. In this case, you can either seriously dive into git and fix it, or delete the whole repository folder and clone anew:<br />
$ cd /home/user/git-repos/<br />
$ rm -rf fgdata<br />
<nowiki>$ git clone git://gitorious.org/fg/fgdata.git</nowiki><br />
<br />
== Where do I take it from here? ==<br />
To be honest: for most ''laymen'' this is the end of the trail, and you'll live happily ever after. <br />
<br />
If however your interest has been piqued and you want to know more about Git in particular and VCS in general - and how they can help you tweak and twitch your copy of flightgear - more power to you. <br />
<br />
First, I'd recommend browsing the net for a good git tutorial - a very good one is available from Linus Torvalds, the famous inventor of Linux - and father of Git - but you'll have to find out which one works for '''you'''. Also read [[FlightGear and Git]], the official wiki page on doing Git the Flightgear way.</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_Git_for_laymen&diff=62547FlightGear Git for laymen2013-08-30T21:59:33Z<p>Raazeer: /* What do I need to use a Git repository that way? */</p>
<hr />
<div>= Git for Laymen =<br />
Git, and its fellow Version Control Systems are a domain of geeks - who are patently incapable of explaining anything in simple terms most of the time. Because of this, many a layman has fled in terror from what is, when all's said and done, easy to use.<br />
<br />
== What is Git? ==<br />
Git is a Version Control System, meaning that it ''tracks changes to files'' - in other words, if you make a change to a file known to Git, or ''commit'' the change as the expert would put it, Git stores what parts of the file have changed between the last version and the current version. That makes it possible to do a lot of great things, the most mind-soothing among them being the ability to get the old version back in case it turns out you've broken something.<br />
<br />
== What does Git do for me? == <br />
Another thing Git does is ''distribute change''. That means, additionally to committing things ''to'' the Git repository, you can also get the changes others made ''from'' the Git repository - thus keeping your local copy of whatever is kept in the repository current. That is the use most laymen will be most interested in. In practical terms, that means you can at any time get all the changes the developers made just by updating your copy from the repository - instead of having to re-download the whole data (or trying to scrape together the changed files manually, a path that leads to insanity without any stop signs or speed limits). With a large repository like Flightgear Base Data for example, the difference is a few kilobytes instead of 15 gigabytes.<br />
<br />
== What do I need to use a Git repository that way? ==<br />
Basicly, all you have to do is install a git client on your machine. For windows users, '''TrotoiseGit''', which is free for download, would be the option of choice, for Linux/Unix users it's just plain '''git''', available from your favorite software repository. Both are rather trivial to set up - the only confusing thing is that they may require you to supply a name and an email adress on install - don't get panicky, it's just a prerequisite Git has for use cases you'll never see unless you decide to come to the geek side of life. Needs to be done, just like you have to klick "I accept" to install most (proprietary) software.<br />
<br />
== How do I use the git repository to update Flightgear stuff? ==<br />
Git has a score of '''very''' confusing options that allow you to do stuff that boggles the mind of even an established geek. To achieve what you, the layman, will want to do, a total of two commands are totally sufficient. <br />
=== Initial cloning ===<br />
The first step to using the Git data for your own purposes is to grab a copy from the repository. Here's how to do that<br />
This description uses the linux commandline version of the git commands, but in principle you do the same with TrotoiseGit, only the commands are in the context menu there.<br />
<br />
First, navigate to where you want the checkout to live<br />
<br />
$ cd /home/user/data/git-repos<br />
<br />
Then, you clone the repository. To do that, you have to know the URL of the repository you want to be cloning. Those are found on the [https://gitorious.org/fg Flightgear Gitorious page]. For this example, we'll be using the Flightgear Base Data repository '''fgdata''', but the principle is exactly the same for simgear or flightgear source. All that changes is the URL to clone.<br />
<nowiki>$ git clone git://gitorious.org/fg/fgdata.git</nowiki><br />
After that, it's time to lean back and get a cup of coffee, because that specific repo is really quite ''huge'' - almost 15 GB of data as of writing this. (There is a better method for cloning huge repos like this, it's described on this page: [[FlightGear and Git#Special for fgdata:|FlightGear and Git]],but it's likely that's exactly the page you fled here from.)<br />
<br />
Now, once that operation completes (without errors hopefully), you're done! Try<br />
$ cd fgdata<br />
$ ls<br />
and enjoy.<br />
<br />
=== Keeping it current ===<br />
Up to this point, we haven't done anything we couldn't have achieved with an archive file. That is, we have, but not in a way you, a layman, are in any position to recognize. Now is the time to take advantage of this fact.<br />
<br />
Let's say you've buggered the guys in the IRC channel until finally somebody has fixed the bug in your favorite airplane just to get rid of you. Now how do you personally get that change? If you had been downloading an archive, you'd have to wait for the archive to be rebuilt, download the whole thing again, and iron it on over the old data. Not so with Git - here's what to do. Navigate to the place where your repository lives, in our example like this:<br />
$ cd /home/user/git-repos/fgdata<br />
Note that this time, we're cding ''into'' the directory.<br />
Now get all the changes since you cloned the repository like this:<br />
$ git pull<br />
That's all. Watch the numbers dance - it'll be much quicker this time than the last time, because only the changes in the files need to be transmitted - and once the command returns, you can jump into your now (hopefully) bug-free airplane and take her for a spin<br />
<br />
== A word about troubleshooting ==<br />
This wouldn't be a good article without a word about troubleshooting. The process described above is really rather reliable and will work 99% of the time, but sometimes it '''does''' break down - mostly because you inadvertedly changed a file that somebody else changed in the "official" repository. If Git finds a conflict, e.g. a file having been edited by you AND somebody else since the last pull - it will refuse to just clobber the local changes. <br />
<br />
Now - if you DID change the file actively, it's time you went over to a ''real'' git tutorial and found out about merging changes. If you didn't, you can revert the changes to the baseline of the repository, that is, reset the file(s) to how it was when you last pulled the changes:<br />
$ cd /home/user/git-repos/fgdata<br />
$ git reset<br />
$ git pull<br />
If it works, all is fine. If Git still complains, e.g. about not being able to "fast-forward" the changes, you'll have to tell it to try a little harder (and with less respect to what it might clobber) to reset your working copy:<br />
$ git reset --hard<br />
Sometimes, IT is simple. This command should undo everything you did in your working copy, that is, get the entire working copy back to the state it was when you last pulled. In 99% of the trouble, this is the end of it, and a <br />
$ git pull<br />
will work. If it still doesn't, your local clone has gotten a nasty dent somewhere. In this case, you can either seriously dive into git and fix it, or delete the whole repository folder and clone anew:<br />
$ cd /home/user/git-repos/<br />
$ rm -rf fgdata<br />
<nowiki>$ git clone git://gitorious.org/fg/fgdata.git</nowiki><br />
<br />
== Where do I take it from here? ==<br />
To be honest: for most ''laymen'' this is the end of the trail, and you'll live happily ever after. <br />
<br />
If however your interest has been piqued and you want to know more about Git in particular and VCS in general - and how they can help you tweak and twitch your copy of flightgear - more power to you. <br />
<br />
First, I'd recommend browsing the net for a good git tutorial - a very good one is available from Linus Torvalds, the famous inventor of Linux - and father of Git - but you'll have to find out which one works for '''you'''. Also read [[FlightGear and Git]], the official wiki page on doing Git the Flightgear way.</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_Git&diff=62324FlightGear Git2013-08-18T17:22:22Z<p>Raazeer: Added a link to the new Git for Laymen article</p>
<hr />
<div>{{Git}}<br />
If you are a non-geek and are confused by all this, try this page first: [[Git for Laymen]]<br />
<br />
'''Git''' is a version control system, used by the [[FlightGear]] project to store all of the files required to build FlightGear. This includes all the programs, the data (e.g. [[aircraft]]), supporting tools, etc. Git tracks updates to every file, as developers from around the world work together concurrently to create new versions.<br />
<br />
While new FlightGear features and additions are in development, they are available from Git before they are available in the standard release version. Using Git allows users to build the newest possible version of FlightGear from the latest source files, to experiment with new aircraft or other features. However, it's not a beginner's tool. Using Git can expose the user to unstable features that show ugly error messages, or crash the computer. <br />
<br />
In May 2010, after a hardware failure on the [[CVS]] servers, the FlightGear project changed its version control system from CVS to Git. The Git repositories are located at [http://gitorious.org/fg Gitorious] and a mirror is hosted at the [http://mapserver.flightgear.org/git/?p=fgdata;a=summary Mapserver].<br />
<br />
Due to the "recent" switch, we are currently doing our best on providing manuals for obtaining FlightGear through Git. The following articles belong to that "work in progress":<br />
* [[FlightGear Git on Mac OS X]]<br />
* [[FlightGear Git on Windows]]<br />
* [[Howto:Start using git]] provides a quick introduction to using a "source code management system"<br />
<br />
== Motivation ==<br />
Much has been written on the advantages of Git over CVS. For the FlightGear project, some advantages are:<br />
* Much better support for branches and merging branches. This is especially important for creating bug-fix releases for major releases while still allowing work on the next major release to continue. It is also very nice for a developer's personal work-flow.<br />
* Easier path for contributors to submit changes and developers to integrate them.<br />
* Much better support for everyday tasks like searching the project history for changes, viewing changes, bisecting the project history to find the original source of a bug.<br />
<br />
Also, as noted before, the CVS servers had a hardware failure on May 2010, speeding up FlightGear's change to Git.<br />
<br />
== Manipulating the GIT ==<br />
=== Work-flow Overview===<br />
{|<br />
||[[File:GIT-Workflow.png]]<br />
|}<br />
For a detailed description see the description of the four repositories (A,B,C,D) in the following chapters.<br />
<br />
=== A) Repositories and branches ===<br />
For historical reasons there continue to be separate repositories for [https://gitorious.org/fg/simgear '''''SimGear'''''] and [https://gitorious.org/fg/flightgear '''''FlightGear''''']. For most users and developers the most interesting ones for those 2 are:<br />
* '''''next''''': The current tip of new development. This branch should always compile and run, but various things could be broken.<br />
* '''''release/*''''': The branch subdirectory containing former and ''(if there is already defined one)'' upcoming releases.<br />
For all available branches, see [https://gitorious.org/fg/simgear/trees SimGear branches] and/or [https://gitorious.org/fg/flightgear/trees FlightGear branches]<br />
<br />
FlightGear [https://gitorious.org/fg/fgdata '''''data''''''] branches of interest are:<br />
* '''''master''''': The one that is used with the '''''next''''' branch of the code.<br />
* '''''release/*''''': The one that is used with the '''''release''''' branch of the code.<br />
For all available branches see https://gitorious.org/fg/fgdata/trees<br />
<br />
In addition, there's a '''fgmeta'' project, intended as a super-project to track compatible simgear & flightgear commits, particular in the context of release and stable branches. "fgmeta" contains the main repositories as git submodules:<br />
* simgear<br />
* flightgear<br />
* fgrun<br />
<br />
To work with the fgmeta project, you'll need to<br />
* clone the fgmeta project: git://gitorious.org/fg/fgmeta.git<br />
* run "git submodule init"<br />
* run "git submodule update"<br />
<br />
For other available projects have a look at our [http://gitorious.org/fg gitorious.org]. Use the "Source tree" button to see all available branches unique to those projects.<br />
<br />
'''''Warning:''''' <br />
* The "fgdata" project will be used in all following examples - thus the "Prime" local repository will always be named "master" (the '''code''' repositories like SimGear/FlightGear will usually use '''next''' instead of '''master''' however)! <br />
* If you test changes, make sure all branches have the same status - otherwise your setup may not be functional!<br />
<br />
=== B) Create your own workspace on Gitorious ===<br />
Prior to be able to manipulate GIT-data you must be a registered user and be logged in as such. See<br />
: https://gitorious.org/users/new <br />
: https://gitorious.org/login<br />
<br />
Then check on http://gitorious.org/fg for the available projects. See e.g.:<br />
* flightgear<br />
* simgear<br />
* fgdata<br />
* getstart<br />
* etc.<br />
<br />
Create your own "GIT-Clone" ''(as a space to work in)'', by activating the "Clone repository" button of the wanted project. By default you will be cloning the '''''next''''' or '''''master''''' branch of that project --> that is the actual repository including the newest, not yet formally distributed, changes. That is probably what you want if you want to <br />
* assist with reporting bugs before they are released as a proper release version<br />
* or participate in the design<br />
* or similar<br />
<br />
The created GIT-clone will be on you private page '''https://gitorious.org/~<small>YourUID</small>'''<br />
<small>''("YourUID" being your ID you logged in with, and do not forget the "~" in front of it!)''</small>)<br />
<br />
=== C) Create a "master" on your local computer ===<br />
<font color="red">'''Note:'''If you should happen to be already using [[Scripted Compilation on Linux Debian/Ubuntu]], you can skip these steps, because you'll already have a cloned fgdata repo.</font><br />
<br />
''All the following is shown as performed in an UBUNTU "Terminal" environment! Please adapt especially the directory trees according to your Operating-System!''<br />
# Create a unique folder on your computer, e.g. "..'''\GIT'''"<br />
# Change into that folder and use the following "git clone" commands to clone the wanted repository<br />
#* ''if you need/want more informations about unique GIT-commands, input "git help [command]"'' <small>(e.g. "git help clone")</small><br />
# Use one of the following commands (or similar) from within that "..'''\GIT'''"-folder:<br />
:*for cloning '''''SimGear''''' use:<br />
::'''<nowiki>git clone git://gitorious.org/fg/simgear.git</nowiki>''' [target]<br />
::<small>To successfully compile <code>fgfs</code> Flight- and Sim-Gear's ''working tree'' they both must have the same state.</small><br />
<br />
:*for cloning '''''FlightGear''''' use:<br />
::'''<nowiki>git clone git://gitorious.org/fg/flightgear.git</nowiki>''' [target]<br />
::<small>To successfully compile <code>fgfs</code> Flight- and Sim-Gear's ''working tree'' they both must have the same state.</small><br />
<br />
:*for cloning '''''fgdata''''' use:<br />
::'''<nowiki>git clone git://gitorious.org/fg/fgdata.git</nowiki>''' [target]<br />
<br />
:By executing one of the above commands the folder ''target'' will be created and a clone will be stored inside it. If no ''target'' is given the new folder's name is the GIT-name <small>''(i.e.: "../GIT/simgear", "../GIT/flightgear", "../GIT/fgdata")''</small>.<br />
<br />
'''<code>cd</code>''' into the new folder [target]<br />
:You are now inside the ''working tree'' of this git repository. The repository itself is stored inside the subfolder <tt>../GIT/[target]/.git</tt>, which we must not edit manually. Git will take care of that.<br />
:<small>Notice the "'''.'''" in front of the name: In Linux that indicates a hidden file, for which you might have to enable "show hidden files"!</small><br />
<br />
;<code>git branch</code><br />
: will show the active [[FlightGear_and_Git#A.29_Repositories_and_branches|branches]]. e.g.<br />
..GIT/fgdata$ '''git branch'''<br />
* master<br />
master.local <small>''(<-- this branch will not be there initially!)''</small><br />
:Right after download the active GIT-repository-branch will be <tt>'''"next"'''</tt>, which in the example is called "master". The "'''*'''" in front means that this is now the active one! i.e. the content of the active ''working tree'' is the bleeding edge of the source code.<br />
<br />
;<code>git branch -a</code><br />
: will list '''''all''''' branches of a git repository. The one marked with an asterisk (*) is the active one. e.g.:<br />
..GIT/fgdata$ '''git branch -a'''<br />
* master<br />
master.local <small>''(<-- this will not be there initially!)''</small><br />
remotes/origin/HEAD -> origin/master<br />
remotes/origin/PRE_OSG_PLIB_20061029<br />
remotes/origin/Short_Empire-public<br />
remotes/origin/Work<br />
remotes/origin/master<br />
remotes/origin/release/2.4.0<br />
remotes/origin/release/2.6.0<br />
remotes/origin/releases/2.2.0<br />
<br />
You now have your local "GIT-master".<br />
'''But:''' To make individual changes ''(like editing a joystick file)'', add a plane to fgdata or patch the source code. It is always recommended to create a local branch inside that "master" repository. In the chapter "[[FlightGear and Git#Edit|Edit]]" we will describe a way to achieve this. But have in mind, that this is very basic and only suits for users who have minor changes. <br />
<br />
==== Special for '''fgdata''':====<br />
At the time of writing the data repository is about ''3.4 GB''. Continuing an interrupted cloning of a repository is '''not supported''' within git. Therefore, if you have a slow or unstable connection to the internet, it is recommended to download the [[FlightGear and Git#fgdata.bundle|fgdata.bundle]].<br />
<br />
Also have in mind, that the repository plus the ''working tree'' will be more than twice the size of the download on your local filesystem.<br />
<br />
There is neither a <tt>"next"</tt> branch nor any tags in that repository. If e.g. you want to build FlightGear 2.0.0 you must fetch the data (FlightGear-data-2.0.0.tar.bz2) at one of the [http://flightgear.org/mirrors.html mirrors].<br />
<br />
==== fgdata.bundle ====<br />
For the FlightGear-data there is a [http://www.kernel.org/pub/software/scm/git/docs/git-bundle.html git-bundle] (snapshot) [http://mxchange.org:23456/file?info_hash=%BF%FF%AB%0C%16%BF%8Eg%B8%A0%CFw%01%0A%5D%8F%3F%81%96y torrent] ([http://mxchange.org:23456/ tracker]; [http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.md5 md5]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha1 sha1]|[http://flightgear.mxchange.org/pub/fgfs/fgdata.bundle.sha512 sha512]) available. This way you can resume interrupted downloads. After unpacking it only a comparatively small amount of data has to be transferred from the git server to synchronize your repository. See also the Develop sections in [[FlightGear Git on Windows]].<br />
<br />
Do the following steps to extract the bundle and bring the repository up to date:<br />
$ git '''clone fgdata.bundle fgdata'''<br />
$ cd fgdata<br />
$ git checkout -b master-tmp<br />
Switched to a new branch 'master-tmp'<br />
$ git remote rm origin<br />
$ git remote add origin git://gitorious.org/fg/fgdata<br />
$ git fetch origin<br />
$ git branch --track master origin/master<br />
$ git checkout master<br />
$ git branch -D master-tmp<br />
<br />
If you get an error at '''<code>git fetch origin</code>''' try:<br />
$ git remote rm origin<br />
$ git remote add origin git://mapserver.flightgear.org/fgdata/<br />
$ git fetch origin<br />
<br />
You should be suspicious if based on the printed progress you estimate the data download during the fetch will exceed 1GB (assuming the bundle is not terribly outdated).<br />
<br />
=== D) Edit and commit data ===<br />
====Edit====<br />
Switch into the branch in which you want to edit your changes ''(without affecting your master yet!)''. We will use for that branch the name "master.local". Thus:<br />
;<code>git checkout master</code><br />
..GIT/fgdata$ '''git checkout master'''<br />
Switched to branch 'master'<br />
:will change the active [[FlightGear and Git#Repositories and Branches|branch]] to <tt>master</tt>. Means, that the content of the ''working tree'' will be changed to that state.<br />
:In case you get an error like<br />
GIT/fgdata$ '''git checkout master'''<br />
Already on 'master'<br />
Your branch is ahead of 'origin/master' by 2 commits.<br />
:you should re-sync your master with e.g.:<br />
:;<code>git fetch</code><br />
<br />
;<code>git checkout -b master.local master</code><br />
..GIT/fgdata$ '''git checkout -b master.local master'''<br />
Switched to a new branch 'master.local'<br />
:Generates the new "master.local" and switches to it.<br />
:In case you get the response:<br />
fatal: A branch named 'master.local' already exists.<br />
::*you have to define another name for that branch<br />
::*or delete it:<br />
::*:Try first: '''''"git branch master.local -d"''''' ⇒ that will delete it if it is "clean"<br />
::*:If needed do: '''''"git branch -D master.local"''''' ⇒ that forces a delete - <span style="color:red">'''''even if there is uncommitted work in it !!'''''</span><br />
<br /><span style="color:green"><br />
'''''You may now<br />
*'''''apply your planned changes''''' into the affected "/GIT/subdir"<br />
*start FlightGear to verify they are proper/functional<br />
*then check what was done:'''''<br />
</span><br />
<br />
;<code>git status</code><br />
:<small>the output may take some time to appear!</small><br />
:see e.g. a dummy-example:<br />
..GIT/fgdata$ '''git status'''<br />
# On branch master.local<br />
# Changes not staged for commit:<br />
# (use "git add <file>..." to update what will be committed)<br />
# (use "git checkout -- <file>..." to discard changes in working directory)<br />
#<br />
# modified: Aircraft/ATC-ML/Version<br />
#<br />
# Untracked files:<br />
# (use "git add <file>..." to include in what will be committed)<br />
#<br />
# Aircraft/ATC-ML/Version (copy)<br />
# Aircraft/DUMMY/<br />
no changes added to commit (use "git add" and/or "git commit -a")<br />
...... etc.<br />
:This gives you a list of files that have been altered or that are new. In the above ''(dummy example)'' you see:<br />
:*the already existing file "Aircraft/ATC-ML/Version" was modified<br />
:*a new file "Aircraft/ATC-ML/Version (copy)" was added<br />
:*and a new directory "Aircraft/DUMMY/" was added, including all its files <br />
<br />
If that is what you wanted/needed continue with the following ''(otherwise correct your work first)''<br />
<br />
'''''So we want to "add" those changes:'''''<br />
;<code>git add "Aircraft/ATC-ML/Version (copy)"</code><br />
;<code>git add Aircraft/ATC-ML/Version</code><br />
;<code>git add Aircraft/DUMMY/</code><br />
If you now perform the '''git status''' again you should see something similar to:<br />
../GIT/fgdata$ ''git status''<br />
# On branch master.local<br />
# '''''Changes to be committed:'''''<br />
# (use "git reset HEAD <file>..." to unstage)<br />
#<br />
# modified: Aircraft/ATC-ML/Version<br />
# new file: Aircraft/ATC-ML/Version (copy)<br />
# new file: Aircraft/DUMMY/ATC-ML (copy).xml<br />
# new file: Aircraft/DUMMY/ATC-ML-set.xml<br />
# new file: Aircraft/DUMMY/ATC-ML.ac<br />
# new file: Aircraft/DUMMY/ATC-ML.nas<br />
''... etc.''<br />
#<br />
If that is all you need - you may "commit" it:<br />
<br />
===="Commit"====<br />
;<code>git commit -m "''your short, accompanying Announcement''"</code><br />
: will commit the updates to the ''master.local'' branch. It shows a list compatible to the one created with the "git status" before, but this "git commit" created something new! ''(Yes: You could have omitted the "git status" and just did the "commit" - but we suggest to "double-check" it this way!)''<br />
<br />
;<code>git log</code><br />
..GIT/fgdata$ git log<br />
commit 7658c67c16a79900acf99dbfd85499b720dcc920<br />
Author: YourName <Your eMail><br />
Date: Mon Jun 4 19:14:29 2012 +0200<br />
<br />
your short, accompanying Announcement<br />
: This is the "commit" as it will be tracked within the GIT.<br />
: You definitely should now copy the ID ''(the first 8 digits may be enough)'' to use it later as a unique identifier!<br />
<br />
Now return to your local "master" with:<br />
;<code>git checkout master</code><br />
<br />
;<code><nowiki>git fetch git://gitorious.org/fg/fgdata.git</nowiki></code><br />
:''replace in that line the "fgdata.git" with the repository you are actually working on''<br />
:this will update the master to the newest GIT-level ''(there may have been changes during all that time!)''<br />
<br />
;<code>git cherry-pick 7658c67c</code><br />
:''replace the "7658c67c" with the first digits of your commit-ID (see above "git log")''<br />
:will pull the commit into the "master"<br />
<br />
;<code>git rebase origin/master</code><br />
:finally update the "master" with the "commit" on top of it<br />
<br />
=== Push your changes to your clone on Gitorious ===<br />
;<code>git push git@gitorious.org:~<small>YourUID</small>/fg/<small>YourUID</small>s-fgdata.git</code><br />
<small><br />
::replace "YourID" with your login-name for Gitorious, do not forget the "~" in front of it!<br />
::replace in that line the "fgdata.git" with the repository you are actually working on<br />
</small><br />
:will finally push your updates to your space inside "gitorious.org"<br />
<br />
Now you can announce to GIT that you have a change that may be merged into the original GIT:<br />
*Open your git-clone on Gitorious: https://gitorious.org/~<small>YourUID</small>/fg/<small>YourUID</small>-fgdata<br />
*and click the "Request merge" button on the right:<br />
<br />
[[File:Create merge request at Gitorious.png|thumb|270px|Creating a merge request at Gitorious.]]<br />
Write a short summary, in which you explain what your commit(s) do(es). Then choose the following settings:<br />
: '''Target directory:''' fgdata, flightgear or simgear<br />
: '''Target branch:''' master, next or whatever<br />
: '''Source branch:''' master, next or whatever<br />
Next select the commits you would like to include in your merge request and click "Create merge request".<br />
<br />
Note that it usually doesn't suffice to just send a merge request via gitorious (unfortunately), but that you'll often also need to "ping" 1-3 core developers who have previously worked with the subsystems affected by the patch (and send a reminder once in a while). <br />
<br />
It makes sense to watch the forums/mailing lists or just the git history to see which developers are currently active. To get a list of people who have previously worked with the affected subsystems/files, just take a look at the commit log of the corresponding files and get in touch with the developers via the devel list or forum.<br />
<br />
Also, it may help to send a follow-up (merge request review) via the issue tracker here: https://code.google.com/p/flightgear-bugs/issues/entry?template=Review%20request<br />
<br />
Currently, it isn't uncommon for merge requests to take 2-4 weeks, and sometimes even 1-2 months before being reviewed and committed. Your chances of getting your code committed upstream are much better directly after a release, than shortly before a release obviously (feature freeze).<br />
<br />
=== Commit the changes into the GIT ===<br />
<span style="color:red">'''''This step is for developers with fgdata commit access only!'''''</span><br />
<br />
For a list of those authorized see: https://gitorious.org/+flightgear-developers/memberships and http://gitorious.org/+fgdata-developers/memberships (fgdata only)<br />
<br />
To push a merge request to fgdata, the following work-flow can be followed:<br />
{{pre2|scroll|<br />
git checkout -b integration # the integration branch should not yet exist. You can use any name you'd like<br />
git pull git://gitorious.org/fg/fgdata.git refs/merge-requests/1 # make sure you change 1 to the id of the merge request<br />
git rebase master # place the new commits on top of existing commits (without ugly "Merge branch into ...")<br />
git checkout master<br />
git cherry-pick b049e1d # repeat this for each commit you'd like to push<br />
git push}}<br />
<br />
== Related content ==<br />
* [[FlightGear Git: splitting fgdata]], an initiative to split the aircraft out of the fgdata repository, in order to decrease its size and thus improve access to the average user/developer.<br />
<br />
{{Building}}<br />
<br />
[[Category:Core developer documentation]]<br />
[[Category:FlightGear]]<br />
[[Category:Git]]<br />
<br />
[[fr:FlightGear et Git]]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_Git_for_laymen&diff=62323FlightGear Git for laymen2013-08-18T17:17:51Z<p>Raazeer: A description of the process of getting and updating Git repositories, tuned to the needs of non-geeks</p>
<hr />
<div>= Git for Laymen =<br />
Git, and its fellow Version Control Systems are a domain of geeks - who are patently incapable of explaining anything in simple terms most of the time. Because of this, many a layman has fled in terror from what is, when all's said and done, easy to use.<br />
<br />
== What is Git? ==<br />
Git is a Version Control System, meaning that it ''tracks changes to files'' - in other words, if you make a change to a file known to Git, or ''commit'' the change as the expert would put it, Git stores what parts of the file have changed between the last version and the current version. That makes it possible to do a lot of great things, the most mind-soothing among them being the ability to get the old version back in case it turns out you've broken something.<br />
<br />
== What does Git do for me? == <br />
Another thing Git does is ''distribute change''. That means, additionally to committing things ''to'' the Git repository, you can also get the changes others made ''from'' the Git repository - thus keeping your local copy of whatever is kept in the repository current. That is the use most laymen will be most interested in. In practical terms, that means you can at any time get all the changes the developers made just by updating your copy from the repository - instead of having to re-download the whole data (or trying to scrape together the changed files manually, a path that leads to insanity without any stop signs or speed limits). With a large repository like Flightgear Base Data for example, the difference is a few kilobytes instead of 15 gigabytes.<br />
<br />
== What do I need to use a Git repository that way? ==<br />
Basicly, all you have to do is install a git client on your machine. For windows users, '''TrotoiseGit''',which is free for download, would be the option of choice, for Linux/Unix users it's just plain '''git''', available from your favorite software repository. Both are rather trivial to set up - the only confusing thing is that they may require you to supply a name and an email adress on install - don't get panicky, it's just a prerequisite Git has for use cases you'll never see unless you decide to come to the geek side of life. Needs to be done, just like you have to klick "I accept" to install most (proprietary) software.<br />
<br />
== How do I use the git repository to update Flightgear stuff? ==<br />
Git has a score of '''very''' confusing options that allow you to do stuff that boggles the mind of even an established geek. To achieve what you, the layman, will want to do, a total of two commands are totally sufficient. <br />
=== Initial cloning ===<br />
The first step to using the Git data for your own purposes is to grab a copy from the repository. Here's how to do that<br />
This description uses the linux commandline version of the git commands, but in principle you do the same with TrotoiseGit, only the commands are in the context menu there.<br />
<br />
First, navigate to where you want the checkout to live<br />
<br />
$ cd /home/user/data/git-repos<br />
<br />
Then, you clone the repository. To do that, you have to know the URL of the repository you want to be cloning. Those are found on the [https://gitorious.org/fg Flightgear Gitorious page]. For this example, we'll be using the Flightgear Base Data repository '''fgdata''', but the principle is exactly the same for simgear or flightgear source. All that changes is the URL to clone.<br />
<nowiki>$ git clone git://gitorious.org/fg/fgdata.git</nowiki><br />
After that, it's time to lean back and get a cup of coffee, because that specific repo is really quite ''huge'' - almost 15 GB of data as of writing this. (There is a better method for cloning huge repos like this, it's described on this page: [[FlightGear and Git#Special for fgdata:|FlightGear and Git]],but it's likely that's exactly the page you fled here from.)<br />
<br />
Now, once that operation completes (without errors hopefully), you're done! Try<br />
$ cd fgdata<br />
$ ls<br />
and enjoy.<br />
<br />
=== Keeping it current ===<br />
Up to this point, we haven't done anything we couldn't have achieved with an archive file. That is, we have, but not in a way you, a layman, are in any position to recognize. Now is the time to take advantage of this fact.<br />
<br />
Let's say you've buggered the guys in the IRC channel until finally somebody has fixed the bug in your favorite airplane just to get rid of you. Now how do you personally get that change? If you had been downloading an archive, you'd have to wait for the archive to be rebuilt, download the whole thing again, and iron it on over the old data. Not so with Git - here's what to do. Navigate to the place where your repository lives, in our example like this:<br />
$ cd /home/user/git-repos/fgdata<br />
Note that this time, we're cding ''into'' the directory.<br />
Now get all the changes since you cloned the repository like this:<br />
$ git pull<br />
That's all. Watch the numbers dance - it'll be much quicker this time than the last time, because only the changes in the files need to be transmitted - and once the command returns, you can jump into your now (hopefully) bug-free airplane and take her for a spin<br />
<br />
== A word about troubleshooting ==<br />
This wouldn't be a good article without a word about troubleshooting. The process described above is really rather reliable and will work 99% of the time, but sometimes it '''does''' break down - mostly because you inadvertedly changed a file that somebody else changed in the "official" repository. If Git finds a conflict, e.g. a file having been edited by you AND somebody else since the last pull - it will refuse to just clobber the local changes. <br />
<br />
Now - if you DID change the file actively, it's time you went over to a ''real'' git tutorial and found out about merging changes. If you didn't, you can revert the changes to the baseline of the repository, that is, reset the file(s) to how it was when you last pulled the changes:<br />
$ cd /home/user/git-repos/fgdata<br />
$ git reset<br />
$ git pull<br />
If it works, all is fine. If Git still complains, e.g. about not being able to "fast-forward" the changes, you'll have to tell it to try a little harder (and with less respect to what it might clobber) to reset your working copy:<br />
$ git reset --hard<br />
Sometimes, IT is simple. This command should undo everything you did in your working copy, that is, get the entire working copy back to the state it was when you last pulled. In 99% of the trouble, this is the end of it, and a <br />
$ git pull<br />
will work. If it still doesn't, your local clone has gotten a nasty dent somewhere. In this case, you can either seriously dive into git and fix it, or delete the whole repository folder and clone anew:<br />
$ cd /home/user/git-repos/<br />
$ rm -rf fgdata<br />
<nowiki>$ git clone git://gitorious.org/fg/fgdata.git</nowiki><br />
<br />
== Where do I take it from here? ==<br />
To be honest: for most ''laymen'' this is the end of the trail, and you'll live happily ever after. <br />
<br />
If however your interest has been piqued and you want to know more about Git in particular and VCS in general - and how they can help you tweak and twitch your copy of flightgear - more power to you. <br />
<br />
First, I'd recommend browsing the net for a good git tutorial - a very good one is available from Linus Torvalds, the famous inventor of Linux - and father of Git - but you'll have to find out which one works for '''you'''. Also read [[FlightGear and Git]], the official wiki page on doing Git the Flightgear way.</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=36614FlightGear glass cockpit2011-10-30T20:23:52Z<p>Raazeer: /* Contributing */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[File:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
* FGGC will move entirely to it's sourceforge page effective immediately. That means, this is the last news entry here on this page. Be on the lookout for more news on the sourceforge page.<br />
* Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]<br />
* The garbage data segfault mentioned in issues earlier has been found and hardened against.<br />
* The heading indicator now correctly shows major headings by name<br />
* Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
* A SourceForge project has been created<br />
* Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
* Due to many uninitialized variables starting up OpenGC is sometimes leading to a crash. If this happens just try again... and again... and again... suddenly it will fire up. Although there's no guaranteed stability.<br />
* Network socket is not starting up every time. If you are faced to "Error writing data" in FG console you can be quite sure either to set the wrong parameters or the before mentioned network socket is not available. By the way: did you check your firewall to pass UDP 5800 packets?<br />
* Just a few gauges are available: Boeing777PFD,NavTestGauge, Keypad,EGyroAltimeterSetting<br />
* Adding own gauges demands knowledge in programming C++ and recompiling the source<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
* Get a CVS resource online<br />
* Improve code hardening to prevent ugly bailouts in FTGL and others<br />
* Get the input processor to correctly convert elevation to barometric altitude<br />
* Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
* Move the configuration to XML to match FG configuration<br />
* Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
* Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)<br />
* Clean up and modernize the codebase<br />
* Further harden the code against garbage data<br />
* Improve codebase documentation<br />
* Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
* Create a working set of generic gauges<br />
* Implement an XML gauge constructor to get away from having to code gauges in C++<br />
* Integrate the code closer with fg<br />
* Remove the necessity to share code between FGGC and FG<br />
* Turn the codebase into a real library<br />
* Improve the input parsing code<br />
* Implement an upstream network interface to send input back to FG<br />
<br />
== Requirements ==<br />
OpenGC 0.3-alpha3 has only been tested on LINUX operating system (Ubuntu 10.04). LINUX systems must have GCC version 4.0.0-8 or later, and graphics card with OpenGL support. Before unpacking and making the modified version of OpenGC there are five open source programs that must be installed on your computer:<br />
<br />
* CMake 2.0+ program used to generate the makefiles that build the OpenGC executable, download from http://www.cmake.org/HTML/Index.html<br />
* FLTK 1.5 includes libraries that are required to build the render windows, download from http://www.fltk.org/<br />
* Freetype 2.19 has important include files that are needed for FTGL to work, download from http://www.freetype.org/<br />
* FTGL 2.0.11 includes libraries and headers that are required for fonts used in OpenGC, download from http://homepages.paradise.net.nz/henryj/code/#FTGL<br />
* Plib 1.6 important math and graphics libraries are included, download from http://plib.sourceforge.net/<br />
<br /><br />
On Ubuntu:<br />
sudo aptitude install cmake libfltk1.1-dev libfreetype6-dev libftgl-dev libplib-dev<br />
<br /><br />
The specifics of each package is available at http://www.opengc.org/developers_building.html. Newer versions of each file have been tested, and there seems to be no backward compatibility issues, but the files above have been proven to work. Installing these programs is the most important part of having a working program. After SUCCESSFUL INSTALLATION of the programs follow the step by step guide to setup OpenGC on your system.<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Compiling the sources on Linux ==<br />
# Unpack the compressed file to a convenient location<br />
# Edit /path/to/your/fggc/source/FindPlib.cmake and modify line 26:(not needed building from Git repository)<br />
#: <pre>FIND_LIBRARY(Plib_SL_LIBRARY NAMES sl plibsl</pre><br />
#: the difference is the last word in this line. Before you edit it it says "plib sl". Remove the space.<br />
# In terminal go to directory .../OpenGC/Applications/FLTKApp<br />
## Create the file "opengc.ini"<br />
## Edit opengc.ini and set the font and navigation path to the location of the Font and Navigation folders within the OpenGC file:<br />
#: <pre><br />
#: NAV DATABASE PATH<br />
#: /path/to/your/install/fggc/navdata/<br />
#: FONT PATH<br />
#: /path/to/OpenGC/Fonts/</pre><br />
# Switch back to .../OpenGC/ and enter the command ccmake CMakeLists.txt (alternatively CMake comes with gui as "cmake-gui" or "cmake-qt-gui", depending on your linux distribution)<br />
## Locate the directories marked with DIR_NOT_FOUND, these are usually Freetype, Plib, and FTGL<br />
## Scan the /usr/ directory for the libraries and include directories of the files. If you cannot locate them, compare the directories in the file packages with what you have in your /usr/... directory<br />
## FLTK directory should be configured manually to "/usr/include/FL"; Plib and FTGL should be modified to work correctly with insertion of "/usr/include/Plib" and "/usr/include/FTGL".<br />
## If you have linked these include directories or libraries, change directories back to the package you are having trouble with and type "make -install" again. To make it easier to find the package you may want to set the build location to a familiar spot. For help doing this type "man make" inside terminal<br />
# Once all the directories are set hit the 'c' key to configure the file, then the 'g' key to generate the makefiles<br />
# Run "make" to build the OpenGC libraries and executable to the location specified in the ccmake script<br />
# If you want to see a preview of the OpenGC application change directories to the .../OpenGC/Applications/FLTKApp and type "./OpenGC opengc.ini" after a list of instructions and a short loading period you should see the display running through a previous flight test.<br />
# Creating your own data source and collecting data in real time requires a bit more work. Start off by opening the Documentation Folder from the OpenGC directory, in that file there is a ReadMe on DataSource Creation that covers how to work with telemetry data from general sources.<br />
# To switch to the DataSource that is compatible with the current Data Packets being sent down from the UAV or airframe platform go to opengc.ini and switch the DATASOURCE field to EGyro.<br />
<br />
Notice that this requires valid data being sent in via the serial port. To get this valid data requires the Autopilot program be loaded onto a processor that is actively transmitting data. In the directory /FLTKApp/ call "./OpenGC opengc.ini: and the cockpit display should appear. After completing your test data should be logged in the /FLTKApp/datalog directory under the name telemetry.txt.<br />
<br />
== Attaching to FlightGear ==<br />
Start FlightGear with your favorite options and the following to your commandline:<br />
--opengc=socket,out,24,aa.bb.cc.dd,5800,udp<br />
* "opengc" describes what data is sent out<br />
* "socket" tells FG how to present the data (here: as network socket)<br />
* "24" = update frequency in Hz; do not change, it's hard coded inside OpenGC<br />
* "aa.bb.cc.dd." = IP address where to send data to; use 127.0.0.1 if you intend to use OpenGC on the local pc<br />
* "5800" describes the used port; don't change, it's also hardcoded within OpenGC<br />
* "udp" is the used network protocol; also hard coded; don't change<br />
<br />
== Contributing ==<br />
A Git repo now exists for FGGC on sourceforge.net. Here's how to clone it:<br />
First, make sure git is installed on your machine. Easiest way to do that is by typing '''git''' in a shell and see what happens.<br />
Then create a directory where you want to host the repository:<br />
mkdir ~/gitrepos/FGGC<br />
Then, cd in:<br />
cd ~/gitrepos/FGGC<br />
Then, check out:<br />
git clone git://fggc.git.sourceforge.net/gitroot/fggc/fggc<br />
The git repository is read-only however, so you still have to patch-mail your improvements to me. Or you might just join the project at sourceforge.net<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the [[FlightGear IRC channel]] under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]<br />
<br />
[[Category:Glass Cockpit related]]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=36613FlightGear glass cockpit2011-10-30T20:15:42Z<p>Raazeer: /* Compiling the sources on Linux */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[File:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
* FGGC will move entirely to it's sourceforge page effective immediately. That means, this is the last news entry here on this page. Be on the lookout for more news on the sourceforge page.<br />
* Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]<br />
* The garbage data segfault mentioned in issues earlier has been found and hardened against.<br />
* The heading indicator now correctly shows major headings by name<br />
* Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
* A SourceForge project has been created<br />
* Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
* Due to many uninitialized variables starting up OpenGC is sometimes leading to a crash. If this happens just try again... and again... and again... suddenly it will fire up. Although there's no guaranteed stability.<br />
* Network socket is not starting up every time. If you are faced to "Error writing data" in FG console you can be quite sure either to set the wrong parameters or the before mentioned network socket is not available. By the way: did you check your firewall to pass UDP 5800 packets?<br />
* Just a few gauges are available: Boeing777PFD,NavTestGauge, Keypad,EGyroAltimeterSetting<br />
* Adding own gauges demands knowledge in programming C++ and recompiling the source<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
* Get a CVS resource online<br />
* Improve code hardening to prevent ugly bailouts in FTGL and others<br />
* Get the input processor to correctly convert elevation to barometric altitude<br />
* Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
* Move the configuration to XML to match FG configuration<br />
* Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
* Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)<br />
* Clean up and modernize the codebase<br />
* Further harden the code against garbage data<br />
* Improve codebase documentation<br />
* Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
* Create a working set of generic gauges<br />
* Implement an XML gauge constructor to get away from having to code gauges in C++<br />
* Integrate the code closer with fg<br />
* Remove the necessity to share code between FGGC and FG<br />
* Turn the codebase into a real library<br />
* Improve the input parsing code<br />
* Implement an upstream network interface to send input back to FG<br />
<br />
== Requirements ==<br />
OpenGC 0.3-alpha3 has only been tested on LINUX operating system (Ubuntu 10.04). LINUX systems must have GCC version 4.0.0-8 or later, and graphics card with OpenGL support. Before unpacking and making the modified version of OpenGC there are five open source programs that must be installed on your computer:<br />
<br />
* CMake 2.0+ program used to generate the makefiles that build the OpenGC executable, download from http://www.cmake.org/HTML/Index.html<br />
* FLTK 1.5 includes libraries that are required to build the render windows, download from http://www.fltk.org/<br />
* Freetype 2.19 has important include files that are needed for FTGL to work, download from http://www.freetype.org/<br />
* FTGL 2.0.11 includes libraries and headers that are required for fonts used in OpenGC, download from http://homepages.paradise.net.nz/henryj/code/#FTGL<br />
* Plib 1.6 important math and graphics libraries are included, download from http://plib.sourceforge.net/<br />
<br /><br />
On Ubuntu:<br />
sudo aptitude install cmake libfltk1.1-dev libfreetype6-dev libftgl-dev libplib-dev<br />
<br /><br />
The specifics of each package is available at http://www.opengc.org/developers_building.html. Newer versions of each file have been tested, and there seems to be no backward compatibility issues, but the files above have been proven to work. Installing these programs is the most important part of having a working program. After SUCCESSFUL INSTALLATION of the programs follow the step by step guide to setup OpenGC on your system.<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Compiling the sources on Linux ==<br />
# Unpack the compressed file to a convenient location<br />
# Edit /path/to/your/fggc/source/FindPlib.cmake and modify line 26:(not needed building from Git repository)<br />
#: <pre>FIND_LIBRARY(Plib_SL_LIBRARY NAMES sl plibsl</pre><br />
#: the difference is the last word in this line. Before you edit it it says "plib sl". Remove the space.<br />
# In terminal go to directory .../OpenGC/Applications/FLTKApp<br />
## Create the file "opengc.ini"<br />
## Edit opengc.ini and set the font and navigation path to the location of the Font and Navigation folders within the OpenGC file:<br />
#: <pre><br />
#: NAV DATABASE PATH<br />
#: /path/to/your/install/fggc/navdata/<br />
#: FONT PATH<br />
#: /path/to/OpenGC/Fonts/</pre><br />
# Switch back to .../OpenGC/ and enter the command ccmake CMakeLists.txt (alternatively CMake comes with gui as "cmake-gui" or "cmake-qt-gui", depending on your linux distribution)<br />
## Locate the directories marked with DIR_NOT_FOUND, these are usually Freetype, Plib, and FTGL<br />
## Scan the /usr/ directory for the libraries and include directories of the files. If you cannot locate them, compare the directories in the file packages with what you have in your /usr/... directory<br />
## FLTK directory should be configured manually to "/usr/include/FL"; Plib and FTGL should be modified to work correctly with insertion of "/usr/include/Plib" and "/usr/include/FTGL".<br />
## If you have linked these include directories or libraries, change directories back to the package you are having trouble with and type "make -install" again. To make it easier to find the package you may want to set the build location to a familiar spot. For help doing this type "man make" inside terminal<br />
# Once all the directories are set hit the 'c' key to configure the file, then the 'g' key to generate the makefiles<br />
# Run "make" to build the OpenGC libraries and executable to the location specified in the ccmake script<br />
# If you want to see a preview of the OpenGC application change directories to the .../OpenGC/Applications/FLTKApp and type "./OpenGC opengc.ini" after a list of instructions and a short loading period you should see the display running through a previous flight test.<br />
# Creating your own data source and collecting data in real time requires a bit more work. Start off by opening the Documentation Folder from the OpenGC directory, in that file there is a ReadMe on DataSource Creation that covers how to work with telemetry data from general sources.<br />
# To switch to the DataSource that is compatible with the current Data Packets being sent down from the UAV or airframe platform go to opengc.ini and switch the DATASOURCE field to EGyro.<br />
<br />
Notice that this requires valid data being sent in via the serial port. To get this valid data requires the Autopilot program be loaded onto a processor that is actively transmitting data. In the directory /FLTKApp/ call "./OpenGC opengc.ini: and the cockpit display should appear. After completing your test data should be logged in the /FLTKApp/datalog directory under the name telemetry.txt.<br />
<br />
== Attaching to FlightGear ==<br />
Start FlightGear with your favorite options and the following to your commandline:<br />
--opengc=socket,out,24,aa.bb.cc.dd,5800,udp<br />
* "opengc" describes what data is sent out<br />
* "socket" tells FG how to present the data (here: as network socket)<br />
* "24" = update frequency in Hz; do not change, it's hard coded inside OpenGC<br />
* "aa.bb.cc.dd." = IP address where to send data to; use 127.0.0.1 if you intend to use OpenGC on the local pc<br />
* "5800" describes the used port; don't change, it's also hardcoded within OpenGC<br />
* "udp" is the used network protocol; also hard coded; don't change<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the [[FlightGear IRC channel]] under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]<br />
<br />
[[Category:Glass Cockpit related]]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=13751FlightGear glass cockpit2009-08-05T01:32:17Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*FGGC will move entirely to it's sourceforge page effective immediately. That means, this is the last news entry here on this page. Be on the lookout for more news on the sourceforge page.<br />
*Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against.<br />
*The heading indicator now correctly shows major headings by name<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
Currently there are no known issues<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the [[FlightGear IRC channel]] under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]<br />
<br />
[[Category:Glass Cockpit related]]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=Start_script&diff=13010Start script2009-06-08T23:23:08Z<p>Raazeer: /* Scripts to set up FlightGear environments */</p>
<hr />
<div>= Scripts to set up FlightGear environments =<br />
<br />
This page is intended to host various start scripts to set up environments to smoothly run FlightGear on various systems, eg. to set the graphics driver straight or run various helper programs, like terrasync or Atlas. Everybody is invited to contribute theirs.<br />
'''Update:''' Please sign yours, so anyone knows whom to turn to for help<br />
<br />
== Bash scripts ==<br />
Simple start script to set up nice, comfortable surroundings for flightgear with an nvidia card. Will run Atlas and terrasync for you. Paths may need to be set of course --[[User:Raazeer|Raazeer]] 19:11, 8 June 2009 (EDT)<br />
<pre>#!/bin/bash<br />
nvidia-settings -a FSAAAppControlled=1<br />
nvidia-settings -a FSAAAppControlled=0<br />
nvidia-settings -a FSAA=10<br />
case "$1" in<br />
stop)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo FGFS environment shut down.<br />
;;<br />
start)<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Atlas ready at port 5500...<br />
echo Ready to run Flightgear<br />
;;<br />
restart)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo restarting terrasync...<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
echo restarting Atlas...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/s<br />
hare/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
;;<br />
*)<br />
echo Bash script to set up a usable environment to run Flightgear.<br />
echo Sets anti-aliasing settings right for nvidia cards.<br />
echo sets up terrasync, Atlas and FGGC for you.<br />
echo <br />
echo "Usage: fgprep {start|stop|restart}"<br />
;;<br />
esac<br />
exit 0<br />
</pre><br />
<br />
== Other Linux/Unix/Mac shell scripts ==<br />
<br />
== Windows/DOS scripts ==<br />
<br />
== VBS Scripts ==</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=Start_script&diff=13009Start script2009-06-08T23:11:10Z<p>Raazeer: /* Bash scripts */</p>
<hr />
<div>= Scripts to set up FlightGear environments =<br />
<br />
This page is intended to host various start scripts to set up environments to smoothly run FlightGear on various systems, eg. to set the graphics driver straight or run various helper programs, like terrasync or Atlas. Everybody is invited to contribute theirs.<br />
<br />
== Bash scripts ==<br />
Simple start script to set up nice, comfortable surroundings for flightgear with an nvidia card. Will run Atlas and terrasync for you. Paths may need to be set of course --[[User:Raazeer|Raazeer]] 19:11, 8 June 2009 (EDT)<br />
<pre>#!/bin/bash<br />
nvidia-settings -a FSAAAppControlled=1<br />
nvidia-settings -a FSAAAppControlled=0<br />
nvidia-settings -a FSAA=10<br />
case "$1" in<br />
stop)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo FGFS environment shut down.<br />
;;<br />
start)<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Atlas ready at port 5500...<br />
echo Ready to run Flightgear<br />
;;<br />
restart)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo restarting terrasync...<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
echo restarting Atlas...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/s<br />
hare/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
;;<br />
*)<br />
echo Bash script to set up a usable environment to run Flightgear.<br />
echo Sets anti-aliasing settings right for nvidia cards.<br />
echo sets up terrasync, Atlas and FGGC for you.<br />
echo <br />
echo "Usage: fgprep {start|stop|restart}"<br />
;;<br />
esac<br />
exit 0<br />
</pre><br />
<br />
== Other Linux/Unix/Mac shell scripts ==<br />
<br />
== Windows/DOS scripts ==<br />
<br />
== VBS Scripts ==</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=Start_script&diff=13008Start script2009-06-08T23:10:08Z<p>Raazeer: These Scripts are not only intended for terrasync or Atlas, but for anything FGish</p>
<hr />
<div>= Scripts to set up FlightGear environments =<br />
<br />
This page is intended to host various start scripts to set up environments to smoothly run FlightGear on various systems, eg. to set the graphics driver straight or run various helper programs, like terrasync or Atlas. Everybody is invited to contribute theirs.<br />
<br />
== Bash scripts ==<br />
Simple start script to set up nice, comfortable surroundings for flightgear with an nvidia card. Will run Atlas and terrasync for you. Paths may need to be set of course<br />
<pre>#!/bin/bash<br />
nvidia-settings -a FSAAAppControlled=1<br />
nvidia-settings -a FSAAAppControlled=0<br />
nvidia-settings -a FSAA=10<br />
case "$1" in<br />
stop)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo FGFS environment shut down.<br />
;;<br />
start)<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Atlas ready at port 5500...<br />
echo Ready to run Flightgear<br />
;;<br />
restart)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo restarting terrasync...<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
echo restarting Atlas...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/s<br />
hare/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
;;<br />
*)<br />
echo Bash script to set up a usable environment to run Flightgear.<br />
echo Sets anti-aliasing settings right for nvidia cards.<br />
echo sets up terrasync, Atlas and FGGC for you.<br />
echo <br />
echo "Usage: fgprep {start|stop|restart}"<br />
;;<br />
esac<br />
exit 0<br />
</pre><br />
<br />
== Other Linux/Unix/Mac shell scripts ==<br />
<br />
== Windows/DOS scripts ==<br />
<br />
== VBS Scripts ==</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12980FlightGear glass cockpit2009-06-07T23:49:55Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against.<br />
*The heading indicator now correctly shows major headings by name<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre style="width:45em;align:left;margin-left:5px;">Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
Currently there are no known issues<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12979FlightGear glass cockpit2009-06-07T23:45:08Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*Alpha 3 is now available from the [http://sourceforge.net/projects/fggc source forge project page]<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against.<br />
*The heading indicator now correctly shows major headings by name<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
Currently there are no known issues<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12978FlightGear glass cockpit2009-06-07T23:40:02Z<p>Raazeer: /* Contributing */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly. More code hardening to come.<br />
*The heading indicator now correctly shows major headings by name<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
Currently there are no known issues<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de. Of course anyone is invited to help in any way he finds might be useful. Feature requests and bug reports are welcome as well of course, but I'll also need footage of the real-world flight displays FGGC is supposed to mimic if I am to get it right.<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12977FlightGear glass cockpit2009-06-07T23:37:03Z<p>Raazeer: /* Mid Term Goals */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly. More code hardening to come.<br />
*The heading indicator now correctly shows major headings by name<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
Currently there are no known issues<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Port the nav interface to work with FlightGear (currently it's only implemented for MSFS)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12976FlightGear glass cockpit2009-06-07T22:28:27Z<p>Raazeer: /* Issues */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the '''[[FlightGear|Flight Gear]] Glass Cockpit''' Project, short '''FGGC'''.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG [[FlightGear CVS|cvs]] code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the [[Boeing 777]].<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly. More code hardening to come.<br />
*The heading indicator now correctly shows major headings by name<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
Currently there are no known issues<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12947FlightGear glass cockpit2009-06-04T11:27:58Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly. More code hardening to come.<br />
*The heading indicator now correctly shows major headings by name<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12946FlightGear glass cockpit2009-06-04T11:25:43Z<p>Raazeer: /* Near Term Goals */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly. More code hardening to come.<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Improve code hardening to prevent ugly bailouts in FTGL and others<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12945FlightGear glass cockpit2009-06-04T11:25:06Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly. More code hardening to come.<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12944FlightGear glass cockpit2009-06-04T11:24:15Z<p>Raazeer: /* Issues */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly.<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12943FlightGear glass cockpit2009-06-04T11:24:00Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*The garbage data segfault mentioned in issues earlier has been found and hardened against. Alpha3 will be online shortly.<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
* A garbage data segfault I thought thoroughly weeded out reared it's ugly head again in alpha2, reason unknown. If anyone has any idea, I'm open to suggestions...<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=Start_script&diff=12942Start script2009-06-04T11:20:28Z<p>Raazeer: New page: = Start Script Page = This page is intended to host various start scripts to set up environments to smoothly run FlightGear on various systems. Everybody is invited to contribute theirs. ...</p>
<hr />
<div>= Start Script Page =<br />
<br />
This page is intended to host various start scripts to set up environments to smoothly run FlightGear on various systems. Everybody is invited to contribute theirs.<br />
<br />
== Bash scripts ==<br />
Simple start script to set up nice, comfortable surroundings for flightgear with an nvidia card. Will run Atlas and terrasync for you. Paths need to be set of course<br />
<pre>#!/bin/bash<br />
nvidia-settings -a FSAAAppControlled=1<br />
nvidia-settings -a FSAAAppControlled=0<br />
nvidia-settings -a FSAA=10<br />
case "$1" in<br />
stop)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo FGFS environment shut down.<br />
;;<br />
start)<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Atlas ready at port 5500...<br />
echo Ready to run Flightgear<br />
;;<br />
restart)<br />
echo killing terrasync...<br />
killall terrasync<br />
echo killing atlas...<br />
killall Atlas<br />
echo restarting terrasync...<br />
terrasync -p 5400 -S -d /usr/local/share/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
echo Terrasync ready at port 5400...<br />
echo restarting Atlas...<br />
Atlas --fg-root=/usr/local/share/FlightGear/data/ --udp=5500 --autocenter-mode --path=/usr/local/share/FlightGear/data/Atlas --size=1024 --lowres-size=256 --fg-scenery=/usr/local/s<br />
hare/FlightGear/data/Scenery/ 2>&1 >/dev/null&<br />
;;<br />
*)<br />
echo Bash script to set up a usable environment to run Flightgear.<br />
echo Sets anti-aliasing settings right for nvidia cards.<br />
echo sets up terrasync, Atlas and FGGC for you.<br />
echo <br />
echo "Usage: fgprep {start|stop|restart}"<br />
;;<br />
esac<br />
exit 0<br />
</pre><br />
<br />
== Other Linux/Unix/Mac shell scripts ==<br />
<br />
== Windows/DOS scripts ==<br />
<br />
== VBS Scripts ==</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12909FlightGear glass cockpit2009-05-31T11:26:56Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
* A garbage data segfault I thought thoroughly weeded out reared it's ugly head again in alpha2, reason unknown. If anyone has any idea, I'm open to suggestions...<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12908FlightGear glass cockpit2009-05-31T11:24:12Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*Project updates will be slow until my finals are over, I'll try not to lose touch with the codebase too much... <br />
<blockquote><pre>Eagleson's Law:<br />
Any code of your own that you haven't looked at for six or more<br />
months, might as well have been written by someone else. (Eagleson<br />
is an optimist, the real number is more like three weeks.)</pre></blockquote><br />
:: -- From the fortunes database<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
* A garbage data segfault I thought thoroughly weeded out reared it's ugly head again in alpha2, reason unknown. If anyone has any idea, I'm open to suggestions...<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12907FlightGear glass cockpit2009-05-31T10:56:00Z<p>Raazeer: /* Issues */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
* A garbage data segfault I thought thoroughly weeded out reared it's ugly head again in alpha2, reason unknown. If anyone has any idea, I'm open to suggestions...<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12906FlightGear glass cockpit2009-05-31T10:54:40Z<p>Raazeer: </p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Issues ==<br />
* A garbage data segfault I thought thoroughly weeded out reared it's ugly head again in alpha2, why and how is so far unknown...<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get a CVS resource online<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's <del>invited</del> '''needed''' to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer<br />
<br />
== Links ==<br />
* [http://sourceforge.net/projects/fggc FGGC Project at SourceForge.net]</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12905FlightGear glass cockpit2009-05-31T10:42:22Z<p>Raazeer: /* Where the project stands */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
<br />
Right now I'm calling the state of the project alpha, and that's not gonna change anytime soon.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12904FlightGear glass cockpit2009-05-31T10:36:17Z<p>Raazeer: /* Getting the Source */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The latest source package can now be downloaded at the downloads section of the sourceforge project at http://sourceforge.net/projects/fggc<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12903FlightGear glass cockpit2009-05-31T10:34:57Z<p>Raazeer: /* News */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*A SourceForge project has been created<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The current Source Code can be downloaded at http://filebin.ca/xvxnwy/FGGC-0.3alpha2.tar.gz<br />
I will update this link whenever I've got something new working, so it is recommended to come back here and get the latest link whenever you're looking for a re-download.<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12643FlightGear glass cockpit2009-05-16T17:18:40Z<p>Raazeer: new version online</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== News ===<br />
*Resolved the remaining issues with the heading indicator<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The current Source Code can be downloaded at http://filebin.ca/xvxnwy/FGGC-0.3alpha2.tar.gz<br />
I will update this link whenever I've got something new working, so it is recommended to come back here and get the latest link whenever you're looking for a re-download.<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12642FlightGear glass cockpit2009-05-16T17:12:09Z<p>Raazeer: /* Where the project stands */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Resolve the remaining issues with the heading indicator<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The current Source Code can be downloaded at http://filebin.ca/qbfdmz/fggc_alpha.tar.gz<br />
I will update this link whenever I've got something new working, so it is recommended to come back here and get the latest link whenever you're looking for a re-download.<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12447FlightGear glass cockpit2009-05-09T21:09:17Z<p>Raazeer: /* The Flight Gear Glass Cockpit Project */</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
== Where the project stands ==<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777. The heading indicator has some unresolved issues yet.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
== Roadmap ==<br />
<br />
=== Near Term Goals ===<br />
*Resolve the remaining issues with the heading indicator<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
=== Mid Term Goals ===<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
=== Long Term Goals ===<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
== Getting the Source ==<br />
The current Source Code can be downloaded at http://filebin.ca/qbfdmz/fggc_alpha.tar.gz<br />
I will update this link whenever I've got something new working, so it is recommended to come back here and get the latest link whenever you're looking for a re-download.<br />
<br />
== Contributing ==<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
== Contact ==<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12445FlightGear glass cockpit2009-05-09T14:04:32Z<p>Raazeer: Added the screenshot</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
=== Where the project stands ===<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777. The heading indicator has some unresolved issues yet.<br />
[[Image:FGGC.jpg|thumb|305px|The Boeing 777 PFD in action]]<br />
=== Roadmap ===<br />
<br />
==== Near Term Goals ====<br />
*Resolve the remaining issues with the heading indicator<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
==== Mid Term Goals ====<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
==== Long Term Goals ====<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
=== Getting the Source ===<br />
The current Source Code can be downloaded at http://filebin.ca/qbfdmz/fggc_alpha.tar.gz<br />
I will update this link whenever I've got something new working, so it is recommended to come back here and get the latest link whenever you're looking for a re-download.<br />
<br />
=== Contributing ===<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
=== Contact ===<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=FlightGear_glass_cockpit&diff=12444FlightGear glass cockpit2009-05-09T13:57:19Z<p>Raazeer: New page: == The Flight Gear Glass Cockpit Project == I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC. The source is largely a dusted-off version of O...</p>
<hr />
<div>== The Flight Gear Glass Cockpit Project ==<br />
<br />
I'm proud to announce the official launch of the Flight Gear Glass Cockpit Project, short FGGC.<br />
The source is largely a dusted-off version of OpenGC by Damion Shelton.<br />
I'd like to thank Damion for leaving us a pretty solid, well-thought-out codebase and hope he will one day return to developing his own version of it. In this case, a re-merge is not out of question.<br />
<br />
=== Where the project stands ===<br />
<br />
So far, we have a dusted-off version of the latest release. I made several small design improvements and updated the interface code to match the current FG cvs code. Right now, the code compiles,runs stable, accepts input at udp port 5800 and processes it mostly correct. There is currently one working set of gauges, modelled after the Boeing 777. The heading indicator has some unresolved issues yet.<br />
[[Image:FGGC.jpg|thumb|The Boeing 777 PFD in action]]<br />
=== Roadmap ===<br />
<br />
==== Near Term Goals ====<br />
*Resolve the remaining issues with the heading indicator<br />
*Get the input processor to correctly convert elevation to barometric altitude<br />
*Implement a command line parser to get rid of statically implemented arguments<br />
<br />
==== Mid Term Goals ====<br />
*Move the configuration to XML to match FG configuration<br />
*Implement more gauges (everybody's invited to help there)<br />
*Clean up and modernize the codebase<br />
*Further harden the code against garbage data<br />
*Improve codebase documentation<br />
*Create a proper API documentation<br />
<br />
==== Long Term Goals ====<br />
*Create a working set of generic gauges<br />
*Implement an XML gauge constructor to get away from having to code gauges in C++<br />
*Integrate the code closer with fg<br />
*Remove the necessity to share code between FGGC and FG<br />
*Turn the codebase into a real library<br />
*Improve the input parsing code<br />
*Implement an upstream network interface to send input back to FG<br />
<br />
=== Getting the Source ===<br />
The current Source Code can be downloaded at http://filebin.ca/qbfdmz/fggc_alpha.tar.gz<br />
I will update this link whenever I've got something new working, so it is recommended to come back here and get the latest link whenever you're looking for a re-download.<br />
<br />
=== Contributing ===<br />
Currently no version control resource exists. Until one can be set up, it is recommended to turn your changes into patch files and mail them to feyn at gmx dot de<br />
<br />
=== Contact ===<br />
I'm available by mail to feyn at gmx dot de, or you can catch me in the flightgear irc under my screen name of Raazeer</div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=File:FGGC.jpg&diff=12443File:FGGC.jpg2009-05-09T13:57:06Z<p>Raazeer: </p>
<hr />
<div></div>Raazeerhttps://wiki.flightgear.org/w/index.php?title=Atlas&diff=10788Atlas2009-02-28T16:12:25Z<p>Raazeer: Added control keys as taken from the source</p>
<hr />
<div>[[Image:Atlas.jpg|thumb|270px|Map view of the San Francisco bay area]]<br />
<br />
''"Atlas aims to produce and display high quality charts of the world for users of FlightGear, an open source flight simulator. This is achieved through two main parts: The map creator (simply called Map) and the Atlas viewer."'' - [http://atlas.sourceforge.net Atlas website] <br />
<br />
==Atlas Help==<br />
Firstly I would greatly thank TheBackMan who posted this on the Flightgear Forums. This is a slightly modified version. To see the original post click [http://www.flightgear.org/forums/viewtopic.php?p=3561 this link].<br />
<br />
===Install Atlas===<br />
This should not be a problem but I messed up my FlightGear when I installed the default way so lets stay on the safe side...<br />
<br />
# Download Atlas Package from here the [http://atlas.sourceforge.net/index.php?page=download Atlas download page].<br />
# Start the installation, but let the directory be something other than the FlightGear directory. Let us say <tt>C:\Atlas</tt>.<br />
# After installation open <tt>C:\Atlas</tt> (or whatever directory you selected during installation).<br />
# In the <tt>bin/win32</tt> folder select everything except <tt>glut32.dll</tt>. And copy the selection to your <tt>flightgear/bin/win32</tt> directory.<br />
# Next copy the data files seperately. Don't copy the folders, copy each file and place it in the respective sub-directory.<br />
<br />
'''Note:''' If you find this method hard you can go ahead with the default installation.<br />
<br />
===Creating the Maps===<br />
<br />
Start the Command Prompt...to do this click start>Run ...type cmd and hit enter.<br />
Type... <br />
cd C:\Program Files\FlightGear\bin\win32<br />
Replace C: with the drive in which FlightGear is installed. This is the default directory. If you changed it during the time of installation then enter your directory (if you don't know your directory then right click your flightgear icon, click properties then copy the target line. Remove the quotes and fgrun.exe).<br />
Now Type...<br />
set FG_ROOT=C:\Program Files\FlightGear\data<br />
Replace the directory if necessary.<br />
Now type...<br />
set FG_SCENERY=C:\Program Files\FlightGear\Data\Scenery;C:\Program Files\FlightGear\Scenery<br />
Replace the directory if necessary. You separate scenery locations with a ";".<br />
Now type<br />
map --headless --size=256 --atlas=C:\Program Files\FlightGear\data\Atlas<br />
This puts the files in <tt>C:\Program Files\FlightGear\data\Atlas</tt>. If you want the files in a different location just replace <tt>C:\Program Files\FlightGear\data\Atlas</tt> with the location you want.<br />
<br />
The option --headless makes the whole process go much much faster!<br />
<br />
The --size=256 gives a certain resolution in Atlas, meaning that each map generated will be 256x256 pixels. For higher resolutions you would use =512 or =1024 or for lower resolutions you would use =64 or =128.<br />
<br />
Therefore, to create low resolution maps type...<br />
map --headless --size=64 --atlas=C:\Program Files\FlightGear\data\Atlas\lowres<br />
<br />
'''Note 1:''' Some PC's show Error when used in headless mode. Remove ''--headless'' if you get such an error.<br />
<br />
'''Note 2:''' Some PC's get errors when they write program files. If you are getting it write Progra~1 instead of Program Files.<br />
<br />
There are a lot of commands that can be used in Map. To see them type...<br />
map --help<br />
<br />
===Run Atlas===<br />
We need to change the Atlas icon on your desktop slightly. Right click the icon and select properties. In the target box completely delete the text and replace with<br />
"C:\Program Files\FlightGear\bin\win32\atlas.exe" "--fg-root=C:\Program Files\FlightGear\Data" --path=F:\FlightGear\Atlas --udp=5500<br />
<br />
This should be all 1 line in the target box. <br />
<br />
In the [[FlightGear Wizard]] that you get after double clicking the FlightGear icon, on the page after selecting your airport there is a check box option for Atlas, tick it. Enter your IP address usually 192.168.1.100 (To find your ip address, run command prompt. Type ipconfig and u will get your ip address from the information you get. In the ports boxes enter 5500. Click Run.<br />
<br />
===Keys===<br />
You can control the Map display with the following keys:<br />
<br />
<table><br />
<tr><td width="70px">+</td><td>Zoom in</td></tr><br />
<tr><td>-</td><td>Zoom out</td></tr><br />
<tr><td>a/A</td><td>Show/hide Airports</td></tr><br />
<tr><td>C</td><td>Toggle auto-centering</td></tr><br />
<tr><td>c</td><td> Center map on Aircraft</td></tr><br />
<tr><td>d/D</td><td> Hide/show the info interface and the graphs window</td></tr><br />
<tr><td>f/F </td><td> Select next (f) or previous (F) flight track</td></tr><br />
<tr><td>j/J </td><td> Toggle search interface</td></tr><br />
<tr><td>L </td><td> Show the next downloading tile</td></tr><br />
<tr><td>l </td><td> Schedule/de-schedule tile at current lat/lon</td></tr><br />
<tr><td>n/N </td><td> Show/hide navaids</td></tr><br />
<tr><td>o/O </td><td> Open flight file</td></tr><br />
<tr><td>s/S </td><td> Save flight file</td></tr><br />
<tr><td>t/T </td><td> Toggle showing the bitmap overlay (yes, that's the maps!)</td></tr><br />
<tr><td>w/W </td><td> Close the current track (Warning, this terminates live aircraft tracking over network for good!)</td></tr><br />
<tr><td>u/U </td><td> Unattach current flight trac, ie start a new track</td></tr><br />
<tr><td>v/V </td><td> Show/hide names of airports/navaids</td></tr><br />
<tr><td>Space </td><td> Show/hide main interface</td></tr><br />
</table><br />
<br />
<br />
<br />
<br />
'''Enjoy Playing!!!'''<br />
<br />
==External links==<br />
* [http://atlas.sourceforge.net The Atlas website]<br />
<br />
[[Category:Software]]<br />
[[Category:GPL]]</div>Raazeer