4,400
edits
Howto:Configure views in FlightGear: Difference between revisions
Jump to navigation
Jump to search
m
Howto:Configure views in FlightGear (view source)
Revision as of 13:28, 26 February 2012
, 26 February 2012Robot: Automated text replacement (-Flight Gear +FlightGear)
m (Robot: Automated text replacement (-Flight Gear +FlightGear)) |
|||
| Line 6: | Line 6: | ||
There are two basic types of views: | There are two basic types of views: | ||
* '''LookFrom''' - This type requires a single coordinate position. The direction of the view is independent of any particular object. Adjusting the heading and pitch offsets moves the direction of observation around. In the default | * '''LookFrom''' - This type requires a single coordinate position. The direction of the view is independent of any particular object. Adjusting the heading and pitch offsets moves the direction of observation around. In the default FlightGear configuration panning with the mouse will move the view around as if the observer was turning their head. | ||
* '''LookAt''' - This type requires a two coordinate positions. The direction of the view is always oriented toward a target and tracks the target if it moves. | * '''LookAt''' - This type requires a two coordinate positions. The direction of the view is always oriented toward a target and tracks the target if it moves. | ||
| Line 12: | Line 12: | ||
== Defining Positions == | == Defining Positions == | ||
There are two methods to define a postion and orientation for use in configuring a view. One method is tied to a model which means the view references the position and orientation of a model (e.g. Aircraft 3D Model) and the other is an independent postion which simply means that the view references location data directly (via the | There are two methods to define a postion and orientation for use in configuring a view. One method is tied to a model which means the view references the position and orientation of a model (e.g. Aircraft 3D Model) and the other is an independent postion which simply means that the view references location data directly (via the FlightGear property tree): | ||
=== Tied to a Model === | === Tied to a Model === | ||
| Line 64: | Line 64: | ||
</sim> | </sim> | ||
Note that the definition is constructed as a path to a numeric data item in the global property tree. If you are unfamiliar with these properties, take a look at the "Property Picker" dialog while | Note that the definition is constructed as a path to a numeric data item in the global property tree. If you are unfamiliar with these properties, take a look at the "Property Picker" dialog while FlightGear is running and you can see the kinds of values in use. You may define your own static values, say for a fixed location of an observer, by adding the following xml to your setup (prefrences.xml or another file): | ||
<somepath> | <somepath> | ||