Third MFD added and working in TARGET

[RogueSqdn]

I've done some searching around lately, and after digging through a few files, I have managed to get a third MFD added and working in TARGET.

 

 

There are three files involved (four if you're using the 120 DX button addon):

 

 

1) TARGET.tmh (C:\Program Files (x86)\Thrustmaster\TARGET\scripts)

 

The first thing is to add the CMFD as a an alias at the top of the file:

 

alias Throttle        = "VID_044F&PID_0404", Joystick        = "VID_044F&PID_0402", LMFD        = "VID_044F&PID_b351";
alias RMFD            = "VID_044F&PID_b352", HCougar        = "VID_044F&PID_0400", T16000    = "VID_044F&PID_B10A";
alias TWCSThrottle    = "VID_044F&PID_B687", TFRPRudder    = "VID_044F&PID_B679", T16000L    = "VID_044F&PID_B10B";
alias TFRPHARudder    = "VID_044F&PID_B68F", JoystickF18    = "VID_044F&PID_0403", CMFD        = "VID_044F&PID_b353";

You will also need to add two lines. First, after the RMFD line in the GetIndexJoy section, add:

 

   &CMFD = GetIndexJoy(Select(&CMFD));            // expect a CMFD to be plugged on USB

Third, you'll need to add the MFDMap line after the RMFD line:

 

   MapList(&CMFD, &MFDMap);

2) dx+.tmh (C:\Program Files (x86)\Thrustmaster\TARGET\scripts)

 

If you're using the 120 button addon here, you'll need to add those GetIndexJoy and MapList lines to this file as well.

 

 

 

 

 

 

 

 

3) VID_044F&PID_B353.dev and VID_044F&PID_B353_MFD3.xaml (C:\Program Files (x86)\Thrustmaster\TARGET\DevCfg)

 

You'll need to make copies of either the left or right MFD files here and edit the information in the .dev file:

 

a) Edit line 3 to say <HWID>VID_044F&PID_B353</HWID>

b) Edit line 4 to say <Name>MFD Cougar 3</Name>

c) Edit line 54 to say <File>DevCfg\VID_044F&PID_B353_MFD3.xaml</File>

 

 

 

 

I haven't tried it, but if you change the references and files to B354, I imagine a fourth MFD would work.

 

 

I've included the four files needed in this zip. Copy everything to C:\Program Files (x86)\Thrustmaster\TARGET (you'll need to give admin approval) and it should work. I included the instructions in case you want to try this on your own.

 

 

 

 

Good luck!

CMFD.zip

[RogueSqdn]

Doing some more fiddling around, and I can't seem to control the lights on the CMFD.

 

 

 

I'll keep looking around, but if anyone has a suggestion, please let me know.

[Oilman100]

Be good to know if you manage to work it out

[RogueSqdn]

Unfortunately I've hit a brick wall on the lighting. I'd have to have someone that knows a lot more about the subject than I do to figure it out.

 

 

That said, when I was trying to get it recognized in TARGET, I did a bunch of googling and saw where people had tried and failed to get it going, but took their failure points and figured out the rest of it. I'm not trying to brag on myself, just saying that perhaps someone can take what I figured out and find the next step that's necessary.

[Dugo]

It dont work for me.

Got this message after starting from GUI

 

 

[Oilman100]

It only works when using the script editor I believe and not the GUI, I got all he keys working perfectly but not the 2 lights with the above files

[VirusAM]

So 3 is possible but not 4?

[Oilman100]

Yes you should be able to do a fourth, if I remember the top post explains what to add into the files to make this happen

[canadianbaken]

I didn’t do anything in the Lua files. I went into control panel in Windows and set it up as MFD 3. Then DCS and target sees it fine and you can adjust lights.

[Oilman100]

Yes you can turn the lights on/off but you can’t script it within Target ie. put the landing gear down and light comes on, applying airbrake makes the light flash

[canadianbaken]

Well I don't use Target but It works fine in DCS.

[VirusAM]

I got this error trying with 4 mfd and the 120 buttons mod (i modified targetdx128.tmh)

 

 

Runtime Error: Index out of bounds for: @3b94c08 in MapKey ( line 353 in targetdx128.tmh )

 

 

Any guess on what could be?

 

 

EDIT: I found the error and corrected...i leave the original post as could be useful for someone else.

 

 

Also i share my modified files and profile with 4 mfd (simply DX buttons from 1 to 120 for the 4 mfd)

Long press for every button is that Dx + dx120 (to set as modifier in DCS for multiple functions on 1 button).

My plan is to make my targetexport work for leds and backlighting (actually works but only in singleplayer)

DCS_4MFD.zip

Edited June 5, 2020 by VirusAM

[Oilman100]

I got this error trying with 4 mfd and the 120 buttons mod (i modified targetdx128.tmh)

 

 

Runtime Error: Index out of bounds for: @3b94c08 in MapKey ( line 353 in targetdx128.tmh )

 

 

Any guess on what could be?

 

 

EDIT: I found the error and corrected...i leave the original post as could be useful for someone else.

 

 

Also i share my modified files and profile with 4 mfd (simply DX buttons from 1 to 120 for the 4 mfd)

Long press for every button is that Dx + dx120 (to set as modifier in DCS for multiple functions on 1 button).

My plan is to make my targetexport work for leds and backlighting (actually works but only in singleplayer)

 

Be interested to see how you mange to get on with getting the additional 2 MFDs LEDs working within a Target script to enable individual programming. Good job so far and thx for sharing

[VirusAM]

Be interested to see how you mange to get on with getting the additional 2 MFDs LEDs working within a Target script to enable individual programming. Good job so far and thx for sharing

 

You do exactly as you do with the other 2 mfds...just instead of LMFD or RMFD you need to use the two names you gave in the modded files.

If you use mine (in the above archive) i called mfd 3 CMFD (for central MFD) and mfd 4 BMFD (for bottom MFD).

In the included target script there is already some code (commented as it is a WIP) for MFD leds but you need to add the same for MFD3 and MFD4.

Let me know if you need help

My profile is intended for using only the 4 mfd as i have not (anymore) other TM devices, but if you have also the warthog, you could give every mfd an unique secondary button to use as modifier in DCS.

For example OSB1 in MFD1 could be (using the chain command) DX120+DX1, in MFD2 DX121+DX1 and going on. Homefries in his wonderful target scripts uses a similar technique

[Oilman100]

You do exactly as you do with the other 2 mfds...just instead of LMFD or RMFD you need to use the two names you gave in the modded files.

If you use mine (in the above archive) i called mfd 3 CMFD (for central MFD) and mfd 4 BMFD (for bottom MFD).

In the included target script there is already some code (commented as it is a WIP) for MFD leds but you need to add the same for MFD3 and MFD4.

Let me know if you need help

My profile is intended for using only the 4 mfd as i have not (anymore) other TM devices, but if you have also the warthog, you could give every mfd an unique secondary button to use as modifier in DCS.

For example OSB1 in MFD1 could be (using the chain command) DX120+DX1, in MFD2 DX121+DX1 and going on. Homefries in his wonderful target scripts uses a similar technique

 

A little bit of help required, I use the original files in the post and got CMFD working no problem, can you tell me exactly what files and line numbers you modified to get the LEDs programmable within the Target script. I have no programming experience so will just mimic what you tell me. Much Appreciated

[VirusAM]

A little bit of help required, I use the original files in the post and got CMFD working no problem, can you tell me exactly what files and line numbers you modified to get the LEDs programmable within the Target script. I have no programming experience so will just mimic what you tell me. Much Appreciated

 

 

 

I just got the 4 mfds being recognized and working in target script.

I didn’t program leds or lights as I don’t need it for now...

But I assume it will be just the same as with the other mfds...

So instead of using lmfd or rmfd you would use for example CMFD

[Oilman100]

Unfortunately not, it doesn’t recognise the additional MFD LEDs, so you can only have them either on or off using the Win controller properties which is pointless. Ok thx for the reply, if you ever solve it please post the solution.

[shu77]

This is awesome, but whats the benefit of running MFD's through Target? Is this purely a button box/modifier thing?

[Oilman100]

This is awesome, but whats the benefit of running MFD's through Target? Is this purely a button box/modifier thing?

 

There are many uses, you can use them for indications e.g. A/P engaged, LED flashes or same for Airbrake, this acts as a simple reminder if the A/P has been on for a long time during straight flight and suddenly you want to maneuver, or if you use advanced features like flags or utilise different curves e.g for refuelling then you can program the LEDs to come on and go off to indicate you have a refuel curve activated, it's a very useful function

[shu77]

Never thought about changing the curve for A2A, thats an interesting idea. I've been loving DX120 and debating adding the Joystick into the warthog profile, but hadnt really thoguht of adding the cougars in.

[VirusAM]

Unfortunately not, it doesn’t recognise the additional MFD LEDs, so you can only have them either on or off using the Win controller properties which is pointless. Ok thx for the reply, if you ever solve it please post the solution.

 

Yeah probably it would need more digging in the target.h file....

As i fly mainly VR, i don't think I am going to lose my sleep on this one...

[Home Fries]

This is great stuff, RogueSqdn!

 

Mind if I include it in my public TARGET script? I'll give you credit.

[Home Fries]

I got DX+ working, and I know you can call a TMH file (including a modified target.tmh) from a folder other than TARGET/Scripts. In fact, I call DX+.tmh from my CTS/Common folder. I haven't tried calling the DevCfg files though (which I assume is most important in getting the CMFD to work). If I could call these from a different folder I would put this into my CTS profile in a heartbeat.

 

Code for the TMH from a relative folder is easy:

include "Common/dx+.tmh"

 

Do you know if it's possible to call the DevCfg files from a different folder (ideally a relative path from the script itself)?

Edited June 12, 2020 by Home Fries

[RogueSqdn]

Third MFD added and working in TARGET

 

I don’t mind at all. I don’t use Target anymore though because the only TM controllers I still use are the WH and Cougar (TUSBA) throttles. I do still use the Hornet grip though, with a T-50CM2 base.

 

I’ve pretty much moved fully to VR and MFDs are one of the things I sacrificed.

 

 

Sent from my iPhone using Tapatalk

[Wolf359]

Did anything come of getting LED control through the script? It's the ONLY reason I run the MFDs through the script - to control the lights with the power switch on my throttle. Otherwise, when used as MFD, DDI, AMPCD, I see no added value of running them through the script - especially when DCS sees all three just fine. Added note: I did change the third to MFD 3 through the game controller panel.