VKB-SIM

Hello,
I have both Gunfighter and STECS.
So for MSFS2024 I got myself SPAD.next, in which I am trying to configure controllers now.
I am having issues with STECS, I believe, due to the reason that in SPAD I see a button flickering, so to say. If I press a button in the GF, and look in SPAD, it is calm. As in - lit up. But in STECS, it's really quickly flickering. And yes, the whole STECS behaves like that.
And - I am pretty sure it should not be doing that, right?
So, what do I do to correct that?

EDIT:
Found this post:
viewtopic.php?t=8130
Going to FW 9.15 does solve the issue.

Did you manage to fix it, because I do have the newest firmware? I don't quite desire to be locked at the older software version.

As I understand it, there is no problem with the devices, only with a third-party program? The conclusion suggests itself.

Is it though? Because: My Gunfighter does not flicker in that software - SPAD.next. While STECS does. So, how is it then software problem? To my understanding, SPAD doesn’t differentiate between those two, I guess.
I am able to help myself by using the so called Gamepad mode.
The issue here though is that faster button reactions, like HDG knob to one of the dials, do not work any more.

I am not pointing fingers, I would just like to have it solved, be that firmware update or software update. Most likely the best solution is for SPAD and VKB to work together to solve the issue.

I understand that this could be a concern for some of our customers, but as a small company, we are unable to collaborate with third parties due to resource constraints. We simply cannot afford the additional support. Additionally, we are committed to building our hardware without compromising its output to accommodate the requirements of other programs.

Okay, I can understand that.
But tell me: why does GF act differently than STECS (steady light vs flickering light)?

It's hard to say without knowing how the 3rd party software is interpreting our devices. From our point of view, they're both the same.

OK.
In the meantime, I contacted the software developer of SPAD.next, and while it doesn't really explain why the two devices behave differently, there is a workaround in his system which seems to work fine, so for anyone looking for a solution, here it is:
First, set up the device as Gamepad, with number 100 (which is default).
Then for all dials (which are buttons, so for each button), check "Encoderbutton".
This makes the TQ work correctly, all buttons and dials.