Open Eetsjone opened 8 months ago
WhiteMagic
commented
7 months ago The data seen by those parts is from exactly the same subsystem so it shouldn't actually be different. I've also never seen this behavior before so I'm not sure what is going on there or even where to begin to debug this. If you add bindings to the buttons do they behave as you'd expect? There might be some delay in switching between "activated" inputs in the configuration view causing the disconnect.
Eetsjone
commented
7 months ago https://github.com/WhiteMagic/JoystickGremlin/assets/25878546/369a8238-d34d-450a-bb5e-eb42bf410eee
I've attached a screen capture video. If you first look at the VKB screen on the left and the Input Viewer Screen on the right you can see that both follow the same key numbers. Then, when you look at the main screen you will that these numbers do not follow. And since the actions are defined for the numbers they are also incorrect for the actions I want. In this case: 65 - gear up, 64 - gear handleww middle position, 63 - gear down.
In the main (default) screen where you define the actions for buttons the software does weird readings for 3-way buttons on the VKB STECS. In the Input Viewer screen if follows exactly the button numbers as also shown in the VKB software where you can test the buttons. On these screens the numbers would be 63 - 64 - 65 with the movement of the button. Back also correct.
But on the main screen it would go like: 64 - 63 - 65 and back 65 -63 - 64. This sequence will change all the time. It will not be consistent like this. It goes also 64 - 65 - 64.
What is the difference between the main screen and the Input Viewer? Can this be solved?