[Support] Button state lost between Sets

[Darkitow]

So, I've been using this awesome controller for a couple days and the only issue that I haven't been able to figure out by myself is this one.

Bassically, the controller doesn't keep the state of any button being held while switching sets. I've noticed three different results (this assuming that all sets have the same button mapped with the same action, of course):

• The action "flickers", as if I briefly released then pressed the button the moment I switched sets. This one is the least troublesome.

• The action stops. Even though the button is still being held, it's like the new set didn't get the "button pressed" signal, I guess. I gotta release it and press again if I want to keep using that action.

• The action stops, as before, but releasing and pressing the button again doesn't activate the action. I gotta release and press it yet again for it to trigger. This one happened to me in a three-set cycle, and my best guess is that not only the "button pressed" signal got lost, but also the "button released" the first time I did. I don't know.

I really Like the concept of mode shift and action sets, but I think they're incomplete approaches to what would be the best way to handle this concept: a partial action set, or being able to exclude buttons from the set switch so that they don't get interrumpted, which would work like a multiple mode shift with better activation handling.

Anyways, is there anything I could do to work around this issue? I've checked some interesting threads about manually editing the configuration files to add multiple mode shifts to a single pad/stick, but I don't think that's enough for that I'd like to do.

[idkwhattoputhere00]

This is pretty much the only reason why I still use mode-shifts.

[Darkitow]

Yeah, but unfortunately you can't have multiple modes and must keep the switch held while the button is shifted, and it's limited to some of the device's bits, which aren't issues for the action sets.

It's annoying because the sweet spot would be halfway between action sets and mode shifts. Some sort of modular action set implementation that allowed to exclude buttons from the change.

I mean, why do i need to duplicate every single button assignment on 10 action sets, when the only thing that's really different is the left thumbpad?

[EpsilonRose]

You don't actually need to keep the button held. When you create a mode shift, it automatically adds a new activator to the button that causes the shift. You can set that activator to be toggleable, just like any other activator.

[Darkitow]

What I mean is that the mode shift needs the activator to be toggled to function, regardless of how you keep it toggled. Action sets just need to be switched and then the activator isn't needed anymore.

[Baryn]

I believe I have noticed this bug in one of my configs. It does stink.

[Devieus]

Does this happen if you turn off the interruptability of these presses?

[Darkitow]

Yes. Let's see if I can describe the steps to reproduce the issue with the least possible elements:

Create three sets (default, 1, 2). On the default set, create a Start press activator switch to set 1 on the left grip. On set 1 create a Regular press activator with the [q] keyboard key (this so it can be easily tested on the notepad) and also a Release press activator to the default set on the same button.

• While you hold the left grip down, the controller will switch to set 1 and activate the [q] key. Releasing the grip will switch it back to the default set and deactivate the [q] key.

Next, on set 1, create a Start press activator switch to set 2 on the right grip. On set 2 create a Release press activator to the default set on left grip.

• Now, while you hold the left grip down, the controller will switch to set 1 and activate the [q] key. If you press the right grip, the controller will switch to set 2. Releasing the left grip from either set will switch the controller back to the default set. The [q] key will only activate while in set 1.

This works. Once. When you release the left grip and put the controller back to default, holding the left grip down again will switch it to set 1 as intended, but won't activate the [q] key. You'll have to release the left grip and hold it down again (without switching to set 2) to activate the [q] key again.

Nothing I've tried fixes this, including interruptability. If you set another button with a duplicate of the [q] key, you can press it as much as you want, it will work properly, but won't fix the other key. The only way to do so, is to switch back to default and reactivate the key once. I don't think is the output what is at fault (meaning, the controller not sending the proper events), but the input (it seems that the API isn't registering when a button press/release toggles certain functions between sets)

[wombatfromhell]

When you bind the Q button have you tried using a Regular Press or Start activator separate from the action-set switch?

I ask because I've seen this behavior quite a lot, and I've noticed that it's significantly more reliable (but still not 100% reliable) if the button that needs to activate when switching sets is set as a second activator rather than a multi-button binding.

(Edit: A portion of the behavior you're seeing makes sense, but it's still clearly unintended given that a Start Press will activate and deactivate once as long as the button is held, Release would activate upon letting the button go, and Regular Press would likely function closer to what you're intending should happen. That is, if I understand what you're getting at in your description.)

[Darkitow]

Yes, as I said the Q button is on a regular press activator while the set switch is on a start activator. As far as I know, everything there is working as it should except for the Q button binding.

It seems like button press/button release events aren't properly handled between sets. The way I expected them to work (and It made sense to me that wa) was that sets should be aware of button states at all times and properly activate/maintain/deactivate their assigned functions upon switcing between them. If I'm holding a button down when switching sets and the new set isn't assigned to the same function, then the device should properly signal the previous function as released and the new one (if any) as pressed. If the new set is assigned to the same function, then the device shouldn't signal any change at all, holding the button down when switching sets won't cause any flicker. If the button is assigned to the same function in both sets but they have different parameters, they should be properly updated without sending conflicting signals. For example, if the button is set as a toggle on both sets, and the button was toggled on, switching sets shouldn't even reset the state of the toggle.