Warthog buttons not registering

[UIV]

You used a wrong version of VKBDevCfg.
For firmware 1.81.7 need to use VKBDev 0.78.9.9
VKBDev v0.79.1.0 for firmware 1.8.2 and higher. Check the attach
But your Gladiator's firmware - 1.8.1x

[rrohde]

Here's the link to the VKBdevCfg UIV was referring to: http://ftp.vkb-sim.pro/Programms/VKBDev ... 78_9_9.zip

[AirHog]

Thanks for the info guys. I'll go through the version numbers and report back.

[AirHog]

Ok ....

VKBDevCfg-C v0.79.10 and Firmware v1.83.5 does not work in terms of accessing the button on the joystick. Uploading the firmware crashes the bootloader 100% of the time, the joystick then seems to go dead, nothing is registering and all I see is a red blinking light.

When I use VKBDevCfg-C v0.78.99 and FIrmware v1.817 everything is fine in the config, but 'some' buttons don't register in game.

Edit: I've just discovered that Elite Dangerous doesn't recognise more than 32 buttons and that what I was trying to configure all this time ... just checked in Star Citizen and it recognises all buttons

Lesson learned. Thanks for eveyone's help! Really appreciate it

So my next question is ... Is 37 buttons the maximum or can I configure the 'mode' button to be a shift button? Right now it acting like a regular button.

[UIV]

Explain in details please, what kinf of buttons mapping you want. I try to create for you.

[tx101]

I have the exact same issue with my Gladiator Pro/Warthog setup
Elite Dangerous does not recognise buttons 32, 33, 34, 35 and 36
This is a known issue that Frontier Developments are aware of but for whatever reason have not fixed it

Some explanation for the issue can be found here

https://forums.frontier.co.uk/showthrea ... ost3135803


As a quick workaround would it be possible to disable buttons that are recognised and reassigning them to the missing buttons on the stick
Example disable 5 buttons situated on the base of the stick, say buttons 7, 8, 9, 10 and 11

[tx101]

I am have the exact same issues with my Gladiator Pro and Warthog set up with Elite Dangerous
It appears that Frontier Developments are aware of this issue but for whatever reason have not fixed this issue

See here for further information

https://forums.frontier.co.uk/showthrea ... ost3135803



As a workaround would it be possible to disable buttons that are recognised and reassigning them to the missing stick buttons
For example buttons on the base disabled, say 7, 8, 9, 10 and 11 and mapping those numbers to the missing stick buttons

[UIV]

You can turn on the Gladiator virtual keyboard and assign the keypress for buttons with # more than 32.

[AirHog]

Explain in details please, what kinf of buttons mapping you want. I try to create for you.

I'd like to get the MODE to work, right now its seen as a normal button. How can I get this to operate as a shift button?

[UIV]

Can you explain with details, what kind of buttons mapping you want. I'll try to create the profile for you.

[AirHog]

Ok ... forget about the mode button for the moment.

What I'd like to do is shift the button range from the Warthog grip to start from Button #1 so it can be seen by Elite Dangerous.

For example, using VKB Config:
Right now Warthog First Trigger is Button #48 and VKB Base "Flaps Up" = Button #1

How do I make Warthog First Trigger = Button #1 and VKB Base "Flaps Up" = N/A ?


EDIT: I worked it out ... I was able to map the button assignements in the LOGICAL tab

Very happy now that I can use all the buttons on the grip, however referring the button image map in my OP, Button #5 (single button located on the RHS of the grip head) is not working at all. I've checked the wiring and it looks ok, there's no kinking or broken wires. Any ideas?

[Victorus]

Check Poll and push button. You must see red dot in button cell. May be this button was configured as Shift so does not respond as common button

[AirHog]

Thanks Victorus, you've been a great help.

Will check this tomorrow night.

After assigning all the buttons in Elite I did a quick test and discovered another problem - All axis respond like on / off switches. I checked in VKBConfig and Wizzo and noticed any axis on the base jumps from 0 to 65XXXX, there's no transition.

Now I created my own profile from scratch when configuring the buttons, would this be cause?

[Victorus]

I think buttons do not affect to axes. Try to calibrate axes using VKBcfg.

[AirHog]

Hey Victorus ... No change after calibration. All axis jump from 0 to 32767 to 65535 and vise versa.