Set up the Thrustmaster MFD Cougar Pack in DCS World, bind both panels by aircraft, fix detection and swapped IDs, and add display screens.
Connect both Thrustmaster MFD Cougar panels by USB, confirm Windows sees them as separate devices, then open DCS World’s Controls screen for the aircraft you fly. Bind each left/right OSB command to the matching panel, save and test the bindings. The Cougar frames are button controllers only; they do not contain LCD displays.
Thrustmaster MFD Cougar setup in DCS World
The most reliable setup is to let DCS read each Cougar as an independent USB controller rather than combining them through profiling software.
- Connect and identify both panels. Plug them in before starting DCS, preferably through motherboard USB ports or a powered hub. Windows should list two controllers with distinct identities, commonly resembling
F16 MFD 1andF16 MFD 2. The exact wording can vary with the installed driver. - Select the correct aircraft. Open DCS World’s Options screen, choose Controls and select the exact aircraft module and crew position. The A-10C II, legacy A-10C and multicrew stations have separate control sets; configuring one does not configure the others.
- Find the bezel commands. Search the command list for terms such as
MFD,MFCD,DDI,OSBorPB. OSB means option-select button, while some modules call the same type of control a push button. - Bind each physical button. Double-click the cell under the correct Cougar device column, press the matching bezel button and accept the assignment. Work around the frame in order so that the physical top-left button corresponds to the virtual top-left button.
- Assign the rocker switches. Bind the four corner rockers only where the module exposes suitable brightness, contrast, gain or display controls. They can instead be used for page selection or other cockpit functions when there is no direct match.
- Test the left and right panels. Load a cockpit with the displays powered and press several buttons around each frame. The matching virtual bezel button should move or the displayed page should change. Do not assume that unit 1 is left until you have verified it.
- Back up both device profiles. DCS stores assignments automatically, but exported profiles are useful after driver or USB changes. Treat each Cougar device column as a separate profile when using the save-profile function.
For a closer explanation of device columns, duplicate assignments and profile backups, see our DCS controller-mapping procedure.
Which DCS commands should I bind?
Bind commands by their position on the simulated bezel, because command names and cockpit layouts differ between aircraft.
| Aircraft type | Suggested mapping | Main caveat |
|---|---|---|
| A-10C and A-10C II | Left Cougar to the left MFCD and right Cougar to the right MFCD | Configure the specific A-10C module you use; their profiles are separate |
| F-16C | Left and right MFD OSBs in matching physical positions | The Cougar frame is based on the F-16 layout, but not every auxiliary control has an identical DCS command |
| F/A-18C | Left Cougar to the left DDI and right Cougar to the right DDI | The centre AMPCD is a third display and is not covered by a two-panel pack |
| Other modules | Bind the nearest equivalent display or avionics commands | Some aircraft have different button counts or no one-to-one MFD layout |
For the Hog, our A-10C cockpit and HOTAS primer explains how the MFCDs fit into the aircraft’s wider control flow.
Do Thrustmaster Cougar MFDs display cockpit screens?
No: the Cougar units provide illuminated frames and physical controls, but no LCD panels or video connection.
You can place each frame over a separate small monitor or position both frames around exported views on one larger monitor. The Cougar USB connection still handles only the controls; the computer’s graphics output supplies the image.
- Connect the display hardware. Arrange the extra screens in Windows using Extend rather than Duplicate.
- Create a DCS monitor configuration. Custom configurations can be kept under
Saved Games\DCS\Config\MonitorSetup. Define the exported viewport positions and dimensions for the module you fly. - Select the configuration in DCS. Choose it in the Monitors setting and set the simulator resolution to cover the complete Windows display rectangle.
- Align the exports. Adjust the viewport coordinates until each rendered display sits behind its physical Cougar frame.
Viewport names and support vary by aircraft, and exporting extra cockpit displays adds rendering load. Our guide to integrating USB panels and exported displays into a DCS cockpit covers that side of the installation without confusing button inputs with video outputs.
Why are my MFD Cougars not detected or swapped?
Most detection problems come from duplicate device identities, USB enumeration changes, an unpowered hub or virtual-controller software hiding the physical panels.
| Symptom | Likely fix |
|---|---|
| Only one Cougar appears | Check both in Windows first, try separate USB ports and use a powered hub if necessary. If the Thrustmaster control panel reports the same unit number for both, assign distinct identities. |
| MFD 1 operates the right display | This is only a placement or binding mismatch. Swap the physical panels or reassign their DCS columns, then keep them in the same USB ports. |
| Windows detects a panel but DCS does not | Connect it before launching DCS and restart the simulator. Confirm that button presses register in Windows before changing any DCS assignment. |
| Buttons register but the cockpit does not respond | Check that the exact aircraft and crew station are selected, then verify the display is powered and the command belongs to the correct left or right unit. |
| Bindings disappeared after moving USB ports | A port or driver change can give the device a different identifier. Return it to the original port or load the saved profile into the new Cougar column. |
| One press causes two or incorrect actions | Look for bindings under both the physical Cougar and a virtual controller. Clear the unwanted assignment or stop the software creating the virtual device. |
Should I use Thrustmaster TARGET with DCS?
DCS World does not require TARGET for the MFD Cougar Pack, and direct native bindings are simpler for most installations.
Use TARGET only when you specifically need shifted layers, macros or a combined virtual controller. If it creates a virtual device, bind either that device or the physical Cougars—not both—or a single press may trigger duplicate commands. Native DCS assignments are also easier to diagnose separately for each aircraft.
Do I need to configure the Cougars for every aircraft?
Yes, DCS stores Cougar bindings separately for each aircraft module and, where applicable, each crew position.
Repeat the mapping while preserving the same physical logic: left panel for the left cockpit display, right panel for the right display, and bezel buttons matched by position. Do not load an A-10C profile into an F-16C or F/A-18C control set; their command identifiers and available display functions differ.