VKB Gladiator does not work

[WheelwrightPL]

I have recently bought VKB Gladiator Pro joystick with VKB Rudders.

First I have created a custom cfg file with more than 64 button presses. Then I configured SV Mapper to map all joystick buttons above 64 to keyboard keys.

SV Mapper appears to be working (it lights up correct keyboard key on pressing its corresponding joystick button).

However, most of my joystick mappings, including SV Mapped keys are not registering in IL2 game.

So right now I am stuck with an expensive paperweight and I have invested countless hours to get this far. Please help.

 

[TP_Silk]

My Gladiator Pro works fine in game without using any other tools. Try it without SV Mapper? It could well be that program not recognising the stick rather than IL-2 BOS not recognising it.

[WheelwrightPL]

39 minutes ago, TP_Silk said:

My Gladiator Pro works fine in game without using any other tools. Try it without SV Mapper? It could well be that program not recognising the stick rather than IL-2 BOS not recognising it.

 

I will try. Do you use more than 64 buttons in your Gladiator Pro ? (I read on this forum you must use SV mapper if you go beyond 64 which is easy to do if you map both "pinky" and "mode" buttons to alter other buttons).

[TP_Silk]

Couldn't say for sure - not counted them - I know that I use both 'modes' plus the pinky switch for some stuff. I've also got a throttle quadrant full of button assignments.

 

I'm not saying that you're wrong to use SV Mapper - just that you should test without it too to find out where the fault lies.

[WheelwrightPL]

I turned off SV Mapper and bound joystick-buttons directly. It is still not working.

 

And one way to know how many buttons are active in Gladiator joystick is to:

1) download VKB device config software

2) run it and go to Action -> Buttons / POVs

3) Click all the buttons and see if any register as greater than 64 (which is supposedly the limit of what IL2 can handle without SV mapper)

 

[-332FG-Gordon200]

If you have "Realism" set to Normal some of the buttons will be on automatic settings by default. In order to have control of throttle, fuel mixture and prop pitch (rpm) for example you need to have the game set to Expert or Custom.

Launch the game, either online or off, and select Quick Mission. When the map opens look in the lower right corner for the tab labeled Realism and make your selection.

I have sort of a bastard arrangement of controllers - VKB Gladiator II stick, VKB Mk IV rudders and a Thrustmaster hotas throttle - and this gives me a wide variety of button assignment options but has been a learning experience coordinating everything. My goal is to be able to start the game in VR and complete a mission without needing to lift the Rift headset to find the keyboard.

Hope this helps you with your problem, mate.

Edited May 18, 2018 by Gordon200

[WheelwrightPL]

I just double-checked and yes, I still have realism set to Custom. Thanks for trying to help and good luck with your Rift challenge.

[Sokol1]

23 hours ago, WheelwrightPL said:

SV Mapper appears to be working (it lights up correct keyboard key on pressing its corresponding joystick button).

However, most of my joystick mappings, including SV Mapped keys are not registering in IL2 game.

 

Problem is how game handle keys combos (e.g. Alt+A) sent be external programs (keymapper), is need delay between key press, SVMapper don't have this function. XPadder have, but  is not solution for your case because follow Windows archaic limit of 32 buttons.

 

BoS see up to 64 Direct X (joystick) buttons (may show 63 if the first is counted as 0), above need keyboard emulation.

 

Try map this buttons above 64 with Joystick Gremlin.

 

 

Edited May 18, 2018 by Sokol1

[WheelwrightPL]

15 minutes ago, Sokol1 said:

 

Problem is how game handle keys combos (e.g. Alt+A) sent be external programs (keymapper), is need delay between key press, SVMapper don't have this function.

 

 

 

I don't use key combos: only simple keys like C for cockpit or G for landing-gear, none of them work. There are no other bindings for those keys. Do I still need to use Joystick Gremlin ?

[Sokol1]

I think no, for what I test for single keys SVMapper work OK in BoS. Is just need put YES in the column CONTINOUS.

 

 

 

 

 

Edited May 18, 2018 by Sokol1

[TWC_Ace]

Dont use SVmapper!

VKBDevCfg  software maps joystick buttons to keystrokes. This is how I got pinky button to work as regular button, amongs other things.

Also try to update the joystick to the latest firmware (1.85b) via bootloader.

Edited May 18, 2018 by blackram

[WheelwrightPL]

Looks like putting YES in column CONTINUOUS in SVmapper fixed button-to-key mapping problem. Thank you everybody.

 

BTW: how do you delete a line from SVmapper ?

Edited May 18, 2018 by WheelwrightPL
added a question

[Sokol1]

Put 0 in the field Repeat - this will disable the assignment for this button, until you remap then for another function.

 

Erase the line only in the .INI file created, but done the above is not necessary.