VKB-SIM

This is not the case in MSFS, DCS etc.

latest fw. is installed.

Any ideas?

If your joystick binds fine in other games and hits the tester properly then it's an Il-2 issue and I think this would get more attention on their forums.

Thank you.

This isn't an IL-2 issue, I'm having the same problem. There's something broken or more likely that I don't understand about the VkbDevCfg program.

Steps to reproduce issue:

Flash TMW blackbox firmware
Test logical button assignments (trigger is 8 and 6, for example)
Save profile (I've tried doing a "get" and then a "save" also)
"Set" the profile you just saved (or I believe even press the "defaults" button)
Test logical button assignments (trigger is now 112 and 105, and even though IL-2 binds it, it doesn't work in game because it's number is too high)

I've been trying to figure this out on and off for weeks.

Also, if you look on the profile>buttons>physical page, when it's working, the physical presses show up in the first 3 registers, but when the bug occurs, it switches to using the last three registers, which I assume causes the issue due to button auto-numbering or whatever.

I assume a given button press in supposed to show up in the physical layer in a constant location. I don't know what I'm doing wrong, or if this is a legit bug.

I'm just trying to save a copy of the default profile with the axises calibrated, and I've been trying for weeks. Anytime i load a profile, the buttons move physical registers.

Okay, so progress of a sort. I think I was using the wrong firmware possibly (not the mk2 version).

Now that I'm using the mk2 firmware, the button physical assignments seem consistent, however in devcfg it will grey out all but the last 3 registers/rows on the physical and logical button pages, however you can see it using reg1-3 on the physical button page, and you can see the default buttons working on the test tab.

I attempted to use a fresh download of the firmwares and devcfg, and it's still doing the thing where it thinks all but reg14-reg16 are unused.

It does seem to be something with the device because the rows are highlighted correctly until "Enumeration 1" gets reported by the device, then the highlighted rows change. So if the button page is up, and you press "defaults", it will change to the top three rows being highlighted for several seconds until the Enumeration 1 message, then the rows change.

Everything appears functional at a glance, but it leaves the button config wizard and the device report looking at the wrong lines, and the greying out of the wrong rows is obviously a bit confusing.