MPCDs and Cougar MFDs

[Backy 51]

Zeus,

 

 

Will the Razbam AV-8B N/A Harrier have the TM Cougar MFDs mapped to the MPCDs or hard-coded like the DCS A-10 does with it's MFDs? For the A-10C, all you need to do is plug in the USB TM Cougar MFDs and you mimic the LSK "buttonology" right out of the box ... a very user friendly feature.

 

 

Cheers,

[1stBEAST]

asked sometime ago if the Cougar MFDs are supported.

and Zeus saied yes. so i asume that this will be the case.

[The LT]

You probably meant OSB's, not LSK's. And how hard can it be to map the buttons?

 

Toggle switches, on the other hand, are a different matter, which cannot be simply mapped unless the commands are created. RAZBAM did that in their Mirage with the position switch abstractions layer, so I hope they did that with the Harrier.

 

Preordered. :)

[Backy 51]

asked sometime ago if the Cougar MFDs are supported.

and Zeus saied yes. so i asume that this will be the case.

 

 

 

 

Thanks for the info! I did not see or remember that earlier post.

[Zeus67]

Zeus,

 

 

Will the Razbam AV-8B N/A Harrier have the TM Cougar MFDs mapped to the MPCDs or hard-coded like the DCS A-10 does with it's MFDs? For the A-10C, all you need to do is plug in the USB TM Cougar MFDs and you mimic the LSK "buttonology" right out of the box ... a very user friendly feature.

 

 

Cheers,

 

I'll have to check that Cougar map thing. But no key bind is hard coded for the MPCDs (Multi Purpose Color Display or Multi Purpose Display).

[Elnocho3]

But no key bind is hard coded for the MPCDs (Multi Purpose Color Display or Multi Purpose Display).

 

Sorry, may have misinterpreted - does that mean we won't be able to assign a joystick button to control one of the MPCD buttons?

[Nero.ger]

i suspect he means you have to do the keybinds yourself, as with every other button on your stick.

in the PocketGuide at the end are 20 binds listet for the MFCD(left and right)

Left MPCD OSB 01    
Left MPCD OSB 02 
.
.
.
Left MPCD OSB 20 

[BIGNEWY]

all MPCD buttons are in the control options for assigning

[Elnocho3]

Great stuff - thanks for the clarification Nero.ger and BIGNEWY

[chev255]

What would be great would be for the MFCDs to use the same export names as the ones from the A-10C, this way no need to re-parameter the export.lua file...

[1stBEAST]

or that they are mapped automatically like for the a-10c ^^ but manual mapping would be fine to

[Zeus67]

Thrustmaster Cougar MFDs presets are now included.

[chev255]

Thanks Zeus

[T_A]

Thanks , i ordered a set on Black Friday just for the Harrier

[1stBEAST]

N I C E ! you are da maaaaan!

 

thanks alot :-)

[Sarge55]

Sweet... Thanks Zeus.

[Cowboy10uk]

Well this news has just made the module a tad more expensive for me.

 

Buying the wife’s Xmas pessys and somehow the Cougar MFD and a 12” screen, just happened to accidentally fall into the Basket on checkout. ;)

 

Cowboy10uk

[Backy 51]

Thank you Zeus! You guys are setting a new standard of outstanding customer service!

[Johnny Dioxin]

Now I just need you to design a way to see them through my Rift :Flush:

[mmaclauchlan]

I just placed them flat on my desk in front of my keyboard. Works perfectly with VR.

[mkiii]

Having the Cougars preset saves a lot of time, but it would be helpful if you could assign ANY new commands to them in the control setup GUI as a default, as you can in other aircraft. At the moment they cannot be assigned with anything other than MFCD commands. Allowing this, especially with shifted/Modified commands gives us a lot more flexibility.

[Deezle]

Having the Cougars preset saves a lot of time, but it would be helpful if you could assign ANY new commands to them in the control setup GUI as a default, as you can in other aircraft. At the moment they cannot be assigned with anything other than MFCD commands. Allowing this, especially with shifted/Modified commands gives us a lot more flexibility.

It's just like the A-10C. You can go into the F161.lua and F162.lua and add the missing commands from the default.lua you'd like to be able to map to them or you just delete both of them and manually map them.

[mkiii]

Thanks Deezle.

 

I never bothered changing the A-10 MFDs, but I do use them a lot with other aircraft that don't have displays, along with shift states to get the most out of them.

 

I did eventually figure out that deleting the default MFD files allowed me to assign anything, which is what I did, but they get replaced with updates, and copying all the keystrokes from default.lua into each mfd file, and using Generic Mod Enabler works, but risks missing out on any new commands that might be added by the devs. Hence the request for the default setting to be that all commands are made available.

 

So my comprimise now is to use JSGME to replace the 2 MFD luas with only slightly modified versions. Rather than copying the whole of the keystrokes/default.lua into each file, I just insert a line at the top to "include" the default.lua contents directly from the DCS AV8 mods folder using the following line in each MFD file. I'm not sure if this is the correct method, but it works, and the MFD files stay short and readable, making it easier to spot any potential changes, and removes the need to manually update the files with new keyboard commands.

 

The fix (in red) is inserted on the second line, just below return { so the top few lines of each F16MFDX.lua read something like this:-

 

return {

local res = external_profile("Mods/Aircraft/AV8BNA/Input/AV8BNA/Keyboard/default.lua")

forceFeedback = {

},

KeyCommands = {

 

-- Right MPCD / Left MPCD

{combos .................

 

 

So the question remains, why this isn't the default setup?

Edited January 9, 2018 by mkiii