1
0
Fork 0

Grid view for ufo

Addition of a coloured 8x8m lattice box around the UFO, switched on/off using
Ctrl+G.  This is to aid configuration of multi-monitor displays.
This commit is contained in:
Stuart Buchanan 2019-01-06 19:41:54 +00:00
parent 7a1cb213dc
commit 14ad6bb9f9
4 changed files with 50336 additions and 1305 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 127 B

File diff suppressed because it is too large Load diff

View file

@ -17,6 +17,19 @@
</condition>
</animation>
<animation>
<type>select</type>
<condition>
<property>/sim/model/display-grid</property>
</condition>
<object-name>GridBottom</object-name>
<object-name>GridFront</object-name>
<object-name>GridPort</object-name>
<object-name>GridRear</object-name>
<object-name>GridStarboard</object-name>
<object-name>GridTop</object-name>
</animation>
<animation>
<type>blend</type>
<object-name>body</object-name>

View file

@ -223,6 +223,10 @@
<name>=</name>
<desc>open/close cursor dialog</desc>
</key>
<key>
<name>Ctrl + G</name>
<desc>Show/hide 8x8x8m box grid around ufo for screen alignment</desc>
</key>
<line>Pre-select initial model (path relative to $FG_ROOT):</line>
<line>&#32;&#32;&#45;&#45;prop:cursor=Model/path.xml</line>
@ -255,15 +259,9 @@
<name>Ctrl-G</name>
<desc>Gear Up.</desc>
<binding>
<command>nasal</command>
<script>controls.gearDown(-1)</script>
<command>property-toggle</command>
<property>/sim/model/display-grid</property>
</binding>
<mod-up>
<binding>
<command>nasal</command>
<script>controls.gearDown(0)</script>
</binding>
</mod-up>
</key>
<key n="61">
@ -714,7 +712,7 @@
<aircraft>
<icao>
<!-- L = light, M = medium, H = heavy, J = jumbo -->
<wake-turbulence-category>L</wake-turbulence-category>
<wake-turbulence-category>L</wake-turbulence-category>
<!-- eg B738, C172, BE9L
http://www.icao.int/publications/DOC8643/Pages/Search.aspx may help finding these
@ -734,7 +732,7 @@
<landing-length-ft type="int">4000</landing-length-ft> -->
</minimum>
<climb>
<!-- potential for climb data in the future
<!-- potential for climb data in the future
<airspeed-knots type="int">280</airspeed-knots>
<vertical-speed-fpm type="int">2000</vertical-speed-fpm>
-->
@ -746,7 +744,7 @@
<!-- <flight-level type="int">330</flight-level> -->
</cruise>
<descent>
<!-- potential for descent data in the future
<!-- potential for descent data in the future
<airspeed-knots type="int">330</airspeed-knots>
<vertical-speed-fpm type="int">-1200</vertical-speed-fpm>
-->
@ -755,10 +753,10 @@
<airspeed-knots type="int">150</airspeed-knots>
</approach>
<maximum>
<!--
<altitude-ft type="int">21000</altitude-ft>
<!--
<altitude-ft type="int">21000</altitude-ft>
<mach type="double">0.875</mach>
<airspeed-knots type="int">180</airspeed-knots>
<airspeed-knots type="int">180</airspeed-knots>
-->
</maximum>
</performance>