Field(s)
Contains the counter how many units are currently alive
- -Field(s)
Contains the counter how many units are currently alive
- -Global RANGE
Don't only practice your art, but force your way into its secrets; art deserves that, for it and knowledge can raise man to the Divine. - Ludwig van Beethoven
++ +
The Range Concept
+ +The RANGE class enables a mission designer to easily set up practice ranges in DCS.
Don't only practice your art, but force your way into its secrets; art deserves that, for it and knowledge can raise man to the Divine. - Ludwig van Beethoven
++ +
The Range Concept
+ +The RANGE class enables a mission designer to easily set up practice ranges in DCS.
-LuaFormatter on
+A new RANGE object can be created with the RANGE.New(rangename) contructor. +The parameter rangename defines the name of the range. It has to be unique since this is also the name displayed in the radio menu.
+ +Generally, a range consists of strafe pits and bombing targets. For strafe pits the number of hits for each pass is counted and tabulated. +For bombing targets, the distance from the impact point of the bomb, rocket or missile to the closest range target is measured and tabulated. +Each player can display his best results via a function in the radio menu or see the best best results from all players.
+ +When all targets have been defined in the script, the range is started by the RANGE.Start() command.
+ +IMPORTANT
+ +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, +there should be an "On the Range" menu items in the "F10. Other..." menu.
+ +Strafe Pits
+ +Each strafe pit can consist of multiple targets. Often one finds two or three strafe targets next to each other.
+ +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. +
- 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. +
- 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! +
Another function to add a strafe pit is RANGE.AddStrafePitGroup(group, boxlength, boxwidth, heading, inverseheading, goodpass, foulline). Here, +the first parameter group is a MOOSE Wrapper.Group object and all units in this group define one strafe pit.
+ +Finally, a valid approach has to be performed below a certain maximum altitude. The default is 914 meters (3000 ft) AGL. This is a parameter valid for all +strafing pits of the range and can be adjusted by the RANGE.SetMaxStrafeAlt(maxalt) function.
+ +Bombing targets
+ +One ore multiple bombing targets can be added to the range by the RANGE.AddBombingTargets(targetnames, goodhitrange, randommove) 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 (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. + 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. +
Adding Groups
+ +Another possibility to add bombing targets is the RANGE.AddBombingTargetGroup(group, goodhitrange, randommove) function. Here the parameter group is a MOOSE Wrapper.Group object +and all units in this group are defined as bombing targets.
+ +Specifying Coordinates
+ +It is also possible to specify coordinates rather than unit or static objects as bombing target locations. This has the advantage, that even when the unit/static object is dead, the specified +coordinate will still be a valid impact point. This can be done via the RANGE.AddBombingTargetCoordinate(coord, name, goodhitrange) function.
+ +Fine Tuning
+ +Many range parameters have good default values. However, the mission designer can change these settings easily with the supplied user functions:
+ +-
+
- RANGE.SetMaxStrafeAlt() sets the max altitude for valid strafing runs. +
- RANGE.SetMessageTimeDuration() sets the duration how long (most) messages are displayed. +
- RANGE.SetDisplayedMaxPlayerResults() sets the number of results displayed. +
- RANGE.SetRangeRadius() defines the total range area. +
- RANGE.SetBombTargetSmokeColor() sets the color used to smoke bombing targets. +
- RANGE.SetStrafeTargetSmokeColor() sets the color used to smoke strafe targets. +
- RANGE.SetStrafePitSmokeColor() sets the color used to smoke strafe pit approach boxes. +
- RANGE.SetSmokeTimeDelay() sets the time delay between smoking bomb/rocket impact points after impact. +
- RANGE.TrackBombsON() or RANGE.TrackBombsOFF() can be used to enable/disable tracking and evaluating of all bomb types a player fires. +
- RANGE.TrackRocketsON() or RANGE.TrackRocketsOFF() can be used to enable/disable tracking and evaluating of all rocket types a player fires. +
- RANGE.TrackMissilesON() or RANGE.TrackMissilesOFF() can be used to enable/disable tracking and evaluating of all missile types a player fires. +
Radio Menu
+ +Each range gets a radio menu with various submenus where each player can adjust his individual settings or request information about the range or his scores.
+ +The main range menu can be found at "F10. Other..." --> "FX . On the Range..." --> "F1.
The range menu contains the following submenus:
+ +
-
+
- "F1. Statistics...": Range results of all players and personal stats. +
- "F2. Mark Targets": Mark range targets by smoke or flares. +
- "F3. My Settings" Personal settings. +
- "F4. Range Info": Information about the range, such as bearing and range. +
F1 Statistics
+ +
F2 Mark Targets
+ +
F3 My Settings
+ +
F4 Range Info
+ +
Voice Overs
+ +Voice over sound files can be downloaded from the Moose Discord. Check the pinned messages in the #func-range channel.
+ +Instructor radio will inform players when they enter or exit the range zone and provide the radio frequency of the range control for hit assessment. +This can be enabled via the RANGE.SetInstructorRadio(frequency) functions, where frequency is the AM frequency in MHz.
+ +The range control can be enabled via the RANGE.SetRangeControl(frequency) functions, where frequency is the AM frequency in MHz.
+ +By default, the sound files are placed in the "Range Soundfiles/" folder inside the mission (.miz) file. Another folder can be specified via the RANGE.SetSoundfilesPath(path) function.
+ +Persistence
+ +To automatically save bombing results to disk, use the RANGE.SetAutosave() function. Bombing results will be saved as csv file in your "Saved Games\DCS.openbeta\Logs" directory. +Each range has a separate file, which is named "RANGE-<RangeName>_BombingResults.csv".
+ +The next time you start the mission, these results are also automatically loaded.
+ +Strafing results are currently not saved.
+ +Examples
+ +Goldwater Range
+ +This example shows hot to set up the Barry M. Goldwater range. +It consists of two strafe pits each has two targets plus three bombing targets.
+ + -- Strafe pits. Each pit can consist of multiple targets. Here we have two pits and each of the pits has two targets.
+ -- These are names of the corresponding units defined in the ME.
+ local strafepit_left={"GWR Strafe Pit Left 1", "GWR Strafe Pit Left 2"}
+ local strafepit_right={"GWR Strafe Pit Right 1", "GWR Strafe Pit Right 2"}
+
+ -- Table of bombing target names. Again these are the names of the corresponding units as defined in the ME.
+ local bombtargets={"GWR Bomb Target Circle Left", "GWR Bomb Target Circle Right", "GWR Bomb Target Hard"}
+
+ -- Create a range object.
+ GoldwaterRange=RANGE:New("Goldwater Range")
+
+ -- Distance between strafe target and foul line. You have to specify the names of the unit or static objects.
+ -- Note that this could also be done manually by simply measuring the distance between the target and the foul line in the ME.
+ GoldwaterRange:GetFoullineDistance("GWR Strafe Pit Left 1", "GWR Foul Line Left")
+
+ -- Add strafe pits. Each pit (left and right) consists of two targets. Where "nil" is used as input, the default value is used.
+ GoldwaterRange:AddStrafePit(strafepit_left, 3000, 300, nil, true, 30, 500)
+ GoldwaterRange:AddStrafePit(strafepit_right, nil, nil, nil, true, nil, 500)
+
+ -- Add bombing targets. A good hit is if the bomb falls less then 50 m from the target.
+ GoldwaterRange:AddBombingTargets(bombtargets, 50)
+
+ -- Start range.
+ GoldwaterRange:Start()
+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
+ C:\Users\<yourname>\Saved Games\DCS\Logs\dcs.log
+All output concerning the RANGE class should have the string "RANGE" in the corresponding line.
+ +The verbosity of the output can be increased by adding the following lines to your script:
+ + BASE:TraceOnOff(true)
+ BASE:TraceLevel(1)
+ BASE:TraceClass("RANGE")
+To get even more output you can increase the trace level to 2 or even 3, c.f. BASE for more details.
+ +The function RANGE.DebugON() can be used to send messages on screen. It also smokes all defined strafe and bombing targets, the strafe pit approach boxes and the range zone.
+ +Note that it can happen that the RANGE radio menu is not shown. Check that the range object is defined as a global variable rather than a local one. +The could avoid the lua garbage collection to accidentally/falsely deallocate the RANGE objects.
+| Fields and Methods inherited from FSM | +Description | +
|---|---|
| + |
+ Adds an End state. + |
+
| + |
+ Set the default Process template with key ProcessName providing the ProcessClass and the process object when it is assigned to a Wrapper.Controllable by the task. + |
+
| + |
+ Adds a score for the FSM to be achieved. + |
+
| + |
+ Adds a score for the FSM_PROCESS to be achieved. + |
+
| + |
+ Add a new transition rule to the FSM. + |
+
| + |
+ Call scheduler. + |
+
| + |
+ Name of the class. + |
+
| + | + + | +
| + |
+ Get current state. + |
+
| + |
+ Returns the End states. + |
+
| + | + + | +
| + |
+ Returns a table of the SubFSM rules defined within the FSM. + |
+
| + |
+ Returns a table with the scores defined. + |
+
| + |
+ Returns the start state of the FSM. + |
+
| + |
+ Get current state. + |
+
| + |
+ Returns a table with the Subs defined. + |
+
| + |
+ Returns a table of the transition rules defined within the FSM. + |
+
| + |
+ Check if FSM is in state. + |
+
| + |
+ Load call backs. + |
+
| + |
+ Creates a new FSM object. + |
+
| + |
+ Scores. + |
+
| + | + + | +
| + |
+ Sets the start state of the FSM. + |
+
| + | + + | +
| + | + + | +
| + | + + | +
| + | + + | +
| + | + + | +
| + | + + | +
| + |
+ Add to map. + |
+
| + |
+ Call handler. + |
+
| + |
+ Create transition. + |
+
| + |
+ Delayed transition. + |
+
| + |
+ Event map. + |
+
| + |
+ Go sub. + |
+
| + |
+ Handler. + |
+
| + |
+ Is end state. + |
+
| + |
+ Sub maps. + |
+
| + |
+ Check if can do an event. + |
+
| + |
+ Check if cannot do an event. + |
+
| + |
+ Current state name. + |
+
| + | + + | +
| + |
+ Check if FSM is in state. + |
+
| + |
+ Options. + |
+
| + |
+ Subs. + |
+
Set case to that of lead.
+Set case of f
Set time stamp.
-table of CSAR unit names
-table of CSAR unit names
-table of CSAR unit names
-Name of the class.
+use as counter
+ +holds #CTLD_ENGINEERING objects
+Beacons
+tables
+noob catch
+time to repair a unit/group
Name of the class.
+use as counter
+ +holds #CTLD_ENGINEERING objects
+Beacons
+tables
+noob catch
+time to repair a unit/group
Name of the class.
+use as counter
+ +holds #CTLD_ENGINEERING objects
+Beacons
+tables
+noob catch
+time to repair a unit/group