I have 3 thrustmaster mfds and 2 of them say MFD3
-
{0402044F-0000-0000-0000-504944564944} “Joystick - HOTAS Warthog”
{0400044F-0000-0000-0000-504944564944} “Thrustmaster HOTAS Cougar”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{B353044F-0000-0000-0000-504944564944} “F16 MFD 3”
{076306A3-0000-0000-0000-504944564944} “Saitek Pro Flight Rudder Pedals USB”
{0404044F-0000-0000-0000-504944564944} “Throttle - HOTAS Warthog”
{B353044F-0000-0000-0000-504944564944} “F16 MFD 3” -
@Mower I didn’t know TM made a “MFD3” product, but ok you got 2 of them for some reason.
I think button bindings should just work … that is part of the point of DeviceSorting.txt file. Keeping track of which one is first/later in the DeviceSorting order might be annoying… and if you unplug/replug them, the order in which the OS enumerates them might flip. Just something to be aware of.
I don’t know anything about display-extraction for MFD panels, so Idk if that is going to be a problem or not…
-
-
Thrustmaster Control Panel never loads for me, I just get the W10 generic usb controller options.
-
You need unified TM driver for that to work.
https://ts.thrustmaster.com/download/accessories/pc/unified_drivers/2018_FFD_2.exe
Says its win10 compatible. Can’t confirm, don’t have MFD’s, I’m using android tablet.
-
@white_fang said in I have 3 thrustmaster mfds and 2 of them say MFD3:
You need unified TM driver for that to work.
https://ts.thrustmaster.com/download/accessories/pc/unified_drivers/2018_FFD_2.exe
Says its win10 compatible. Can’t confirm, don’t have MFD’s, I’m using android tablet.
reinstalling this fixed it.
-
@Mower said in I have 3 thrustmaster mfds and 2 of them say MFD3:
@white_fang said in I have 3 thrustmaster mfds and 2 of them say MFD3:
You need unified TM driver for that to work.
https://ts.thrustmaster.com/download/accessories/pc/unified_drivers/2018_FFD_2.exe
Says its win10 compatible. Can’t confirm, don’t have MFD’s, I’m using android tablet.
reinstalling this fixed it.
My guess is the TM firmware for MFD1 was changed to now show MFD1 as “B351044F-0000-0000-0000-504944564944” in DeviceSorting.txt…
-
Could you fix it ?
-
@Echo yes… two post above yours, OP reported that reinstalling the unified TM driver fixed it.
-
where are my thx, didnt see that post
-