From aacf7ee1d729b207e9109b21167c6c77b0421dd0 Mon Sep 17 00:00:00 2001
From: Applevangelist The Defender Default Settings over all Squadrons.
The Defender Default Settings over all Squadrons.
- - - -The Defender Default Settings over all Squadrons.
- - - -The Defender Default Settings over all Squadrons.
- - - -meter
-kph
-meter
-kph
-meter
-kph
-meter
-kph
-This table contains the targets detected during patrol.
-This table contains the targets detected during patrol.
-This table contains the targets detected during patrol.
-This table contains the targets detected during patrol.
-self.CargoObject:Destroy()
- -self.CargoObject:Destroy()
- -Set cargo object.
-Set cargo object.
-The text will reflect the temperature like this:
A text containing a pressure will look like this:
Temperature: %n.d °C Temperature: %n.d °F
+ Temperature: %n.d °C Temperature: %n.d °F
The text will reflect the wind like this:
A text containing a pressure will look like this:
Wind: %n ° at n.d mps Wind: %n ° at n.d kps
+ Wind: %n ° at n.d mps Wind: %n ° at n.d kps
the y coordinate in meters.
+the y coordinate in meters.
+ + + +The text will reflect the temperature like this:
A text containing a pressure will look like this:
Temperature: %n.d °C Temperature: %n.d °F
+ Temperature: %n.d °C Temperature: %n.d °F
The text will reflect the wind like this:
A text containing a pressure will look like this:
Wind: %n ° at n.d mps Wind: %n ° at n.d kps
+ Wind: %n ° at n.d mps Wind: %n ° at n.d kps
the y coordinate in meters.
+ + + +SPAWN:_TranslateRotate(SpawnIndex, SpawnRootX, SpawnRootY, SpawnX, SpawnY, SpawnAngle)
The internal counter of the amount of spawning the has happened since SpawnStart.
-When the first Spawn executes, all the Groups need to be made visible before start.
+Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.
When working in UnControlled mode, all planes are Spawned in UnControlled mode before the scheduler starts.
+ + + +The internal counter of the amount of spawning the has happened since SpawnStart.
-Flag that indicates if all the Groups of the SpawnGroup need to be visible when Spawned.
@@ -9237,6 +9265,28 @@ This is needed to ensure that Re-SPAWNing only is done for landed AIR Groups. When working in UnControlled mode, all planes are Spawned in UnControlled mode before the scheduler starts. + + + +Upon a visual detection, the higher the unit is during the detecting process, the more likely the detected unit is to be detected properly. A detection at a 90% alpha angle is the most optimal, a detection at 10% is less and a detection at 0% is less likely to be correct.
-A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
+A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
For example, if a alpha angle probability factor of 0.7 is given, the extrapolated probabilities of the different angles would look like: -0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%
+0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100% -Use the method Functional.Detection#DETECTION_BASE.SetAlphaAngleProbability() to set the probability factor if 0°.
+Use the method Functional.Detection#DETECTION_BASE.SetAlphaAngleProbability() to set the probability factor if 0°.
A detection at a 90% alpha angle is the most optimal, a detection at 10% is less and a detection at 0% is less likely to be correct.
-A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
+A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
For example, if a alpha angle probability factor of 0.7 is given, the extrapolated probabilities of the different angles would look like: -0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%
+0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%A detection at a 90% alpha angle is the most optimal, a detection at 10% is less and a detection at 0% is less likely to be correct.
-A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
+A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
For example, if a alpha angle probability factor of 0.7 is given, the extrapolated probabilities of the different angles would look like: -0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%
+0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%A detection at a 90% alpha angle is the most optimal, a detection at 10% is less and a detection at 0% is less likely to be correct.
-A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
+A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
For example, if a alpha angle probability factor of 0.7 is given, the extrapolated probabilities of the different angles would look like: -0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%
+0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%A detection at a 90% alpha angle is the most optimal, a detection at 10% is less and a detection at 0% is less likely to be correct.
-A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
+A probability factor between 0 and 1 can be given, that will model a progressive extrapolated probability if the target would be detected at a 0° angle.
For example, if a alpha angle probability factor of 0.7 is given, the extrapolated probabilities of the different angles would look like: -0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%
+0°: 70%, 10°: 75,21%, 20°: 80,26%, 30°: 85%, 40°: 89,28%, 50°: 92,98%, 60°: 95,98%, 70°: 98,19%, 80°: 99,54%, 90°: 100%Notching heading right, i.e. missile heading +90°.
+Notching heading right, i.e. missile heading +90°.
Notching heading left, i.e. missile heading -90°.
+Notching heading left, i.e. missile heading -90°.
switch alarm state RED
-switch alarm state RED
-Contains the counter how many units are currently alive
+ +Contains the counter how many units are currently alive
+ +RAT:_TranslateRotate(SpawnIndex, SpawnRootX, SpawnRootY, SpawnX, SpawnY, SpawnAngle)
The same holds true after the recovery window closes. The carrier will head back to the place where he left its assigned route and resume the path to the next waypoint defined in the mission editor.
-Note that the carrier will only head into the wind, if the wind direction is different by more than 5° from the current heading of the carrier (the angled runway, if any, fis taken into account here).
+Note that the carrier will only head into the wind, if the wind direction is different by more than 5° from the current heading of the carrier (the angled runway, if any, fis taken into account here).
The graph displays the lineup error (LUE) as a function of the distance to the carrier.
-The pilot approaches the carrier from the port side, LUE>0°, at a distance of ~1 NM. -At the beginning of the groove (X), he significantly overshoots to the starboard side (LUE<5°). +
The pilot approaches the carrier from the port side, LUE>0°, at a distance of ~1 NM. +At the beginning of the groove (X), he significantly overshoots to the starboard side (LUE<5°). In the middle (IM), he performs good corrections and smoothly reduces the lineup error. -Finally, at a distance of ~0.3 NM (IC) he has corrected his lineup with the runway to a reasonable level, |LUE|<0.5°.
+Finally, at a distance of ~0.3 NM (IC) he has corrected his lineup with the runway to a reasonable level, |LUE|<0.5°.The graph displays the glideslope error (GSE) as a function of the distance to the carrier.
In this case the pilot already enters the groove (X) below the optimal glideslope. He is not able to correct his height in the IM part and -stays significantly too low. In close, he performs a harsh correction to gain altitude and ends up even slightly too high (GSE>0.5°). +stays significantly too low. In close, he performs a harsh correction to gain altitude and ends up even slightly too high (GSE>0.5°). At his point further corrections are necessary.
Relative Marshal radial in degrees for Case II/III recoveries. Default 30°.
+Relative Marshal radial in degrees for Case II/III recoveries. Default 30°.
Set case to that of lead.
+Set current case.
Also decrease flag for section members of flight.
+ +Data table at each position in the groove. Elements are of type AIRBOSS.GrooveData.
+Set section lead of player flight.
-Set new time stamp.
+Set magnetic runway headings as depicted on the runway, e.g. "13" for 130° or "25L" for the left runway with magnetic heading 250°.
+Set magnetic runway headings as depicted on the runway, e.g. "13" for 130° or "25L" for the left runway with magnetic heading 250°.
0° (East).
+0° (East).
+2° (East).
++2° (East).
+12° (East).
++12° (East).
-10° (West).
+-10° (West).
+2° (East).
++2° (East).
+5° (East).
++5° (East).
-10° (West).
+-10° (West).
Runway magnetic heading divided by ten (and rounded). Eg, "13" for 130°.
+Runway magnetic heading divided by ten (and rounded). Eg, "13" for 130°.
To get true from magnetic heading one has to add easterly or substract westerly variation, e.g
-A magnetic heading of 180° corresponds to a true heading of
+A magnetic heading of 180° corresponds to a true heading of
Likewise, to convert true into magnetic heading, one has to substract easterly and add westerly variation.
@@ -6021,7 +6021,7 @@ Note that the dew point is only an artificial information as DCS does not have aSet magnetic runway headings as depicted on the runway, e.g. "13" for 130° or "25L" for the left runway with magnetic heading 250°.
+Set magnetic runway headings as depicted on the runway, e.g. "13" for 130° or "25L" for the left runway with magnetic heading 250°.
Magnetic headings. Inverse (-180°) headings are added automatically. You only need to specify one heading per runway direction. "L"eft and "R" right can also be appended.
+Magnetic headings. Inverse (-180°) headings are added automatically. You only need to specify one heading per runway direction. "L"eft and "R" right can also be appended.
0° (East).
+0° (East).
+2° (East).
++2° (East).
+12° (East).
++12° (East).
-10° (West).
+-10° (West).
+2° (East).
++2° (East).
+5° (East).
++5° (East).
-10° (West).
+-10° (West).
contain a table for each SAR with all units he has with the original names
- - - -contain a table for each SAR with all units he has with the original names
- - - -contain a table for each SAR with all units he has with the original names
- - - -Name of the class.
+ + + +tables
+radio beacons
+Name of the class.
+tables
+radio beacons
+Name of the class.
+tables
+radio beacons
+set to false to suppress flash messages
+set to false to suppress flash messages
+set to false to suppress flash messages
+set to false to suppress flash messages
+Runway ID: heading 070° ==> idx="07".
+Runway ID: heading 070° ==> idx="07".
Runway ID: heading 070° ==> idx="07".
+Runway ID: heading 070° ==> idx="07".
diff --git a/Documentation/Wrapper.Marker.html b/Documentation/Wrapper.Marker.html index 0f701b3c3..0ced76afd 100644 --- a/Documentation/Wrapper.Marker.html +++ b/Documentation/Wrapper.Marker.html @@ -2899,28 +2899,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defauCoordinate of the mark.
- - - -Coordinate of the mark.
-Coordinate of the mark.
-