VKBDevCfg-C.exe Issue - boolean "AND" not working

[WarCop]

Hello there,

I just encountered, that the boolean "AND" operators aren't working in the current versions of VKBDevCfg-C.exe (both in 0.92.17 and 0.92.31).
This happens regardless of the types of inputs/outputs and whether 2 AND or 3 AND is selected.
All the other boolean operators work.

Best regards.

[fallout9]

Thank you for reporting it, we'll forward it to the dev.

[TwoLemonsInARow]

I think for the time being, the boolean functions are best viewed as off limits as they seem to have numerous bugs and errors.
It's necessary to use workarounds where possible, in some cases features are limited due to this.
Hopefully it can be resolved in future firmware updates.

[Ron61]

Can you see an example where they don't work?

[Alex Oz]

Checked, the functions AND2 & AND3 works. Set it up right.
VKBDevCfg is just a configuration tool.

[Alex Oz]

I think for the time being, the boolean functions are best viewed as off limits as they seem to have numerous bugs and errors.
It's necessary to use workarounds where possible, in some cases features are limited due to this.
Hopefully it can be resolved in future firmware updates.

Either show specific mistakes or better keep quiet .

[TwoLemonsInARow]

I cannot use any of the Boolean functions without having issues with the sticks resetting or things not working.
I have just decided to wait until the issue is eventually fixed.

[Ron61]

No, that won't work. We need specific examples (screenshots) to understand what does not work and repeat this situation with us.

[Victorus]

Hello there,
I just encountered, that the boolean "AND" operators aren't working in the current versions of VKBDevCfg-C.exe (both in 0.92.17 and 0.92.31).
This happens regardless of the types of inputs/outputs and whether 2 AND or 3 AND is selected.
All the other boolean operators work.
Best regards.

1. What device(s) were tested?
2. Versions of firmware?
3. Detailed settings description. What do you want, what've you done, What's wrong in your opinion. Screenshots please. Your current description is not enough. "All is bad"
4. Study User Guide https://disk.yandex.ru/d/LlqiYtIrIetBOQ. I've checked all Booleans and they work. If some of them do not work, I've written - not implemented.

[WarCop]

1. My configuration: MCG Ultimate w/ twist + Gunfighter Mk. II Base with orange Blackbox
2. v. 2.09 (from file _BlackBox_GF_MCG_Ultimate_Twist_v2_09_0.vkb)
4. I've already done that - maybe I've overseen something?
3. My usual plan was the implementation of a MiG29-like AP-light (I managed to get it to work via registers). Even if you're sure that all Booleans work - at least they don't for my configuration.

1st test setting
1st line: Original Boolean configuration

I started to test them again with the profile I had created some days ago: same results. So I reflashed the firmware and reset the device to factory settings - same result! I guess I found the programming issue: The Booleans themselves work, but the first value is not being registered .

Let me show you:

If have used this Bool setting, just changing the Boolean type

Using this setting with different boolean types I came to the following truth table:

Truth table
Left side: 2nd test setting with reset device
Right side: 3rd test setting (inputs D1 and D2 exchanged)

As you see, the issue always happens because of not registering ON (1) values of the first input (D1 or 1st Layer as named in the software).
So I exchanged the D1 and D2 inputs with exactly the same result. I've also tested it with Logical buttons, Boolean truth (from the Bool field before, where I just a NOT on a FALSE led event) and so on. The problem stays the same: The first Input/Layer is not recognized (Maybe it's being written to the wrong register ). Just as a proof of concept I then moved on to test it with XOR3 - once more confirming my suspicion.

Best regards

P.S.: The Config tool itself with all its functions is absolutely amazing! Great job, man!

[Victorus]

Agreed. Issue. On your screenshot vkbdevcfg.exe v0.92.31 (FW 2.10.0). Try this FW. Works. Success attend you!

[WarCop]

Thank you!
As you've already said: The latest firmware solved the issue - I've just tested the Bools and they do work now (same test procedure as above).
Thank you for the hint about the window title - I didn't realize the current firmware version being mentioned there, yet.
Keep doing your great job!