cannot repoduce and missing track file Binding to MFD's

[MadCartographer]

Need some help.
I cant seem to bind anything to my MFD's.
How can I get the A-10C II to see my MFD's so I can bind to them.

I have reset my MFD's, rescanned them but nothing lets the C II see them at all.

EDIT:
I can bind to my MFD's in other aircraft, just not the C II for some reason.

Edited December 12, 2023 by MadCartographer

[LeCuvier]

What kind of MFD modules do you have?
If you have the MFD 16 MFD's (from Thrustmaster I guess) they should have default bindings to all MFD buttons and switches. But you cannot bind anything else to them without tampering.

[Tippis]

Just noticed this old thing while doing the rounds as well, and this is the same problem.

For various reasons, this ancient annoyance just popped up for me and I feel it needs to be addressed at some point.

 

The problem is that the A-10C module comes with a pre-defined bind template specifically for the MFDs, and this template blocks out all other bind capabilities. No other functions are available to be bound and the UI reflects this by greying out binds that do not specifically match the button config.

A “left” Cougar MFD can only ever be bound to left-MFD fuctions. A “right” Cougar MFD can only ever be bound to right-MFD functions. No other binds are available because the module hasn't defined them for these input devices. If, like many do after the Hornet and Mudhen came out, run with triple or quad MFDs, the A-10C module still only sees those as 2x Left MFD and 2x Right MFD, and all those extra buttons can't be used.

This can be bodged by hard-modding the module and adding all other binds to the templates, but of course, this gets wiped by every update and require a mod manager to maintain (not to mention that if you're not careful, your “incorrect” binds will be wiped as well).

This is a long-standing error in how the module has been made to match specific input hardware, but done in a uselessly restrictive way so that you are not allowed to use that special-supported hardware in any other way than what the module programmers imagined. It is actually pretty trivial to fix — just about every other module that detects and default-binds the MFDs can handle it just fine so it's already a solved problem. ED just needs to do it for the A-10C as well.

[LeCuvier]

11 hours ago, Tippis said:

... the module has been made to match specific input hardware, but done in a uselessly restrictive way so that you are not allowed to use that special-supported hardware in any other way than what the module programmers imagined.

I totally agree, ED should add all the bindings available in the "default.lua" to the files for the MFD's.

But I don't expect ED to make the change. I use the Command Injector by @Quaggles which uses one modified LUA file in the game folder. Of course I still have to use OvGME or another mod manager to protect that mod. But now, the additions to the module-related files are in the Saved Games folder structure and are no longer wiped out by updates.

I have been using this for about a year now, and I'm happy with the solution.

[Tippis]

On 2/14/2025 at 11:47 AM, LeCuvier said:

I totally agree, ED should add all the bindings available in the "default.lua" to the files for the MFD's.

But I don't expect ED to make the change.

We'll see. I've given them my files, but I suspect others have as well.

For anyone interested, they are here: A-10C_MFDs.zip and A-10C_2_MFDs.zip for the A-10C and A-10C II respectively. Use your favourite mod manager to plonk them into the module's Input/Joystick directory and everything is opened up.

[Raisuli]

This is odd, because I had to do all the manual bindings for my (TM Cougar) MFDs when I (finally) set up the A-10 again.  Try re-numbering the MFDs; mine are 4, 4, and 5.  I have a 4th that's not plugged in, no idea what the numbers are.

I don't even have TMs software loaded any more, so not sure how I would, or even if I could, re-renumber them out of that odd configuration. 

Of course now I remember just how incredibly sparse A-10 bindings are again.  Of course that means @LeCuvier and I need to talk...