Joystick not recognized

[PaladinX]

Hello everyone,

i need some support: Bought and installed WOFF 2 today successfully.
When it comes to the workshop and my input configuration, the problem starts.

I use:
- Joystick: Virpil Constellation Alpha on a Virpil WarBRD base.
- Throttle: HOTAS Warthog Throttle
- Throttle: Saitek / Logitech Throttle Quadrant
- Pedals: MFG Crosswind Pedals
- Trim: Saitek / Logitech Trim Wheel
- Track IR

Problem: When i am in the input configuration and want to bind the joystick axis to elevator or ailerions, it beeps and tells me "only joystick axis can be assigned!"

WTF?!

The input shows me correctly that the X-axis and Y-axis move, when i move the joystick, so the axis are recognized.
I tried with all other devices unplugged, only with the joystick plugged in.

I use this configuration with WOFF 1, IL2 1946, IL2 Great Battles, FSX, P3D, MSFS, DCS without any issues.
Why does WOFF 2 not allow me to bind my usual joystick x- and y-axis to the ailerons and elevators?

PC WIndows 10, 8600K, 32 GB Ram, RTX 3070, etc...

Any ideas?

Regards,
Jan

[+Winder]

Make sure you have no stuck buttons on the controller.

Also make sure you have no third party joystick or button app scripts running.

Its the same setup app as WOFF1

WM

Edited April 7, 2021 by Winder

[+Polovski]

It may be worth resetting devices to default - because by default those axis are assigned already.

Also, you must move the stick fully left/right or up/down to the max for the axis to be assigned. 

Note pressing a joystick button, then going to the axis to assign it will say "Only Joystick axis can be assigned" but this is simply overridden when you move the stick fully to assign the axis.
If it does not, then a button or script is running as above, or a fault with buttons pressing.

Edited April 7, 2021 by Polovski

[PaladinX]

Update:

The hints regarding a button stuck was the correct one!

What was wrong:

The VIRPIL Constellation Alpha has a 4-Step-Trigger (!), means a lever switched forward (button 1), switched backward with contact to the trigger (Button 2), then the trigger itself (Button 3) and a second step on the trigger (Button 4).
If this lever is forward, it sets button 1 to "up" --> Means its pushed all the time --> Means, when i want the game to recognize an axis, the button permanently sends data and the game does not "see" the axis im moving...
When i bring everything in the standard position and all the buttons are shown as "up" - then it works.
So basically my fault with the buttons on my Joystick. Cant blame the game for it!

[+Polovski]

Great PaladinX glad you found it.  4 -step trigger sounds impressive :)

Edited April 8, 2021 by Polovski