fly/fgdata
1
0
Fork 0
Code Activity
fgdata/Aircraft/Instruments/radar.xml

496 lines
11 KiB
XML
Raw Normal View History

David Culp: The radar instrument uses the above three items, and applies a scale factor to the x-shift and y-shift in order to match the instrument's scale. Changing the display scale can be done entirely in the XML code for the instrument. Right now it's set up only to display a 40 mile scale. The radar is an AWACS view, which is not very realistic, but it is useful and demonstrates the technology. With just a little more work I can get a HUD marker. All I need to do there is make a bank angle adjustment to the current values. This works great with one target. For two or more targets the radar instrument will have to know the numbering of the aircraft model properties. This isn't implemented yet. David Culp: I couldn't stop. Here's a better radar instrument. It has: 1) range select knob 20 and 40 nm (not clickable.. yet) 2) target altitude readout at lower right 3) target disappears when range exceeds 43 nm 4) range ring values now are read from instrumentation/radar/range 5) instrumentation/radar/range is preset in the *-set.xml file to 40 nm The next step would be a clickable range selection. The problem here is that the instrument currently displays the "blip" only if the target's range is less then 43 nm. If the range scale is decreased to 20 nm, then the "blip" will show past the edges of the instrument. I might need to make another instrument for the 20 nm scale to make that work.
2004-02-27 10:22:23 +00:00
<PropertyList>
<name>Radar</name>
<w-base>256</w-base>
<h-base>256</h-base>
<layers>
<layer>
<name>background</name>
<w>256</w>
<h>256</h>
<texture>
<path>Aircraft/Instruments/Textures/radar_background.rgb</path>
<x1>0</x1>
<y1>0</y1>
<x2>1</x2>
<y2>1</y2>
</texture>
</layer>
David Culp: Here's some new AI stuff. 1) AI objects must now be defined in a scenario file, not in preferences.xml or a *-set file. (Of course this doesn't prevent objects from being created dynamically, as with Durk's traffic manager). 2) A new demo_scenario file is attached. It creates 3 aircraft, a sailboat, and a thunderstorm. 3) Objects without flightplans live forever. 4) FGAIShip::ProcessFlightplan() is not yet implemented. 5) preferences.xml should now define only <enabled> and <scenario>
2004-05-29 11:41:20 +00:00
<layer>
<name>target0 - range 40</name>
<w>8</w>
<h>17</h>
<condition>
<and>
Okay, maybe it was a good idea to assume that not all targets are target[0].
2004-06-11 17:19:59 +00:00
<equals>
<property>ai/models/aircraft[0]/radar/in-range</property>
<value>true</value>
</equals>
David Culp: Here's some new AI stuff. 1) AI objects must now be defined in a scenario file, not in preferences.xml or a *-set file. (Of course this doesn't prevent objects from being created dynamically, as with Durk's traffic manager). 2) A new demo_scenario file is attached. It creates 3 aircraft, a sailboat, and a thunderstorm. 3) Objects without flightplans live forever. 4) FGAIShip::ProcessFlightplan() is not yet implemented. 5) preferences.xml should now define only <enabled> and <scenario>
2004-05-29 11:41:20 +00:00
<equals>
<property>/instrumentation/radar/range</property>
<value>40</value>
</equals>
</and>
</condition>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0429687</x1>
<y1>0.8320312</y1>
<x2>0.0703125</x2>
<y2>0.8945312</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<property>ai/models/aircraft[0]/radar/x-shift</property>
<scale>2.55</scale>
</transformation>
<transformation>
<type>y-shift</type>
<property>ai/models/aircraft[0]/radar/y-shift</property>
<scale>2.55</scale>
</transformation>
<transformation>
<type>rotation</type>
<property>ai/models/aircraft[0]/radar/rotation</property>
</transformation>
</transformations>
</layer>
<layer>
<name>target0 - range 20</name>
<w>8</w>
<h>17</h>
<condition>
<and>
Okay, maybe it was a good idea to assume that not all targets are target[0].
2004-06-11 17:19:59 +00:00
<equals>
<property>ai/models/aircraft[0]/radar/in-range</property>
<value>true</value>
</equals>
David Culp: Here's some new AI stuff. 1) AI objects must now be defined in a scenario file, not in preferences.xml or a *-set file. (Of course this doesn't prevent objects from being created dynamically, as with Durk's traffic manager). 2) A new demo_scenario file is attached. It creates 3 aircraft, a sailboat, and a thunderstorm. 3) Objects without flightplans live forever. 4) FGAIShip::ProcessFlightplan() is not yet implemented. 5) preferences.xml should now define only <enabled> and <scenario>
2004-05-29 11:41:20 +00:00
<equals>
<property>/instrumentation/radar/range</property>
<value>20</value>
</equals>
</and>
</condition>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0429687</x1>
<y1>0.8320312</y1>
<x2>0.0703125</x2>
<y2>0.8945312</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<property>ai/models/aircraft[0]/radar/x-shift</property>
<scale>5.1</scale>
</transformation>
<transformation>
<type>y-shift</type>
<property>ai/models/aircraft[0]/radar/y-shift</property>
<scale>5.1</scale>
</transformation>
<transformation>
<type>rotation</type>
<property>ai/models/aircraft[0]/radar/rotation</property>
</transformation>
</transformations>
</layer>
David Culp: The radar instrument uses the above three items, and applies a scale factor to the x-shift and y-shift in order to match the instrument's scale. Changing the display scale can be done entirely in the XML code for the instrument. Right now it's set up only to display a 40 mile scale. The radar is an AWACS view, which is not very realistic, but it is useful and demonstrates the technology. With just a little more work I can get a HUD marker. All I need to do there is make a bank angle adjustment to the current values. This works great with one target. For two or more targets the radar instrument will have to know the numbering of the aircraft model properties. This isn't implemented yet. David Culp: I couldn't stop. Here's a better radar instrument. It has: 1) range select knob 20 and 40 nm (not clickable.. yet) 2) target altitude readout at lower right 3) target disappears when range exceeds 43 nm 4) range ring values now are read from instrumentation/radar/range 5) instrumentation/radar/range is preset in the *-set.xml file to 40 nm The next step would be a clickable range selection. The problem here is that the instrument currently displays the "blip" only if the target's range is less then 43 nm. If the range scale is decreased to 20 nm, then the "blip" will show past the edges of the instrument. I might need to make another instrument for the 20 nm scale to make that work.
2004-02-27 10:22:23 +00:00
<layer>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
<name>target1 - range 40</name>
David Culp: The radar instrument uses the above three items, and applies a scale factor to the x-shift and y-shift in order to match the instrument's scale. Changing the display scale can be done entirely in the XML code for the instrument. Right now it's set up only to display a 40 mile scale. The radar is an AWACS view, which is not very realistic, but it is useful and demonstrates the technology. With just a little more work I can get a HUD marker. All I need to do there is make a bank angle adjustment to the current values. This works great with one target. For two or more targets the radar instrument will have to know the numbering of the aircraft model properties. This isn't implemented yet. David Culp: I couldn't stop. Here's a better radar instrument. It has: 1) range select knob 20 and 40 nm (not clickable.. yet) 2) target altitude readout at lower right 3) target disappears when range exceeds 43 nm 4) range ring values now are read from instrumentation/radar/range 5) instrumentation/radar/range is preset in the *-set.xml file to 40 nm The next step would be a clickable range selection. The problem here is that the instrument currently displays the "blip" only if the target's range is less then 43 nm. If the range scale is decreased to 20 nm, then the "blip" will show past the edges of the instrument. I might need to make another instrument for the 20 nm scale to make that work.
2004-02-27 10:22:23 +00:00
<w>8</w>
<h>17</h>
<condition>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
<and>
Okay, maybe it was a good idea to assume that not all targets are target[0].
2004-06-11 17:19:59 +00:00
<equals>
<property>ai/models/aircraft[1]/radar/in-range</property>
<value>true</value>
</equals>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
<equals>
<property>/instrumentation/radar/range</property>
<value>40</value>
</equals>
</and>
David Culp: The radar instrument uses the above three items, and applies a scale factor to the x-shift and y-shift in order to match the instrument's scale. Changing the display scale can be done entirely in the XML code for the instrument. Right now it's set up only to display a 40 mile scale. The radar is an AWACS view, which is not very realistic, but it is useful and demonstrates the technology. With just a little more work I can get a HUD marker. All I need to do there is make a bank angle adjustment to the current values. This works great with one target. For two or more targets the radar instrument will have to know the numbering of the aircraft model properties. This isn't implemented yet. David Culp: I couldn't stop. Here's a better radar instrument. It has: 1) range select knob 20 and 40 nm (not clickable.. yet) 2) target altitude readout at lower right 3) target disappears when range exceeds 43 nm 4) range ring values now are read from instrumentation/radar/range 5) instrumentation/radar/range is preset in the *-set.xml file to 40 nm The next step would be a clickable range selection. The problem here is that the instrument currently displays the "blip" only if the target's range is less then 43 nm. If the range scale is decreased to 20 nm, then the "blip" will show past the edges of the instrument. I might need to make another instrument for the 20 nm scale to make that work.
2004-02-27 10:22:23 +00:00
</condition>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0429687</x1>
<y1>0.8320312</y1>
<x2>0.0703125</x2>
<y2>0.8945312</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<property>ai/models/aircraft[1]/radar/x-shift</property>
<scale>2.55</scale>
</transformation>
<transformation>
<type>y-shift</type>
<property>ai/models/aircraft[1]/radar/y-shift</property>
<scale>2.55</scale>
</transformation>
<transformation>
<type>rotation</type>
<property>ai/models/aircraft[1]/radar/rotation</property>
</transformation>
</transformations>
</layer>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
<layer>
<name>target1 - range 20</name>
<w>8</w>
<h>17</h>
<condition>
<and>
Okay, maybe it was a good idea to assume that not all targets are target[0].
2004-06-11 17:19:59 +00:00
<equals>
<property>ai/models/aircraft[1]/radar/in-range</property>
<value>true</value>
</equals>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
<equals>
<property>/instrumentation/radar/range</property>
<value>20</value>
</equals>
</and>
</condition>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0429687</x1>
<y1>0.8320312</y1>
<x2>0.0703125</x2>
<y2>0.8945312</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<property>ai/models/aircraft[1]/radar/x-shift</property>
<scale>5.1</scale>
</transformation>
<transformation>
<type>y-shift</type>
<property>ai/models/aircraft[1]/radar/y-shift</property>
<scale>5.1</scale>
</transformation>
<transformation>
<type>rotation</type>
<property>ai/models/aircraft[1]/radar/rotation</property>
</transformation>
</transformations>
</layer>
David Culp: Here's some new AI stuff. 1) AI objects must now be defined in a scenario file, not in preferences.xml or a *-set file. (Of course this doesn't prevent objects from being created dynamically, as with Durk's traffic manager). 2) A new demo_scenario file is attached. It creates 3 aircraft, a sailboat, and a thunderstorm. 3) Objects without flightplans live forever. 4) FGAIShip::ProcessFlightplan() is not yet implemented. 5) preferences.xml should now define only <enabled> and <scenario>
2004-05-29 11:41:20 +00:00
<layer>
<name>target2 - range 40</name>
<w>8</w>
<h>17</h>
<condition>
<and>
Okay, maybe it was a good idea to assume that not all targets are target[0].
2004-06-11 17:19:59 +00:00
<equals>
<property>ai/models/aircraft[2]/radar/in-range</property>
<value>true</value>
</equals>
David Culp: Here's some new AI stuff. 1) AI objects must now be defined in a scenario file, not in preferences.xml or a *-set file. (Of course this doesn't prevent objects from being created dynamically, as with Durk's traffic manager). 2) A new demo_scenario file is attached. It creates 3 aircraft, a sailboat, and a thunderstorm. 3) Objects without flightplans live forever. 4) FGAIShip::ProcessFlightplan() is not yet implemented. 5) preferences.xml should now define only <enabled> and <scenario>
2004-05-29 11:41:20 +00:00
<equals>
<property>/instrumentation/radar/range</property>
<value>40</value>
</equals>
</and>
</condition>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0429687</x1>
<y1>0.8320312</y1>
<x2>0.0703125</x2>
<y2>0.8945312</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<property>ai/models/aircraft[2]/radar/x-shift</property>
<scale>2.55</scale>
</transformation>
<transformation>
<type>y-shift</type>
<property>ai/models/aircraft[2]/radar/y-shift</property>
<scale>2.55</scale>
</transformation>
<transformation>
<type>rotation</type>
<property>ai/models/aircraft[2]/radar/rotation</property>
</transformation>
</transformations>
</layer>
<layer>
<name>target2 - range 20</name>
<w>8</w>
<h>17</h>
<condition>
<and>
Okay, maybe it was a good idea to assume that not all targets are target[0].
2004-06-11 17:19:59 +00:00
<equals>
<property>ai/models/aircraft[2]/radar/in-range</property>
<value>true</value>
</equals>
David Culp: Here's some new AI stuff. 1) AI objects must now be defined in a scenario file, not in preferences.xml or a *-set file. (Of course this doesn't prevent objects from being created dynamically, as with Durk's traffic manager). 2) A new demo_scenario file is attached. It creates 3 aircraft, a sailboat, and a thunderstorm. 3) Objects without flightplans live forever. 4) FGAIShip::ProcessFlightplan() is not yet implemented. 5) preferences.xml should now define only <enabled> and <scenario>
2004-05-29 11:41:20 +00:00
<equals>
<property>/instrumentation/radar/range</property>
<value>20</value>
</equals>
</and>
</condition>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0429687</x1>
<y1>0.8320312</y1>
<x2>0.0703125</x2>
<y2>0.8945312</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<property>ai/models/aircraft[2]/radar/x-shift</property>
<scale>5.1</scale>
</transformation>
<transformation>
<type>y-shift</type>
<property>ai/models/aircraft[2]/radar/y-shift</property>
<scale>5.1</scale>
</transformation>
<transformation>
<type>rotation</type>
<property>ai/models/aircraft[2]/radar/rotation</property>
</transformation>
</transformations>
</layer>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
David Culp: The radar instrument uses the above three items, and applies a scale factor to the x-shift and y-shift in order to match the instrument's scale. Changing the display scale can be done entirely in the XML code for the instrument. Right now it's set up only to display a 40 mile scale. The radar is an AWACS view, which is not very realistic, but it is useful and demonstrates the technology. With just a little more work I can get a HUD marker. All I need to do there is make a bank angle adjustment to the current values. This works great with one target. For two or more targets the radar instrument will have to know the numbering of the aircraft model properties. This isn't implemented yet. David Culp: I couldn't stop. Here's a better radar instrument. It has: 1) range select knob 20 and 40 nm (not clickable.. yet) 2) target altitude readout at lower right 3) target disappears when range exceeds 43 nm 4) range ring values now are read from instrumentation/radar/range 5) instrumentation/radar/range is preset in the *-set.xml file to 40 nm The next step would be a clickable range selection. The problem here is that the instrument currently displays the "blip" only if the target's range is less then 43 nm. If the range scale is decreased to 20 nm, then the "blip" will show past the edges of the instrument. I might need to make another instrument for the 20 nm scale to make that work.
2004-02-27 10:22:23 +00:00
<layer>
<name>frame</name>
<w>256</w>
<h>256</h>
<texture>
<path>Aircraft/Instruments/Textures/radar_frame.rgb</path>
<x1>0</x1>
<y1>0</y1>
<x2>1</x2>
<y2>1</y2>
</texture>
</layer>
<layer>
<name>range knob</name>
<condition>
<equals>
<property>instrumentation/radar/range</property>
<value>20</value>
</equals>
</condition>
<w>22</w>
<h>22</h>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0273437</x1>
<y1>0.9101562</y1>
<x2>0.0898437</x2>
<y2>0.9765662</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<offset>-108</offset>
</transformation>
<transformation>
<type>y-shift</type>
<offset>-112</offset>
</transformation>
<transformation>
<type>rotation</type>
<offset>-45</offset>
</transformation>
</transformations>
</layer>
<layer>
<name>range knob</name>
<condition>
<equals>
<property>instrumentation/radar/range</property>
<value>40</value>
</equals>
</condition>
<w>22</w>
<h>22</h>
<texture>
<path>Aircraft/Instruments/Textures/radar_misc.rgb</path>
<x1>0.0273437</x1>
<y1>0.9101562</y1>
<x2>0.0898437</x2>
<y2>0.9765662</y2>
</texture>
<transformations>
<transformation>
<type>x-shift</type>
<offset>-108</offset>
</transformation>
<transformation>
<type>y-shift</type>
<offset>-112</offset>
</transformation>
<transformation>
<type>rotation</type>
<offset>40</offset>
</transformation>
</transformations>
</layer>
<layer>
<name>altitude</name>
<type>text</type>
<font>led</font>
<point-size>6</point-size>
<color>
<red>0.96</red>
<green>1.0</green>
<blue>0.96</blue>
</color>
<chunks>
<chunk>
<type>number-value</type>
Some updated files per request of David Culp.
2004-07-03 11:13:09 +00:00
<property>ai/models/aircraft[0]/position/altitude-ft</property>
David Culp: The radar instrument uses the above three items, and applies a scale factor to the x-shift and y-shift in order to match the instrument's scale. Changing the display scale can be done entirely in the XML code for the instrument. Right now it's set up only to display a 40 mile scale. The radar is an AWACS view, which is not very realistic, but it is useful and demonstrates the technology. With just a little more work I can get a HUD marker. All I need to do there is make a bank angle adjustment to the current values. This works great with one target. For two or more targets the radar instrument will have to know the numbering of the aircraft model properties. This isn't implemented yet. David Culp: I couldn't stop. Here's a better radar instrument. It has: 1) range select knob 20 and 40 nm (not clickable.. yet) 2) target altitude readout at lower right 3) target disappears when range exceeds 43 nm 4) range ring values now are read from instrumentation/radar/range 5) instrumentation/radar/range is preset in the *-set.xml file to 40 nm The next step would be a clickable range selection. The problem here is that the instrument currently displays the "blip" only if the target's range is less then 43 nm. If the range scale is decreased to 20 nm, then the "blip" will show past the edges of the instrument. I might need to make another instrument for the 20 nm scale to make that work.
2004-02-27 10:22:23 +00:00
<scale>0.001</scale>
<format>%2.1f</format>
</chunk>
</chunks>
<transformations>
<transformation>
<type>x-shift</type>
<offset>85</offset>
</transformation>
<transformation>
<type>y-shift</type>
<offset>-121</offset>
</transformation>
</transformations>
</layer>
<layer>
<name>outer range ring</name>
<type>text</type>
<font>led</font>
<point-size>6</point-size>
<color>
<red>0.96</red>
<green>1.0</green>
<blue>0.96</blue>
</color>
<chunks>
<chunk>
<type>number-value</type>
<property>instrumentation/radar/range</property>
<format>%2.0f</format>
</chunk>
</chunks>
<transformations>
<transformation>
<type>x-shift</type>
<offset>-90</offset>
</transformation>
<transformation>
<type>y-shift</type>
<offset>66</offset>
</transformation>
</transformations>
</layer>
<layer>
<name>inner range ring</name>
<type>text</type>
<font>led</font>
<point-size>6</point-size>
<color>
<red>0.96</red>
<green>1.0</green>
<blue>0.96</blue>
</color>
<chunks>
<chunk>
<type>number-value</type>
<property>instrumentation/radar/range</property>
<scale>0.5</scale>
<format>%2.0f</format>
</chunk>
</chunks>
<transformations>
<transformation>
<type>x-shift</type>
<offset>-50</offset>
</transformation>
<transformation>
<type>y-shift</type>
<offset>32</offset>
</transformation>
</transformations>
</layer>
</layers>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
<actions>
<action>
<name>set range 40</name>
<button>0</button>
<x>-120</x>
<y>-120</y>
<w>35</w>
<h>35</h>
<condition>
<equals>
<property>/instrumentation/radar/range</property>
<value>20</value>
</equals>
</condition>
<binding>
<command>property-assign</command>
<property>/instrumentation/radar/range</property>
<value>40</value>
</binding>
</action>
<action>
<name>set range 20</name>
<button>0</button>
<x>-120</x>
<y>-120</y>
<w>35</w>
<h>35</h>
<condition>
<equals>
<property>/instrumentation/radar/range</property>
<value>40</value>
</equals>
</condition>
<binding>
<command>property-assign</command>
<property>/instrumentation/radar/range</property>
<value>20</value>
</binding>
</action>
David Culp: Add a "minimize" button to the radar screen. It will default maximized.
2004-03-20 22:34:30 +00:00
<action>
<name>minimize</name>
<button>0</button>
<x>112</x>
<y>112</y>
<w>16</w>
<h>16</h>
<binding>
<command>property-assign</command>
<property>/instrumentation/radar/minimized</property>
<value>true</value>
</binding>
</action>
David Culp: Add clickable range selection for the radar and wxradar. Right now it is clickable only between 20 and 40 mile ranges, which should work for most uses.
2004-03-12 15:06:04 +00:00
</actions>
David Culp: The radar instrument uses the above three items, and applies a scale factor to the x-shift and y-shift in order to match the instrument's scale. Changing the display scale can be done entirely in the XML code for the instrument. Right now it's set up only to display a 40 mile scale. The radar is an AWACS view, which is not very realistic, but it is useful and demonstrates the technology. With just a little more work I can get a HUD marker. All I need to do there is make a bank angle adjustment to the current values. This works great with one target. For two or more targets the radar instrument will have to know the numbering of the aircraft model properties. This isn't implemented yet. David Culp: I couldn't stop. Here's a better radar instrument. It has: 1) range select knob 20 and 40 nm (not clickable.. yet) 2) target altitude readout at lower right 3) target disappears when range exceeds 43 nm 4) range ring values now are read from instrumentation/radar/range 5) instrumentation/radar/range is preset in the *-set.xml file to 40 nm The next step would be a clickable range selection. The problem here is that the instrument currently displays the "blip" only if the target's range is less then 43 nm. If the range scale is decreased to 20 nm, then the "blip" will show past the edges of the instrument. I might need to make another instrument for the 20 nm scale to make that work.
2004-02-27 10:22:23 +00:00
</PropertyList>
Copy permalink