Is it possible to change mouse button functions in clickable cockpits?

[Baldrick33]

Most modules have a three position switch convention of RMB for switch forward, LMB for switch back. Plus LMB to push a button (including MFD buttons)

I would prefer the switch forward function to be the same as the push button function so I can map the CMS switch in my Warthog stick to emulate the mouse buttons and wheel using VR.

Either I need to be able to make RMB operate buttons or swap the switch functions on three position switches so that LMB is forward.

The alternative is to map the push function of the CMS to also be LMB for button pushes but it is more intuitive to push it forward for MFD buttons etc.

I just wondered if this is possible?

[The LT]

Methinks it's possible by manipulating clickabledata.lua but I am not able to test it atm...

[Munkwolf]

Have you tried the options in UI Layer controls, in the UI group?

[Baldrick33]

5 hours ago, Munkwolf said:

Have you tried the options in UI Layer controls, in the UI group?

 

Yes, I have CMS Up mapped to RMB, CMS Dn to LMB, CMS right to Mouse wheel forward,& CMS Left to Mouse wheel backward

It all works fine, however to push a button I need to press CMS Dn which is counter intuitive. So I have also mapped CMS push as LMB for buttons.

What I really want is to be able to use CMS Up for buttons and to push switches forward. So I either need to make RMB work for buttons or switch the convention for three position switches so that LMB pushes forward and RMB back.

I had a look in clickabledata.lua but I was somewhat lost!

[Baldrick33]

After some digging around I found one way of doing it.

Edit the clickable_defs.lua in the mods\aircraft\cockpit\scripts folder

Switch the inverted value for multi position and 3 position switches e.g.

    local    inversed = -1
    if    inversed_ then
        inversed = 1
    end

Now LMB pushes multiposition switches forward (or rotate CW) and also pushes buttons and RMB pull switches back (or CCW)

The downside of course is this needs to be updated for all aircraft each time there is a patch. Assuming these files rarely change a batch file should suffice although always with a risk the files do change, so probably need to copy the originals and compare them with the new ones each time.

Edit: note for some aircraft they do not have a clickable_defs.lua file and you need to edit the clickabledata.lua file

Edit2: this method may not be really feasible as there are many variants of switch commands like spring 3 position switches to edit for some aircraft.

Edited October 22, 2021 by Baldrick33