Bug with Shift layer stuck

[bushez]

so there is a big bug with layer change that when I use my left right button on my mouse and then click the right one(this one change to another layer) still holding both and if i keep the press on the left but release the right my left button get stuck when the layer change happen and I need to click it again for it to work

[Gogeba]

Hi!
Turning ON this option should resolve your issue:

[bushez]

its already on

[Gogeba]

its already on

Hmm, could you specify - whole LMB get stuck after you release RMB or it just stick keep going down?

[bushez]

its unpress the LMB, when I hold and press the LMB and at the same time press and then release the RMB my LMB just unpress himself like I don't click it at all

[1ncorrect]

The problem in the game may be caused by the fact that you remap the keyboard and mouse to a virtual controller, but in the Shift 2 layer your mouse buttons continue to work as mouse buttons.
Try to remap RMB and LMB in Shift 2 to L2 and R2 respectively.

[bushez]

i need it to be RMB and LMB I don't want to replace it and its not only in the game I even used mouse click test website and u can see that it getting stuck

[Support Agent]

Please provide a short video of the issue so we can see it.

Ensure the video includes the mouse testing site and the ViewKeyCode app before and after applying the config in reWASD.
Remember to have the "RawInput Mouse" tab selected and the "Pressed" and "Released" options checked in the ViewKeyCode app.

[lankaras]

I've noticed that shift layers can be glitchy and get stuck sometimes... I have two paddles which are mapped to KB through Razer Synapse, then I remap the KB again in reWASD. I use these paddles for shifts and one of them tends to get stuck, but not the other one. Why??? That's very strange when they are configured the same. The 're-press the button' option does not help, but what DOES help is setting the "delay before jump" on the release activator. Even setting it to 1ms seems to solve it! So that's my solution for now, maybe it should have the 1ms delay by default?

[strokel]

Hi lankaras

Could you please send us a video showing this issue?

[lankaras]

Hi lankaras

Could you please send us a video showing this issue?

Sure. In this example, I mapped the paddle to XBOX (B16) and SHIFT layer 1 (Hold mode). Then I spam the button and vary the interval a little. I also press X (B2) sometimes because it seems easier to get stuck when I press two buttons. In the top right you can see that the layer mostly goes back, and sometimes not. I think it gets stuck 3 times in this video.

https://jumpshare.com/share/CKGTxJg3hTwaeWZuaqMA

[strokel]

This seems to be related to Razer software, since the same mapping works correctly on another keyboard without the Shift layers getting stuck.

[lankaras]

This seems to be related to Razer software, since the same mapping works correctly on another keyboard without the Shift layers getting stuck.

It's quite mysterious to me at the moment. It also works correctly on my end... *most* of the time. Sometimes I can't replicate it myself. But sometimes it gets into the "situation where it gets stuck" and then I can replicate it pretty easily, as you can see in the video.

I think the release always gets triggered, the button (Xbox in the example) does not get stuck. It's only the shift layer. But it's a specific situation where that happens, and I'm not quite sure how to get there.

I understand it's going to be hard to debug if you can't replicate it, and it seems to be solved for me by adding the "Delay before jump". So don't worry about it too much. If I happen to discover anything else related to this, I will let you know.

[strokel]

Please send us a screenshot showing how your mapping looks in Razer Synapse.

[lankaras]

Please send us a screenshot showing how your mapping looks in Razer Synapse.

It's just keyboard keys 1-6. It's the Tournament Edition so they don't allow advanced mappings, I can set it to a keyboard key or a gamepad button and nothing else.