Keybinding

[usaf77]

Hello to all. Can someone point me to maybe a video that shows the most painless way for a noob to keybind his WW2 Gladiator stick and throttle to a game? I'd prefer using the VKD software to assign keys because I also use a separate game board/controller for the infantry part of the game and I have a mishmash of keys assigned for different things. So I can't really go into the game itself, WW2OL, and assign the buttons in its keymapper. I also have keys assigned for my TrackIR that I need to assign in VKD.

Its all a little confusing. Also I assume the VKD app has to be running for all this to work so do I have to start it each time I want to play? its not really a program that I can auto-start when I turn my computer on. This must all sound very simple to you guys but I need a little help here. Thank you very much.

[fallout9]

First of all, our software doesn't have to run in the background at all. You just have to run it once, calibrate it, assign the buttons to your keyboard keys, then close it; all the changes will be saved into the joystick's internal memory.
Then, in order to have it working as you wish, you'll have to follow this tutorial which shows how to assign keyboard keys to joystick buttons. It's relatively easy to follow, but if you have issues please update this thread for further assistance.

[usaf77]

Outstanding. Thank you.

[usaf77]

Not having much luck here. I keep getting "error read CPUID" messages in the firmware. When I restart the firmware i keep getting 'need to calibrate". Im able to calibrate and the buttons light up in "test" but when I go to action/profile/buttons...............OK I got it working but can I ask this. Can you save your game profiles in the firmware and is there a Latch key you can use so you can assign two functions to one button or trigger. For instance the Saitek pinkie trigger allowed you to do this and I was thinking of using the lower trigger on the stick for this function.

I found the "save" button on the firmware to save the CFG files so I answered my first question. Thank you for the help.

[tomhighway]

First of all, our software doesn't have to run in the background at all. You just have to run it once, calibrate it, assign the buttons to your keyboard keys, then close it; all the changes will be saved into the joystick's internal memory.
Then, in order to have it working as you wish, you'll have to follow this tutorial which shows how to assign keyboard keys to joystick buttons. It's relatively easy to follow, but if you have issues please update this thread for further assistance.

Howdy,

I have a Gladiator NXT pro, and a STECS mini plus. I play IL-2 1946, which only recognizes 32 buttons per device. After watching the tutorial in your link, I mapped some of the buttons on the STECS (from number 33 up) to the keyboard per the instructions in the video. When I went back into the game, the buttons I mapped to the keyboard worked great, but nothing else on either of my controllers worked at all. None of the axes, or buttons/switches. I went back into the config software, changed the keyboard setting from "classic" to "off", and everything on both controllers worked again, except the buttons I mapped to the keyboard. They no longer function at all. Is there a setting I missed somewhere? Is there a way to make the keyboard mapped buttons work while the controllers are working?

[fallout9]

Pretty sure the Il-2 can read up to 64 buttons per device, so you might not need to reprogram the STECS at all.

[tomhighway]

I have several versions of IL-2 1946 installed, that I play. The 3 most widely used ones do not support more than 32 buttons per device. They are; B.A.T. v4.2.3 Flashpoint, VPMod, and YPack v1.2.3.
UltraPack v3.4 Cassie does support more than 32 buttons per device, but unfortunately, it's not one I prefer to play very often.

So, if there is a simple way to solve this issue, I'd love to know what it is.

(edit) I have attempted to map buttons from number 33 up on all of them, that is how I know which ones do and don't support more than 32 buttons per device.

[tomhighway]

Well, after doing more research, I found a solution to the problem. I created a virtual STEC with the VKB config tool, and now I can use the buttons that are numbered above 32.