FlightGear logos

2009-09-21T19:17:11Z

Hellosimon:

Feel free to add your FlightGear logo here :

== Official logo ==
[[Image:Fglogosm.jpg]]

* Author: Michael Smith ([http://flightgear.org/thanks.shtml ?])
* Source: [http://www.flightgear.org www.flightgear.org]

== A-10 Logo ==

[[Image:Wiki_logo.png]]

* Author: Wes Summers
* License: http://creativecommons.org/licenses/by-sa/3.0/
* Source: [[Media:A-10_logo.pdf| Illustrator PDF]]

== New Test Logo ==
[[Image:Flightgear-logov2.png]]

* Author: BBCTV (Japanese Flightgear User)
* License: Copyright Flightgear
* Source: Made with Adobe Illustrator

== Set of logos for Wiki ==

[[Image:Fg_trails_lc.png]] [[Image:Fg_wings_large.png]] [[Image:Fg_wings_up.png]] [[Image:Fg_trails_large.png]]

* Author: Wes Summers
* License: http://creativecommons.org/licenses/by/3.0/

File:Fg wings up.png

2009-09-21T19:11:50Z

Hellosimon: uploaded a new version of "File:Fg wings up.png"

File:Fg wings large.png

2009-09-21T19:09:58Z

Hellosimon: uploaded a new version of "File:Fg wings large.png"

File:Fg trails lc.png

2009-09-21T14:02:12Z

Hellosimon: uploaded a new version of "File:Fg trails lc.png"

FlightGear logos

2009-09-21T13:42:15Z

2009-09-18T17:25:02Z

Hellosimon: upgrade notice

Upgraded MediaWiki to 1.15.1 from 1.11. Converted database character set from latin1 to UTF-8. Document any errors with garbled characters or pages not working here. [[User:Hellosimon|Hellosimon]] 17:25, 18 September 2009 (UTC)

Mediawiki has been updated to 1.6.7. Email me (hellosimon at gmail com) with any site problems. [[User:Hellosimon|Hellosimon]] 12:16, 10 June 2006 (EDT)
:Isn't it time to upgrade the wiki to the latest version (1.15)? There's a lot improved over de past three years ;)
:Regards, [[User:Gijs|Gijs]] 08:22, 8 September 2009 (EDT)

The rss and atom feeds have been fixed - There were extra newlines that needed to be removed at the end of LocalSettings.php [[User:Hellosimon|Hellosimon]] 13:12, 20 June 2006 (EDT)

I've now restricted edits to users who have confirmed their email address. I've done this because I think we have some spam bot users and a captcha won't help those at this point. Also, I plan on updating medawiki to 1.7.x after I test the upgrade on a local mirror. [[User:Hellosimon|Hellosimon]] 11:21, 18 July 2006 (EDT)

Portal:Developer

2008-08-12T03:00:33Z

Hellosimon: add link

<div align="center">
[[Portal:Developer|Developer]] - [[Portal:User|User]]
</div>

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:100%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="1" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">The Developer Portal</h2>
|-
|style="color:#000;"|
This portal is for developers contributing to FlightGear. If you wanna help with FlightGears development, it's a good idea to subscribe yourself to the [http://lists.sourceforge.net/lists/listinfo/flightgear-devel FlightGear devel] mailing list. The [http://sourceforge.net/mailarchive/forum.php?forum_name=flightgear-devel list archive] is also available and should be searched before posting the same question.<br><br>
'''The FlightGear project is looking for organizations/individuals who would be willing to help sponsor a fulltime project coordinator/manager to help oversee the overall development process If you are interested in helping or have anything else to contribute to this issue, please subscribe to the the [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg11813.html FlightGear Devel mailing list] to discuss details.'''
|}
|}

{|style="border-spacing:8px; margin:0px -8px;"
|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top; color:#000;"|
{|width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Latest Organizational Issues</h2>
|-
|style="color:#000;"|
* [[ Project Infrastructure Enhancements ]]
* [[Google Summer of Code Candidate Projects]] - application template to allow community members to prepare a possible application to decrease the effort required to actually apply
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Background Info</h2>
|-
|style="color:#000;"|
* [[Resources]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Current Efforts/Branches & Work in Progress</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.org/forums/viewtopic.php?t=1378 Efforts to create photo realistic scenery for FlightGear] (Images: [http://www.brest-metropole-oceane.fr/vueduciel/images/101_106.jpg] [http://blaniel.free.fr/pub/flightgear/brest/brest1.png] [http://helijah.free.fr/LFRB/fgfs-screen-001.jpg] [http://helijah.free.fr/LFRB/fgfs-screen-003.jpg]
* [http://www.flightgear.org/forums/viewtopic.php?t=755 New aircraft model under development: Bede BD-5J]
* [http://www.flightgear.org/forums/viewtopic.php?t=542 F14-Tomcat aircraft model under development]
* [http://www.flightgear.org/forums/viewtopic.php?t=1001 787 being revamped]
* [http://www.flightgear.org/forums/viewtopic.php?t=1436 LFLJ enhancements]
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg16176.html Free Walking mode for FlightGear using the Jeep vehicle in CVS]
* [http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg15388.html Random Trees for FlightGear]

'''[[Work in progress|More...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Compiling</h2>
|-
|style="color:#000;"|
* [[ Building Flightgear ]]
* [[ Building Flightgear - Windows]]
* [[ Building FlightGear Launch Control ]]
* [[ Building Terragear ]]
* [[ Keeping FlightGear (win32) up to date without compiling]]
* [[ OpenSceneGraph ]]
* [[ Tools of the Trade ]]
* [[ Using TortoiseCVS with FlightGear ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Contributing</h2>
|-
|style="color:#000;"|
* [[ Code Cleanup ]]
* [[ Contributor Repositories ]] mirrors, branches and forks privately maintained by contributors
* [[ Development Resources ]]
* [[ Extension Support ]]
* [[ Submitting Patches ]]
* [[ Technical Reports ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Code Internals</h2>
|-
|style="color:#000;"|
* [[ Commands ]]
* [[ FDM API ]]
* [[ File Formats ]]
* [[ Initialization Sequence ]]
* [[ Nasal scripting language ]]
* [[ Property Tree ]]
* [[ Subsystems ]]
* [[ UML Diagrams ]]
* [[ YASim ]]
|-
|}

|class="MainPageBG" style="width:50%; border:1px solid #d9e2e2; background:#efefef; vertical-align:top"|
{| width="100%" cellpadding="2" cellspacing="5" style="vertical-align:top; background:#efefef;"
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Todo</h2>
|-
|style="color:#000;"|
* [[ Bugs ]]
* [[ Feature Requests / Proposals / Ideas ]]
* [[ FGFS Todo ]]
* [[ FlightGear Expo Checklist ]]
* [[ Long Term Goals ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Done</h2>
|-
|style="color:#000;"|
* [[ Changes since 0.9.10 ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">HowTos</h2>
|-
|style="color:#000;"|
* [[Howto: Add smooth ("Ambient Occlusion") shadows in Blender|Add smooth shadows in Blender]]
* [[Howto: 3D Aircraft Models|3D Aircraft Models]]
* [[Howto: Add aircraft lights|Add aircraft lights]]
* [[Howto: Edit a livery|Edit a livery]]
* [[Howto: Illuminate faces|Illuminate faces]]
* [[Howto: Make a helicopter|Make a helicopter]]
* [[Howto: Set up a multiplayer server|Set up a multiplayer server]]
'''[[:Category:Howto|More...]]'''
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Instrumentation</h2>
|-
|style="color:#000;"|
* [[ Creating instruments for FG ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Nasal scripting</h2>
|-
|style="color:#000;"|
* [[ Nasal scripting language ]]
* [[ Writing simple scripts in %22nasal%22 ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Autopilot configuration</h2>
|-
|style="color:#000;"|
* [http://www.flightgear.org/Docs/XMLAutopilot/ FlightGear Autopilot] (Theory, Configuration, and Tuning)
* [[ Autopilot Tuning Resources ]]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">3D Modeling</h2>
|-
|style="color:#000;"|
* [[ Howto: 3D Aircraft Models|3D Aircraft Models]] (howto)
* [[ Aircraft Information Resources ]]
* [[ Model Import and Export ]]
* [[ Modeling - FAQ ]]
* [[ Modeling - Getting Started ]]
* [[ Modeling Resources ]]
* [[ Modeling - SketchUp]]
* [[ Normals and Transparency Tutorial ]]
* [http://en.wikibooks.org/wiki/Blender_3D:_Noob_to_Pro Blender3D Modeling]
|-
! <h2 style="margin:0; background:#0f7a71; font-size:120%; font-weight:bold; border:1px solid #d9e2e2; text-align:left; color:white; padding:0.2em 0.4em;">Scenery</h2>
|-
|style="color:#000;"|
* [[ Blender Ground Signs Tutorial]]
* [[ Placing 3D Objects with the UFO ]]
* [[ Signs ]] (placing and explanation)
* [[ Using Terragear ]]
* [[ Using the Custom Scenery TerraGear Toolset ]]
|-
|}
|}

__NOTOC__
__NOEDITSECTION__

== Developer Documentation ==
=== RFC Topics ===
'''Clarification:'''In its current form, the RFC section is exclusively based on and covered by previous mailing list and forum discussions (as well as various wiki entries), as such it is not supposed to reflect work in progress (RFC="Request For Comments" and not WIP), but is rather to be seen as an attempt to provide comprehensive analyses and summaries of key issues identified in various FlightGear related discussions and feature requests (which are to be linked to in the corresponding resource sections, if that didn't yet take place, it's because of most of these RFCs being indeed WIP).

Thus, RFC entries are not meant to imply anyone "working" on any of these issues, in fact only because an RFC entry is listed here doesn't necessarily mean that work on that particular issue is endorsed by the FlightGear community.

* [[Next Generation Scenery ]] - revamping the FG scenery engine
* [[Keyboard function priority list]] - reorganizing FlightGear keybindings
* [[FlightGear Sessions]] - discussing possible steps to finally allow aircraft to be reliably switched at runtime
* [[Formalizing Aircraft Status]] - discussing suggestions about how to more properly describe aircraft development status
* [[Simplifying Aircraft Deployment]] - identifying potential steps to simplify deployment of FlightGear aircraft
* [[FDM engine feature standardization]] - discussing possible steps to standardize feature support of mainstream FlightGear FDM engines
* [[FlightGear Glass Cockpits]] - discussing required infrastructure changes to enable non-developers to easily access FlightGear-internals in order to enable them to model complex glass cockpit-type aircraft instrumentation systems
* [[Recommended Property Tree Enhancements]] - discussing possible property tree enhancements to help ensure integrity of crucial runtime state
* [[Backwards Compatibility Initiative]] - discussing possible ways to improve FlightGear's backwards compatibility
* [[Recommended Project Policies]] - discussing recommended policies for future contributions to the project
* [[Distributed Interactive Simulation]] - discussing possible steps to prepare FlightGear for HLA
* [[Property Tree Reorganization]] - reorganizing the property tree (i.e. implementing and enforcing existing property/node naming conventions)

=== Miscellaneous ===
* [[ Glass Cockpit Projects ]]
* [[ Copyright Inquiry ]]
* [http://www.cafepress.com/fgfs_gear FlightGear - Gear]
* [[ Sign Specification Proposal ]]

== Middleware & Base Package Development ==

* [[:Category:Aircraft TODO]]

=== Misc ===
* [[FGSD- How to make a airport]]

Portal:User

2008-07-10T16:36:04Z

Hellosimon: add link to logo repository

FlightGear logos

2008-07-10T16:33:58Z

Hellosimon: add logo repository

File:A-10 logo.pdf

2008-07-10T16:25:42Z

Hellosimon: Vector file for logo Author: Wes Summers License: http://creativecommons.org/licenses/by-sa/3.0/

Vector file for logo
Author: Wes Summers
License: http://creativecommons.org/licenses/by-sa/3.0/

File:Wiki logo.png

2008-07-10T16:24:20Z

Hellosimon: Current wiki logo Author: Wes Summers License: http://creativecommons.org/licenses/by-sa/3.0/

Current wiki logo
Author: Wes Summers
License: http://creativecommons.org/licenses/by-sa/3.0/

Talk:Main Page/Archive/2006-2011

2008-06-10T15:26:23Z

Hellosimon: cleanup and update

== Making the manual accessible via wiki software ==
On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users.
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).

As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST)

== Using a dedicated FAQ database ==
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).

== Using a dedicated bug tracker ==

A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)

* how to define and limit editing rights for certain users?

It's better to have one consolidated source of information for both bugs and descriptions. For now, user has to search through mailing lists, forums, user manuals (even not a single user manual, but several) and this wiki. It's absolutely not convinient for both users (they spend lot's of time searching required information) and developers (they spend lot's of time updating and syncronizing certain information in various sources).

This wiki is suitable for bug tracking too. Users can provide feedback in a convinient form. They just open the corresponding page and add their bug to the list. Developers can respond to the posted bugs right away. Mailing lists are a lot less user-friendly and effective and a lot less popular among users (not developers) in this regard, this is the reason why some bugs may stay unreported and why many users forget about FlightGear as soon as they run into a problem.

Unfortunately, it seems to me, this wiki is not popular among developers and users. -- [[User:Alfozavr|Alfozavr]] 06:59, 17 June 2007 (EDT)

== Backups ==
Is the database regularly backed up? What about hosting the wiki directly at flightgear.org?
--[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST)

Yes, there are daily backups of the [http://hellosimon.org/backups code] and of the [http://hellosimon.org/backups/mysql database]. We also have off-site backups. [[User:Hellosimon|Hellosimon]] 17:04, 4 February 2008 (EST)
----

== Updates ==

I've updated MediaWiki to 1.11.1 so if you notice any regressions let me know. [[User:Hellosimon|Hellosimon]] 15:03, 2 March 2008 (EST)

The wiki has moved to a new server which should relieve the performance problems. [[User:Hellosimon|Hellosimon]] 11:26, 10 June 2008 (EDT)

=== Regressions ===
* code passages (i.e. XML) are not highlighted anymore

=== Proposed Additions ===
* what about some sort of true syntax-highlighting module, that would properly highlight XML & C++ ?
* PDF Export - [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF]

Regarding the manual: isn't there a possibility to export wikimedia pages to PDF format? That way, we could maintain the whole manual via this wiki. Any thoughts?--[[User:FlightZilla|FlightZilla]] 18:10, 17 June 2006 (EDT)

If you check out the following links, you'll see that there are extensions available that would make it possible to easily provide PDF exports for all contents stored here, that way it would also become feasible to consider migrating the entire manual over to this wiki, so that it would also become more maintainble in the end:
http://meta.wikimedia.org/wiki/WikiPDF
http://meta.wikimedia.org/wiki/PDF_Export
--[[User:FlightZilla|FlightZilla]] 17:21, 19 June 2006 (EDT)

Hello, guys. If I get it right, you're discussing various documentation types here.

I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?

Talk:Main Page/Archive/2006-2011

2008-03-02T20:03:05Z

Hellosimon: mediawiki update

= Initial ramblings=
Sorry, I don't want to junk up the main page with someone's opinion on "the manual" and the wiki documentation. [[User:Hellosimon|Hellosimon]] 10:41, 5 June 2006 (PDT)

I too think that the Main Page shouldn't get too verbose. I don't understand the need for that little comment in the User Documentation section, but if someone insists on having it placed on the wiki, then a compromise should be reached somehow. I suggest moving it to some other articles. --[[User:64.229.232.249|64.229.232.249]] 16:14, 5 June 2006 (PDT)

I agree: Simon, while you have definitely done some nice job here, you need to realize that you can achieve much more by collaborating constructively with other contributors rather than by simply opposing contributions of people who have in fact contributed significant amounts of work to the project for quite some time.
I think, the corresponding paragraph wasn't an "opinion" on the manual or the wiki and it certainly wasn't meant to reflect badly upon your efforts, rather it was merely meant to complement the wiki.
There's simply a very clear relationship between "The Manual" and "the wiki", if you fail to recognize this, your contribution (that is, this wiki) -even though very much needed and extremely worthwhile- is condemned to fail eventually.

== Making the manual accessible via wiki software ==
On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users.
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).

As the manual is maintained in LaTex, is would be very hard to translate the wiki notes to include them in the manual. I suspect that this will be a "Won't Fix" as it is easier to copy and paste the text from the wiki and go from there. I am open to ideas though. [[User:Gorilla|Gorilla]] 06:33, 2 March 2008 (EST)

== Using a dedicated FAQ database ==
Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).

Concerning database backups: you should preferably set up a cron job to upload a compresed SQL dump to the flightgear FTP server on a regular (daily?) basis, I am sure you'll be granted write access to a corresponding directory, this would ensure that everything will in fact be backed up regularly and possibly even mirrored.

["I think, the corresponding paragraph wasn't an "opinion" on the manual or the wiki and it certainly wasn't meant to reflect badly upon your efforts, rather it was merely meant to complement the wiki."]
This assumption is correct. The manual is the center piece of the FlightGear user documentation, so does anyone have a suggestion (one that makes sense) on how to deal with my comments aside from "removing it" or "moving it into negligence/insignificance" ?
Martin.
== Using a dedicated bug tracker ==
Martin's text has been placed (not by me) in the paragraphs at the top. I rather like this compromise and hope it works for everyone. I agree a bugtracker would be ideal - didn't someone start one? Also, if anyone wants to grant ftp access to a server, I'll gladly cron a script to upload the backup tarball. I have it backed up to multiple locations in the meantime.
- [[User:Hellosimon|Hellosimon]] 11:36, 11 June 2006 (EDT)

A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)
= PDF Export Facilities =
* [http://sourceforge.net/projects/wikipdf/ Wikimedia plugin to export to PDF]

Regarding the manual: isn't there a possibility to export wikimedia pages to PDF format? That way, we could maintain the whole manual via this wiki. Any thoughts?--[[User:FlightZilla|FlightZilla]] 18:10, 17 June 2006 (EDT)

If you check out the following links, you'll see that there are extensions available that would make it possible to easily provide PDF exports for all contents stored here, that way it would also become feasible to consider migrating the entire manual over to this wiki, so that it would also become more maintainble in the end:
http://meta.wikimedia.org/wiki/WikiPDF
http://meta.wikimedia.org/wiki/PDF_Export
--[[User:FlightZilla|FlightZilla]] 17:21, 19 June 2006 (EDT)

Hello, guys. If I get it right, you're discussing various documentation types here.

I think, this wiki is a lot more convenient than any other form of keeping documentation and at the same time communicating. It can be edited fast and easily and maintained up-to-date. However, the following questions need be solved:
* how to convert it to an offline version (maybe .pdf) so that it could be bundled with the FlightGear base package?

= Limiting access rights =
* how to define and limit editing rights for certain users?

It's better to have one consolidated source of information for both bugs and descriptions. For now, user has to search through mailing lists, forums, user manuals (even not a single user manual, but several) and this wiki. It's absolutely not convinient for both users (they spend lot's of time searching required information) and developers (they spend lot's of time updating and syncronizing certain information in various sources).

This wiki is suitable for bug tracking too. Users can provide feedback in a convinient form. They just open the corresponding page and add their bug to the list. Developers can respond to the posted bugs right away. Mailing lists are a lot less user-friendly and effective and a lot less popular among users (not developers) in this regard, this is the reason why some bugs may stay unreported and why many users forget about FlightGear as soon as they run into a problem.

Unfortunately, it seems to me, this wiki is not popular among developers and users. -- [[User:Alfozavr|Alfozavr]] 06:59, 17 June 2007 (EDT)

= 02/2008: Wiki issues (database, login & performance problems) =
Recently, the wiki seems to be suffering rather seriously from database connection issues, also often login information doesn't seem to be retained properly and performance is often seriously affected, as well.

Error messages include:
Sorry! This site is experiencing technical difficulties.

Try waiting a few minutes and reloading.

(Can't contact the database server: User hellosimonor1 already has more than 'max_user_connections' active connections (mysql01.powweb.com))

I too am frustrated and fed up with the performance issues I've had with this host and I'm currently researching alternative hosting. [[User:Hellosimon|Hellosimon]] 15:06, 4 February 2008 (EST)

Is the database regularly backed up? What about hosting the wiki directly at flightgear.org?
--[[User:MILSTD|MILSTD]] 15:25, 4 February 2008 (EST)

Yes, there are daily backups of the [http://hellosimon.org/backups code] and of the [http://hellosimon.org/backups/mysql database]. We also have off-site backups. I'm trying to reduce the burden on Curt rather than add to it, but he owns the domain so it's his call. [[User:Hellosimon|Hellosimon]] 17:04, 4 February 2008 (EST)
----
There's a problem with the images to. I get this message at the place of a thumbnail when I upload new images:

Image:Error creating thumbnail: sh: line 1: /usr/bin/convert: No such file or directory
It looks like something with the database to...--[[User:Gijs|Gijs]] 15:01, 5 February 2008 (EST)

The link to convert changed to /usr/local/bin. This should be fixed now. [[User:Hellosimon|Hellosimon]] 15:00, 2 March 2008 (EST)

= 03/02/2008: Wiki Update =

I've updated MediaWiki to 1.11.1 so if you notice any regressions let me know. [[User:Hellosimon|Hellosimon]] 15:03, 2 March 2008 (EST)

2006-07-15T06:53:40Z

Hellosimon: Reverted edits by 195.175.37.71 (Talk); changed back to last version by Hellosimon

Sorry, I don't want to junk up the main page with someone's opinion on "the manual" and the wiki documentation. [[User:Hellosimon|Hellosimon]] 10:41, 5 June 2006 (PDT)

I too think that the Main Page shouldn't get too verbose. I don't understand the need for that little comment in the User Documentation section, but if someone insists on having it placed on the wiki, then a compromise should be reached somehow. I suggest moving it to some other articles. --[[User:64.229.232.249|64.229.232.249]] 16:14, 5 June 2006 (PDT)

I agree: Simon, while you have definitely done some nice job here, you need to realize that you can achieve much more by collaborating constructively with other contributors rather than by simply opposing contributions of people who have in fact contributed significant amounts of work to the project for quite some time.
I think, the corresponding paragraph wasn't an "opinion" on the manual or the wiki and it certainly wasn't meant to reflect badly upon your efforts, rather it was merely meant to complement the wiki.
There's simply a very clear relationship between "The Manual" and "the wiki", if you fail to recognize this, your contribution (that is, this wiki) -even though very much needed and extremely worthwhile- is condemned to fail eventually.

On the other hand, I would recommend to also look into making "The Manual" editable via some sort of web based frontend, this would also ensure that people are able to easily contribute modifications to the manual, which is really the ultimate source for flightgear users.
A possible approach might be to import the underlying LaTex sources in docbook format into some sort of docbook based wiki (i.e. http://sourceforge.net/projects/doc-book/).

Also, I feel there are some sections covered in the wiki that aren't really optimally handled by a wiki: most notably the "FAQ" section should preferably be implemented via some sort of dynamic FAQ system (i.e. http://www.phpmyfaq.de), likewise the sections titled "Bugs", "TODO", "Feature Requests", "ideas" etc. could probably all be handled far more effectively by using a real bug tracker such as bugzilla (http://www.bugzilla.org/), phpbugtracker (http://phpbt.sourceforge.net/) or mantis (http://www.mantisbt.org).

Concerning database backups: you should preferably set up a cron job to upload a compresed SQL dump to the flightgear FTP server on a regular (daily?) basis, I am sure you'll be granted write access to a corresponding directory, this would ensure that everything will in fact be backed up regularly and possibly even mirrored.

["I think, the corresponding paragraph wasn't an "opinion" on the manual or the wiki and it certainly wasn't meant to reflect badly upon your efforts, rather it was merely meant to complement the wiki."]
This assumption is correct. The manual is the center piece of the FlightGear user documentation, so does anyone have a suggestion (one that makes sense) on how to deal with my comments aside from "removing it" or "moving it into negligence/insignificance" ?
Martin.

Martin's text has been placed (not by me) in the paragraphs at the top. I rather like this compromise and hope it works for everyone. I agree a bugtracker would be ideal - didn't someone start one? Also, if anyone wants to grant ftp access to a server, I'll gladly cron a script to upload the backup tarball. I have it backed up to multiple locations in the meantime.
- [[User:Hellosimon|Hellosimon]] 11:36, 11 June 2006 (EDT)

A couple of days ago I started setting up a local test bugZilla installation, while I am currently unable to provide reliable hosting, I would really not mind installing it on whatever webspace is available, likewise I can provide the preconfigured database dump if someone else wants to use the preconfigured Flightgear specific categories.--[[User:FlightZilla|FlightZilla]] 17:59, 17 June 2006 (EDT)

Regarding the manual: isn't there a possibility to export wikimedia pages to PDF format? That way, we could maintain the whole manual via this wiki. Any thoughts?--[[User:FlightZilla|FlightZilla]] 18:10, 17 June 2006 (EDT)

If you check out the following links, you'll see that there are extensions available that would make it possible to easily provide PDF exports for all contents stored here, that way it would also become feasible to consider migrating the entire manual over to this wiki, so that it would also become more maintainble in the end:
http://meta.wikimedia.org/wiki/WikiPDF
http://meta.wikimedia.org/wiki/PDF_Export
--[[User:FlightZilla|FlightZilla]] 17:21, 19 June 2006 (EDT)

Talk:Main Page/Archive/2006-2011

2006-07-15T00:34:06Z

Hellosimon: Reverted edits by 195.175.37.71 (Talk); changed back to last version by Hellosimon

Talk:Main Page/Archive/2006-2011

2006-07-14T16:40:15Z

Hellosimon: Reverted edits by 194.165.130.93 (Talk); changed back to last version by FlightZilla

Command line options

2006-07-11T17:10:32Z

Hellosimon: /* Features */ remove nonsense

Usage: fgfs [ option ... ]

{|
|__TOC__
|}

==== General Options ====
--help, -h Show the most relevant command line options
--verbose, -v Show all command line options when combined
with --help or -h
--fg-root=path Specify the root data path
--fg-scenery=path Specify the base scenery path;
Defaults to $FG_ROOT/Scenery
--language=code Select the language for this session
--disable-game-mode Disable full-screen game mode
--enable-game-mode Enable full-screen game mode
--disable-splash-screen Disable splash screen
--enable-splash-screen Enable splash screen
--disable-intro-music Disable introduction music
--enable-intro-music Enable introduction music
--disable-mouse-pointer Disable extra mouse pointer
--enable-mouse-pointer Enable extra mouse pointer
(i.e. for full screen Voodoo based cards)
--disable-random-objects Exclude random scenery objects
(buildings, etc.)
--enable-random-objects Include random scenery objects
(buildings, etc.)
--disable-ai-models Disable the artifical traffic subsystem.
--enable-ai-models Enable the artifical traffic.
--disable-freeze Start in a running state
--enable-freeze Start in a frozen state
--disable-fuel-freeze Fuel is consumed normally
--enable-fuel-freeze Fuel tank quantity forced to remain constant
--disable-clock-freeze Clock advances normally
--enable-clock-freeze Do not advance clock
--control=mode Primary control mode (joystick, keyboard,
mouse)
--enable-auto-coordination Enable auto coordination
--disable-auto-coordination Disable auto coordination
--browser-app=path Specify path to your web browser
--prop:name=value Set property to
--config=path Load additional properties from path
--units-feet Use feet for distances
--units-meters Use meters for distances

==== Features ====
--disable-panel Disable instrument panel
--enable-panel Enable instrument panel
--disable-sound Disable sound effects
--enable-sound Enable sound effects
--disable-hud Disable Heads Up Display (HUD)
--enable-hud Enable Heads Up Display (HUD)
--disable-anti-alias-hud Disable anti-aliased HUD
--enable-anti-alias-hud Enable anti-aliased HUD
--disable-hud-3d Disable 3D HUD
--enable-hud-3d Enable 3D HUD

==== Aircraft ====
--aircraft=name Select an aircraft profile as defined by a top
level -set.xml
--show-aircraft Print a list of the currently available
aircraft types

==== Flight Model ====
--fdm=name Select the core flight dynamics model
Can be one of jsb, larcsim, yasim, magic,
balloon, ada, external, or null
--aero=name Select aircraft aerodynamics model to load
--model-hz=n Run the FDM this rate (iterations per second)
--speed=n Run the FDM 'n' times faster than real time
--notrim Do NOT attempt to trim the model
(only with fdm=jsbsim)
--on-ground Start at ground level (default)
--in-air Start in air (implied when using --altitude)
--wind=DIR@SPEED Specify wind coming from DIR (degrees) at SPEED
(knots)
--turbulence=0.0 to 1.0 Specify turbulence from 0.0 (calm) to 1.0
(severe)

--ceiling=FT_ASL[:THICKNESS_FT]
Create an overcast ceiling, optionally with a
specific thickness (defaults to 2000 ft).

==== Aircraft model directory (UIUC FDM ONLY) ====
--aircraft-dir=path Aircraft directory relative to the path of the
executable

==== Initial Position and Orientation ====
--airport=ID Specify starting position relative to an
airport
--runway=rwy_no Specify starting runway (must also specify an
airport)
--vor=ID Specify starting position relative to a VOR
--ndb=ID Specify starting position relative to an NDB
--fix=ID Specify starting position relative to a fix
--airport-id=ID (Obsolete; use --airport instead.)
--offset-distance=nm Specify distance to reference point (statute
miles)
--offset-azimuth=degrees Specify heading to reference point
--lon=degrees Starting longitude (west = -)
--lat=degrees Starting latitude (south = -)
--altitude=value Starting altitude
(in feet unless --units-meters specified)
--heading=degrees Specify heading (yaw) angle (Psi)
--roll=degrees Specify roll angle (Phi)
--pitch=degrees Specify pitch angle (Theta)
--uBody=units_per_sec Specify velocity along the body X axis
(in feet unless --units-meters specified)
--vBody=units_per_sec Specify velocity along the body Y axis
(in feet unless --units-meters specified)
--wBody=units_per_sec Specify velocity along the body Z axis
(in feet unless --units-meters specified)
--vc=knots Specify initial airspeed
--mach=num Specify initial mach number
--glideslope=degrees Specify flight path angle (can be positive)
--roc=fpm Specify initial climb rate (can be negative)

==== Rendering Options ====
--bpp=depth Specify the bits per pixel
--fog-disable Disable fog/haze
--fog-fastest Enable fastest fog/haze
--fog-nicest Enable nicest fog/haze
--disable-horizon-effect Disable celestial body growth illusion near the
horizon
--enable-horizon-effect Enable celestial body growth illusion near the
horizon
--disable-enhanced-lighting Disable enhanced runway lighting
--enable-enhanced-lighting Enable enhanced runway lighting

--disable-distance-attenuation
Disable runway light distance attenuation

--enable-distance-attenuation
Enable runway light distance attenuation

--disable-specular-highlight
Disable specular reflections on textured
objects
--enable-specular-highlight Enable specular reflections on textured objects
--enable-clouds Enable 2D (flat) cloud layers
--disable-clouds Disable 2D (flat) cloud layers
--enable-clouds3d Enable 3D (volumetric) cloud layers
--disable-clouds3d Disable 3D (volumetric) cloud layers
--fov=degrees Specify field of view angle
--disable-fullscreen Disable fullscreen mode
--enable-fullscreen Enable fullscreen mode
--shading-flat Enable flat shading
--shading-smooth Enable smooth shading
--disable-skyblend Disable sky blending
--enable-skyblend Enable sky blending
--disable-textures Disable textures
--enable-textures Enable textures
--disable-wireframe Disable wireframe drawing mode
--enable-wireframe Enable wireframe drawing mode
--geometry=WxH Specify window geometry (640x480, etc)
--view-offset=value Specify the default forward view direction as
an offset from straight ahead. Allowable values
are LEFT, RIGHT, CENTER, or a specific number
in degrees
--visibility=meters Specify initial visibility
--visibility-miles=miles Specify initial visibility in miles

==== Hud Options ====
--hud-tris Hud displays number of triangles rendered
--hud-culled Hud displays percentage of triangles culled

==== Time Options ====

--timeofday={dawn,noon,dusk,midnight}
Specify a time of day
--time-offset=[+-]hh:mm:ss Add this time offset
--time-match-real Synchronize time with real-world time
--time-match-local Synchronize time with local real-world time

--start-date-sys=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
system time

--start-date-gmt=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Greenwich Mean Time

--start-date-lat=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Local Aircraft Time

==== Network Options ====
--httpd=port Enable http server on the specified port
--telnet=port Enable telnet server on the specified port
--jpg-httpd=port Enable screen shot http server on the specified
port

==== MultiPlayer Options ====
--callsign assign a unique name to a player

--multiplay={in|out},hz,address,port
Specify multipilot communication settings
multiple instances can be used

==== Route/Way Point Options ====
--wp=ID[@alt] Specify a waypoint for the GC autopilot;
multiple instances can be used
--flight-plan=file Read all waypoints from a file

==== IO Options ====
--generic=params Open connection using a predefined
communication interface and a preselected
communication protocol
--garmin=params Open connection using the Garmin GPS protocol
--joyclient=params Open connection to an Agwagon joystick
--jsclient=params Open connection to a remote joystick
--native-ctrls=params Open connection using the FG Native Controls
protocol
--native-fdm=params Open connection using the FG Native FDM
protocol
--native=params Open connection using the FG Native protocol
--nmea=params Open connection using the NMEA protocol
--opengc=params Open connection using the OpenGC protocol
--props=params Open connection using the interactive property
manager
--pve=params Open connection using the PVE protocol
--ray=params Open connection using the Ray Woodworth motion
chair protocol
--rul=params Open connection using the RUL protocol
--atc610x Enable atc610x interface

==== Avionics Options ====
--nav1=[radial:]frequency Set the NAV1 radio frequency, optionally
preceded by a radial.
--nav2=[radial:]frequency Set the NAV2 radio frequency, optionally
preceded by a radial.
--adf=[rotation:]frequency Set the ADF radio frequency, optionally
preceded by a card rotation.
--dme={nav1|nav2|frequency} Slave the ADF to one of the NAV radios, or set
its internal frequency.

==== Situation Options ====

--failure={pitot|static|system|vacuum}
Fail the pitot, static, vacuum, or electrical
system (repeat the option for multiple system
failures).

==== Debugging Options ====

--log-level={bulk,debug,info,warn,alert}
Set the logging level for this session.
0=verbose, 5=alerts only
--trace-read=property Trace the reads for a property;
multiple instances can be used
--trace-write=property Trace the writes for a property;
multiple instances can be used

Command line options

2006-07-11T16:06:46Z

Hellosimon: Reverted edits by 219.240.12.173 (Talk); changed back to last version by 201.17.253.220

Usage: fgfs [ option ... ]

{|
|__TOC__
|}

==== General Options ====
--help, -h Show the most relevant command line options
--verbose, -v Show all command line options when combined
with --help or -h
--fg-root=path Specify the root data path
--fg-scenery=path Specify the base scenery path;
Defaults to $FG_ROOT/Scenery
--language=code Select the language for this session
--disable-game-mode Disable full-screen game mode
--enable-game-mode Enable full-screen game mode
--disable-splash-screen Disable splash screen
--enable-splash-screen Enable splash screen
--disable-intro-music Disable introduction music
--enable-intro-music Enable introduction music
--disable-mouse-pointer Disable extra mouse pointer
--enable-mouse-pointer Enable extra mouse pointer
(i.e. for full screen Voodoo based cards)
--disable-random-objects Exclude random scenery objects
(buildings, etc.)
--enable-random-objects Include random scenery objects
(buildings, etc.)
--disable-ai-models Disable the artifical traffic subsystem.
--enable-ai-models Enable the artifical traffic.
--disable-freeze Start in a running state
--enable-freeze Start in a frozen state
--disable-fuel-freeze Fuel is consumed normally
--enable-fuel-freeze Fuel tank quantity forced to remain constant
--disable-clock-freeze Clock advances normally
--enable-clock-freeze Do not advance clock
--control=mode Primary control mode (joystick, keyboard,
mouse)
--enable-auto-coordination Enable auto coordination
--disable-auto-coordination Disable auto coordination
--browser-app=path Specify path to your web browser
--prop:name=value Set property to
--config=path Load additional properties from path
--units-feet Use feet for distances
--units-meters Use meters for distances

==== Features ====
--disable-panel Disable instrument panel
--enable-panel Enable instrument panel
--disable-sound Disable sound effects
--enable-sound Enable sound effects
--disable-hud Disable Heads Up Display (HUD)
--enable-hud Enable Heads Up Display (HUD)
--disable-anti-alias-hud Disable anti-aliased HUD
--enable-anti-alias-hud Enable anti-aliased HUD
--disable-hud-3d Disable 3D HUD
--enable-hud-3d Enable 3D HUD
210149511073119693344

==== Aircraft ====
--aircraft=name Select an aircraft profile as defined by a top
level -set.xml
--show-aircraft Print a list of the currently available
aircraft types

==== Flight Model ====
--fdm=name Select the core flight dynamics model
Can be one of jsb, larcsim, yasim, magic,
balloon, ada, external, or null
--aero=name Select aircraft aerodynamics model to load
--model-hz=n Run the FDM this rate (iterations per second)
--speed=n Run the FDM 'n' times faster than real time
--notrim Do NOT attempt to trim the model
(only with fdm=jsbsim)
--on-ground Start at ground level (default)
--in-air Start in air (implied when using --altitude)
--wind=DIR@SPEED Specify wind coming from DIR (degrees) at SPEED
(knots)
--turbulence=0.0 to 1.0 Specify turbulence from 0.0 (calm) to 1.0
(severe)

--ceiling=FT_ASL[:THICKNESS_FT]
Create an overcast ceiling, optionally with a
specific thickness (defaults to 2000 ft).

==== Aircraft model directory (UIUC FDM ONLY) ====
--aircraft-dir=path Aircraft directory relative to the path of the
executable

==== Initial Position and Orientation ====
--airport=ID Specify starting position relative to an
airport
--runway=rwy_no Specify starting runway (must also specify an
airport)
--vor=ID Specify starting position relative to a VOR
--ndb=ID Specify starting position relative to an NDB
--fix=ID Specify starting position relative to a fix
--airport-id=ID (Obsolete; use --airport instead.)
--offset-distance=nm Specify distance to reference point (statute
miles)
--offset-azimuth=degrees Specify heading to reference point
--lon=degrees Starting longitude (west = -)
--lat=degrees Starting latitude (south = -)
--altitude=value Starting altitude
(in feet unless --units-meters specified)
--heading=degrees Specify heading (yaw) angle (Psi)
--roll=degrees Specify roll angle (Phi)
--pitch=degrees Specify pitch angle (Theta)
--uBody=units_per_sec Specify velocity along the body X axis
(in feet unless --units-meters specified)
--vBody=units_per_sec Specify velocity along the body Y axis
(in feet unless --units-meters specified)
--wBody=units_per_sec Specify velocity along the body Z axis
(in feet unless --units-meters specified)
--vc=knots Specify initial airspeed
--mach=num Specify initial mach number
--glideslope=degrees Specify flight path angle (can be positive)
--roc=fpm Specify initial climb rate (can be negative)

==== Rendering Options ====
--bpp=depth Specify the bits per pixel
--fog-disable Disable fog/haze
--fog-fastest Enable fastest fog/haze
--fog-nicest Enable nicest fog/haze
--disable-horizon-effect Disable celestial body growth illusion near the
horizon
--enable-horizon-effect Enable celestial body growth illusion near the
horizon
--disable-enhanced-lighting Disable enhanced runway lighting
--enable-enhanced-lighting Enable enhanced runway lighting

--disable-distance-attenuation
Disable runway light distance attenuation

--enable-distance-attenuation
Enable runway light distance attenuation

--disable-specular-highlight
Disable specular reflections on textured
objects
--enable-specular-highlight Enable specular reflections on textured objects
--enable-clouds Enable 2D (flat) cloud layers
--disable-clouds Disable 2D (flat) cloud layers
--enable-clouds3d Enable 3D (volumetric) cloud layers
--disable-clouds3d Disable 3D (volumetric) cloud layers
--fov=degrees Specify field of view angle
--disable-fullscreen Disable fullscreen mode
--enable-fullscreen Enable fullscreen mode
--shading-flat Enable flat shading
--shading-smooth Enable smooth shading
--disable-skyblend Disable sky blending
--enable-skyblend Enable sky blending
--disable-textures Disable textures
--enable-textures Enable textures
--disable-wireframe Disable wireframe drawing mode
--enable-wireframe Enable wireframe drawing mode
--geometry=WxH Specify window geometry (640x480, etc)
--view-offset=value Specify the default forward view direction as
an offset from straight ahead. Allowable values
are LEFT, RIGHT, CENTER, or a specific number
in degrees
--visibility=meters Specify initial visibility
--visibility-miles=miles Specify initial visibility in miles

==== Hud Options ====
--hud-tris Hud displays number of triangles rendered
--hud-culled Hud displays percentage of triangles culled

==== Time Options ====

--timeofday={dawn,noon,dusk,midnight}
Specify a time of day
--time-offset=[+-]hh:mm:ss Add this time offset
--time-match-real Synchronize time with real-world time
--time-match-local Synchronize time with local real-world time

--start-date-sys=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
system time

--start-date-gmt=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Greenwich Mean Time

--start-date-lat=yyyy:mm:dd:hh:mm:ss
Specify a starting date/time with respect to
Local Aircraft Time

==== Network Options ====
--httpd=port Enable http server on the specified port
--telnet=port Enable telnet server on the specified port
--jpg-httpd=port Enable screen shot http server on the specified
port

==== MultiPlayer Options ====
--callsign assign a unique name to a player

--multiplay={in|out},hz,address,port
Specify multipilot communication settings
multiple instances can be used

==== Route/Way Point Options ====
--wp=ID[@alt] Specify a waypoint for the GC autopilot;
multiple instances can be used
--flight-plan=file Read all waypoints from a file

==== IO Options ====
--generic=params Open connection using a predefined
communication interface and a preselected
communication protocol
--garmin=params Open connection using the Garmin GPS protocol
--joyclient=params Open connection to an Agwagon joystick
--jsclient=params Open connection to a remote joystick
--native-ctrls=params Open connection using the FG Native Controls
protocol
--native-fdm=params Open connection using the FG Native FDM
protocol
--native=params Open connection using the FG Native protocol
--nmea=params Open connection using the NMEA protocol
--opengc=params Open connection using the OpenGC protocol
--props=params Open connection using the interactive property
manager
--pve=params Open connection using the PVE protocol
--ray=params Open connection using the Ray Woodworth motion
chair protocol
--rul=params Open connection using the RUL protocol
--atc610x Enable atc610x interface

==== Avionics Options ====
--nav1=[radial:]frequency Set the NAV1 radio frequency, optionally
preceded by a radial.
--nav2=[radial:]frequency Set the NAV2 radio frequency, optionally
preceded by a radial.
--adf=[rotation:]frequency Set the ADF radio frequency, optionally
preceded by a card rotation.
--dme={nav1|nav2|frequency} Slave the ADF to one of the NAV radios, or set
its internal frequency.

==== Situation Options ====

--failure={pitot|static|system|vacuum}
Fail the pitot, static, vacuum, or electrical
system (repeat the option for multiple system
failures).

==== Debugging Options ====

--log-level={bulk,debug,info,warn,alert}
Set the logging level for this session.
0=verbose, 5=alerts only
--trace-read=property Trace the reads for a property;
multiple instances can be used
--trace-write=property Trace the writes for a property;
multiple instances can be used

2006-06-26T20:55:00Z

Hellosimon:

File:Catii-iii addon html m19c5fb92.jpg

2006-06-26T20:54:49Z

Hellosimon:

File:Catii-iii addon html a5eaae.jpg

2006-06-26T20:54:39Z

Hellosimon: