Axes X and Y activate buttons 54 and 55

[Pmax]

Hi!
I need som help.

I got this system.:

Product Name: VKBsim Gladiator EVO R SEM FSM.GA
PRO version
T-Link supported
Firmware version: v2.189
And as you can see, updated with the latest firmware.

I use this system with Microsoft Flightsim 2020, and so far it has worked flawlessly.

But today when I had to configure buttons 54 and 55 I discovered that my X and Y axis also go in and affect/activate these buttons. These are the only buttons that are affected. But if I activate the "Default" button in VKBDevCfg-C_v0.93.17 everything works as normal. I can't recall changing anything in my axes or the buttons, so I'm hoping someone can give a hint as to what might be wrong.

Many thanks in advance.
Kind regards, Per from Denmark

[fallout9]

It's hard to tell without knowing what kind of changes you're making to the default profile.

[Pmax]

Thank you very much for your reply.
I have not changed anything on the X and Y axis and the buttons. These are the default settings. Could there be other settings that have nothing to do with the axes and these buttons that could be influencing the problem?

[ouch]

You probably have to post your profile here. It is real easy to accidentally change something.

[Pmax]

Okay.
I saved my setup as Cessna.cfg, is that the file you want to see? And should I just copy what's in the file and paste it here?'
Sorry, I don't have much knowledge about this.
Thanks in advance

[Pmax]

You probably have to post your profile here. It is real easy to accidentally change something.

I have figured it out.
Under "Action" >"Profile">"Axes" on the far right there is a tab called "Axes2Buttons"
There was A2B.:
#1 set to - Type "Edges1 :3 H:0% VB:53"
#2 set to - Type "Edges1 :7 H:0% VB:54"
I don't know what this function is for and why it was set, at least I don't remember that I set it myself. But now I set them to Type "Off" and that solved the problem.
Maybe someone can tell what these settings can be used for.
Kind regards
Per

[Ron61]

Read about this in paragraph 3.7 of this guide.