Volunteer: Difference between revisions

Jump to navigation Jump to search
1,726 bytes removed ,  31 July 2010
m
Line 87: Line 87:


==== HowTo Writers ====
==== HowTo Writers ====
Various parts of FlightGear are currently not yet sufficiently documented, also available documentation is often not really suitable to be used by non-developers. This results in users being unaware of the wide range of features and possibilities that FlightGear supports already. As "HowTo writer" you should be able to document your own experiences with FlightGear in a clear and concise style, so that others can easily follow your instructions on order to make use of FlightGear's less known features. HowTo guides do not need to be very comprehensive, they shall only serve the purpose of providing users with easy to follow instructions about how to set up their version of FlightGear.  
Various parts of FlightGear are currently not yet sufficiently documented, also available documentation is often not really suitable to be used by non-developers. This results in users being unaware of the wide range of features and possibilities that FlightGear supports already.  


'''Topics that could currently use some HowTos are:'''
As "HowTo writer" you should be able to document your own experiences with FlightGear in a clear and concise style, so that others can easily follow your instructions on order to make use of FlightGear's less known features. HowTo guides do not need to be very comprehensive, they shall only serve the purpose of providing users with easy to follow instructions about how to set up their version of FlightGear.


* configuring FlightGear for multi screen setups, where a single "master" machine running FlightGear is connected to an arbitrary amount of "slaves" that can be set up to display different views, most of the required information can be obtained from the mailing list archives by searching for "multi", "screen", "head", "slave", "master", "display","frustrum" (or any combination of these) [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16803.html]
Adding screenshots to articles is another excellent way for improving the existing documentation.
* using basic radio navigation equipment in FlightGear
 
* using the GUI autopilot
Topics that could use some HowTos are listed in [[Article requests].
* using the KAP140 autopilot
* interfacing FlightGear to real hardware (basically, how to use the property tree network interfaces)
* creating custom [[AI]] scenarios
* interfacing FlightGear with other software (mainly atlas,opencockpits - property tree usage again)
* creating and modifying scenery using fgsd
* creating and adding custom views
* setting up additional aircraft panels
* adding arbitrary instruments from the base package to existing aircraft panels
* using the nasal scripting language to add custom logics to FlightGear
* adding custom menu items to the FlightGear menubar
* creating and using XML based GUI dialogs
* creating customized joystick configuration files
* using and creating XML protocols
* configuring and using [[AI]] ATC
* creating and adding support for new textures to FlightGear
* translating FlightGear
* modifying and creating new sound effects for aircraft
* helicopter flying with FlightGear
* creating custom FDMs
* using the replay system
* recording FlightGear videos
* using fgsd
* using taxidraw
* modifying the airports database
* modifying the navaid database
* using terraysnc
* converting 3D models from other flight simulators for use with FlightGear
* installing nvidia drivers under linux (misc mailing list discussions recently)


==== Documentation Editors/Reviewers ====
==== Documentation Editors/Reviewers ====

Navigation menu