> For the complete documentation index, see [llms.txt](https://docs.miltechsimulations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.miltechsimulations.com/miltech-fighters-m2k-c/aircraft-and-systems/weapon-and-defensive-systems/countermeasures.md). # Countermeasures {% hint style="info" %} Flares and Chaff are for visual effect only. These serve no practical function. UNSUPPORTED: Flares are not rendered across multiplayer. {% endhint %} Countermeasures (Flares) are automatically loaded onto the aircraft upon first spawn. There are a limited number of flare pods loaded onto the aircraft, and as such these will run out after extended use. Flares will be automatically reloaded onto the aircraft as soon as the aircraft is stationary on the ground - no manual action is required. Flares are modeled for cosmetic purposes only. Single manual flare drops, as well as flare programs are supported. Current Flare Count is displayed on the HUD, for more information see [Head-Up Display (HUD)](/miltech-fighters-m2k-c/aircraft-and-systems/avionics-and-radar-systems/head-up-display-hud.md) Flares and Countermeasures are controlled from the Countermeasures Panel, just under the INS Panel, on the right side of the aircraft cockpit.

1. **Jammer Operational Mode Selector:** INOP 2. **Jammer master Switch:** INOP 3. **Radar Warning Receiver master switch:** INOP 4. **D2M IR launch detector master switch:** INOP 5. **Flare Dispenser master switch:** Three positions are available 1. A is ARRET (Off) 2. SA for Semiautomatic (manual release) 3. AU for Automatic (program release) 6. **Flare program selector knob:** Flare programs are dictated by the following table:

## Flare Release Operations 1. **Locate the Countermeasures Panel on your aircraft**. 2. **Switch the Flare Dispenser Master Switch** to the SA or AU Position. 3. **Use SA to release flares individually.** A limited amount of flares are loaded onto the aircraft, HUD symbology will automatically display flare count. Single keybind toggle will deploy a single flare. 4. **If on AU, use knob in the right to select program.** A means ARRET, program is off. Any other number indicates a different program to use. 5. Use Keybind **`Toggle Alternator 3`** to trigger a program. Single keybind toggle will deploy a single flare (SA Mode), or a single Flare Program round (AU). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.miltechsimulations.com/miltech-fighters-m2k-c/aircraft-and-systems/weapon-and-defensive-systems/countermeasures.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.