- Rebind the d-pad buttons to any keyboard function (note: I use the up/down/left/right keys, but I've also tried mapping to w,a,s,d with the same results. I use the d-pad for movement in games).
- Bind a key on the keypad to CTRL and one to SHIFT (note: I have key 16: CTRL and key 11: Shift)
- The d-pad will function properly, and can easily be tested by opening a text file and moving around the text with your d-pad (or typing a bunch of "w,a,s,d" if you have it bound that way)
- HOWEVER, if you now hold the CTRL or SHIFT keys and use the d-pad, it will not respond...it is like having the modifier keys pressed first will deactivate the d-pad's key presses. In theory, it should be typing capital "W, A, S, D" now if you're holding SHIFT (for example) but it doesn't do anything.
- This only seems to be an issue with it blocking the d-pad commands specifically, as holding CTRL or SHIFT and hitting other keys on the keypad seem to work fine, so it's something unique to how the new software is handling the d-pad and modifier keys
Help: Latest Synapse 3.0 (v3.4.331.31119) - breaks Tartarus V2
Hello,
Since updating to the latest version of Synapse 3 yesterday (3/18/2019) the Tartarus Chroma V2 keypad is no longer handling the d-pad on the device properly. Based on some testing, I believe this should be fairly easy to reproduce and seems related to using modifier keys (i.e., CTRL, SHIFT) in combination with the d-pad.
Steps to reproduce the issue:
This topic has been closed for comments
Sign up
Already have an account? Login
Log in with Razer ID to create new threads and earn badges.
LOG INEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.