78
edits
Property tree: Difference between revisions
Jump to navigation
Jump to search
m
typos, rewording.
m (Major revamp for Property Tree articles) |
m (typos, rewording.) |
||
| Line 1: | Line 1: | ||
{{PropertyTree}}The so called '''Property Tree''' in [[FlightGear]] is generally considered FlightGear's central nervous system and one of FlightGear greatest assets | {{PropertyTree}}The so called '''Property Tree''' in [[FlightGear]] is generally considered FlightGear's central nervous system and one of FlightGear's greatest assets! | ||
This is because the Property Tree system | This is because the Property Tree system provides access to low level run time state variables via a very intuitive tree-like hierarchy. This allows FlightGear's behavior to be easily controlled and manipulated at run time. | ||
The FlightGear Property Tree is the common denominator for crucial | The FlightGear Property Tree is the common denominator for crucial run time state and also the interface to these internal state variables. | ||
The concepts and mechanisms behind the "Property Tree" may not be immediately obvious to FlightGear beginners. This page is meant to help new users familiarize themselves with the FlightGear property tree. | |||
To make it easier to | To make it easier to manipulate the tree, start FlightGear with the following command line | ||
fgfs --httpd=5480 | fgfs --httpd=5480 | ||
Then after a few moments open in a new window - [http://localhost:5480 http://localhost:5480] | Then after a few moments open in a new window - [http://localhost:5480 http://localhost:5480] | ||
| Line 35: | Line 35: | ||
What makes FG powerful is that a new aircraft can easily be designed with its unique set of properties that somehow affect the simulation. The Aircraft model has an xml file of properties within the property tree. | What makes FG powerful is that a new aircraft can easily be designed with its unique set of properties that somehow affect the simulation. The Aircraft model has an xml file of properties within the property tree. | ||
This is why the property tree is not | This is why the property tree is not consistent with fixed variables, they are created dynamically, to represent a propeller plane vs Jumbo or even a "Caspian Sea Monster". | ||
The property tree is read, written, accessed and manipulated in a variety of ways, such as | The property tree is read, written, accessed and manipulated in a variety of ways, such as | ||
| Line 43: | Line 43: | ||
* telnet interface - query and fly the plane on the command line | * telnet interface - query and fly the plane on the command line | ||
* html interface - fly the plane with a browser or an PDA | * html interface - fly the plane with a browser or an PDA | ||
For example, multiplayer mode is accomplished by exchanging sets of variables from the tree (height, position, speed, etc). | |||
==Flight Dynamics Model (FDM)== | ==Flight Dynamics Model (FDM)== | ||
| Line 54: | Line 51: | ||
* [[JSBSim]] | * [[JSBSim]] | ||
* [[YASim]] | * [[YASim]] | ||
These flight dynamics | These flight dynamics models present themselves differently in the tree, using different variables, in different places. That is what an aircraft can be designed around. | ||