> 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-simulations-mh60/aircraft-and-systems/aircraft-systems/flir-forward-looking-infrared.md).
# FLIR (Forward Looking Infrared)
The Forward-Looking Infrared (FLIR) system on the MH-60 (Sierra, Romeo, and Tango variants) is simulated as a cosmetic-only feature. While the external 3D model is fully articulated and integrated into the cockpit controls, users should be aware of the following functional limitations:
* **Articulated Turret:** The FLIR ball on the nose of the aircraft is fully animated. It will respond to control inputs (Pan/Tilt) via the assigned keybinds:
Function
MSFS Key Bindings
Clickable in Cockpit
Move FLIR Right/Left
INCREASE MIXTURE 3 DECREASE MIXTURE 3
❌
Move FLIR Up/Down
INCREASE MIXTURE 4 DECREASE MIXTURE 4
❌
Increase/Decrease Zoom
INCREASE MAGNETO 3 DECREASE MAGNETO 3
❌
* **No Thermal Overlay:** The system does not generate a true "thermal" (infrared) image. While you may see a camera feed on the Multi-Function Displays (MFDs), it functions as a standard daylight or low-light digital camera with filters, rather than a heat-signature sensor.
* **Target Tracking:** The "Cosmetic Only" designation means the FLIR cannot autonomously slave to, lock onto, or track AI entities (vehicles, ships, or people) based on heat signatures.
* **Objects rendering limitations:** The FLIR implementation will not render SimObjects (Buildings, Ships, vehicles, aircraft or people). It is limited to render terrain, satellite imagery, and airport grounds, as fed by the Synthetic Vision engine in MSFS.
The primary reason the FLIR system is restricted to a cosmetic or "synthetic" view is the absence of Camera-in-Gauge support within the MSFS SDK.
---
# 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-simulations-mh60/aircraft-and-systems/aircraft-systems/flir-forward-looking-infrared.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.
