- #number
+
DETECTION_BASE.RefreshTimeInterval
@@ -23610,7 +23610,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
-Bomb, rocket and missile impact points can be marked by smoke.
Direct hits on targets can trigger flares.
Smoke and flare colors can be adjusted for each player via radio menu.
- Range information and weather at the range can be obtained via radio menu.
+ Range information and weather report at the range can be reported via radio menu.
Persistence: Bombing range results can be saved to disk and loaded the next time the mission is started.
Range control voice overs (>40) for hit assessment.
@@ -1599,7 +1599,7 @@ Each player can display his best results via a function in the radio menu or see
...".
-
+
+
- #number
+
DETECTION_BASE.RefreshTimeInterval
@@ -25356,7 +25356,7 @@ zones that reflect cloudy areas where detected units may not be so easily visual
-
-
-
- #number
+
DETECTION_BASE.RefreshTimeInterval
diff --git a/Documentation/Functional.Mantis.html b/Documentation/Functional.Mantis.html
index 3e282e831..5ac6964ed 100644
--- a/Documentation/Functional.Mantis.html
+++ b/Documentation/Functional.Mantis.html
@@ -2899,17 +2899,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
-
-The #DETECTION_AREAS object for AWACS
-
-
@@ -6564,17 +6553,6 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`
-
-
-MANTIS.AWACS_Prefix
-
-
-
The #DETECTION_AREAS object for AWACS
-
-
diff --git a/Documentation/Functional.Range.html b/Documentation/Functional.Range.html
index 1129a269c..5c100056d 100644
--- a/Documentation/Functional.Range.html
+++ b/Documentation/Functional.Range.html
@@ -1515,7 +1515,7 @@ by a script by SNAFU s
-
-
-MANTIS.AWACS_Prefix
-
-
-
Due to a DCS bug, it is not possible to directly monitor when a player enters a plane. So in a mission with client slots, it is vital that a player first enters as spectator or hits ESC twice and after that jumps into the slot of his aircraft! -If that is not done, the script is not started correctly. This can be checked by looking at the radio menus. If the mission was entered correctly, +If that is not done, the script is not started correctly. This can be checked by looking at the radio menues. If the mission was entered correctly, there should be an "On the Range" menu items in the "F10. Other..." menu.
Strafe Pits
@@ -1609,12 +1609,12 @@ there should be an "On the Range" menu items in the "F10. Other..." menu.A strafe pit can be added to the range by the RANGE.AddStrafePit(targetnames, boxlength, boxwidth, heading, inverseheading, goodpass, foulline) function.
-
-
- The first parameter targetnames defines the target or targets. This can be a single item or a Table with the name(s) of Wrapper.Unit or Static objects defined in the mission editor. +
- The first parameter targetnames defines the target or targets. This has to be given as a lua table which contains the names of Wrapper.Unit or Static objects defined in the mission editor.
- In order to perform a valid pass on the strafe pit, the pilot has to begin his run from the correct direction. Therefore, an "approach box" is defined in front - of the strafe targets. The parameters boxlength and boxwidth define the size of the box in meters, while the heading parameter defines the heading of the box FROM the target. - For example, if heading 120 is set, the approach box will start FROM the target and extend outwards on heading 120. A strafe run approach must then be flown apx. heading 300 TOWARDS the target. - If the parameter heading is passed as nil, the heading is automatically taken from the heading set in the ME for the first target unit. -
- The parameter inverseheading turns the heading around by 180 degrees. This is useful when the default heading of strafe target units point in the wrong/opposite direction. + of the strafe targets. The parameters boxlength and boxwidth define the size of the box while the parameter heading defines its direction. + If the parameter heading is passed as nil, the heading is automatically taken from the heading of the first target unit as defined in the ME. + The parameter inverseheading turns the heading around by 180 degrees. This is sometimes useful, since the default heading of strafe target units point in the + wrong/opposite direction.
- The parameter goodpass defines the number of hits a pilot has to achieve during a run to be judged as a "good" pass.
- The last parameter foulline sets the distance from the pit targets to the foul line. Hit from closer than this line are not counted!
-
-
- The first parameter targetnames defines the target or targets. This can be a single item or a Table with the name(s) of Wrapper.Unit or Static objects defined in the mission editor. -
- The (optional) parameter goodhitrange specifies the radius in metres around the target within which a bomb/rocket hit is considered to be "good". -
- If final (optional) parameter randommove can be enabled to create moving targets. If this parameter is set to true, the units of this bombing target will randomly move within the range zone. +
- The first parameter targetnames has to be a lua table, which contains the names of Wrapper.Unit and/or Static objects defined in the mission editor. + Note that the Range logic automatically determines, if a name belongs to a Wrapper.Unit or Static object now. +
- The (optional) parameter goodhitrange specifies the radius around the target. If a bomb or rocket falls at a distance smaller than this number, the hit is considered to be "good". +
- If final (optional) parameter "randommove" can be enabled to create moving targets. If this parameter is set to true, the units of this bombing target will randomly move within the range zone. Note that there might be quirks since DCS units can get stuck in buildings etc. So it might be safer to manually define a route for the units in the mission editor if moving targets are desired.
The range menu contains the following submenus:
+The range menu contains the following submenues:
The 476th - Air Weapons Range Objects mod is (implicitly) used in this example.
+Debugging
In case you have problems, it is always a good idea to have a look at your DCS log file. You find it in your "Saved Games" folder, so for example in
@@ -1774,6 +1776,158 @@ It consists of two strafe pits each has two targets plus three bombing targets.< The could avoid the lua garbage collection to accidentally/falsely deallocate the RANGE objects. + + +