tulip gyro
ever since the last firmware update for the wooting two he when pressing W A S or D in mixed movement profile the input stays at about 10% tilt towards that direction and it only goes away after giving some input to the opposite side or waiting
I've also noticed diagonal input being inaccurate (see attached images)
Analog input inaccurate
river bobcat
the input stays at about 10% tilt towards that direction
By this, do you mean that the input doesn't fully reset by itself once released?
I take it this is with Xbox controller mode?
Are the attached images both with the new firmware/have you compared with the previous version?
The max diagonal axis is kinda a property of how the xbox controller interface works, we provide a integer number, not a float. So it's the driver that interprets what the values represent here. Does it cause a problem for you?
If you want to try downgrading to do some comparisons, you can do this:
2.6.21-test.downgrade - ...
@tulip gyro
tulip gyro
By this, do you mean that the input doesn't fully reset by itself once released?
it takes a while to reset
I take it this is with Xbox controller mode?
yes
Are the attached images both with the new firmware/have you compared with the previous version?
they are both with the new firmware, I haven't been able to test with the previous version (will do so soon)
The max diagonal axis is kinda a property of how the xbox controller interface works, we provide a integer number, not a float. So it's the driver that interprets what the values represent here. Does it cause a problem for you?
it's just something I noticed while testing the input and might be the reason why I stop sprinting in some games when switching direction from front left to front right
the downgraded firmware seems to have reverted the issue with input not fully resetting once released, however the inconsistency with diagonal input still persists (which I guess can't be fixed since the interface does that, not the firmware)
river bobcat
I'd be surprised that the diagonal value differences would cause issues with sprinting. The difference in the numbers is extremely small and very unlikely to be handled differently by a game engine.
tulip gyro
yeah, I'm really not sure about that one either 😅
river bobcat
What analog curve do you use? If you're on the latest firmware, does the issue with the input not resetting still happen if you increase the start of press deadzone?
Also, what model of keyboard do you have and how long have you had it?
tulip gyro
What analog curve do you use? If you're on the latest firmware, does the issue w...
I currently use Smooth (will test the deadzone in a second)
tulip gyro
Also, what model of keyboard do you have and how long have you had it?
Wooting Two HE (ARM), had it for about a month
increasing the key start deadzone seems to fix it not properly resetting
had to set it to about this to mostly avoid the improper resetting
river bobcat
Hmmm, I see. Thanks for the confirmation. Do you see it happening in all directions?
tulip gyro
it seems to happen only when pressing forward or right
river bobcat
Hmmm, if you have like 0.1mm actuation, do you also observe the key press staying active after release in a similar way?
tulip gyro
no, that doesn't seem to happen
river bobcat
Hmmm
With the Analog curve workaround, are you able to tell roughly what mm it changes from being a problem to being okay? Also, do you have tachyon on or off?
tulip gyro
it seems to change shortly before or at 0.2mm, tachyon mode is off with no external program other than wootility accessing the wooting in any way
river bobcat
it seems to change shortly before or at 0.2mm, tachyon mode is off with no exter...
I think I know why you're getting this and it should be solved by the further improvements to analog signal processing that we're actively working on. Are the workarounds we've found for you alright for now?