I use a Logitech Extreme 3D PRO joystick. The hat switch on the top of the joystick is treated by the VO client as a pair of axes, rather than as buttons. Combined with the fact that very few commands can be bound to axes in VO, this makes the hat switch essentially unusable.

I would expect the hat switch to operate as 8 (or even just 4) distinct buttons, so that (for example) I could cycle through targets forward/backward by flipping the hat one way or the other.

I used to use the 3 d pro and had the hat switch set for targetting, I use osx. Note that vo numbers stick buttons from 0 though they are numbered from 1 on the stick.

From config.ini;

[Logitech Extreme 3D]
enabled=1
JOYX=Turn
xaxisinvert=1
xaxiscenter=10
xaxismindeadzone=-10
xaxisdeadzone=6
xaxisminsaturation=-74
xaxissaturation=81
JOYY=Pitch
yaxisinvert=0
yaxiscenter=0
yaxismindeadzone=-10
yaxisdeadzone=7
yaxisminsaturation=-77
yaxissaturation=70
JOYRZ=Roll
Rzaxisinvert=0
Rzaxiscenter=0
Rzaxismindeadzone=-8
Rzaxisdeadzone=5
Rzaxisminsaturation=-63
Rzaxissaturation=53
JOYRU=NONE
Ruaxisinvert=0
Ruaxiscenter=0
Ruaxismindeadzone=-10
Ruaxisdeadzone=10
Ruaxisminsaturation=-95
Ruaxissaturation=95
JOYBUTTON0=+Shoot2
JOYBUTTON1=+Shoot1
JOYBUTTON2=FlyModeToggle
JOYBUTTON3=+Turbo
JOYBUTTON4=+Shoot3
JOYBUTTON5=toggleautoaim
JOYBUTTON6=showall
JOYBUTTON7=
JOYBUTTON8=CharInfo
JOYBUTTON9=
JOYBUTTON10=Activate
JOYBUTTON11=nav

( this is the hat switch part )

JOYPOV0UP=RadarNextFront
JOYPOV0RIGHT=RadarNext
JOYPOV0DOWN=RadarNextNearestEnemy
JOYPOV0LEFT=RadarPrev

16_hascenter=1
16_min=0
16_max=1023
16_center=508
17_hascenter=1
17_min=0
17_max=1023
17_center=508
19_hascenter=1
19_min=0
19_max=255
19_center=128
20_hascenter=0
20_min=0
20_max=255
20_center=255

hope that helps

Hm, I didn't realize you could manually assign axis positions as buttons like that. I'll try that and see if it works for me as well. Thanks for the tip.

Hmm, yes, it is cool that you can manually fix it, and I have been doing so for years too, but it would be nice if they just did away with the joystick page and keyboad page and just called it controls, (because assigning joystick buttons on a page called keyboard makes 0 sense).

I have brought this up in the past, as have many others. The entire *controls* menu needs a redo. You should be able to assign buttons, keys, and joystick axes on the same page, and to anything! Should this be high priority? Hell yeah, I can only imagine how confusing this is to new players, because I set all my sticks up manually too,

Aye , fair comment Yoda.

Wait, POV hats shouldn't be showing up as axes. If they are, I place blame on the joystick manufacturer.

Buttons are not the same thing as axes. Maybe there should be a way to assign a digital action to an analog axis, but then it would need yet another configuration screen to define what axis position is 'pressed' and what axis position is 'not pressed'.

I do agree that the 'Keyboard' label should not be called that and instead be called something like 'Buttons' and 'Joysticks' should be 'Axes' or maybe 'Digital Input' and 'Analog Input' or something like that.

The client's input menu is available to be modded via lua, so if someone can come up with a better input configuration menu system, please do.

not all hats are digital... a few are in fact analog axis...

Heh, then again I wish VO had a use for my thottle quadrant as well...

What's a thottle quadrant? <looks it up> It doesn't automatically enumerate as axes? What OS are you using?

a Throttle Quadrant is normally used to control engine rpm, fuel mixtures and flaps on flight sims... for the larger jets two or more quadrants can be used to control each engine separately

My pov hat does show as axis.
Granted my setup is not typical but lets see

Flight Yoke - 11 "buttons" 6 Axis
Rudder Pedals - 3 axis
Throttle Quadrant - 3 axis 9- buttons

Total- 12 axis and 20 buttons

VO just simply does not have any need for all of that LOL..