Total Controls MFBB fix for usng the axes

[skypickle]

put the file attached to this post into the folder

 

D:\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick

(Your DCS root folder might be on another drive like C:)

 

Although the MFBB only has dials, you can assign them to the axes you desire in the settings->adjust controls->axis drop down

Total Controls MFBB.lua

Edited September 18, 2021 by skypickle
sp

[skypickle]

actually, i spoke too soon. I enabled the dial mappings but somehow prevented any button mappings.

[skypickle]

ok i fixed it. Put these two files in your folder

 

DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick

 

Total Controls MFBB.luaTotal Controls MFBB.diff.lua

 

Now you have many more choices. If you want to bind something not on this list then go find it in another lua file (for example Saitek X52 Pro Flight Control System.lua) 

 

find the control you want

copy the entire lline

paste it into Total Controls MFBB.lua

[nick_thain]

Hey @skypickle,

I know this is an old thread, but have you had any issues with the MFBB mapped axes (dials) throwing other axes off center? For me, when I map an axis to an MFBB dial and turn the dial, my WinWing stick axes are thrown off-center...  

 

Also, with your luas, I'm curious; isn't that the default behavior for the MFFB dials? I've been able to assign axes to them since the start... 

[skypickle]

I have noticed that sometimes when I start up DCS, the default mappings get put in-as a result sometimes two controls will get bound to the same axis resulting in conflict.

as the MFFB was designed for the F18, its default Lua file does not include axes in the A10.

[nick_thain]

Apologies,

That description was a little brief, I should have been more specific to better explain; I’m very familiar with DCS’s auto-mapping issue, and in this situation, I’ve cleared all of the controllers, then mapped them all from scratch (I didn’t use the lua provided by Total Controls). If I leave the MFBB dials unmapped, my WinWing device axes are dead center when I check them in the DCS controls. If I map a function to the MFBB dials, and then rotate them away from center, then re-check the WinWing device axes, they are now showing as being way off center. Weird.

What’s even weirder is that, even with the WW X/Y axes being pushed off-center, the WW-mapped pitch and roll are only affected in some DCS modules; the warbirds are only slightly affected and easily trimmed out, but the Viggen is unflyable, even with trimming…

Regardless,

It sounds like you’re not having this issue, which is good news for you  I’m just glad that I isolated that the MFBB is the cause, was driving me nuts trying to figure out why my WW X and Y axes were showing so far off-center, and only in DCS, and only when MFBB is mapped and dials are off-centered.. Total Controls are working with me to get a fix.

Cheers!