Skip to content

AEGIS IADS Roadmap

Current: v0.8.3

What's In v0.8.3

  • NEZ frustration gating — ALERT SAMs use full WEZ for frustration decisions (ambush reset). Dropping to AWARE resets the ambush.
  • DIR burn-through fix — Directional jammers were ~22% weaker than intended at range. Normalization corrected.
  • SET_BRG ABS/REL — Magnetic bearing input when calibrated. Old hooks backward compatible.
  • EA GUI reliability — SP fallback no longer collides in MP, REQ logging gated behind debug, poll interval reduced.

What's In v0.8.2

  • HARM reaction tuning — crew delay 6-9s, first-HARM-only, per-SAM saturation threshold (4-8)
  • SP + PD saturation exception — selfProtect + live PD fights through multi-HARM saturation
  • HARM detection range gate (40 NM default)
  • Six singleplayer EA GUI fixes (AI→player upgrade, localhost discovery, LuaSocket path, name mismatch, connection retry, dormant skip)

What's In v0.8.1

  • EA v2 — Physics-based burn-through with antenna gain curves, EW contact filtering with angular masking, four jammer modes (OMNI, WIDE, 2xDIR, OFF), WIDE cone presets (W90/W70/W50)
  • Home-on-Jam — HOJ-capable SAMs break through jamming with escalating probability per peek
  • Passive ESM — NATO radar identification, signal strength bars, relative bearing, stale emitter retention
  • EA GUI overlay — Optional clickable panel for EA pilots with server auto-discovery, copilot/WSO support
  • Differentiated jammed EMCON — HOJ SAMs peek aggressively, standard SAMs peek cautiously
  • ECM→EA rename — EA- prefix (old ECM- still accepted)

Previous Releases

v0.8.0 — Critical unit tracking, EW detection range override, HDS + CurrentHill mod support, round-robin EW polling, zone-aware actRange, alert frustration cooldown

v0.7.2 — Alert frustration, Nat 20 bravery roll, orphan PD promotion

v0.7.1 — HARM detection realism (8-12s crew delay), PB HARM EW detection delay (score-per-sweep), harmInbound flag, ECM jam effect revision (jammed EMCON cycling)

v0.7.0 — ECM jammer framework (AI + player discovery, F10 menu, jammed EMCON cycling, burn-through)

v0.6.2 — PB HARM network warning (trajectory projection), PD HARM defense, weapon-alive cooldown extension

v0.3.2 — HARM reaction policies (STAY_HOT, LAST_DITCH, GO_DARK), crew hysteresis (panic, multi-HARM saturation)

v0.3.1 — HARM detection (TOO/SP mode), contact filtering (aircraft + TALDs only)

v0.2.0 — Infrastructure dependencies (EW, PWR), EMCON cycling with jitter behaviors

v0.1.0 — Core IADS (EW-driven WEZ gating, point defense, naming convention, F10 debug)

Recently Completed

Mobile SAM Position Tracking (v0.8.4-beta2)

SAMs with the MOB suffix get periodic position updates. Tiered polling: 60s idle, 20s active. Round-robin spread. Enables shoot-and-scoot and convoy escort scenarios.

Coming Next

SAM-as-EW Promotion

When all EWs in a sector die, the biggest SAM promotes to EW role — fires its search radar and feeds contacts to remaining SAMs. Creates a middle step between full integration and individual EMCON cycling.

Late Activation & Respawn Support

Late activation groups that spawn mid-mission will evaluate the current sector state and enter the correct degraded mode. Includes backup generator restoration for destroyed power sources.

AWACS / Airborne EW Feed

Airborne early warning aircraft feeding contacts to the IADS network.

Future Ideas

  • Ship-based air defense — naval SAM integration with SHIP- prefix
  • Shot tracking / ammo awareness
  • Theater command (cross-sector coordination)
  • C2 hierarchy (cross-sector coordination, multi-parent PD)

Design Principles

  1. Naming convention is the primary interface. If you can't do it by naming a group, it should be doable with one API call.
  2. Event-driven, not poll-driven. Minimize DCS API calls. React to events, don't scan continuously.
  3. Degrade gracefully. Every infrastructure kill makes the IADS worse, not broken. The AI always has a fallback behavior.
  4. Trust the mission maker. If they named it NORTH, it's NORTH. Don't second-guess with distance checks.
  5. Keep it lightweight. If it adds per-tick cost, it needs to justify itself. One-time costs at init or on events are fine.
  6. Non-determinism over predictability. Human crews are not metronomes. Jitter, randomization, and adaptive behavior make SEAD harder and more interesting.