Thrustmaster MFD controversy redux

[Slipstick]

BIGNEWY locked the original thread, shown below, but I wanted to throw in my zwei Pfennige, as well as offer a possible workaround.

The fact that the TM MFD's 1 and 2 are preassigned to the OSB in the DCS controls setup is a genuinely nice plug'n'play time-saving feature for those that add them and should, IMHO, definitely not be changed, unless a "remap TM MFD buttons" option switch, the default being option off, is also added somewhere in the setup screens.

The workaround: I have 3 TM MFD's setup and use the third for the CMSP in the A-10C, the plethora of switches on the MFD allowing all the CMSP controls to be mapped with switches to spare.  To do this, I had to load the TM drivers in Windows and change the MFD number assignment through the Windows Game Controller dialog -> F16 MFD x -> [Properties].  There is a drop-down to select the "F16 MFD" number, as well as ID LED checkboxes and button test map.  Setting my third MFD as '3', it listed as "F16 MFD 3" in the DCS Controls setup and the buttons are freely mapped.  Although I haven't tried this, if you change MFD's 1 and 2 to 3 and 4, I suspect you will be able map the buttons normally.

Mi dos centavos,

Slipstick

 

 

[Hawkeye_UK]

Community finds another work around .  Yea that sounds a good idea, stupid though really when its not a complex or time consuming fix from the get go (like every other controller in the game or module.  Look forward to having to import every controls for all modules to 3 and 4, will give it another month and see if ED fix it first.  Funny how the F18, F16 or basically any other module didnt have every other keybound lock.  

I hold to my original statement, the original implementation was poorly considered.

 

Edited April 15, 2023 by Hawkeye_UK

[Ala12Rv-Tundra]

What I do is deleting the default f16 mfd 1 and f16 mfd 2 lua files and you are good to go again 

[ColinM9991]

On 4/15/2023 at 7:16 PM, Slipstick said:

The workaround: I have 3 TM MFD's setup and use the third for the CMSP in the A-10C, the plethora of switches on the MFD allowing all the CMSP controls to be mapped with switches to spare.  To do this, I had to load the TM drivers in Windows and change the MFD number assignment through the Windows Game Controller dialog -> F16 MFD x -> [Properties].  There is a drop-down to select the "F16 MFD" number, as well as ID LED checkboxes and button test map.  Setting my third MFD as '3', it listed as "F16 MFD 3" in the DCS Controls setup and the buttons are freely mapped.  Although I haven't tried this, if you change MFD's 1 and 2 to 3 and 4, I suspect you will be able map the buttons normally.

Or, you know, just leave users decide how to bind their controls without yet another work around.

The point isn't to remove the convenience of having them pre-assigned to the OSB keys of an MFCD. It's to remove the restriction that forces them to be locked so they can only be mapped to the MFCD OSB keys. It really doesn't have to be any more complicated than that. That's exactly how joysticks and throttles work. They are pre-mapped for your convenience, you can remap as you see fit.

[Slipstick]

6 hours ago, ColinM9991 said:

Or, you know, just leave users decide how to bind their controls without yet another work around.

The point isn't to remove the convenience of having them pre-assigned to the OSB keys of an MFCD. It's to remove the restriction that forces them to be locked so they can only be mapped to the MFCD OSB keys. It really doesn't have to be any more complicated than that. That's exactly how joysticks and throttles work. They are pre-mapped for your convenience, you can remap as you see fit.

Which is why I suggested that to map or go with default premapped buttons be an option.