fly/fgdata
1
0
Fork 0
Code Activity
fgdata/preferences.xml

1221 lines
41 KiB
XML
Raw Normal View History

Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<?xml version="1.0"?>
<!--
************************************************************************
Global defaults for FlightGear property values.
Started September 2000 by David Megginson, david@megginson.com
************************************************************************
-->
<PropertyList>
<!-- General simulation preferences -->
Added /sim/aircraft property back in, removed include from preferences.xml, and added <sim>...</sim> tags back into the *-set.xml files. You need the newest FlightGear CVS changes to use together with these changes.
2001-12-11 18:32:36 +00:00
<sim>
don't reset the simulator when the aircraft hits the ground
2005-06-11 08:22:31 +00:00
<!-- show-aircraft option: show ALL aircraft regardless by default -->
<aircraft-min-status>all</aircraft-min-status>
<!-- don't reset the simulator when the aircraft hits the ground -->
<reset-on-crash type="bool">false</reset-on-crash>
Mathias Fröhlich: Limit the maximum time we spent in the simulation loops. That means, if the /sim/max-simtime-per-frame value is strictly positive you can limit the maximum amount of time you will do simulations for one frame to display. The cpu time spent in simulations code is roughtly at least O(real_delta_time_sec). If this is (due to running debug builds or valgrind or something different blowing up execution times) larger than the real time you will no more get any response from flightgear. This limits that effect. Just set to property from your .fgfsrc or commandline ...
2006-01-30 10:36:20 +00:00
<!-- Limit the time we need to spend in simulation loops to 1 second -->
<max-simtime-per-frame>1.0</max-simtime-per-frame>
Have a current session number that will be saved in user prefs.
2009-10-24 09:25:04 +00:00
<session type="int" userarchive="y">0</session>
add paths and runway parameter defaults, so that people are aware of the possibilities
2008-05-02 21:47:53 +00:00
<paths>
<screenshot-dir/> <!-- defaults to current working dir -->
initialize validation callback properties as string
2008-07-11 16:44:29 +00:00
<validate>
<read type="string"/>
<write type="string"/>
</validate>
Make the "use-custom-scenery-data" property more generic. This will also enable us to use it for loading airport geometry data, as well as using the shared model repository that is maintained by the custom scenery project.
2009-10-04 07:52:54 +00:00
<use-custom-scenery-data type="bool">false</use-custom-scenery-data>
add paths and runway parameter defaults, so that people are aware of the possibilities
2008-05-02 21:47:53 +00:00
</paths>
New locale structure.
2002-10-03 14:41:17 +00:00
<intl include="Translations/locale.xml"/>
Reference Aircraft/Generic instead of Aircraft/c172 and point to the (new) default aircraft, c172p
2005-02-19 12:52:23 +00:00
<aircraft>c172p</aircraft>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<virtual-cockpit type="bool">false</virtual-cockpit>
Two minor property name changes corresponding to source code changes.
2002-11-15 21:05:30 +00:00
<presets>
<airport-id>KSFO</airport-id>
don't enforce runway 28R. It's chosen automatically under default wind conditions, but when a users sets wind from 90, then s/he shouldn't start from here by default. S/he can still set heading & runway explicitly.
2007-10-04 15:50:35 +00:00
<runway></runway>
Two minor property name changes corresponding to source code changes.
2002-11-15 21:05:30 +00:00
<trim type="bool">true</trim>
</presets>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<startup>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<xsize type="int">800</xsize>
<ysize type="int">600</ysize>
<splash-screen type="bool">true</splash-screen>
prepare for progress information line
2005-05-06 08:16:23 +00:00
<splash-progress type="bool">true</splash-progress>
'unhide' hidden feature: splash screen title line; can be used by packagers for version info ("Version 0.9.9") or important messages ("type '?' for aircraft help") etc.
2005-10-08 12:40:02 +00:00
<splash-title><!-- --></splash-title>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<intro-music type="bool">false</intro-music>
<game-mode type="bool">false</game-mode>
<fullscreen type="bool">false</fullscreen>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<units>feet</units>
add type for "save-on-exit"
2007-01-22 18:55:41 +00:00
<save-on-exit type="bool" userarchive="y">true</save-on-exit>
use firefox as browser and create new tab by default
2008-07-09 19:36:41 +00:00
<browser-app write="n">firefox -new-tab "%u"</browser-app><!-- help viewer; only used under Unix -->
- add property /sim/startup/terminal-ansi-colors {BOOL}. This is used by debug.nas to turn on/off syntax coloring for dumped data (which is desirable as compound data types can fill several screens with rather hard to read data). Unfortunately, it can't be reliably deduced from the OS whether ANSI colors are available or not. - move "multiplayer chat" properties to where they belong
2007-02-18 17:21:50 +00:00
<terminal-ansi-colors type="bool">true</terminal-ansi-colors>
Bug fix - missing ">"
2009-10-24 10:30:10 +00:00
<season type="string">summer</season>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</startup>
Documented the new --disable-random-objects and --enable-random-objects options, and provided a default value for /sim/rendering/random-objects.
2002-07-20 21:12:23 +00:00
<rendering>
Add a debug option for rendering
2003-05-06 13:52:08 +00:00
<debug type="bool">false</debug>
Add a level of realism property which can varry between highly accurate (level=10) and low resolution (level-0) rendering. The default is set to five for now.
2003-08-21 11:16:44 +00:00
<realism>5</realism>
Default to some anisotropic texture filtering since unfiltered textures are distracting blury when viewed from nearly edge on (as runway textures almost always are.) This can be adjusted to individual preferences with the --texture-filter={0,1,2,4,8,16} command line option.
2008-02-20 19:46:38 +00:00
<filtering>8</filtering>
Implement three level LOD for static scenery
2003-09-28 11:16:19 +00:00
<static-lod>
Add the remaining changes of Stefan Seifert's patch.
2005-12-17 22:22:50 +00:00
<detailed userarchive="y">1500</detailed>
<rough userarchive="y">9000</rough>
<bare userarchive="y">30000</bare>
Implement three level LOD for static scenery
2003-09-28 11:16:19 +00:00
</static-lod>
remember state of random-{objects,vegetation}
2008-04-20 09:17:45 +00:00
<random-objects type="bool" userarchive="y">true</random-objects>
<random-vegetation type="bool" userarchive="y">true</random-vegetation>
Add the remaining changes of Stefan Seifert's patch.
2005-12-17 22:22:50 +00:00
<horizon-effect type="bool" userarchive="y">false</horizon-effect>
Default to turning point sprites on for runway lighting.
2006-07-20 14:31:25 +00:00
<point-sprites type="bool" userarchive="y">true</point-sprites>
Add the remaining changes of Stefan Seifert's patch.
2005-12-17 22:22:50 +00:00
<enhanced-lighting type="bool" userarchive="y">false</enhanced-lighting>
<distance-attenuation type="bool" userarchive="y">false</distance-attenuation>
add flag/checkbox to enable/disable particles
2008-10-17 21:21:22 +00:00
<particles type="bool" userarchive="y">true</particles>
only enable precipitation if it's enabled in the gui (/sim/rendering/precipitation-gui-enabled) *and* if the aircraft wants it (/sim/rendering/precipitation-aircraft-enabled). Some aircraft model rain on the windshield and want to turn rain off for interior views.
2008-11-23 09:53:46 +00:00
<precipitation-gui-enable type="bool" userarchive="y">false</precipitation-gui-enable>
Added <precipitation-enable> to the list , prevents rain even when set to false in the dialog ...
2009-11-19 20:14:50 +00:00
<precipitation-enable type="bool" userarchive="y">false</precipitation-enable>
only enable precipitation if it's enabled in the gui (/sim/rendering/precipitation-gui-enabled) *and* if the aircraft wants it (/sim/rendering/precipitation-aircraft-enabled). Some aircraft model rain on the windshield and want to turn rain off for interior views.
2008-11-23 09:53:46 +00:00
<precipitation-aircraft-enable type="bool">true</precipitation-aircraft-enable>
Vassilii KHACHATUROV: add rain parameter set "an addition to preferences.xml, listing the current defaults (i.e., it'll work the same without this one applied, but is there for the docu. sake)"
2006-03-23 16:33:41 +00:00
<precipitation>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
<!-- streaks coloring and transparency -->
<min-light type="float">0.35</min-light>
<streak-brightness-nearmost-layer type="float">0.9</streak-brightness-nearmost-layer>
<streak-brightness-farmost-layer type="float">0.5</streak-brightness-farmost-layer>
<!-- streak period as a function of the speed, decreases with speed -->
<streak-period-max type="float">2.5</streak-period-max>
<streak-period-change-per-kt type="float">0.005</streak-period-change-per-kt>
<streak-period-min type="float">1.0</streak-period-min>
<!-- streak length as a function of the speed, increases with speed -->
<streak-length-min type="float">0.03</streak-length-min>
<streak-length-change-per-kt type="float">0.0005</streak-length-change-per-kt>
<streak-length-max type="float">0.1</streak-length-max>
<!-- # of rain streaks at the 100.0% precipitation density -->
<streak-count-min type="int">40</streak-count-min><!-- lightest rain -->
<streak-count-max type="int">190</streak-count-max><!-- heaviest rain -->
<!-- numbers over MAX_RAIN_SLICE in simgear/environment/visual_enviro.cxx
will be ignored in the current implementation. -->
<!-- the precipitation cone geometry -->
<cone-base-radius type="float">15.0</cone-base-radius>
<cone-height type="float">30.0</cone-height>
Vassilii KHACHATUROV: add rain parameter set "an addition to preferences.xml, listing the current defaults (i.e., it'll work the same without this one applied, but is there for the docu. sake)"
2006-03-23 16:33:41 +00:00
</precipitation>
Add the remaining changes of Stefan Seifert's patch.
2005-12-17 22:22:50 +00:00
<lightning-enable type="bool" userarchive="y">false</lightning-enable>
and set it to 'false' :-)
2007-01-30 21:14:53 +00:00
<specular-highlight type="bool" userarchive="y">false</specular-highlight>
Add the remaining changes of Stefan Seifert's patch.
2005-12-17 22:22:50 +00:00
<bump-mapping type="bool" userarchive="y">false</bump-mapping>
<clouds3d-enable type="bool" userarchive="y">false</clouds3d-enable>
Stuart Buchanan : This provides the following enhancements & bug fixes - Fix the chequer-board bug. - Add proper cloud coverage function - so scattered clouds are now truly scattered. - Add real-time control for visibility range. - Use a limited set of clouds rather than generating a completely new Geode for each cloud. This saves sorting and display time. - Add controls to Rendering dialog to allow fine-tuning of the number of sprites, cloud visibility and the number of different types of cloud. - Add some variance to the sort back-off to avoid all clouds being sorted at the same time. - Pack attributes into vectors for performance - Re-order the cloud type determination code so that if a cloud layer could either be stratus or cumulus, cumulus is used. - Lowered the cloud level in the standard cloud configuration slightly so a cumulus layer is generated rather than stratus. These last two mean that you should see some 3D cumuli if disabling real weather fetch. My thanks to Yon Uriarte for his help with performance work.
2008-12-04 20:57:55 +00:00
<clouds3d-vis-range type="float" userarchive="y">20000.0</clouds3d-vis-range>
<clouds3d-density type="float" userarchive="y">1.0</clouds3d-density>
Initialize some default rendering options
2003-06-17 16:56:58 +00:00
<draw-otw type="bool">true</draw-otw>
Add the remaining changes of Stefan Seifert's patch.
2005-12-17 22:22:50 +00:00
<shadows-ac type="bool" userarchive="y">false</shadows-ac>
<shadows-ac-transp type="bool" userarchive="y">false</shadows-ac-transp>
<shadows-ai type="bool" userarchive="y">false</shadows-ai>
<shadows-to type="bool" userarchive="y">false</shadows-to>
<shadows-debug type="bool" userarchive="y">false</shadows-debug>
new properties for shadows
2009-07-15 22:49:00 +00:00
<shadows>
<enabled type="bool" userarchive="y">true</enabled>
<debug type="bool" userarchive="y">false</debug>
</shadows>
Till Busch - effects, shaders and textures for crop and water effects Incorporated changes to effects file syntax. Changed Till's landmass to mix in the base terrain texture. Some shader cleanup. Also, add a GUI control for enabling shaders.
2009-08-08 10:17:58 +00:00
<shader-experimental type="bool" userarchive="y">false</shader-experimental>
Toggle effects use with property
2009-07-15 22:49:53 +00:00
<shader-effects type="bool" userarchive="y">true</shader-effects>
remove garbage; add fps-display
2006-01-30 10:43:36 +00:00
<fps-display type="bool" userarchive="y">false</fps-display>
- initialize /sim/rendering/on-screen-statistics, and - increase it in steps from Menu->Debug
2008-04-21 14:21:14 +00:00
<on-screen-statistics type="int">0</on-screen-statistics>
add glide slope tunnel option to help menu
2007-12-04 10:51:45 +00:00
<glide-slope-tunnel type="bool" userarchive="y">false</glide-slope-tunnel>
Add generic blackout/redout for all aircraft, along with a gui. Based on previous work by vivian and myself.
2008-02-16 08:26:59 +00:00
<redout>
<enabled type="bool" userarchive="y">true</enabled>
Update to generic blackout, incorporating feedback from Melchior FRANZ: - Update redout level every frame - Replace reading of properties every iteration with listeners - move -onset and -complete properties into a parameters subtree
2008-02-16 20:23:27 +00:00
<parameters>
<blackout-onset-g>3.5</blackout-onset-g>
<blackout-complete-g>5</blackout-complete-g>
<redout-onset-g>-2</redout-onset-g>
<redout-complete-g>-4</redout-complete-g>
</parameters>
Add generic blackout/redout for all aircraft, along with a gui. Based on previous work by vivian and myself.
2008-02-16 08:26:59 +00:00
</redout>
Add generic redout.
2008-04-23 20:44:57 +00:00
<headshake>
Disable generic headshake by default. Various people have pointed out that this is not particularly realistic (though I quite like the effect myself so will leave it as an option).
2008-05-30 19:19:35 +00:00
<enabled type="bool" userarchive="y">false</enabled>
Add generic redout.
2008-04-23 20:44:57 +00:00
<rate-m-g>0.005</rate-m-g>
Disable generic headshake by default. Various people have pointed out that this is not particularly realistic (though I quite like the effect myself so will leave it as an option).
2008-05-30 19:19:35 +00:00
</headshake>
Retain advanced terrain shader settings between sessions.
2010-01-24 19:40:09 +00:00
<crop-shader userarchive="y">0</crop-shader>
<landmass-shader userarchive="y">0</landmass-shader>
<water-shader userarchive="y">0</water-shader>
First iteration of the urban effect with relief mapping. Relief map by HB-Gral.
2010-03-12 22:25:19 +00:00
<urban-shader userarchive="y">0</urban-shader>
Allow the snow level of the landmass shader to be set from the property system, and expose it in the rendering dialog. Could be used in future to set the snow level based on the current weather.
2010-03-27 14:02:56 +00:00
<snow-level-m type="double">2000.0</snow-level-m>
Add a quality index that will help user to choose the level of eye candy vs available hardware performance
2010-04-10 13:31:05 +00:00
<quality-level type="double" userarchive="y">0.0</quality-level>
Documented the new --disable-random-objects and --enable-random-objects options, and provided a default value for /sim/rendering/random-objects.
2002-07-20 21:12:23 +00:00
</rendering>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<model-hz type="int">120</model-hz>
Add a flag to specify if localizers should be automatically aligned with their corresponding runways.
2004-05-28 16:22:40 +00:00
<navdb>
Allow a "threshold" value to determine which localizers to snap to the runway heading or not.
2004-05-28 20:56:54 +00:00
<localizers>
<auto-align>true</auto-align>
<auto-align-threshold-deg>5.0</auto-align-threshold-deg>
</localizers>
Add a flag to specify if localizers should be automatically aligned with their corresponding runways.
2004-05-28 16:22:40 +00:00
</navdb>
Initialize the /sim/sound/audible and /sim/sound/voice properties to reasonable values.
2003-02-18 16:52:55 +00:00
<sound>
autosave atc-chatter and volume
2006-02-12 10:49:30 +00:00
<volume type="float" userarchive="y">0.8</volume>
match sound code changes
2009-11-30 12:02:55 +00:00
<enabled type="bool">true</enabled>
add atc and external view selection checkboxes
2009-12-08 10:35:52 +00:00
<atc>
<enabled type="bool" userarchive="y">true</enabled>
<external-view type="bool" userarchive="y">true</external-view>
<volume type="float" userarchive="y">0.6</volume>
</atc>
use consistent property name for the default sound device in the code and configuration files.
2009-12-01 10:35:00 +00:00
<avionics>
<enabled type="bool" userarchive="y">true</enabled>
add atc and external view selection checkboxes
2009-12-08 10:35:52 +00:00
<external-view type="bool" userarchive="y">true</external-view>
use consistent property name for the default sound device in the code and configuration files.
2009-12-01 10:35:00 +00:00
<volume type="float" userarchive="y">0.6</volume>
</avionics>
match sound code changes
2009-11-30 12:02:55 +00:00
<chatter>
<enabled type="bool" userarchive="y">false</enabled>
add atc and external view selection checkboxes
2009-12-08 10:35:52 +00:00
<volume type="float" userarchive="y">0.6</volume>
match sound code changes
2009-11-30 12:02:55 +00:00
</chatter>
<effects>
<enabled type="bool" userarchive="y">true</enabled>
<volume type="float" userarchive="y">0.6</volume>
</effects>
use consistent property name for the default sound device in the code and configuration files.
2009-12-01 10:35:00 +00:00
<device-name type="string" userarchive="y"/>
Initialize the /sim/sound/audible and /sim/sound/voice properties to reasonable values.
2003-02-18 16:52:55 +00:00
<voice type="bool">true</voice>
pre-set callsign
2006-02-10 19:57:06 +00:00
<voices>
SECURITY: only the owner of this file can change the voice host. not aircraft *-set.xml files. Otherwise someone could offer an aircraft for download that sets the host to one of their machines and lets a nasal script write arbitrary information there. (Not that we had a lot of sensible information. Yet.)
2006-03-17 12:25:27 +00:00
<host type="string" write="n">localhost</host>
make port number immutable, too. Otherwise one could make it write to localhost:25 etc.
2006-03-17 12:28:28 +00:00
<port type="string" write="n">1314</port>
turn off voice subsystem; use --prop:/sim/sound/voices/enabled=true to enable
2006-02-11 12:01:30 +00:00
<enabled type="bool">false</enabled>
pre-set callsign
2006-02-10 19:57:06 +00:00
<atc alias="/sim/sound/voices/voice[0]/text"/>
<approach alias="/sim/sound/voices/voice[0]/text"/>
<ground alias="/sim/sound/voices/voice[0]/text"/>
<pilot alias="/sim/sound/voices/voice[1]/text"/>
<copilot alias="/sim/sound/voices/voice[2]/text"/>
<ai-plane alias="/sim/sound/voices/voice[3]/text"/>
<voice>
<desc>ATC/Approach/Ground</desc>
<text type="string"></text>
<volume type="double">1.0</volume>
<pitch type="double">100.0</pitch>
<speed type="double">1.0</speed>
<preamble type="string"></preamble>
<festival type="bool">true</festival>
</voice>
<voice>
<desc>Pilot</desc>
<text type="string"></text>
<volume type="double">1.0</volume>
<pitch type="double">100.0</pitch>
<speed type="double">1.0</speed>
- use en1_mbrola for the instructor: it's the clearest voice and, unlike us3_mbrola doesn't lack some phonemes, causing interrupted messages - use us2_mbrola for the pilot (seems to be rather complete, too; pity that the female voice us1_mbrola sounds so ugly :-)
2007-03-23 10:56:54 +00:00
<preamble type="string">(voice_us2_mbrola)</preamble>
pre-set callsign
2006-02-10 19:57:06 +00:00
<festival type="bool">true</festival>
</voice>
<voice>
<desc>Copilot/Instructor</desc>
<text type="string"></text>
<volume type="double">1.0</volume>
<pitch type="double">100.0</pitch>
<speed type="double">1.0</speed>
- use en1_mbrola for the instructor: it's the clearest voice and, unlike us3_mbrola doesn't lack some phonemes, causing interrupted messages - use us2_mbrola for the pilot (seems to be rather complete, too; pity that the female voice us1_mbrola sounds so ugly :-)
2007-03-23 10:56:54 +00:00
<preamble type="string">(voice_en1_mbrola)</preamble>
pre-set callsign
2006-02-10 19:57:06 +00:00
<festival type="bool">true</festival>
</voice>
<voice>
<desc>AI-Plane</desc>
<text type="string"></text>
<volume type="double">1.0</volume>
<pitch type="double">100.0</pitch>
<speed type="double">1.0</speed>
<preamble type="string">(voice_don_diphone)</preamble>
<festival type="bool">true</festival>
</voice>
</voices>
Initialize the /sim/sound/audible and /sim/sound/voice properties to reasonable values.
2003-02-18 16:52:55 +00:00
</sound>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<speed-up type="double">1.0</speed-up>
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
<current-view>
Default for fov is 55 degrees in viewer code. Changed to 55 here to match.
2003-04-01 02:02:57 +00:00
<field-of-view type="double">55.0</field-of-view>
Add a default aspect ratio multiplier of 1.0.
2005-02-25 22:29:15 +00:00
<aspect-ratio-multiplier type="double">1.0</aspect-ratio-multiplier>
change global dynamic-view flag from /sim/view[0]/dynamic/enabled to /sim/current-view/dynamic-view. There are additionally <dynamic-view> settings per view, but those only enable it for that view if it's globally turned on.
2007-11-03 14:08:39 +00:00
<dynamic-view type="bool" userarchive="y">false</dynamic-view>
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
</current-view>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<panel>
Reference Aircraft/Generic instead of Aircraft/c172 and point to the (new) default aircraft, c172p
2005-02-19 12:52:23 +00:00
<path>Aircraft/Generic/Panels/generic-vfr-panel.xml</path>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<visibility type="bool">false</visibility>
<jitter type="bool">false</jitter>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</panel>
Reference Aircraft/Generic instead of Aircraft/c172 and point to the (new) default aircraft, c172p
2005-02-19 12:52:23 +00:00
<panel_2>
<path>Aircraft/Generic/Panels/generic-trans-mini-panel.xml</path>
</panel_2>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<hud>
<path>Huds/Default/default.xml</path>
use NTPS HUD as default for the new implementation
2006-08-21 08:54:15 +00:00
<path>Huds/NTPS.xml</path> <!-- new HUD -->
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<visibility type="bool">false</visibility>
/sim/hud/visibility[1] controls the new HUD
2006-07-04 15:46:39 +00:00
<visibility type="bool">false</visibility> <!-- new HUD -->
add hud font definition (same as hard-coded default)
2006-06-06 15:35:05 +00:00
<font>
<name type="string">Helvetica.txf</name>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
<size type="float">8</size>
add hud font definition (same as hard-coded default)
2006-06-06 15:35:05 +00:00
</font>
make HUD colors settable. The number of color groups isn't fixed. Add as many as you like, but not at runtime. Some aircraft may especially want to change the first ("day") color, as the predefined green is IMHO a bit dark and should possibly be more white-ish.
2006-06-07 17:57:12 +00:00
<current-color type="int">0</current-color>
add <palette> group, from which values are copied to /sim/hud/color
2006-06-08 17:16:55 +00:00
<palette>
make HUD colors settable. The number of color groups isn't fixed. Add as many as you like, but not at runtime. Some aircraft may especially want to change the first ("day") color, as the predefined green is IMHO a bit dark and should possibly be more white-ish.
2006-06-07 17:57:12 +00:00
<color n="0"><!-- day -->
make default HUD semitransparent bright green (looks generally better, except on dark backgrounds)
2007-09-30 10:08:21 +00:00
<transparent type="bool">true</transparent>
<antialiased type="bool">true</antialiased>
<brightness type="float">0.85</brightness>
<alpha type="float">0.85</alpha>
<red type="float">0.38</red>
<green type="float">1.0</green>
<blue type="float">0.22</blue>
make HUD colors settable. The number of color groups isn't fixed. Add as many as you like, but not at runtime. Some aircraft may especially want to change the first ("day") color, as the predefined green is IMHO a bit dark and should possibly be more white-ish.
2006-06-07 17:57:12 +00:00
</color>
<color n="1"><!-- night -->
make default HUD semitransparent bright green (looks generally better, except on dark backgrounds)
2007-09-30 10:08:21 +00:00
<transparent type="bool">false</transparent>
<antialiased type="bool">false</antialiased>
<brightness type="float">0.75</brightness>
<alpha type="float">0.67</alpha>
make HUD colors settable. The number of color groups isn't fixed. Add as many as you like, but not at runtime. Some aircraft may especially want to change the first ("day") color, as the predefined green is IMHO a bit dark and should possibly be more white-ish.
2006-06-07 17:57:12 +00:00
<red type="float">0.9</red>
<green type="float">0.1</green>
<blue type="float">0.1</blue>
</color>
add <palette> group, from which values are copied to /sim/hud/color
2006-06-08 17:16:55 +00:00
</palette>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</hud>
remember the HUD's lat/lon format ("Menu->Autopilot->Set Lat/Lon Format" to cycle)
2008-03-17 19:55:00 +00:00
<lon-lat-format type="int" userarchive="y">2</lon-lat-format>
Autopilot overhaul.
2004-01-31 19:55:13 +00:00
<systems>
Roy Vegard Ovesen: Instrumentation and systems are now configureable from xml files. The two generic configurations generic-systems.xml and generic-instrumentation.xml configures the systems and instrumentation as it was hardcoded. You can override the generic configurations in a similar way as you override the autopilot configuration.
2004-10-16 12:37:46 +00:00
<path>Aircraft/Generic/generic-systems.xml</path>
Autopilot overhaul.
2004-01-31 19:55:13 +00:00
<autopilot>
<path>Aircraft/Generic/generic-autopilot.xml</path>
</autopilot>
</systems>
Roy Vegard Ovesen: Instrumentation and systems are now configureable from xml files. The two generic configurations generic-systems.xml and generic-instrumentation.xml configures the systems and instrumentation as it was hardcoded. You can override the generic configurations in a similar way as you override the autopilot configuration.
2004-10-16 12:37:46 +00:00
<instrumentation>
<path>Aircraft/Generic/generic-instrumentation.xml</path>
</instrumentation>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<instrument-options>
<nav n="0">
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<has-gs-needle type="bool">true</has-gs-needle>
<needles-pivot type="bool">true</needles-pivot>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</nav>
<nav n="1">
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<has-gs-needle type="bool">false</has-gs-needle>
<needles-pivot type="bool">true</needles-pivot>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</nav>
<hsi n="0">
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<has-gs-needle type="bool">true</has-gs-needle>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</hsi>
<dg>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<style type="int">0</style>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</dg>
</instrument-options>
Added keybindings for selecting a current engine, for changing magneto position, and for engaging the starter. Here's how it works: 1. To select an engine, use '!' (shift-1) for engine 1, '@' (shift-2) for engine 2, '#' (shift-3) for engine 3, '$' (shift-4) for engine 4, or '~' to select all engines. These bindings set the bool properties /sim/input/selected/engine[0], /sim/input/selected/engine[1], etc. 2. To decrease the magneto for the selected engine(s), use '{'. 3. To increase the magneto for the selected engine(s), use '}'. 4. To engage the starter for the selected engine(s), use SPACE. Eventually, I'll extend this so that the throttle uses the selected engine as well, and will perhaps even support engine selection in the joystick bindings. Right now, only engine 1 (engines[0]) is selected by default.
2001-12-18 12:37:21 +00:00
<input>
- add Debug->Development Extensions dialog with two checkboxes to - allow turning on/off extra widgets for developers (HUD dialog: colors, rendering dialog: visualization of shadow edges), and to turn on/off new - property key handler ('/'-key) Both features are off by default, and their state is saved to autosave.xml.
2007-11-18 12:20:17 +00:00
<property-key-handler type="bool" userarchive="y">false</property-key-handler>
Added keybindings for selecting a current engine, for changing magneto position, and for engaging the starter. Here's how it works: 1. To select an engine, use '!' (shift-1) for engine 1, '@' (shift-2) for engine 2, '#' (shift-3) for engine 3, '$' (shift-4) for engine 4, or '~' to select all engines. These bindings set the bool properties /sim/input/selected/engine[0], /sim/input/selected/engine[1], etc. 2. To decrease the magneto for the selected engine(s), use '{'. 3. To increase the magneto for the selected engine(s), use '}'. 4. To engage the starter for the selected engine(s), use SPACE. Eventually, I'll extend this so that the throttle uses the selected engine as well, and will perhaps even support engine selection in the joystick bindings. Right now, only engine 1 (engines[0]) is selected by default.
2001-12-18 12:37:21 +00:00
</input>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
Use a common z-offset definiton for all external views
2003-07-12 12:02:40 +00:00
<chase-distance-m type="double">-25.0</chase-distance-m>
Fix virtual cockpit toggle binding ("c"). Switches between 2D/3D mode on the fly.
2004-03-24 16:07:09 +00:00
<allow-toggle-cockpit type="bool">false</allow-toggle-cockpit>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<!-- "tower" positioned to right of runway at KSFO -->
<tower>
was a quick shot: the nonsense coords were intentional. The whole tower handling is suboptimal.
2007-04-07 00:05:41 +00:00
<longitude-deg type="double">-122.23045</longitude-deg>
<latitude-deg type="double">37.37027</latitude-deg>
<altitude-ft type="double">150</altitude-ft>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<roll-deg type="double">0</roll-deg>
<pitch-deg type="double">0</pitch-deg>
<heading-deg type="double">0</heading-deg>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
</tower>
added the view-name-popup property ,set to true
2009-10-09 00:19:58 +00:00
<view-name-popup type="bool" userarchive="y">true</view-name-popup>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<view>
<name>Cockpit View</name>
make system and aircraft views configurable in Menu->Views->View Options. These are then skipped with view.stepView(n), unless the second, optional argument is set to 1: view.stepView(n, 1); Whether a view is enabled or not, is saved in $FG_ROOT/.fgfs/autosave.xml (system views) or $FG_ROOT/.fgfs/aircraft-data/<aircraft>.xml
2007-11-19 16:26:15 +00:00
<enabled type="bool" userarchive="y">true</enabled>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<type>lookfrom</type>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<internal type="bool">false</internal>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<config>
Update to viewmgr. Reference models in views for location data.
2002-04-11 02:40:17 +00:00
<from-model type="bool">true</from-model>
<from-model-idx type="int">0</from-model-idx>
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
<ground-level-nearplane-m type="double">0.5f</ground-level-nearplane-m>
Finished setting up configurable default viewing properties, and implement them for the C172P 3D model. Look near the top of preferences.xml for an example. The recognized properties are as follow, with vanilla defaults in parentheses: /sim/view/config/default-field-of-view-deg (30) /sim/view/config/default-pitch-deg (0) /sim/view/config/front-direction-deg (0) /sim/view/config/front-left-direction-deg (45) /sim/view/config/left-direction-deg (90) /sim/view/config/back-left-direction-deg (135) /sim/view/config/back-direction-deg (180) /sim/view/config/back-right-direction-deg (225) /sim/view/config/right-direction-deg (270) /sim/view/config/front-right-direction-deg (315) These are particularly useful for the view from inside a 3D aircraft model.
2002-11-02 21:41:53 +00:00
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
<default-pitch-deg type="double">0</default-pitch-deg>
Jim Wilson: There are a number of little changes. Tested with current cvs as of 20:30EST 04Feb. Actually been running since the beginning of January with these patches. All changes work without crashing with the current base package cvs, but there are some visual problems with the views (other than pilot view) without changes to the base package. As soon as you can build test and commit I can add in those base package updates that will make it all work nicely. I will also go through all the 3D Aircraft configs to make sure the change in the "pitch-offset" for cockpit views (see below) are made to maintain current behavior. Here are the files (changes listed below): http://www.spiderbark.com/fgfs/viewerupdate.diffs.gz http://www.spiderbark.com/fgfs/viewerupdate.tar.gz
2003-02-06 19:46:48 +00:00
<default-heading-deg type="double">0</default-heading-deg>
Finished setting up configurable default viewing properties, and implement them for the C172P 3D model. Look near the top of preferences.xml for an example. The recognized properties are as follow, with vanilla defaults in parentheses: /sim/view/config/default-field-of-view-deg (30) /sim/view/config/default-pitch-deg (0) /sim/view/config/front-direction-deg (0) /sim/view/config/front-left-direction-deg (45) /sim/view/config/left-direction-deg (90) /sim/view/config/back-left-direction-deg (135) /sim/view/config/back-direction-deg (180) /sim/view/config/back-right-direction-deg (225) /sim/view/config/right-direction-deg (270) /sim/view/config/front-right-direction-deg (315) These are particularly useful for the view from inside a 3D aircraft model.
2002-11-02 21:41:53 +00:00
<front-direction-deg type="double">0</front-direction-deg>
<front-left-direction-deg type="double">45</front-left-direction-deg>
<left-direction-deg type="double">90</left-direction-deg>
<back-left-direction-deg type="double">135</back-left-direction-deg>
<back-direction-deg type="double">180</back-direction-deg>
<back-right-direction-deg type="double">225</back-right-direction-deg>
<right-direction-deg type="double">270</right-direction-deg>
<front-right-direction-deg type="double">315</front-right-direction-deg>
enable dynamic view explicitly for cockpit view. This flag can now also be set for other views, such as copilot, backseat, etc.
2007-10-03 17:32:39 +00:00
<dynamic-view type="bool">true</dynamic-view>
davidB21 + Vivian MEAZZA + /me: pilot view limiter If a <view> contains a <limits> block, then a view handler gets attached to it, which limits head turns to a given range, whereby headings beyond a given threshold cause an additional sideways movement. This is turned off by default for now.
2008-04-14 10:00:27 +00:00
<limits>
disallow 360 degree head turns (pilot view)
2008-04-15 17:28:05 +00:00
<enabled type="bool">true</enabled>
view_limiter: - new parameter naming (left/right instead of min/max; signs are ignored) - fix wrap-around skips - use regular constructor so as not to confuse people ;-)
2008-04-15 13:02:18 +00:00
<left>
<heading-max-deg type="double">140</heading-max-deg>
<x-offset-max-m type="double">0.15</x-offset-max-m>
<x-offset-threshold-deg type="double">65</x-offset-threshold-deg>
</left>
<right>
<heading-max-deg type="double">140</heading-max-deg>
<x-offset-max-m type="double">0.15</x-offset-max-m>
<x-offset-threshold-deg type="double">65</x-offset-threshold-deg>
</right>
davidB21 + Vivian MEAZZA + /me: pilot view limiter If a <view> contains a <limits> block, then a view handler gets attached to it, which limits head turns to a given range, whereby headings beyond a given threshold cause an additional sideways movement. This is turned off by default for now.
2008-04-14 10:00:27 +00:00
</limits>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
</config>
Indentation cleanups from Martin Dressler.
2002-03-02 23:44:28 +00:00
</view>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<view>
Add a new chase view from Melchior FRANZ. I think it's time tom move some of the views into it's own menu option and leave about three aircraft related views in the prefferences file
2003-07-12 09:55:04 +00:00
<name>Helicopter View</name>
make system and aircraft views configurable in Menu->Views->View Options. These are then skipped with view.stepView(n), unless the second, optional argument is set to 1: view.stepView(n, 1); Whether a view is enabled or not, is saved in $FG_ROOT/.fgfs/autosave.xml (system views) or $FG_ROOT/.fgfs/aircraft-data/<aircraft>.xml
2007-11-19 16:26:15 +00:00
<enabled type="bool" userarchive="y">true</enabled>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<type>lookat</type>
<config>
fix problem with new chase view config. this btw illustrates for some people a problem that might be lurking in the property code. it should have worked with this config the way it was before this change.
2002-06-14 19:17:05 +00:00
<from-model type="bool">false</from-model>
Update to viewmgr. Reference models in views for location data.
2002-04-11 02:40:17 +00:00
<from-model-idx type="int">0</from-model-idx>
fix problem with new chase view config. this btw illustrates for some people a problem that might be lurking in the property code. it should have worked with this config the way it was before this change.
2002-06-14 19:17:05 +00:00
<eye-lat-deg-path>/position/latitude-deg</eye-lat-deg-path>
<eye-lon-deg-path>/position/longitude-deg</eye-lon-deg-path>
<eye-alt-ft-path>/position/altitude-ft</eye-alt-ft-path>
<eye-heading-deg-path>/orientation/heading-deg</eye-heading-deg-path>
Update to viewmgr. Reference models in views for location data.
2002-04-11 02:40:17 +00:00
<at-model type="bool">true</at-model>
<at-model-idx type="int">0</at-model-idx>
Make sure the sixth view is accessible, and remove the damping factor from the helicopter view
2003-07-18 08:56:14 +00:00
<at-model-heading-damping type="double">0.0</at-model-heading-damping>
Jim Wilson: There are a number of little changes. Tested with current cvs as of 20:30EST 04Feb. Actually been running since the beginning of January with these patches. All changes work without crashing with the current base package cvs, but there are some visual problems with the views (other than pilot view) without changes to the base package. As soon as you can build test and commit I can add in those base package updates that will make it all work nicely. I will also go through all the 3D Aircraft configs to make sure the change in the "pitch-offset" for cockpit views (see below) are made to maintain current behavior. Here are the files (changes listed below): http://www.spiderbark.com/fgfs/viewerupdate.diffs.gz http://www.spiderbark.com/fgfs/viewerupdate.tar.gz
2003-02-06 19:46:48 +00:00
<target-z-offset-m type="double">0</target-z-offset-m>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
<ground-level-nearplane-m type="double">0.5f</ground-level-nearplane-m>
Jim Wilson: There are a number of little changes. Tested with current cvs as of 20:30EST 04Feb. Actually been running since the beginning of January with these patches. All changes work without crashing with the current base package cvs, but there are some visual problems with the views (other than pilot view) without changes to the base package. As soon as you can build test and commit I can add in those base package updates that will make it all work nicely. I will also go through all the 3D Aircraft configs to make sure the change in the "pitch-offset" for cockpit views (see below) are made to maintain current behavior. Here are the files (changes listed below): http://www.spiderbark.com/fgfs/viewerupdate.diffs.gz http://www.spiderbark.com/fgfs/viewerupdate.tar.gz
2003-02-06 19:46:48 +00:00
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<x-offset-m type="double">0</x-offset-m>
<y-offset-m type="double">0</y-offset-m>
Use a common z-offset definiton for all external views
2003-07-12 12:02:40 +00:00
<z-offset-m alias="/sim/chase-distance-m"/>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
</config>
</view>
Add a new chase view from Melchior FRANZ. I think it's time tom move some of the views into it's own menu option and leave about three aircraft related views in the prefferences file
2003-07-12 09:55:04 +00:00
<view>
<name>Chase View</name>
make system and aircraft views configurable in Menu->Views->View Options. These are then skipped with view.stepView(n), unless the second, optional argument is set to 1: view.stepView(n, 1); Whether a view is enabled or not, is saved in $FG_ROOT/.fgfs/autosave.xml (system views) or $FG_ROOT/.fgfs/aircraft-data/<aircraft>.xml
2007-11-19 16:26:15 +00:00
<enabled type="bool" userarchive="y">true</enabled>
Add a new chase view from Melchior FRANZ. I think it's time tom move some of the views into it's own menu option and leave about three aircraft related views in the prefferences file
2003-07-12 09:55:04 +00:00
<type>lookat</type>
<config>
<from-model type="bool">false</from-model>
<from-model-idx type="int">0</from-model-idx>
<eye-lat-deg-path>/position/latitude-deg</eye-lat-deg-path>
<eye-lon-deg-path>/position/longitude-deg</eye-lon-deg-path>
<eye-alt-ft-path>/position/altitude-ft</eye-alt-ft-path>
<eye-pitch-deg-path>/orientation/pitch-deg</eye-pitch-deg-path>
<eye-roll-deg-path>/orientation/roll-deg</eye-roll-deg-path>
<eye-heading-deg-path>/orientation/heading-deg</eye-heading-deg-path>
<at-model type="bool">true</at-model>
<at-model-idx type="int">0</at-model-idx>
Adjust the damping factors slightly
2003-07-17 08:54:06 +00:00
<at-model-roll-damping type="double">1.8</at-model-roll-damping>
<at-model-pitch-damping type="double">1.8</at-model-pitch-damping>
<at-model-heading-damping type="double">1.8</at-model-heading-damping>
Add a new chase view from Melchior FRANZ. I think it's time tom move some of the views into it's own menu option and leave about three aircraft related views in the prefferences file
2003-07-12 09:55:04 +00:00
<target-z-offset-m type="double">0</target-z-offset-m>
<ground-level-nearplane-m type="double">0.5f</ground-level-nearplane-m>
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
adapt "Chase View" offsets for fixed "lookat" mode (src/Main/viewer.cxx)
2007-11-05 22:15:44 +00:00
<x-offset-m type="double">0</x-offset-m>
<y-offset-m type="double">5</y-offset-m>
Use a common z-offset definiton for all external views
2003-07-12 12:02:40 +00:00
<z-offset-m alias="/sim/chase-distance-m"/>
Add a new chase view from Melchior FRANZ. I think it's time tom move some of the views into it's own menu option and leave about three aircraft related views in the prefferences file
2003-07-12 09:55:04 +00:00
</config>
</view>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<view>
<name>Tower View</name>
make system and aircraft views configurable in Menu->Views->View Options. These are then skipped with view.stepView(n), unless the second, optional argument is set to 1: view.stepView(n, 1); Whether a view is enabled or not, is saved in $FG_ROOT/.fgfs/autosave.xml (system views) or $FG_ROOT/.fgfs/aircraft-data/<aircraft>.xml
2007-11-19 16:26:15 +00:00
<enabled type="bool" userarchive="y">true</enabled>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
<type>lookat</type>
<config>
<eye-lat-deg-path>/sim/tower/latitude-deg</eye-lat-deg-path>
<eye-lon-deg-path>/sim/tower/longitude-deg</eye-lon-deg-path>
<eye-alt-ft-path>/sim/tower/altitude-ft</eye-alt-ft-path>
<eye-roll-deg-path>/sim/tower/roll-deg</eye-roll-deg-path>
<eye-pitch-deg-path>/sim/tower/pitch-deg</eye-pitch-deg-path>
<eye-heading-deg-path>/sim/tower/heading-deg</eye-heading-deg-path>
Update to viewmgr. Reference models in views for location data.
2002-04-11 02:40:17 +00:00
<at-model type="bool">true</at-model>
<at-model-idx type="int">0</at-model-idx>
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
<ground-level-nearplane-m type="double">10.0f</ground-level-nearplane-m>
Jim Wilson: There are a number of little changes. Tested with current cvs as of 20:30EST 04Feb. Actually been running since the beginning of January with these patches. All changes work without crashing with the current base package cvs, but there are some visual problems with the views (other than pilot view) without changes to the base package. As soon as you can build test and commit I can add in those base package updates that will make it all work nicely. I will also go through all the 3D Aircraft configs to make sure the change in the "pitch-offset" for cockpit views (see below) are made to maintain current behavior. Here are the files (changes listed below): http://www.spiderbark.com/fgfs/viewerupdate.diffs.gz http://www.spiderbark.com/fgfs/viewerupdate.tar.gz
2003-02-06 19:46:48 +00:00
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
Update to viewmgr. Reference models in views for location data.
2002-04-11 02:40:17 +00:00
<x-offset-m type="double">0</x-offset-m>
<y-offset-m type="double">0</y-offset-m>
<z-offset-m type="double">0</z-offset-m>
</config>
</view>
<view>
<name>Tower View Look From</name>
make system and aircraft views configurable in Menu->Views->View Options. These are then skipped with view.stepView(n), unless the second, optional argument is set to 1: view.stepView(n, 1); Whether a view is enabled or not, is saved in $FG_ROOT/.fgfs/autosave.xml (system views) or $FG_ROOT/.fgfs/aircraft-data/<aircraft>.xml
2007-11-19 16:26:15 +00:00
<enabled type="bool" userarchive="y">true</enabled>
Update to viewmgr. Reference models in views for location data.
2002-04-11 02:40:17 +00:00
<type>lookfrom</type>
<config>
<eye-lat-deg-path>/sim/tower/latitude-deg</eye-lat-deg-path>
<eye-lon-deg-path>/sim/tower/longitude-deg</eye-lon-deg-path>
<eye-alt-ft-path>/sim/tower/altitude-ft</eye-alt-ft-path>
<eye-roll-deg-path>/sim/tower/roll-deg</eye-roll-deg-path>
<eye-pitch-deg-path>/sim/tower/pitch-deg</eye-pitch-deg-path>
<eye-heading-deg-path>/sim/tower/heading-deg</eye-heading-deg-path>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
<ground-level-nearplane-m type="double">10.0f</ground-level-nearplane-m>
Jim Wilson: There are a number of little changes. Tested with current cvs as of 20:30EST 04Feb. Actually been running since the beginning of January with these patches. All changes work without crashing with the current base package cvs, but there are some visual problems with the views (other than pilot view) without changes to the base package. As soon as you can build test and commit I can add in those base package updates that will make it all work nicely. I will also go through all the 3D Aircraft configs to make sure the change in the "pitch-offset" for cockpit views (see below) are made to maintain current behavior. Here are the files (changes listed below): http://www.spiderbark.com/fgfs/viewerupdate.diffs.gz http://www.spiderbark.com/fgfs/viewerupdate.tar.gz
2003-02-06 19:46:48 +00:00
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
Jim Wilson: These are the updates for the View manager properties. Removed the last of items (within the viewer/viewmgr) hard coded to view number. Added support for per view configuration of ground level nearplane value. Tower views look very nice with little or no z-buffer problem in the models. Pilot offset dialog can be used to move eye in all views.
2002-04-18 14:52:32 +00:00
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<x-offset-m type="double">0</x-offset-m>
<y-offset-m type="double">0</y-offset-m>
<z-offset-m type="double">0</z-offset-m>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
</config>
We should probably discuss deleting/adding default views on the list. AFAIK there was only the addition of the 5th view discussed, and a developer noted that the Lookfrom Tower view was useful for multi-aircraft development. So this patch preserves the new 5th view, returns the Lookfrom Tower and removes the second Lookat Tower. One is enough for now IMHO, but still open for discussion of course. -- Jim
2002-11-17 03:55:00 +00:00
</view>
Changing fixed tower view ("look from") to new tower view ("lookat"), but the view position is near the aircraft. Adding in a new 5th view that looks in a fixed direction at the external airplane. In this new view the yaw does not cause the view to swing back and forth along the horizon as it does w/ the first view. MSS
2002-11-12 01:08:56 +00:00
<view>
better view name, as it's used in the Menu->View Options dialog
2007-11-19 19:06:52 +00:00
<name>Chase View Without Yaw</name>
make system and aircraft views configurable in Menu->Views->View Options. These are then skipped with view.stepView(n), unless the second, optional argument is set to 1: view.stepView(n, 1); Whether a view is enabled or not, is saved in $FG_ROOT/.fgfs/autosave.xml (system views) or $FG_ROOT/.fgfs/aircraft-data/<aircraft>.xml
2007-11-19 16:26:15 +00:00
<enabled type="bool" userarchive="y">true</enabled>
Changing fixed tower view ("look from") to new tower view ("lookat"), but the view position is near the aircraft. Adding in a new 5th view that looks in a fixed direction at the external airplane. In this new view the yaw does not cause the view to swing back and forth along the horizon as it does w/ the first view. MSS
2002-11-12 01:08:56 +00:00
<type>lookat</type>
<config>
<from-model type="bool">false</from-model>
<from-model-idx type="int">0</from-model-idx>
<eye-lat-deg-path>/position/latitude-deg</eye-lat-deg-path>
<eye-lon-deg-path>/position/longitude-deg</eye-lon-deg-path>
<eye-alt-ft-path>/position/altitude-ft</eye-alt-ft-path>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
Changing fixed tower view ("look from") to new tower view ("lookat"), but the view position is near the aircraft. Adding in a new 5th view that looks in a fixed direction at the external airplane. In this new view the yaw does not cause the view to swing back and forth along the horizon as it does w/ the first view. MSS
2002-11-12 01:08:56 +00:00
<at-model type="bool">true</at-model>
<at-model-idx type="int">0</at-model-idx>
<ground-level-nearplane-m type="double">0.5f</ground-level-nearplane-m>
Jim Wilson: There are a number of little changes. Tested with current cvs as of 20:30EST 04Feb. Actually been running since the beginning of January with these patches. All changes work without crashing with the current base package cvs, but there are some visual problems with the views (other than pilot view) without changes to the base package. As soon as you can build test and commit I can add in those base package updates that will make it all work nicely. I will also go through all the 3D Aircraft configs to make sure the change in the "pitch-offset" for cockpit views (see below) are made to maintain current behavior. Here are the files (changes listed below): http://www.spiderbark.com/fgfs/viewerupdate.diffs.gz http://www.spiderbark.com/fgfs/viewerupdate.tar.gz
2003-02-06 19:46:48 +00:00
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
Changing fixed tower view ("look from") to new tower view ("lookat"), but the view position is near the aircraft. Adding in a new 5th view that looks in a fixed direction at the external airplane. In this new view the yaw does not cause the view to swing back and forth along the horizon as it does w/ the first view. MSS
2002-11-12 01:08:56 +00:00
Fix Chase View Without Yaw on the basis of: http://mapserver.flightgear.org/git/gitweb.pl?p=flightgear;a=commitdiff;h=b4e4dc8531aa2c72ad7a1016450b7f5366e2d98a http://mapserver.flightgear.org/git/gitweb.pl?p=fgdata;a=commitdiff;h=c952f8ddda9106a2ca3f88b52dc1d30b3c8a7a68
2007-12-25 19:42:13 +00:00
<x-offset-m type="double">25</x-offset-m>
<y-offset-m type="double">2</y-offset-m>
Use a common z-offset definiton for all external views
2003-07-12 12:02:40 +00:00
<z-offset-m alias="/sim/chase-distance-m"/>
Changing fixed tower view ("look from") to new tower view ("lookat"), but the view position is near the aircraft. Adding in a new 5th view that looks in a fixed direction at the external airplane. In this new view the yaw does not cause the view to swing back and forth along the horizon as it does w/ the first view. MSS
2002-11-12 01:08:56 +00:00
</config>
added new viewer config stuff
2002-04-05 02:53:08 +00:00
</view>
first stab at fly-by view mode
2007-05-04 17:59:45 +00:00
<view>
<name>Fly-By View</name>
make system and aircraft views configurable in Menu->Views->View Options. These are then skipped with view.stepView(n), unless the second, optional argument is set to 1: view.stepView(n, 1); Whether a view is enabled or not, is saved in $FG_ROOT/.fgfs/autosave.xml (system views) or $FG_ROOT/.fgfs/aircraft-data/<aircraft>.xml
2007-11-19 16:26:15 +00:00
<enabled type="bool" userarchive="y">true</enabled>
first stab at fly-by view mode
2007-05-04 17:59:45 +00:00
<type>lookat</type>
<config>
<eye-lon-deg-path>/sim/viewer/longitude-deg</eye-lon-deg-path>
<eye-lat-deg-path>/sim/viewer/latitude-deg</eye-lat-deg-path>
<eye-alt-ft-path>/sim/viewer/altitude-ft</eye-alt-ft-path>
<at-model type="bool">true</at-model>
<at-model-idx type="int">0</at-model-idx>
<ground-level-nearplane-m type="double">0.5f</ground-level-nearplane-m>
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
</config>
</view>
add model-view: switch through all AI/MP models via dialog in bottom/left corner
2009-01-30 01:28:54 +00:00
<view>
<name>Model View</name>
<type>lookat</type>
<config>
<from-model type="bool">false</from-model>
<from-model-idx type="int">0</from-model-idx>
<eye-lat-deg-path>/sim/viewer/eye/latitude-deg</eye-lat-deg-path>
<eye-lon-deg-path>/sim/viewer/eye/longitude-deg</eye-lon-deg-path>
<eye-alt-ft-path>/sim/viewer/eye/altitude-ft</eye-alt-ft-path>
<eye-heading-deg-path>/sim/viewer/eye/heading-deg</eye-heading-deg-path>
<eye-pitch-deg-path>/sim/viewer/eye/pitch-deg</eye-pitch-deg-path>
<eye-roll-deg-path>/sim/viewer/eye/roll-deg</eye-roll-deg-path>
<at-model type="bool">false</at-model>
<at-model-idx type="int">0</at-model-idx>
<target-lat-deg-path>/sim/viewer/target/latitude-deg</target-lat-deg-path>
<target-lon-deg-path>/sim/viewer/target/longitude-deg</target-lon-deg-path>
<target-alt-ft-path>/sim/viewer/target/altitude-ft</target-alt-ft-path>
<target-heading-deg-path>/sim/viewer/target/heading-deg</target-heading-deg-path>
<target-pitch-deg-path>/sim/viewer/target/pitch-deg</target-pitch-deg-path>
<target-roll-deg-path>/sim/viewer/target/roll-deg</target-roll-deg-path>
<target-x-offset-m type="double">0</target-x-offset-m>
<target-y-offset-m type="double">0</target-y-offset-m>
<target-z-offset-m type="double">0</target-z-offset-m>
<ground-level-nearplane-m type="double">0.5f</ground-level-nearplane-m>
<default-field-of-view-deg type="double">55.0</default-field-of-view-deg>
<x-offset-m type="double">0</x-offset-m>
<y-offset-m type="double">0</y-offset-m>
<z-offset-m type="double">100</z-offset-m>
<heading-offset-deg>0</heading-offset-deg>
<pitch-offset-deg>0</pitch-offset-deg>
<roll-offset-deg>0</roll-offset-deg>
</config>
</view>
Set the default visibility for the menubar. Default the ADF card to 0.
2003-01-18 22:03:45 +00:00
<menubar>
- use the best voice for the copilot & instructor - save menu visibility (should we pop up a hint if it's turned off at startup?)
2006-02-22 17:24:19 +00:00
<visibility type="bool" userarchive="y">true</visibility>
Boris Koenig: This will modify menubar.cxx/hxx so that it exports the entire menubar (from menubar.xml) to the property tree, so that it can now be changed dynamically using Nasal's setprop() instruction and afterwards running a newly added fgcommand to update the menubar based on those changes using the appropriate menubar path within the property tree. By default the menubar from menubar.xml will be stored within: /sim/menubar/default Erik: I have moved the loading of menubar.xml into preferences.xml and made sure that the menubar is destroyed every time a new menubar is created.
2004-10-22 09:26:50 +00:00
<default include="gui/menubar.xml"/>
Add the autovisibility functionality for the menubar. If /sim/menubar/autovisibility/enabled is true, show the menubar when the mouse hits the upper edge of the window and hide the menubar on click outside a pui element.
2009-11-16 20:40:20 +00:00
<autovisibility>
<enabled type="bool" userarchive="y">false</enabled>
<edge-size type="int">5</edge-size>
</autovisibility>
Set the default visibility for the menubar. Default the ADF card to 0.
2003-01-18 22:03:45 +00:00
</menubar>
Setup default values for mouse pointer hide feature (default to off) and the default timeout for when it is enabled.
2004-06-14 18:48:10 +00:00
move gui styles from /sim/gui[n] to /sim/gui/style[n] to make /sim/gui free for other gui related properties
2006-03-09 23:05:08 +00:00
<gui>
change default GUI style
2007-12-04 13:12:15 +00:00
<current-style type="int" userarchive="y">1</current-style>
rename default.xml to classic.xml (who says that this needs to be the default? :-)
2007-03-16 10:47:14 +00:00
<style n="0" include="gui/styles/classic.xml"/>
move gui styles from /sim/gui[n] to /sim/gui/style[n] to make /sim/gui free for other gui related properties
2006-03-09 23:05:08 +00:00
<style n="1" include="gui/styles/anthrax.xml"/>
- add Debug->Development Extensions dialog with two checkboxes to - allow turning on/off extra widgets for developers (HUD dialog: colors, rendering dialog: visualization of shadow edges), and to turn on/off new - property key handler ('/'-key) Both features are off by default, and their state is saved to autosave.xml.
2007-11-18 12:20:17 +00:00
<devel-widgets type="bool" userarchive="y">false</devel-widgets>
move gui styles from /sim/gui[n] to /sim/gui/style[n] to make /sim/gui free for other gui related properties
2006-03-09 23:05:08 +00:00
</gui>
include the style file
2005-07-07 21:03:49 +00:00
Setup default values for mouse pointer hide feature (default to off) and the default timeout for when it is enabled.
2004-06-14 18:48:10 +00:00
<mouse>
Default to cursor hiding enabled for the next release. Default to AI aircraft disabled for next release until we can get to the bottom of potential memory leaks.
2004-07-27 20:42:17 +00:00
<hide-cursor>true</hide-cursor>
Setup default values for mouse pointer hide feature (default to off) and the default timeout for when it is enabled.
2004-06-14 18:48:10 +00:00
<cursor-timeout-sec>10.0</cursor-timeout-sec>
</mouse>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
Added a replay manager dialog box. Other misc. tweaks and updates.
2003-09-11 19:35:18 +00:00
<replay>
<duration type="double">90</duration>
<view type="int">1</view>
</replay>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
add paths and runway parameter defaults, so that people are aware of the possibilities
2008-05-02 21:47:53 +00:00
<airport>
<runways>
<start-offset-m>5.0</start-offset-m>
<search>
<length-weight>0.01</length-weight>
<width-weight>0.01</width-weight>
<surface-weight>10</surface-weight>
<deviation-weight>1</deviation-weight>
</search>
</runways>
</airport>
don't use /sim/ATC/ and /sim/atc/ wildly mixed together; it's lower case everywhere, just as in every other property name
2005-05-10 09:41:19 +00:00
<atc>
Turn the ATC back on - after asking Curt first\!
2004-12-27 00:24:28 +00:00
<enabled type="bool">true</enabled>
don't use /sim/ATC/ and /sim/atc/ wildly mixed together; it's lower case everywhere, just as in every other property name
2005-05-10 09:41:19 +00:00
</atc>
Enable ATC and AI traffic by default
2003-04-01 14:27:45 +00:00
<ai-traffic>
Sorry guys , that local change wasn't supposed to be commited
2009-02-06 23:10:00 +00:00
<enabled type="bool" userarchive="y">true</enabled>
autosave ai-traffic settings
2006-02-13 15:12:40 +00:00
<level type="int" userarchive="y">1</level>
Enable ATC and AI traffic by default
2003-04-01 14:27:45 +00:00
</ai-traffic>
Set the default visibility for the menubar. Default the ADF card to 0.
2003-01-18 22:03:45 +00:00
Durk Talsma: I've included the latest fixes to the Traffic Manager/AI flightplan generation code. Most of the code changes are in AIFllightplan.cxx. This is the code that runs without depending on predefined FlightPlans in #FG_ROOT/Data/AI/Flightplans.i As suggested by Dave, I've also added a new property in preferences.xml: /sim/traffic-manager/enabled, which is used to control whether or not the traffic manager is active. I'm still working on a few more 737 traffic patterns, those are going to take a little longer, so I didn't want to wait sending in this code. Finally, I haven't put much effort into ensuring "aeronautical correctness" in this version yet. The code works on my system, but what the AI plane do may actaully be quite rediculous. But I'd like to leave that for the next version.
2004-07-22 18:50:30 +00:00
<traffic-manager>
Sorry guys , that local change wasn't supposed to be commited
2009-02-06 23:10:00 +00:00
<enabled type="bool">true</enabled>
Innis Cunningham: A traffic demo for the San Fransisco area. Airports populated are: KHAF, KHWD, KOAK, KSJC, and KSFO. Includes traffic for two to three major US based airlines for each aircraft type. Traffic is included for the 737, 747, 767, A320, A333, and an assorted selection of smaller aircraft.
2007-06-28 18:46:57 +00:00
<instantaneous-action type="bool">false</instantaneous-action>
Changed the default value for the proportion of AI traffic back to 1.0.
2008-07-13 10:52:57 +00:00
<proportion>1.0</proportion>
Durk Talsma: I've included the latest fixes to the Traffic Manager/AI flightplan generation code. Most of the code changes are in AIFllightplan.cxx. This is the code that runs without depending on predefined FlightPlans in #FG_ROOT/Data/AI/Flightplans.i As suggested by Dave, I've also added a new property in preferences.xml: /sim/traffic-manager/enabled, which is used to control whether or not the traffic manager is active. I'm still working on a few more 737 traffic patterns, those are going to take a little longer, so I didn't want to wait sending in this code. Finally, I haven't put much effort into ensuring "aeronautical correctness" in this version yet. The code works on my system, but what the AI plane do may actaully be quite rediculous. But I'd like to leave that for the next version.
2004-07-22 18:50:30 +00:00
</traffic-manager>
Add a sailboat to the bay area.
2003-11-30 18:32:39 +00:00
<ai>
Change the type 'storm' to 'thunderstorm' and enable the ai-models code by default again.
2004-09-23 11:10:09 +00:00
<enabled type="bool">true</enabled>
Release related updates: - Disable the 737 AI demo (because it uses the user 737-300, which is currently not part of the base package). - New version number - Add some more 747 size parking areas at KSFO.
2007-12-11 21:44:02 +00:00
<scenario>nimitz_demo</scenario>
Initial import of the balloon scenario from gooneybird
2010-04-07 14:15:24 +00:00
<!-- <scenario>balloon_demo</scenario> -->
Release related updates: - Disable the 737 AI demo (because it uses the user 737-300, which is currently not part of the base package). - New version number - Add some more 747 size parking areas at KSFO.
2007-12-11 21:44:02 +00:00
<!-- <scenario>aircraft_demo</scenario> -->
Default to turning point sprites on for runway lighting.
2006-07-20 14:31:25 +00:00
<!-- <scenario>refueling_demo</scenario> -->
Preparation for 0.9.11-pre1 release.
2007-05-15 16:09:55 +00:00
<!-- <scenario>lead_aircraft</scenario> -->
Add a sailboat to the bay area.
2003-11-30 18:32:39 +00:00
</ai>
pre-set callsign
2006-02-10 19:57:06 +00:00
- add property /sim/startup/terminal-ansi-colors {BOOL}. This is used by debug.nas to turn on/off syntax coloring for dumped data (which is desirable as compound data types can fill several screens with rather hard to read data). Unfortunately, it can't be reliably deduced from the OS whether ANSI colors are available or not. - move "multiplayer chat" properties to where they belong
2007-02-18 17:21:50 +00:00
<multiplay>
<chat type="string">Hello</chat>
<transmission-freq-hz type="string">118500000</transmission-freq-hz>
- we prefer hyphens in property names to underscores - save /sim/multiplayer/chat-display to autosave.xml - remove trailing spaces
2007-08-01 19:37:51 +00:00
<chat-display type="bool" userarchive="y">true</chat-display>
Stuart Buchanan: Add chat menu
2007-12-08 19:01:03 +00:00
<chat-menu include="ATC/chat-menu-entries.xml"/>
entry for /sim/multiplay/write-message-log (off by default)
2009-02-15 18:06:30 +00:00
<write-message-log type="bool">false</write-message-log>
set the blue/yellow glider as default model (This isn't really necessary, as this is also the hard-coded default, but the entry should make people aware of the configuration option.)
2009-02-03 15:53:45 +00:00
<default-model type="string">Models/Geometry/glider.ac</default-model>
- add property /sim/startup/terminal-ansi-colors {BOOL}. This is used by debug.nas to turn on/off syntax coloring for dumped data (which is desirable as compound data types can fill several screens with rather hard to read data). Unfortunately, it can't be reliably deduced from the OS whether ANSI colors are available or not. - move "multiplayer chat" properties to where they belong
2007-02-18 17:21:50 +00:00
</multiplay>
pre-set callsign
2006-02-10 19:57:06 +00:00
<user>
<callsign type="string">Golf Foxtrot Sierra</callsign>
</user>
Indentation cleanups from Martin Dressler.
2002-03-02 23:44:28 +00:00
</sim>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
Add a preset mouse mode entry
2003-12-28 17:41:21 +00:00
<!-- mouse mode -->
<devices>
<status>
<mice>
<mouse n="0">
<mode>0</mode>
</mouse>
</mice>
</status>
</devices>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<!-- Position -->
<position>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<altitude-ft type="double">-9999</altitude-ft>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</position>
<!-- Velocities -->
<velocities>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<speed-north-fps type="double">0.0</speed-north-fps>
<speed-east-fps type="double">0.0</speed-east-fps>
<speed-down-fps type="double">0.0</speed-down-fps>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</velocities>
<!-- Orientation -->
<orientation>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<heading-deg type="double">270</heading-deg>
<roll-deg type="double">0.0</roll-deg>
<pitch-deg type="double">0.424</pitch-deg>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</orientation>
<!-- Environment -->
<environment>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<weather-scenarios>
<scenario>
<name>Disabled</name>
<description>METAR weather generation is disabled. Use 'Weather Conditions' and 'Clouds' dialogs to setup your weather.</description>
</scenario>
<scenario>
<name>Live data</name>
<description>Fetch live weather data for your nearest airport from noaa.gov. You need a working internet connection.</description>
</scenario>
<scenario>
<name>Manual input</name>
<description>Enter your favorite METAR weather in the textbox below. A valid METAR syntax is required.</description>
</scenario>
<scenario>
<name>Fair weather</name>
<metar>XXXX 012345Z 15003KT 12SM SCT041 FEW200 20/08 Q1015 NOSIG</metar>
<description>A lovely day for trip to your favorite 100$ hamburger airfield</description>
</scenario>
<scenario>
<name>Thunderstorm</name>
<metar>XXXX 012345Z 15012G25KT 4000 TSRA FEW030CB SCT035TCU 27/24 Q0995</metar>
<description>A hot and damp summer day with thunderstorms developing in the afternoon.
Be prepared for reduction of visibility in showers and strong gusts
near thunderstorms</description>
</scenario>
<scenario>
<name>Stormy Monday</name>
<metar>XXXX 012345Z 28035G50KT 9999 TSRA SCT022CB BKN030 13/09 Q1005</metar>
Correct typo
2009-05-29 12:22:47 +00:00
<description>You're out for an adventure? Gusty winds blowing from the west
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
and isolated thunderstorms should be avoided. Fasten your seatbelt!</description>
</scenario>
<scenario>
<name>Marginal VFR</name>
<metar>XXXX 012345Z 23010KT 5000 SHRA SCT012 BKN018 OVC060 15/11 Q1010</metar>
<description>After the storm - limited visibility and some showers.
Go or No-Go?</description>
</scenario>
<scenario>
<name>CAT I minimum</name>
<metar>XXXX 012345Z 15015KT 0800 -RA BKN002 OVC004 08/06 Q0990</metar>
<description>If you just got your IFR rating, this is what you are allowed to do. But can you?</description>
</scenario>
<scenario>
<name>CAT II minimum</name>
<metar>XXXX 012345Z 15010KT 0400 -RA BKN001 OVC002 08/06 Q0990</metar>
<description>With just a 1/4 mile visibility and clouds at 100ft, you don't see much of the runway until
seconds before touchdown. Trust your instruments to stay alive.</description>
</scenario>
<scenario>
<name>CAT IIIb minimum</name>
<metar>XXXX 012345Z VRB01KT 0100 FG OVC001 OVC002 02/02 Q0990</metar>
<description>This is expert level. You will barely see the taxiway from the cockpit, even if you are
on ground. Fog and light drizzle, freezing level at 1000ft.</description>
</scenario>
</weather-scenarios>
Default start in Fair weather
2005-08-25 17:27:17 +00:00
<weather-scenario>Fair weather</weather-scenario>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
<config>
<boundary-transition-ft>500</boundary-transition-ft>
<boundary>
<entry>
<elevation-ft>0</elevation-ft>
<wind-from-heading-deg>270</wind-from-heading-deg>
<wind-speed-kt>3</wind-speed-kt>
Make default visibility exactly 10 miles.
2003-07-17 18:17:13 +00:00
<visibility-m>16093.44</visibility-m>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
<pressure-sea-level-inhg>29.92</pressure-sea-level-inhg>
Set temperature-degc (at altitude temp) for the environment layers rather than temperature-sea-level-degc. It made no sense to specify the sea level temperature at different altitudes ... :-)
2003-06-24 19:53:21 +00:00
<temperature-degc>15.0</temperature-degc>
<dewpoint-degc>5.0</dewpoint-degc>
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<factor>0.2</factor>
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<magnitude-norm>0.0</magnitude-norm>
<rate-hz>1.0</rate-hz>
</turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<wind-heading-change-deg>0</wind-heading-change-deg>
<wind-speed-change-rel>0</wind-speed-change-rel>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
</entry>
<entry>
<elevation-ft>500</elevation-ft>
<wind-from-heading-deg>280</wind-from-heading-deg>
<wind-speed-kt>6</wind-speed-kt>
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<factor>1.0</factor>
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<magnitude-norm>0.1</magnitude-norm>
<rate-hz>1.0</rate-hz>
</turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<wind-heading-change-deg>5</wind-heading-change-deg>
<wind-speed-change-rel>0.3</wind-speed-change-rel>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
</entry>
</boundary>
<aloft>
<entry>
<elevation-ft>3000</elevation-ft>
<wind-from-heading-deg>300</wind-from-heading-deg>
<wind-speed-kt>10</wind-speed-kt>
Make default visibility exactly 10 miles.
2003-07-17 18:17:13 +00:00
<visibility-m>16093.44</visibility-m>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
<pressure-sea-level-inhg>29.92</pressure-sea-level-inhg>
Set temperature-degc (at altitude temp) for the environment layers rather than temperature-sea-level-degc. It made no sense to specify the sea level temperature at different altitudes ... :-)
2003-06-24 19:53:21 +00:00
<!-- <temperature-degc>15.0</temperature-degc> -->
<!-- <dewpoint-degc>5.0</dewpoint-degc> -->
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<factor>0.5</factor>
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<magnitude-norm>0.05</magnitude-norm>
<rate-hz>1.0</rate-hz>
</turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<wind-heading-change-deg>25</wind-heading-change-deg>
<wind-speed-change-rel>1</wind-speed-change-rel>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
</entry>
<entry>
<elevation-ft>6000</elevation-ft>
<wind-from-heading-deg>310</wind-from-heading-deg>
<wind-speed-kt>20</wind-speed-kt>
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<factor>0.0</factor>
More turbulence tweaks and fixes.
2003-07-15 01:26:37 +00:00
<magnitude-norm>0.0</magnitude-norm>
<rate-hz>1.0</rate-hz>
</turbulence>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<wind-heading-change-deg>30</wind-heading-change-deg>
<wind-speed-change-rel>1.2</wind-speed-change-rel>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
</entry>
<entry>
<elevation-ft>9000</elevation-ft>
<wind-from-heading-deg>320</wind-from-heading-deg>
<wind-speed-kt>30</wind-speed-kt>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<wind-heading-change-deg>35</wind-heading-change-deg>
<wind-speed-change-rel>1.3</wind-speed-change-rel>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
</entry>
</aloft>
</config>
Initialize all five cloud layers.
2002-05-17 15:54:24 +00:00
<clouds>
<status>true</status>
<layer n="0">
Use "coverage" instead of "type". Rename "mostly-cloudy" to "broken" and "mostly-sunny" to "scattered", to follow standard weather terminology. Add "few".
2003-04-05 03:36:20 +00:00
<coverage>scattered</coverage>
Stuart Buchanan : This provides the following enhancements & bug fixes - Fix the chequer-board bug. - Add proper cloud coverage function - so scattered clouds are now truly scattered. - Add real-time control for visibility range. - Use a limited set of clouds rather than generating a completely new Geode for each cloud. This saves sorting and display time. - Add controls to Rendering dialog to allow fine-tuning of the number of sprites, cloud visibility and the number of different types of cloud. - Add some variance to the sort back-off to avoid all clouds being sorted at the same time. - Pack attributes into vectors for performance - Re-order the cloud type determination code so that if a cloud layer could either be stratus or cumulus, cumulus is used. - Lowered the cloud level in the standard cloud configuration slightly so a cumulus layer is generated rather than stratus. These last two mean that you should see some 3D cumuli if disabling real weather fetch. My thanks to Yon Uriarte for his help with performance work.
2008-12-04 20:57:55 +00:00
<elevation-ft>4000</elevation-ft>
Use "coverage" instead of "type". Rename "mostly-cloudy" to "broken" and "mostly-sunny" to "scattered", to follow standard weather terminology. Add "few".
2003-04-05 03:36:20 +00:00
<thickness-ft>600</thickness-ft>
<transition-ft>150</transition-ft>
Initialize all five cloud layers.
2002-05-17 15:54:24 +00:00
<span-m>40000</span-m>
</layer>
We default to having two active cloud layers. Let's fill in layers 0 and 1 rather than layers 1 and 4.
2003-06-23 20:55:57 +00:00
<layer n="1">
<coverage>cirrus</coverage>
<elevation-ft>19500</elevation-ft>
<thickness-ft>65</thickness-ft>
<transition-ft>25</transition-ft>
<span-m>40000</span-m>
</layer>
Initialize all five cloud layers.
2002-05-17 15:54:24 +00:00
<layer n="2">
Use "coverage" instead of "type". Rename "mostly-cloudy" to "broken" and "mostly-sunny" to "scattered", to follow standard weather terminology. Add "few".
2003-04-05 03:36:20 +00:00
<coverage>clear</coverage>
Initialize all five cloud layers.
2002-05-17 15:54:24 +00:00
<span-m>40000</span-m>
</layer>
<layer n="3">
Use "coverage" instead of "type". Rename "mostly-cloudy" to "broken" and "mostly-sunny" to "scattered", to follow standard weather terminology. Add "few".
2003-04-05 03:36:20 +00:00
<coverage>clear</coverage>
Initialize all five cloud layers.
2002-05-17 15:54:24 +00:00
<span-m>40000</span-m>
</layer>
We default to having two active cloud layers. Let's fill in layers 0 and 1 rather than layers 1 and 4.
2003-06-23 20:55:57 +00:00
<layer n="5">
<coverage>clear</coverage>
Initialize all five cloud layers.
2002-05-17 15:54:24 +00:00
<span-m>40000</span-m>
</layer>
</clouds>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
Harald JOHNSEN: Changes ======= New volumetric shadows for FlightGear. There is now two new checkboxes in the rendering dialog to enable/disable shadows for the user aircraft and for static scenery objects (ie those defined in the .stg files). AI and random objects are not handled for the moment. known bugs ========== - ghost objects
2005-06-26 17:19:58 +00:00
<cloudlayers include="cloudlayers.xml"/>
Default values for base and gusting wind speeds.
2002-05-06 21:43:40 +00:00
<params>
rename the live weather property
2004-02-21 14:04:06 +00:00
<real-world-weather-fetch type="bool">false</real-world-weather-fetch>
Add the ability to set the minimum allowed age for metar reports.
2005-02-22 18:12:53 +00:00
<metar-max-age-min type="long">240</metar-max-age-min>
new command line option --metar="some metar string" provide some predefined weather scenarios
2009-05-29 11:41:32 +00:00
<metar-updates-environment type="bool">true</metar-updates-environment>
let JSBSim use FlightGear's atmosphere by default
2007-10-26 16:44:08 +00:00
<control-fdm-atmosphere type="bool">true</control-fdm-atmosphere>
David Culp: Here are files to get automated contrails working. I've set up contrails for the 737, using my simple, untextured contrail model. Vivian has made another contrail model, but I'm still trying to get his to work. I'm hoping others will try to make contrail models also. Here's some code that defines a top to thermals. When the top of a thermal is reached the strength is phased-out linearly over the next 100 feet of altitude. At first I tried just capping the thermal at the top, but the change in thermal strength was too fast for the FDM to handle well. Included is a new version of the thermal scenario that includes a top (height-msl) to the thermal. The default value is 5000 feet.
2004-11-07 14:50:01 +00:00
<contrail-altitude>30000</contrail-altitude>
Default values for base and gusting wind speeds.
2002-05-06 21:43:40 +00:00
</params>
Added initialization and user dialog for improved weather system.
2003-06-08 14:44:53 +00:00
Anders GIDENSTAM: wildfire (read $FG_ROOT/Models/Effects/Wildfire/README)
2009-01-18 15:58:57 +00:00
<wildfire>
Because wild fire is still an "experimental" feature (i.e. default operation can lead to extreme performance reduction in a relatively short time.) Let's set the default mode to "off". Users can turn on the various components of this features according to their own preferences and those preferences are then autosaved.
2009-02-16 17:02:48 +00:00
<enabled type="bool" userarchive="y">false</enabled>
Anders GIDENSTAM: wildfire (read $FG_ROOT/Models/Effects/Wildfire/README)
2009-01-18 15:58:57 +00:00
<share-events type="bool" userarchive="y">false</share-events>
<save-on-exit type="bool" userarchive="y">false</save-on-exit>
<restore-on-startup type="bool" userarchive="y">false</restore-on-startup>
Because wild fire is still an "experimental" feature (i.e. default operation can lead to extreme performance reduction in a relatively short time.) Let's set the default mode to "off". Users can turn on the various components of this features according to their own preferences and those preferences are then autosaved.
2009-02-16 17:02:48 +00:00
<fire-on-crash type="bool" userarchive="y">false</fire-on-crash>
<report-score type="bool" userarchive="y">false</report-score>
Anders GIDENSTAM: wildfire (read $FG_ROOT/Models/Effects/Wildfire/README)
2009-01-18 15:58:57 +00:00
<data type="string"/>
</wildfire>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</environment>
<controls>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<flight>
<aileron type="double">0.0</aileron>
<aileron-trim type="double">0.0</aileron-trim>
<elevator type="double">0.0</elevator>
<elevator-trim type="double">0.0</elevator-trim>
<rudder type="double">0.0</rudder>
<rudder-trim type="double">0.0</rudder-trim>
<flaps type="double">0.0</flaps>
Add a default value for the flaps-servicable flag.
2003-08-01 19:42:42 +00:00
<flaps-serviceable type="bool">true</flaps-serviceable>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
</flight>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<engines>
<engine n="0">
<starter type="bool">false</starter>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
<magnetos type="int">0</magnetos>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<throttle type="double">0.0</throttle>
<mixture type="double">1.0</mixture>
Default to cursor hiding enabled for the next release. Default to AI aircraft disabled for next release until we can get to the bottom of potential memory leaks.
2004-07-27 20:42:17 +00:00
<condition type="double">1.0</condition>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<propeller-pitch type="double">1.0</propeller-pitch>
Add initial defaults for engine failure parameters
2003-08-01 00:28:33 +00:00
<faults>
<serviceable>true</serviceable>
<left-magneto-serviceable>true</left-magneto-serviceable>
<right-magneto-serviceable>true</right-magneto-serviceable>
<spark-plugs-serviceable>true</spark-plugs-serviceable>
<oil-pressure-status>0</oil-pressure-status>
<fuel-pump-serviceable>true</fuel-pump-serviceable>
</faults>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
</engine>
<engine n="1">
<starter type="bool">false</starter>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
<magnetos type="int">0</magnetos>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<throttle type="double">0.0</throttle>
<mixture type="double">1.0</mixture>
Default to cursor hiding enabled for the next release. Default to AI aircraft disabled for next release until we can get to the bottom of potential memory leaks.
2004-07-27 20:42:17 +00:00
<condition type="double">1.0</condition>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<propeller-pitch type="double">1.0</propeller-pitch>
Add initial defaults for engine failure parameters
2003-08-01 00:28:33 +00:00
<faults>
<serviceable>true</serviceable>
<left-magneto-serviceable>true</left-magneto-serviceable>
<right-magneto-serviceable>true</right-magneto-serviceable>
<spark-plugs-serviceable>true</spark-plugs-serviceable>
<oil-pressure-status>0</oil-pressure-status>
<fuel-pump-serviceable>true</fuel-pump-serviceable>
</faults>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
</engine>
<engine n="2">
<starter type="bool">false</starter>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
<magnetos type="int">0</magnetos>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<throttle type="double">0.0</throttle>
<mixture type="double">1.0</mixture>
Default to cursor hiding enabled for the next release. Default to AI aircraft disabled for next release until we can get to the bottom of potential memory leaks.
2004-07-27 20:42:17 +00:00
<condition type="double">1.0</condition>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<propeller-pitch type="double">1.0</propeller-pitch>
Add initial defaults for engine failure parameters
2003-08-01 00:28:33 +00:00
<faults>
<serviceable>true</serviceable>
<left-magneto-serviceable>true</left-magneto-serviceable>
<right-magneto-serviceable>true</right-magneto-serviceable>
<spark-plugs-serviceable>true</spark-plugs-serviceable>
<oil-pressure-status>0</oil-pressure-status>
<fuel-pump-serviceable>true</fuel-pump-serviceable>
</faults>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
</engine>
<engine n="3">
<starter type="bool">false</starter>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
<magnetos type="int">0</magnetos>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<throttle type="double">0.0</throttle>
<mixture type="double">1.0</mixture>
Default to cursor hiding enabled for the next release. Default to AI aircraft disabled for next release until we can get to the bottom of potential memory leaks.
2004-07-27 20:42:17 +00:00
<condition type="double">1.0</condition>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<propeller-pitch type="double">1.0</propeller-pitch>
Add initial defaults for engine failure parameters
2003-08-01 00:28:33 +00:00
<faults>
<serviceable>true</serviceable>
<left-magneto-serviceable>true</left-magneto-serviceable>
<right-magneto-serviceable>true</right-magneto-serviceable>
<spark-plugs-serviceable>true</spark-plugs-serviceable>
<oil-pressure-status>0</oil-pressure-status>
<fuel-pump-serviceable>true</fuel-pump-serviceable>
</faults>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
</engine>
</engines>
<gear>
Attempt #1 to sort out confusion between left / right / parking brake controls in the cockpit vs. which wheels they apply to. FlightGear now sets /controls/gear/brake-left, /controls/gear/brake-right, and /controls/gear/brake-parking. It should be up to the FDM to sort out which wheels under which circumstances are affected by these controls and ultimately what happens to the physical motion of the aircraft.
2004-01-12 17:49:33 +00:00
<brake-left type="double">0.0</brake-left>
<brake-right type="double">0.0</brake-right>
<brake-parking type="double">0.0</brake-parking>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<gear-down type="bool">true</gear-down>
</gear>
<lighting>
<taxi-light type="bool">true</taxi-light>
<landing-lights type="bool">true</landing-lights>
<nav-lights type="bool">true</nav-lights>
Added property defaults for aircraft lighting: /controls/lights/beacon = true /controls/lights/navigation = false
2002-11-06 15:50:29 +00:00
<beacon type="bool">true</beacon>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<strobe type="bool">false</strobe>
</lighting>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<anti-ice>
<pitot-heat type="bool">false</pitot-heat>
<engine n="0">
<carb-heat type="bool">false</carb-heat>
</engine>
<engine n="1">
<carb-heat type="bool">false</carb-heat>
</engine>
<engine n="2">
<carb-heat type="bool">false</carb-heat>
</engine>
<engine n="3">
<carb-heat type="bool">false</carb-heat>
</engine>
</anti-ice>
Initialize more cockpit controls.
2002-11-26 04:05:27 +00:00
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</controls>
<!-- User input devices -->
<input>
load multikey.xml file
2008-09-28 16:34:43 +00:00
<keyboard include="keyboard.xml">
<multikey include="Input/Keyboard/multikey.xml"/>
</keyboard>
add joysticks.xml again; It doesn't do anything, but explains how to make local changes. People are used to modifying this file, and seem helpless without it. Further explanations will be added to README.Joystick.html. The dummy entry is necessary because EasyXML aborts without at least one entry, and segfaults without <PropertyList> entry.
2005-11-24 10:51:24 +00:00
<joysticks include="joysticks.xml"/>
Initial mouse configuration support. This will be ignored unless you configure --with-new-mouse, and there's not much there yet anyway.
2002-03-23 22:30:39 +00:00
<mice include="mice.xml"/>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</input>
Fix the default radio frequencies.
2004-12-03 22:24:41 +00:00
<instrumentation>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
Fix the default radio frequencies.
2004-12-03 22:24:41 +00:00
<!-- Radio settings -->
Provided some default property values, to use the caching more efficiently.
2002-04-06 21:48:39 +00:00
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<comm n="0">
<frequencies>
Changed default frequencies. KSFO ATIS is not on standby on COM1, and KOAK ATIS is on standby on COM2 (this one doesn't seem to work, though).
2002-12-30 19:47:22 +00:00
<selected-mhz type="double">120.500</selected-mhz>
<standby-mhz type="double">118.850</standby-mhz>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</frequencies>
Set default comm volume in preparation for honouring this property
2003-01-09 13:48:41 +00:00
<volume type="double">0.6</volume>
Default comm radios to "serviceable".
2004-12-30 21:11:13 +00:00
<serviceable>true</serviceable>
pre-set /instrumentation/comm[*]/ptt to int(0)
2007-07-13 14:29:52 +00:00
<ptt type="int">0</ptt>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</comm>
<comm n="1">
<frequencies>
Changed default frequencies. KSFO ATIS is not on standby on COM1, and KOAK ATIS is on standby on COM2 (this one doesn't seem to work, though).
2002-12-30 19:47:22 +00:00
<selected-mhz type="double">118.300</selected-mhz>
<standby-mhz type="double">133.775</standby-mhz>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</frequencies>
Set default comm volume in preparation for honouring this property
2003-01-09 13:48:41 +00:00
<volume type="double">0.6</volume>
Default comm radios to "serviceable".
2004-12-30 21:11:13 +00:00
<serviceable>true</serviceable>
pre-set /instrumentation/comm[*]/ptt to int(0)
2007-07-13 14:29:52 +00:00
<ptt type="int">0</ptt>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</comm>
<nav n="0">
<frequencies>
Changed the default nav frequencies to be more appropriate for SFO.
2002-09-02 21:35:42 +00:00
<selected-mhz type="double">115.80</selected-mhz>
<standby-mhz type="double">111.70</standby-mhz>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</frequencies>
<radials>
Changed the default nav frequencies to be more appropriate for SFO.
2002-09-02 21:35:42 +00:00
<selected-deg type="double">280.0</selected-deg>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</radials>
Nav instruments now check power on /systems/electrical/outputs/nav[0/1]. Need to update most electrical system configs to reflect this property name change.
2004-12-04 21:15:43 +00:00
<serviceable>true</serviceable>
<cdi>
<serviceable>true</serviceable>
</cdi>
<gs>
<serviceable>true</serviceable>
</gs>
<to-from>
<serviceable>true</serviceable>
</to-from>
Support for gps annunciator and nav-gps switch
2005-10-02 18:04:54 +00:00
<slaved-to-gps type="bool">false</slaved-to-gps>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</nav>
<nav n="1">
<frequencies>
Changed the default nav frequencies to be more appropriate for SFO.
2002-09-02 21:35:42 +00:00
<selected-mhz type="double">116.80</selected-mhz>
<standby-mhz type="double">113.90</standby-mhz>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</frequencies>
<radials>
Add explicit types for all non-string properties. This will help a lot, since otherwise a property that is never set or tied by FlightGear itself will always be kept as a string and converted on each access. That's why fgGetBool and friends could take up a lot of processor time sometimes.
2002-04-09 10:45:47 +00:00
<selected-deg type="double">029.0</selected-deg>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</radials>
Nav instruments now check power on /systems/electrical/outputs/nav[0/1]. Need to update most electrical system configs to reflect this property name change.
2004-12-04 21:15:43 +00:00
<serviceable>true</serviceable>
<cdi>
<serviceable>true</serviceable>
</cdi>
<gs>
<serviceable>true</serviceable>
</gs>
<to-from>
<serviceable>true</serviceable>
</to-from>
Support for gps annunciator and nav-gps switch
2005-10-02 18:04:54 +00:00
<slaved-to-gps type="bool">false</slaved-to-gps>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
</nav>
Default transponder serviceable = true.
2004-12-30 21:36:35 +00:00
<transponder>
<inputs>
<serviceable>true</serviceable>
</inputs>
</transponder>
Josh BABCOCK: "Here is a patch that allows marker beacon volume to be set via /instrumentation/marker-beacon/volume."
2006-06-24 07:43:04 +00:00
<marker-beacon>
<volume type="double">0.3</volume>
</marker-beacon>
Fix the default radio frequencies.
2004-12-03 22:24:41 +00:00
<!-- Instruments -->
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
New pitot system and airspeed indicator.
2002-09-28 20:49:56 +00:00
<airspeed-indicator>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
New pitot system and airspeed indicator.
2002-09-28 20:49:56 +00:00
</airspeed-indicator>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
Initialize all instruments to serviceable.
2003-01-26 16:06:41 +00:00
<attitude-indicator>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
<config>
<!-- true if this AI can tumble -->
<tumble-flag type="bool" archive="y">false</tumble-flag>
</config>
<caged type="bool" archive="y">false</caged>
Initialize all instruments to serviceable.
2003-01-26 16:06:41 +00:00
<serviceable type="bool" archive="y">true</serviceable>
<spin type="double" archive="y">0.0</spin>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
<tumble-norm type="double" archive="y">0.0</tumble-norm>
<indicated-pitch-deg type="double">0.0</indicated-pitch-deg>
<indicated-roll-deg type="double">0.0</indicated-roll-deg>
Initialize all instruments to serviceable.
2003-01-26 16:06:41 +00:00
</attitude-indicator>
Initialize all of the attitude-indicator properties explicitly.
2003-04-05 15:04:20 +00:00
Modifications to support new altimeter and static port models in FlightGear.
2002-09-27 18:26:42 +00:00
<altimeter>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
<setting-inhg type="double" archive="y">29.92</setting-inhg>
Modifications to support new altimeter and static port models in FlightGear.
2002-09-27 18:26:42 +00:00
</altimeter>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
Initialize all instruments to serviceable.
2003-01-26 16:06:41 +00:00
<turn-indicator>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
Initialize all instruments to serviceable.
2003-01-26 16:06:41 +00:00
</turn-indicator>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
Initialize all instruments to serviceable.
2003-01-26 16:06:41 +00:00
<slip-skid-ball>
<serviceable type="bool" archive="y">true</serviceable>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
</slip-skid-ball>
only dme.xml knows that it should use the selected nav[0] frequency with switch-position=1, so let's set it here for all others. This shouldn't be done in aircraft *-set.xml files (unless there's a *very* good reason), because this overwrites the settings that were made by the --dme option, and thus breaks it.
2006-03-10 20:22:24 +00:00
Modifications to support new VSI and HI models in FlightGear.
2002-09-27 22:00:02 +00:00
<heading-indicator>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
<spin type="double" archive="y">0.0</spin>
Updates to refelect the controls update of FlightGear. It could be there are a few unupdated controls left. To simplify the transisition there is a file called README.properties in the docs-mini directory of FlightGear that explains the new controls layout.
2003-04-01 12:41:12 +00:00
<offset-deg type="double" archive="y">4.5</offset-deg> <!-- just for fun -->
Modifications to support new VSI and HI models in FlightGear.
2002-09-27 22:00:02 +00:00
</heading-indicator>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
Modifications to support new VSI and HI models in FlightGear.
2002-09-27 22:00:02 +00:00
<vertical-speed-indicator>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
Modifications to support new VSI and HI models in FlightGear.
2002-09-27 22:00:02 +00:00
</vertical-speed-indicator>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
Initialize all instruments to serviceable.
2003-01-26 16:06:41 +00:00
<magnetic-compass>
<serviceable type="bool" archive="y">true</serviceable>
</magnetic-compass>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
Roy Vegard Ovesen: There are two <dme> entries in preferences.xml, resulting in two dme branches under /instrumentation/ (dme[0] and dme[1]). The serviceable property is only set for the second entry (dme[1]), and that one is not connected to the dme module. Solution: Remove the first <dme> entry, and set the index explicitly to 0 for the remaining <dme> entry.
2004-12-13 09:56:42 +00:00
<dme n="0">
Initialize DME to serviceable.
2003-03-09 03:38:59 +00:00
<serviceable type="bool" archive="y">true</serviceable>
no, even with this active seems the dme to behave correctly for me. preferences.xml is read first, then the --dme option is considered. After that nobody touches the switch. Only a few buggy aircraft. (??)
2006-03-10 19:41:22 +00:00
<switch-position type="int" archive="y">1</switch-position>
only dme.xml knows that it should use the selected nav[0] frequency with switch-position=1, so let's set it here for all others. This shouldn't be done in aircraft *-set.xml files (unless there's a *very* good reason), because this overwrites the settings that were made by the --dme option, and thus breaks it.
2006-03-10 20:22:24 +00:00
<frequencies>
<source>/instrumentation/nav[0]/frequencies/selected-mhz</source>
</frequencies>
Initialize DME to serviceable.
2003-03-09 03:38:59 +00:00
</dme>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
Basic initialization for the GPS.
2003-03-10 14:13:44 +00:00
<gps>
<serviceable type="bool" archive="y">true</serviceable>
Support for gps annunciator and nav-gps switch
2005-10-02 18:04:54 +00:00
<message-alert type="bool">false</message-alert>
<waypoint-alert type="bool">false</waypoint-alert>
<leg-mode type="bool">true</leg-mode>
<obs-mode type="bool">false</obs-mode>
<approach-arm type="bool">false</approach-arm>
<approach-active type="bool">false</approach-active>
<cdi-deflection type="double">0</cdi-deflection>
Basic initialization for the GPS.
2003-03-10 14:13:44 +00:00
</gps>
only dme.xml knows that it should use the selected nav[0] frequency with switch-position=1, so let's set it here for all others. This shouldn't be done in aircraft *-set.xml files (unless there's a *very* good reason), because this overwrites the settings that were made by the --dme option, and thus breaks it.
2006-03-10 20:22:24 +00:00
Use middle click to pull/push the pull-to-scan middle knob
2006-02-03 20:58:47 +00:00
<kln89>
<scan-pull type="bool" archive="y">false</scan-pull>
</kln89>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
Melchior FRANZ: These patches add a clock instrument, which allows to model failure ("serviceable") and to adjust the time independently of the system time (defaults to GMT). The main incentive is to make the p51d clock work and adjustable via the knob. o Offers a time string ("12:03:15") for the LCD or for LED clocks, or an empty string in case of failure/power off. The instrument assumes that digital clocks are battery buffered, so they will be updated even if there's nothing on the display. o Offers the number of seconds since midnight for analog clocks, like in the p51d. This number is not increased if !serviceable. So the clock will stand still and continue where it stopped when it's serviceable again. I did not consider voltage yet, because the Mustang's clock will need a lot more current than the LCD clock. The instrument is updated 4 times per second but returns immediately if neither time nor offset changed. The function getGMTString() in fg_props.cxx could be removed after applying these patches.
2003-06-27 08:45:35 +00:00
<clock>
<serviceable type="bool" archive="y">true</serviceable>
<offset-sec type="long" archive="y">0</offset-sec>
</clock>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
<adf>
<frequencies>
Melchior FRANZ: Don't know if this was intentional, but since revision 1.128 (2003/10/01 21:15:55; david; "Add some whitespace, and initialize the new ADF subsystem.") the ADF isn't initialized with useful frequencies any more. It should be something in the bay area. 379 is for BRIJJ again (in the glide slope of KSFO) and 341 is for RORAY (KOAK). Don't know what the standby frequency was before.
2004-03-19 18:05:58 +00:00
<selected-khz type="int">379</selected-khz>
<standby-khz type="int">341</standby-khz>
Add some whitespace, and initialize the new ADF subsystem.
2003-10-01 21:15:55 +00:00
</frequencies>
<serviceable type="bool" archive="y">true</serviceable>
<indicated-bearing-deg type="double">90</indicated-bearing-deg>
<error-deg type="double">2</error-deg>
<mode>adf</mode>
<rotation-deg type="double">0</rotation-deg>
<volume-norm type="double">0.5</volume-norm>
</adf>
Move the kr-87 adf from /radios to /instrumentation
2004-11-19 23:56:47 +00:00
<kr-87>
<inputs>
<rotation-deg type="double">0</rotation-deg>
</inputs>
<outputs>
<selected-khz type="double">379.0</selected-khz>
<standby-khz type="double">341.0</standby-khz>
</outputs>
</kr-87>
- set HUD font size to 8 px - remove trailing spaces/fix indentation
2006-07-24 16:01:41 +00:00
Support for gps annunciator and nav-gps switch
2005-10-02 18:04:54 +00:00
<gps-annunciator>
<lamp-test type="bool">false</lamp-test>
</gps-annunciator>
Move the kr-87 adf from /radios to /instrumentation
2004-11-19 23:56:47 +00:00
Vivian Meazza: This adds a TACAN instrument to the inventory. Range and bearing are calculated to the TACAN or VORTAC beacon selected by means of the Channel Selector in the E quipment/Radio pull-down menu. A TACAN beacon has also been added to the aircraft carrier Nimitz (channel #029Y ).
2005-10-01 09:56:18 +00:00
<tacan n="0">
perset Nimitz carrier TACAN channel (029Y)
2005-10-02 20:18:47 +00:00
<serviceable type="bool" archive="y">true</serviceable>
<switch-position type="int" archive="y">1</switch-position>
<frequencies>
<selected-channel n="1">0</selected-channel>
<selected-channel n="2">2</selected-channel>
<selected-channel n="3">9</selected-channel>
<selected-channel n="4">Y</selected-channel>
</frequencies>
Vivian Meazza: This adds a TACAN instrument to the inventory. Range and bearing are calculated to the TACAN or VORTAC beacon selected by means of the Channel Selector in the E quipment/Radio pull-down menu. A TACAN beacon has also been added to the aircraft carrier Nimitz (channel #029Y ).
2005-10-01 09:56:18 +00:00
</tacan>
Support new attitude indicator with spin-down.
2002-09-24 16:39:53 +00:00
</instrumentation>
Make the vacuum system serviceable by default.
2002-09-23 19:56:53 +00:00
<systems>
New pitot system and airspeed indicator.
2002-09-28 20:49:56 +00:00
<pitot>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
New pitot system and airspeed indicator.
2002-09-28 20:49:56 +00:00
</pitot>
Modifications to support new altimeter and static port models in FlightGear.
2002-09-27 18:26:42 +00:00
<static>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
<pressure-inhg type="double" archive="y">29.92</pressure-inhg>
Modifications to support new altimeter and static port models in FlightGear.
2002-09-27 18:26:42 +00:00
</static>
Start out with a serviceable electrical system.
2003-01-25 21:51:20 +00:00
<electrical>
<serviceable type="bool" archive="y">true</serviceable>
</electrical>
Make the vacuum system serviceable by default.
2002-09-23 19:56:53 +00:00
<vacuum>
Initialize spin. Set archivable flag on systems and instruments properties.
2002-09-29 18:28:06 +00:00
<serviceable type="bool" archive="y">true</serviceable>
Make the vacuum system serviceable by default.
2002-09-23 19:56:53 +00:00
</vacuum>
Make the 2nd (right) vacuum pump serviceable by default.
2003-05-27 19:48:03 +00:00
<vacuum>
<serviceable type="bool" archive="y">true</serviceable>
</vacuum>
refuel serviceable setting
2007-06-16 00:35:25 +00:00
<refuel>
<serviceable type="bool" archive="y">true</serviceable>
</refuel>
Make the vacuum system serviceable by default.
2002-09-23 19:56:53 +00:00
</systems>
Add a default value that the KAP140 autopilot needs.
2004-04-16 22:07:01 +00:00
<autopilot>
<internal>
<ft type="double">0.1</ft>
</internal>
set min altitude-agl above which the route-manager automatically locks heading/altitude on entering a waypoint. This is a convenience feature, and some aircraft may want to turn it off using a very high altitude.
2006-05-12 09:40:21 +00:00
<route-manager>
<min-lock-altitude-agl-ft type="double">300</min-lock-altitude-agl-ft>
</route-manager>
Add a default value that the KAP140 autopilot needs.
2004-04-16 22:07:01 +00:00
</autopilot>
Added some basic logging properties (disabled by default).
2003-02-01 17:58:59 +00:00
<logging>
<log n="0">
<enabled>false</enabled>
<interval-ms>1000</interval-ms>
<filename>fg_log.csv</filename>
<delimiter>,</delimiter>
<entry n="0">
<enabled>false</enabled>
<title>Longitude</title>
<property>/position/longitude-deg</property>
</entry>
<entry n="1">
<enabled>false</enabled>
<title>Latitude</title>
<property>/position/latitude-deg</property>
</entry>
<entry n="2">
<enabled>false</enabled>
<title>Altitude</title>
<property>/position/altitude-ft</property>
</entry>
<entry n="3">
<enabled>false</enabled>
<title>Roll</title>
<property>/orientation/roll-deg</property>
</entry>
<entry n="4">
<enabled>false</enabled>
<title>Pitch</title>
<property>/orientation/pitch-deg</property>
</entry>
<entry n="5">
<enabled>false</enabled>
<title>Heading</title>
<property>/orientation/heading-deg</property>
</entry>
</log>
</logging>
Added a replay manager dialog box. Other misc. tweaks and updates.
2003-09-11 19:35:18 +00:00
</PropertyList>
Converted to unix line endings Added /sim/startup/trim = true
2001-11-07 00:46:52 +00:00
<!-- end of preferences.xml -->
Copy permalink