weyne/MOOSE_DOCS
1
0
Fork 0
mirror of https://github.com/FlightControl-Master/MOOSE_DOCS.git synced 2025-08-15 10:37:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Auto commit by GitHub Actions Workflow

Browse Source
This commit is contained in:
MooseBotter
2025-05-12 15:53:12 +00:00
parent 889b4574c8
commit 6eaf3f4a76
24 changed files with 575 additions and 609 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
Documentation/Functional.Mantis.html
View File

@@ -1752,10 +1752,9 @@
<ul>
<li>Controls a network of SAM sites. Uses detection to switch on the SAM site closest to the enemy.</li>
<li><strong>Automatic mode</strong> (default since 0.8) will set-up your SAM site network automatically for you</li>
<li><strong>Classic mode</strong> behaves like before</li>
<li>Leverage evasiveness from SEAD, leverage attack range setting</li>
<li>Automatic setup of SHORAD based on groups of the class "short-range"</li>
<li><strong>Automatic mode</strong> (default) will set-up your SAM site network automatically for you.</li>
<li>Leverage evasiveness from SEAD, leverage attack range setting.</li>
<li>Automatic setup of SHORAD based on groups of the class "short-range".</li>
</ul>
<h1>0. Base considerations and naming conventions</h1>
@@ -1819,7 +1818,8 @@ This is case-sensitive, so "sa-11" is not equal to "SA-11" is not equal to "Sa-1
<p>Set up your SAM sites in the mission editor. Name the groups using a systematic approach like above.
Set up your EWR system in the mission editor. Name the groups using a systematic approach like above. Can be e.g. AWACS or a combination of AWACS and Search Radars like e.g. EWR 1L13 etc.
Search Radars usually have "SR" or "STR" in their names. Use the encyclopedia in the mission editor to inform yourself.
Set up your SHORAD systems. They need to be <strong>close</strong> to (i.e. around) the SAM sites to be effective. Use <strong>one</strong> group per SAM location. SA-15 TOR systems offer a good missile defense.</p>
Set up your SHORAD systems. They need to be <strong>close</strong> to (i.e. around) the SAM sites to be effective. Use <em>*one unit *</em> per group (multiple groups) for the SAM location.
Else, evasive manoevers might club up all defenders in one place. Red SA-15 TOR systems offer a good missile defense.</p>
<p>[optional] Set up your HQ. Can be any group, e.g. a command vehicle.</p>
@@ -1877,7 +1877,7 @@ in the mission editor are absolute maximum ranges; in-game this is rather 50-75%
<h2>2.1 Auto mode features</h2>
<h3>2.1.1 You can now add Accept-, Reject- and Conflict-Zones to your setup, e.g. to consider borders or de-militarized zones:</h3>
<h3>2.1.1 You can add Accept-, Reject- and Conflict-Zones to your setup, e.g. to consider borders or de-militarized zones:</h3>
<pre><code> -- Parameters are tables of Core.Zone#ZONE objects!
-- This is effectively a 3-stage filter allowing for zone overlap. A coordinate is accepted first when
@@ -1897,10 +1897,7 @@ in the mission editor are absolute maximum ranges; in-game this is rather 50-75%
<h3>2.1.4 Advanced features</h3>
<pre><code> -- Option to switch off auto mode **before** you start MANTIS (not recommended)
mybluemantis.automode = false
-- Option to set the scale of the activation range, i.e. don't activate at the fringes of max range, defaults below.
<pre><code> -- Option to set the scale of the activation range, i.e. don't activate at the fringes of max range, defaults below.
-- also see engagerange below.
self.radiusscale[MANTIS.SamType.LONG] = 1.1
self.radiusscale[MANTIS.SamType.MEDIUM] = 1.2
@@ -1914,6 +1911,13 @@ in the mission editor are absolute maximum ranges; in-game this is rather 50-75%
mybluemantis.checkforfriendlies = true
</code></pre>
<h3>2.1.6 Shoot &amp; Scoot</h3>
<pre><code> -- Option to make the (driveable) SHORAD units drive around and shuffle positions
-- We use a SET_ZONE for that, number of zones to consider defaults to three, Random is true for random coordinates and Formation is e.g. "Vee".
mybluemantis:AddScootZones(ZoneSet, Number, Random, Formation)
</code></pre>
<h1>3. Default settings [both modes unless stated otherwise]</h1>
<p>By default, the following settings are active:</p>
@@ -1938,27 +1942,7 @@ in the mission editor are absolute maximum ranges; in-game this is rather 50-75%
<p> Use this option if you want to make use of or allow advanced SEAD tactics.</p>
<h1>5. Integrate SHORAD [classic mode, not necessary in automode, not recommended for manual setup]</h1>
<p> You can also choose to integrate Mantis with <a href="Functional.Shorad.html##(SHORAD)">Functional.Shorad#SHORAD</a> for protection against HARMs and AGMs manually. When SHORAD detects a missile fired at one of MANTIS' SAM sites, it will activate SHORAD systems in
the given defense checkradius around that SAM site. Create a SHORAD object first, then integrate with MANTIS like so:</p>
<pre><code> local SamSet = SET_GROUP:New():FilterPrefixes("Blue SAM"):FilterCoalitions("blue"):FilterStart()
myshorad = SHORAD:New("BlueShorad", "Blue SHORAD", SamSet, 22000, 600, "blue")
-- now set up MANTIS
mymantis = MANTIS:New("BlueMantis","Blue SAM","Blue EWR",nil,"blue",false,"Blue Awacs")
mymantis:AddShorad(myshorad,720)
mymantis:Start()
</code></pre>
<p> If you systematically name your SHORAD groups starting with "Blue SHORAD" you'll need exactly <strong>one</strong> SHORAD instance to manage all SHORAD groups.</p>
<p> (Optionally) you can remove the link later on with</p>
<pre><code> mymantis:RemoveShorad()
</code></pre>
<h1>6. Integrated SEAD</h1>
<h1>5. Integrated SEAD</h1>
<p> MANTIS is using <a href="Functional.Sead.html##(SEAD)">Functional.Sead#SEAD</a> internally to both detect and evade HARM attacks. No extra efforts needed to set this up!
Once a HARM attack is detected, MANTIS (via SEAD) will shut down the radars of the attacked SAM site and take evasive action by moving the SAM
@@ -5086,9 +5070,6 @@ When Moose is loaded statically, (as one file), tracing is switched off by defau
<p> switch alarm state RED</p>
</div>
</div>
@@ -9891,9 +9872,6 @@ E.g. `mymantis:SetAdvancedMode(true, 90)`</code></pre>
<p> switch alarm state RED</p>
</div>
</div>