New to FlightGear: Difference between revisions

Jump to navigation Jump to search

New to FlightGear (view source)

Revision as of 12:53, 28 May 2014

264 bytes removed ,  28 May 2014
more cleanup and update
(→‎Making your first flight: cleanup, update, removed duplication)
(more cleanup and update)
Line 12: Line 12:
Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you're willing to do some testing there's a nightly build for Windows or Mac available for download at the [[FlightGear Build Server]].
Depending on your technical expertise you may choose the [[Git]] development version of FlightGear, which typically has more features and can be required by some of the latest developmental aircraft, but can be unstable and is more complicated to get for non-Windows users. In general, the development version is not advised to the average user, but if you're willing to do some testing there's a nightly build for Windows or Mac available for download at the [[FlightGear Build Server]].


You may also order FlightGear on a set of DVDs, available at [http://www.flightgear.org/dvd/].
Also, note that those using the Git version of FlightGear may choose to update their aircraft files through the Git system.
 
You may also order FlightGear on a set of DVDs, available on the [http://www.flightgear.org/dvd/ FlightGear main site].


=== Installing on Windows ===
=== Installing on Windows ===
Line 138: Line 140:
The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You cannot use the ''Autopilot'' dialog from the menu with this aircraft. You must use the autopilot device in the panel.
The Cessna 172 comes with a [[Bendix/King KAP140 Autopilot]] in its virtual cockpit. You cannot use the ''Autopilot'' dialog from the menu with this aircraft. You must use the autopilot device in the panel.


== Getting help ==
== The FlightGear community ==
Besides this wiki, there are more places that can be visited to obtain information or request help:
=== Getting help ===
This page is designed to give the user the essential things they need to know about using FlightGear for the first time. Besides the [[Portal:Users|User portal]] of this wiki, there are other pages you may want to read:
* [[Troubleshooting Problems]] to help you with the most common issues;
* [[Frequently asked questions]];
...and communication channels that can be used to obtain information or request help:
* The [[FlightGear Manual]], a ''must read'' for beginners;
* [http://forum.flightgear.org FlightGear Forum] and its subforums;
* [[FlightGear IRC channel]], the quickest way to get help;
* [[Mailing list|FlightGear users mailing list]], biggest chance to get in contact with core developers;
* Documents bundled with the release package.
* Documents bundled with the release package.
* [http://forum.flightgear.org FlightGear Forum]
* [[FlightGear IRC channel]], the quickest way to get help.
* [[Malinglists|FlightGear users mailing list]], biggest chance to get in contact with developers.


== Getting more detailed information ==
=== Customizing FlightGear without compiling it ===
This page is designed to give the user the essential things they need to know about using FG for the first time.
[http://www.flightgear.org/Downloads/ Our website] offers precompiled binaries for download and install on Windows and Mac OSX, while most Linux distros provide a packaged version in their repositories.


You now know enough to get started with FlightGear. To learn more, you may wish to start at the main page of this wiki and read the more detailed Getting Started section, or Using FlightGear section or study the Flying Resources to learn more about flight instruments and how to navigate and fly your aircraft.
Although the install is binary, most of FlightGear's systems are open to configuration through [[XML]] files and [[NASAL scripting]]. You are free ''and encouraged'' to make changes to aircraft flight models, scenery, textures, OpenGL [[shader]]s and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. If this is what you intend to do, take a look at the [[Portal:Developer|Developer portal]].


Also, note that those using the Git version of FlightGear may choose to update their aircraft files through the Git system.
=== How you can help ===
 
{{Main article|Volunteer}}
The following are some issues raised by new users of FlightGear. More detailed troubleshooting and answers can be found in [[Troubleshooting Problems]] and the [[FAQ]].
FlightGear is an opensource, volunteer based project. That means that whatever you find here comes from passion, spare time and nothing else. This includes the simulator, the scenery, the aircraft, the wiki, the forum and everything else. Volunteers, i.e. ''people that do things'', are fundamental to this project: without them, it wouldn't make a single step forward. So it is essential that contributors have fun in what they do.
 
=== I do not want to compile FlightGear, what can I do? ===
[http://www.flightgear.org/Downloads/ Our website] offers precompiled binaries for download and install on a variety of systems. Current platforms are Windows, Linux, Solaris, SGI, Mac OSX and FreeBSD. These are offered as a convienence and availablility may vary at times.


Note: FlightGear is highly configurable through editable [[XML]] files. You are free, and encouraged to, make changes to aircraft flight models and any other feature you wish to change for your personal satisfaction or to share with other FlightGear users. The flight model is not defined in a binary file. It is easy to modify (given enough knowledge). Although the install is binary, most of FlightGear's system is open to configuration through XML files and [[NASAL scripting]].
If you really plan to contribute to this project, you should take a look at some articles that will give you some hints:
* [[Howto:Understand the FlightGear development process]]
* [[Implementing new features for FlightGear]]
* [[How the FlightGear project works]]


=== Does FlightGear come with a printed manual? ===
There are never enough people contributing, and the fields where their help would be appreciated are many:
You are invited to read the [[FlightGear Manual]] online as HTML or download it as PDF for viewing with Acrobar Reader or printing. It's not always up to date with bleeding-edge developments but provides a good start for beginners and it's a ''must read'' if you have no or little idea of how to fly.
;Testing :
 
== How you can help ==
{{Main article|Volunteer}}
 
=== Testing ===
* [[Building Flightgear|Build]] the latest Git code or download snapshots (link)
* [[Building Flightgear|Build]] the latest Git code or download snapshots (link)
* [http://flightgear-bugs.googlecode.com File bug reports]
* [http://flightgear-bugs.googlecode.com File bug reports]
=== Debugging & Profiling ===
* Running FlightGear via valgrind to track down memory leaks
* Running FlightGear via valgrind to track down memory leaks


=== Support ===
;Support :
* Help new users with downloading, compiling, installing and running FlightGear (http://forum.flightgear.org or on IRC)
* Help new users with downloading, compiling, installing and running FlightGear (http://forum.flightgear.org or on IRC)
* Provide Ideas & Suggestions, see: [[Feature Requests / Proposals / Ideas]]
* Provide Ideas & Suggestions, see: [[Feature Requests / Proposals / Ideas]]
Line 178: Line 178:
* Help provide new contents for missing wiki pages
* Help provide new contents for missing wiki pages


=== Development ===
;Development :
* Writing documentation! Everyone is welcome to contribute to "The Manual"; having at least a little experience with LaTeX makes the task easier. Please contact the authors of The Manual if you would like to add corrections or whole chapters, you may also simply use this wiki to contribute fixes, modifications and new contents.
* C/C++ Coding:
* C/C++ Coding:
** provide source code cleanups (i.e. help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
** provide source code cleanups (i.e. help in the process of migrating over to a primarily smart pointer-based memory management approach using SGSharedPtr)
** provide bug fixes [[Bugs]]
** provide bug fixes [[Bugs]] or new features  
** provide enhanced features [[Feature Requests / Proposals / Ideas]]
** provide new features  
** get involved in any of the other FlightGear-affiliated projects  
** get involved in any of the other FlightGear-affiliated projects  
* Aircraft development (3D modelling, textures, FDMs, scripting)
* Aircraft development (3D modelling, textures, FDMs, scripting)
* Scenery development
* Scenery development (terrain, model, weather)


[[Category:FlightGear]]
[[Category:FlightGear]]
Bigstones
573

edits

Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/71968"

Navigation menu