Set up Thrustmaster MFD Cougar panels in DCS World, map F-16, F/A-18C and A-10C buttons, add screens and fix USB detection problems.
Connect each Thrustmaster MFD Cougar panel by USB, verify that Windows identifies two separate controllers, then bind the left and right display push-buttons in DCS World’s aircraft-specific Controls page. No extra profiling software is required. The Cougar frames are input devices only: an MFD Cougar screen must be supplied separately.
Thrustmaster MFD Cougar setup for DCS World
The most reliable DCS MFD setup uses each frame as a separate native USB controller. Connect the panels before launching DCS and avoid TARGET or another virtual-controller layer unless you need features that direct bindings cannot provide.
- Check both panels in Windows. Open the Windows USB game-controller utility and confirm that two MFD devices appear. Select each one and press several bezel buttons to make sure its inputs register. Names commonly distinguish MFD 1 from MFD 2, although the wording varies with the installed driver.
- Give the panels unique identities. If both units report the same MFD number or only one is recognised, use the Thrustmaster MFD control-panel utility to assign separate unit numbers. Reconnect them and repeat the Windows input test.
- Open the correct DCS control set. In DCS World, open Options and then Controls. Select the exact aircraft module and, for a multicrew aircraft, the correct crew position. The A-10C and A-10C II, for example, have separate assignments.
- Find the display commands. Search for terms such as
MFD,MFCD,DDI,OSBorPB. DCS modules use different names for functionally similar bezel buttons. - Bind by physical position. Double-click the cell beneath the correct Cougar device, press the matching bezel button and accept the assignment. Work around the frame in order so that the physical upper-left button operates the virtual upper-left button.
- Assign the corner rockers selectively. Bind their directions to brightness, contrast, gain or symbol controls where the module provides suitable commands. Otherwise, they can operate page selection or other frequently used avionics functions.
- Test left and right in the cockpit. Power the aircraft’s displays and try buttons on every side of each frame. A label such as MFD 1 does not require that device to be on the left; placement and bindings determine which display it controls.
- Back up the assignments. DCS saves bindings automatically, but export the profile from each Cougar column or back up the active
Saved Games\DCS\Config\Inputfolder. Its exact parent-folder name can differ on older or customised installations.
A mistake we see constantly is configuring the right aircraft but the wrong device column. Our explanation of DCS device columns, duplicate bindings and controller-profile backups covers the wider control-mapping process.
How should I map the DCS F/A-18C, F-16C and A-10C displays?
Match every Cougar button to the same physical position on the simulated display bezel rather than trying to reuse one aircraft’s profile across several modules.
| DCS aircraft | Recommended mapping | Main caveat |
|---|---|---|
| F-16C | Left Cougar to the left MFD and right Cougar to the right MFD; bind the corresponding OSBs by position | The MFD Cougar frame follows the F-16-style layout closely, but auxiliary functions and rocker assignments may not match every DCS command exactly |
| F/A-18C | Left Cougar to the left DDI and right Cougar to the right DDI; look for left and right DDI push-button commands | The centre AMPCD is a third display, so a standard two-panel arrangement does not provide a dedicated frame for it |
| A-10C II or A-10C | Left Cougar to the left MFCD and right Cougar to the right MFCD | Configure the specific A-10C module you fly because their DCS control profiles are separate |
| Other modules | Use the nearest equivalent avionics-display commands and preserve the physical button order | Some cockpits have different button counts, extra displays or no one-to-one MFD layout |
Do I need to configure the MFD Cougars for every aircraft?
Yes. DCS stores MFD Cougar bindings separately for each aircraft module and, where applicable, each crew station.
Repeat the mapping while keeping a consistent physical scheme: left frame for the left display, right frame for the right display and bezel buttons matched by position. Do not import an F-16C profile into the DCS F/A-18C or A-10C control set; the available commands and their internal identifiers differ.
Does the Thrustmaster MFD Cougar include a screen?
No. The Thrustmaster MFD Cougar contains the bezel controls and lighting, but it has no LCD panel, video input or graphics connection.
An MFD Cougar screen is separate hardware placed behind the frame. You can use one small display per Cougar or position both frames over exported viewports on a single larger monitor. The Cougar’s USB cable continues to carry button inputs only; the added monitor needs its own video connection.
- Extend the Windows desktop. Use Extend rather than Duplicate and arrange the accessory displays to match their physical positions. Placing them to the right of or below the main monitor usually makes DCS coordinates easier to manage.
- Create a monitor configuration. Store the custom
.luafile in the activeSaved Games\DCS\Config\MonitorSetupfolder. Define the main cockpit viewport and the exported display viewports supported by the aircraft. - Select it in DCS. Choose the configuration in the simulator’s Monitors setting and use a resolution covering the complete display rectangle represented by that configuration.
- Align and test the exports. Adjust the viewport coordinates and dimensions until each rendered image sits behind its frame. Viewport names differ between modules, so a configuration that works for an A-10C MFCD may not export an F/A-18C DDI correctly.
Extra viewports add rendering load, and the combined desktop’s bounding rectangle can include unused pixels. Our DCS cockpit guide to exported displays and USB panels explains this part of the installation in more depth.
Why are my DCS MFD Cougars not detected, swapped or losing bindings?
Most MFD Cougar problems are caused by duplicate device identities, USB changes, insufficient hub power, the wrong aircraft profile or software replacing the physical panels with a virtual controller.
| Symptom | What to check |
|---|---|
| Windows detects only one panel | Try separate known-good USB ports or a powered hub, then check the unit identities in the Thrustmaster control panel. Both panels must register separately in Windows before DCS can map them reliably. |
| Windows sees both, but DCS does not | Connect them before launching DCS and restart the simulator. Stop any TARGET or virtual-controller profile temporarily and check whether the physical devices then appear. |
| MFD 1 operates the right cockpit display | This is a placement or binding mismatch, not a failed panel. Swap the physical frames or reassign the two DCS device columns, then keep them connected to consistent USB ports. |
| A button registers in Controls but does nothing in flight | Confirm that you selected the exact aircraft and crew station, assigned the correct left or right display command and powered the cockpit display. Also check for mode-dependent avionics functions. |
| Bindings vanished after a USB or driver change | Windows may have assigned a new device identifier. Return the panel to its previous port or load the saved profile into the new Cougar column. Also confirm that DCS is using the expected Saved Games folder. |
| One press triggers two actions | Look for assignments under both the physical Cougar and a TARGET-generated virtual device. Remove the unwanted binding or use only one controller path. |
| The frame lights up but shows no cockpit image | This is normal without a separate monitor. The Cougar lighting does not indicate that a screen is installed, and its USB connection cannot carry video. |
Do I need TARGET or a HOTAS Cougar?
No. The MFD Cougar panels work independently of the older Thrustmaster HOTAS Cougar stick-and-throttle system, and DCS can bind the frames directly without TARGET.
Use TARGET only when you specifically need shifted layers, macros or a combined virtual controller. While a TARGET script is running, DCS may see a combined device instead of the individual panels; stopping the script can therefore make an apparently different set of bindings appear. Bind either the virtual device or the physical Cougars, not both.
The frames can be used alongside any joystick and throttle. If you are configuring the rest of the cockpit controls at the same time, keep separate aircraft profiles and clear unwanted automatic assignments before testing the complete setup.