Help: Latest Synapse 3.0 (v3.4.331.31119) - breaks Tartarus V2 | Razer Insider
Skip to main content

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:
  • 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
The reason why this is such a deal-breaker, for me at least, is that I use SHIFT as my sprint and CTRL as my push-to-talk in games like PUBG. And since updating to the new version, it is basically deactivating my movement in game (dpad) whenever I try to sprint or talk. This has never been an issue prior to this new update. Please help -- it's literally unusable now...and I'd gladly roll-back to the old version if anyone has a download link?
Did this topic help you find an answer to your question?
This topic has been closed for comments

2 Replies

  • 3 replies
  • March 20, 2019
Would love a rollback as my razer tarterus v2 does the same as yours

  • Author
  • 12 replies
  • March 20, 2019
FYI - this has been fixed via a hotfix posted yesterday (3/19). Awesome how quickly it was addressed, thanks Razer!

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings