Skip to content
Medusa IADS Medusa IADS

FAQ

Does Medusa work with modded SAMs?

Yes. Medusa has no hardcoded SAM database. It probes DCS APIs at runtime for sensor ranges, weapon envelopes, and unit roles. Any SAM that DCS recognizes will work, including mods. You do not need to update any lookup table or config file.

One exception: HARM defense uses a built-in list of system name substrings to identify which units can shoot down anti-radiation missiles (DCS has no API for this). The default list covers S-300, Tor, Pantsir, Patriot, and NASAMS. If your mod adds a HARM-capable system not matched by those substrings, you can extend the list via HarmCapableSystems in your config.

Can I run Medusa for both red and blue coalitions?

Yes. Define multiple networks in MEDUSA_CONFIG.Networks. Each network specifies its coalition, prefix, and optionally its own doctrine. You can have as many networks as you want on any combination of coalitions.

MEDUSA_CONFIG = {
    Networks = {
        { name = "PVO",   coalition = "red",  prefix = "pvo" },
        { name = "SyADF", coalition = "red",  prefix = "SyADF" },
        { name = "BLUE",  coalition = "blue", prefix = "blueads" },
    },
}
Do I need to know Lua to configure Medusa?

No. If you know how to add a DO SCRIPT FILE trigger in the Mission Editor, you’re set. Configuration is done by setting values in a plain Lua table before loading Medusa. The syntax looks like FieldName = value inside curly braces. You do not need to write functions, conditionals, or any real code. The Config Builder can generate your config table for you, or see the Quick Start guide.

What makes Medusa different from other IADS scripts?
  • No SAM database. Medusa probes DCS APIs at runtime for sensor ranges, weapon envelopes, and unit roles. Modded SAMs work without updates.
  • Kill probability model. Batteries are activated based on estimated Pk using range, aspect angle, and altitude. Only the batteries most likely to score a kill go hot.
  • Performance. DCS API results are cached at init, sensor polling is budgeted per tick, and range queries use spatial indexing. Dense networks stay lightweight.
  • Zero scripting. Configuration is a flat Lua table. Discovery is automatic by group name prefix. No manual role assignment or wiring.
  • Auto point defense. SHORAD is discovered via DCS unit attributes and assigned to nearby long-range SAMs automatically.
Will Medusa hurt server performance?

Medusa is built for large missions. Sensor capabilities and weapon envelopes are cached once at init. Sensor polling is budgeted per tick so only a few sensors are polled each cycle. Range queries use a spatial index instead of iterating every battery. In testing, a mission with 2 IADS networks, around 100 batteries, and around 100 contacts runs at an average tick time of 500 microseconds to 1.5 ms depending on server hardware. The goal is that your mission hits DCS unit count limits before Medusa becomes the bottleneck.

Can I change doctrine during a mission?

Yes. Medusa exposes a runtime API for changing doctrine fields mid-mission. For example, you can change ROE from TIGHT to FREE when a specific trigger fires. See the Doctrine guide for details.

What happens when my EWR sites are destroyed?

It depends on the SAMAsEWR doctrine setting. With WHEN_NO_EWR (the default), SAM batteries with search radars will start contributing sensor data when no dedicated EWR sites remain. With ALWAYS, eligible SAMs contribute EWR data regardless. With DISABLED, SAMs only use their own organic sensors. See SAM-as-EWR for details.

Can batteries defend themselves against HARMs?

Yes. Medusa detects anti-radiation missiles using kinematic scoring (velocity, dive angle, heading rate, and closest point of approach). When a HARM is detected heading toward a battery, Medusa responds based on the HARMResponse doctrine setting. Options range from smart shutdown with point defense handoff (AUTO_DEFENSE) to ignoring HARMs entirely (IGNORE). See HARM Defense for the full breakdown.

Does Medusa control what SAMs shoot at?

No. Medusa is an emissions harness, not a fire control system. It controls whether a battery’s radar is on or off and whether its ROE allows engagement. DCS AI independently decides what to fire at and when. If ED adds Scripting Engine APIs for directing SAM fire control in the future, Medusa could support this. See Target Assignment for how Medusa picks which batteries to activate.

How does point defense assignment work?

Medusa auto-discovers SHORAD using DCS unit attributes and assigns them to nearby long-range SAMs automatically. No manual placement or naming conventions required. See HARM Detection and Defense for the full breakdown.