Keymapper one button off

[Drano]

So I'm trying to set up a common button to center my view in both the game and reset Necksafer in VR. I'm using the VKB software to map my stick as usual. I'd had the KP5 button to center in IL2 and the hat down button to reset Necksafer and that worked just fine but it was suggested to make them a common button so things don't get out of sync. Makes sense and easy enough right? Necksafer doesn't accept keyboard buttons, only the DX buttons so kp5 wouldn't work for that. So I thought I'd just make a button on the stick button 55. No problem. VKB software sees it as button 55. Button tester sees it as button 55. Necksafer sees it as button 55. Resets just fine. I go to IL2 and try to add it to the keymapper and it shows it as---button 54? So naturally it doesn't do anything. I figure I'll just go back into the VKB software and change the button to 54 if that's what IL2 likes. I change it in Necksafer, working there fine. Back into IL2, nope. Check the maymapper, it now shows it as button53! So why is it one button off? Is there a limit? Some bug with DX buttons? Filed under ain't nothin easy!

 

Upon further review trying to make a button1 shows in the keymapper as button0? That would explain the math being off one. What's up with that?

Edited March 25, 2021 by Drano

[-332FG-Gordon200]

@Drano IL2 game key mapping numbers begin with 0. Button 1 will appear as joy button 0 in game key mapping.

It should function as intended regardless of what the key bind calls it.

Is your hat down button press and hold and not toggle?

[Drano]

It's a simple button press and hold, same button I've been using prior set up the same way other than the button. If I reapply KP5 it works fine in IL2. Whatever DX button map I apply seems to work fine everywhere but in IL2. I just assumed since it showed in the mapper as one off that was the problem. It's like it isn't recognizing it like you're saying it should. Confusing as it's mapped to button 55 but when I hit it in the mapper it says button 54 so you'd thing that'd work right?

 

Could it be that instead of removing KP5 as the recenter for several other things I just added this second command? I'd have thought that would still work as there are several commands that are duplicated or have alternates.

[Sokol1]

Quote

Confusing as it's mapped to button 55 but when I hit it in the mapper it says button 54 so you'd thing that'd work right?

 

This difference between Joy DX button # in VKB tester (or Windows) and game don't cause any issue, happens that game just translate DX button number -1, like in old il2:46.

Your joy button #1 is #0 for the game and work OK.

 

But you can just set HAT down in TrackIR interface for the neck thing and the same HAT down in the game for center camera (same what NP5 do), one assignment don't interfere in another.

 

Of course can set in VKB DevCfg for Hat down press two logical buttons, I suggest ask in VKB Forum - Techinical Support, how to, Fallout9, VictorUS can explain this.

 

 

 

 

 

 

 

[grcurmudgeon]

People start counting at 1. Computers (and often programmers) start counting at 0, because we deal in offsets from the start.

[Drano]

Still, no matter what I add to the key mapper the only one that gets a response to center in IL2 is numpad5, which is the default. As I said I'd even removed that and put, for example, hat switch down just to match with something. It'll reset NeckSafer but not recenter the view in IL2. Clearly I'm missing something.