Mouse wheel "delay" with Shift mode

[AerryFaery]

Hi ReWASD-Team,

I ran into a technical problem with my latest config.

Because of physical limitations (I use ReWASD purely for accessibility features and wouldn't know what do to without it! ♥) and need to make the most out of my mouse buttons, so I use a shift layer on my scroll wheel.

Scroll Up -> Weapon 1
Scroll Down -> Reload
Scroll Up (Layer 1) -> Weapon 2
Scroll Down (Layer 2) -> Unequip Weapon

Main Layer isn't muted to keep basic scrolling on the game's map intact.




And this actually works ... sort of.


When I hold down my shift button (X1 / Mouse 4) and move the wheel by one "click" and then release both, my computer will receive both inputs.

So, instead of grabbing my Weapon 2, the animation stops immediately and my character pulls out Weapon 1.


To demonstrate it more "clearly":

I get this:

But want this:


I can circumvent the issue by holding my shift key longer. However, this feels very unnatural to do and can get pretty messy in stressful game situations.


Strange thing is: When I set up the shown configuration in Razer Synapse by using Razer's own "Hypershift", it works perfectly.

But this will prevent me from doing any additional remaps with ReWASD, which is, unfortunately, a No-Go for me.



I also tested multiple mice, to sort out a hardware related issue.

I'm on ReWASD version 9.3.1.10917


I would be super grateful for any suggestions / workarounds!

Thank you!

[Support Agent]

Screenshots weren't uploaded correctly.

Main Layer isn't muted to keep basic scrolling on the game's map intact.

But something tells me this is the source of your issue. Might tell more once the screenshots are up.

[AerryFaery]

Pictures are reuploaded – it should work now.

I also just tried muting the scroll wheel on my main layer, but unfortunately, the behavior didn't change.

It's like ReWASD still registers the main layers input, even though I release the shift key the very second the scroll step is completed. Like I said – if I hold the shift key a little while longer, everything goes smooth.

[Support Agent]

Screenshots and despription suggests that you are making another scroll input after releasing [X1], which is the only reason you'd get that 1 right after the 2 in this config.

You could try doing this:

• Disable the [Re-press the held button when switching the Shift layer] option at [Preferences > General] (might do nothing here, but just in case).
• Add a [Delay before jump] and increase the value until that unwanted 1 stops appearing.

But it will likely result in 2 being typed twice, but I suppose that's not the problem here.

[AerryFaery]

Thank you so much for taking the time!

[Re-press the held button when switching the Shift layer] did indeed nothing.

And adding a delay resulted in a lot of random double-presses, just as you had suspected.


There is no way / workaround to use Razer's build-in Shift-Mode in addition to ReWASD, right? It works very well there, but when I remap just the wheel in Synapse, I miss out on any ReWASD functionality.

[Support Agent]

You could try adding the device Razer uses for remapping to the group with your mouse and remap that.

For example, you remap Scroll up to [1] in Razer, use device detection mode in reWASD, and scroll up - the flashing device would be the one you need to add and remap its [1] key for effect.

[AerryFaery]

Unfortunately, that didn't work either. Thank you anyway for sharing that idea!

The moment I map something into Hypershift Mode in Razer Synapse, ReWASD doesn't detect it anymore. Buttons that still have standard mappings, will still trigger ReWASD's detection mode. It's like my mouse button become invisible.

I also noticed, that the standard scroll behavior (without any active ReWASD config) is a lot more smooth and responsive. Maybe this could have to do with a tiny bit of lag that ReWASD adds to the mix?

[strokel]

Hi. Could you please send us your config?

Also, please send a video showing the difference in scrolling with and without reWASD.

[ControlFreak]

I remapped the same just for the test but have a different result.

22222211 (the clean return should be only 2, those 1 is triggered when the shift key is released)
If I purposely hold the shift layer button longer, then those last unwanted 1 will be gone.

I guess the wheel "press" is buffered and still keeps playing after the shift layer is released and shifts back to default layer.

[Re-press the held button when switching the Shift layer] is off