Razer Tartarus V2 controller D-pad sticking / glitch
Userlevel 1
so while using the Tartarus V2, the d pad sticks and you keep moving in one direction till u press the same direction again. I know a lot of people have this problem while looking through the forums and the one solution is to delete razer synaps. but unfortunately I use a lot of razer products and that's the best way to match and customize RGB. so its either I deal with that annoying glitch and have cool colors and effects. or i delete synaps and don't deal with that glitch but now half my RGB features are useless. I was hoping to bring this back to the attention of the developers to see if u can make a small patch for synaps so the people who use the Tartarus can enjoy there gaming and RGB lights at the same time. Please and thank you.
This topic has been closed for comments
Page 6 / 20
alexxedo
Another clue about the issue can be seen in the "keyboard properties" window of the system.
The "Repeat delay" and "Repeat rate" settings are applied to the Tartarus input only when Synapse is not running. If Synapse is running the settings are ignored and the keystrokes continue to arrive at a given non-configurable speed.
If Razer wants to stop RMA-ing perfectly working hardware, they really shall correct this bug.
This is an incredible discovery! Thanks a lot for checking it out!
Another clue about the issue can be seen in the "keyboard properties" window of the system.
The "Repeat delay" and "Repeat rate" settings are applied to the Tartarus input only when Synapse is not running. If Synapse is running the settings are ignored and the keystrokes continue to arrive at a given non-configurable speed.
If Razer wants to stop RMA-ing perfectly working hardware, they really shall correct this bug.
The "Repeat delay" and "Repeat rate" settings are applied to the Tartarus input only when Synapse is not running. If Synapse is running the settings are ignored and the keystrokes continue to arrive at a given non-configurable speed.
If Razer wants to stop RMA-ing perfectly working hardware, they really shall correct this bug.
D-Mouse
Given that the issue supposedly doesn't occur when Synapse is not running (e.g., when using reWASD instead), can't this potential cause be eliminated?
Nope cause the keypad changes its behaviour when Synapse is running, it sends a lot more data for each keypress (around 70 frames)
Maybe there is a bug in the behaviour with synapse. There is a lot of frame output and I have a tartarus pro so there is a lot more position than on/off. I don’t know what the traffic looks like for a V2 but I don’t have the time to reverse-engineer all those frames.
Even if we identified precisely the issue, it will be useless if Razer does not take the bug into account.
alexxedo
- Either the keypad does not send the key release USB frame and Synapse continues to act as the keypad is pressed and sends the command
Given that the issue supposedly doesn't occur when Synapse is not running (e.g., when using reWASD instead), can't this potential cause be eliminated?
I sniffed the USB connection between the keypad and my computer and triggered the issue.
I can see that the keypad does not send anything when the key is considered as stuck by the game.
So there can be two reasons:
- Either the keypad does not send the key release USB frame and Synapse continues to act as the keypad is pressed and sends the command
- Or the keypad does send the key release USB frame, Synapse "misses" it and continues to act as the keypad is pressed and sends the command
In addition the keypad is a lot more chattier with the host when Synapse is active. I killed it and observed there is a lot less frame (basically 1 keypress and 1 keyup per keystroke which is normal)
Maybe disassembling the software to know how it processes the USB frame could point the problem however it is a complex and tedious task compared to actually looking to the original source code directly...
I can see that the keypad does not send anything when the key is considered as stuck by the game.
So there can be two reasons:
- Either the keypad does not send the key release USB frame and Synapse continues to act as the keypad is pressed and sends the command
- Or the keypad does send the key release USB frame, Synapse "misses" it and continues to act as the keypad is pressed and sends the command
In addition the keypad is a lot more chattier with the host when Synapse is active. I killed it and observed there is a lot less frame (basically 1 keypress and 1 keyup per keystroke which is normal)
Maybe disassembling the software to know how it processes the USB frame could point the problem however it is a complex and tedious task compared to actually looking to the original source code directly...
Thanks, everyone, for the info. I would have liked to buy a Tartarus Pro but am going to wait until this is fully fixed in Synapse. Posting so I can subscribe.
Have exactly the same issue with my Tartarus V2, seems predominantly the WASD keys. Close Synapse 3 this morning and ran around without issues for an hour or 2 so convinced it's synapse related but maybe need a longer test.
Another buyer of a Tartarus Pro here, another victim of this bug.
For me its the WASD keys which are getting stuck randomly. I didn’t try without Synapse but I guess it would solve the issue as other people stated.
I can’t understand why Razer doesn’t react and solves the issue, especially if it is only a software issue.
! now hope that one of their other keyboards gets the same problem as it will maybe leads them to really tackle the issue if it impacts more people.
It is really a shame as the Tartarus Pro completely fulfills the need for a gaming keypad in my setup.
For me its the WASD keys which are getting stuck randomly. I didn’t try without Synapse but I guess it would solve the issue as other people stated.
I can’t understand why Razer doesn’t react and solves the issue, especially if it is only a software issue.
! now hope that one of their other keyboards gets the same problem as it will maybe leads them to really tackle the issue if it impacts more people.
It is really a shame as the Tartarus Pro completely fulfills the need for a gaming keypad in my setup.
Zwory1
Not sure if this helps but I remapped the WASD keys to the arrow keys on the keyboard and no lockups anymore.
I've done that and the issue persists for me
NoahArk620
Just to answer your question. I had used on a USB A hub before, and the issue persisted. As a matter of fact, I started using this device through a USB A hub device, and thought it was the problem at first. xD
thanks for answering. now i wonder whether there is a way for synapse to ignore specific devices? i'm using razer blade so i need synapse for setting its performance profile. if there is, i can just ignore the tartarus from synapse and use reWASD or something else to remap the keys haha
Ahiru
I just want a fix for this issue already...
not to be pessimistic but i got my tartarus pro for the equivalent of 55 usd brand new so there's a chance that may be they're already giving up on this product lol
I just want a fix for this issue already...
Daisame
Razer Support likes to send automated emails to folks with open cases asking if they are still having their reported problem. So instead of having to respond to them manually, I set up an automatic reply to their automated email letting them know that the issue has not been resolved.
:big_grin_: Lolololol!! :stuck_out_tongue_winking_eye_:
Razer Support likes to send automated emails to folks with open cases asking if they are still having their reported problem. So instead of having to respond to them manually, I set up an automatic reply to their automated email letting them know that the issue has not been resolved.
teguhash
Hello,
Just purchased Tartarus Pro recently and got this issue as well. It's infrequent may be like once in a 2 hour session but it's still frustating.
I read on reddit some people mentioned that the problem doesn't affect them when using a usb A hub. anybody have tried this and confirm whether it's true? i only have access to usb c hub right now and can confirm that the problem still persists when using usb c hub.
Thank before
Just to answer your question. I had used on a USB A hub before, and the issue persisted. As a matter of fact, I started using this device through a USB A hub device, and thought it was the problem at first. xD
Yeah the problem is with Synapse (for most if not all of us). The Issue goes away without Synapse installed. But does not matter what you map to what with Synapse because all of the keys will have this 'stuck' behavior, even the d-pad. So eventually, you will see it again... assuming you are using Synapse.
Zwory1
Not sure if this helps but I remapped the WASD keys to the arrow keys on the keyboard and no lockups anymore.
Hello,
are you using synapse to remap the keys? or are you using other software?
cpoChiD
so while using the Tartarus V2, the d pad sticks and you keep moving in one direction till u press the same direction again. I know a lot of people have this problem while looking through the forums and the one solution is to delete razer synaps. but unfortunately I use a lot of razer products and that's the best way to match and customize RGB. so its either I deal with that annoying glitch and have cool colors and effects. or i delete synaps and don't deal with that glitch but now half my RGB features are useless. I was hoping to bring this back to the attention of the developers to see if u can make a small patch for synaps so the people who use the Tartarus can enjoy there gaming and RGB lights at the same time. Please and thank you.
Not sure if this helps but I remapped the WASD keys to the arrow keys on the keyboard and no lockups anymore.
Support finally said they have escalated my ticket to the development team and not to expect any further communication. I just need to keep the software updated to see if it ever gets fixed. Needless to say, I am not holding my breath. And if I uninstall Synpase to use reWASD or some other software, not like I will ever see it.
teguhash
Hello,
Just purchased Tartarus Pro recently and got this issue as well. It's infrequent may be like once in a 2 hour session but it's still frustating.
I read on reddit some people mentioned that the problem doesn't affect them when using a usb A hub. anybody have tried this and confirm whether it's true? i only have access to usb c hub right now and can confirm that the problem still persists when using usb c hub.
Thank before
That is interesting. I normally don't use a hub with controller type devices, like keyboards or mice. I may give it a try. I have watched a hardware video recently saying that not all hubs or even build in USB controllers have discrete control chips per USB port. For some applications, this reportedly can cuase issues with high end flightsticks that operatate on those types of ports. So it makes sense to me anyway, that this COULD be a problem with this controller if it is on a USB port that is sharing a control chip with another used port. Of course a hub should not change that. If anything it seems like it could make the issue worse.
Hello,
Just purchased Tartarus Pro recently and got this issue as well. It's infrequent may be like once in a 2 hour session but it's still frustating.
I read on reddit some people mentioned that the problem doesn't affect them when using a usb A hub. anybody have tried this and confirm whether it's true? i only have access to usb c hub right now and can confirm that the problem still persists when using usb c hub.
Thank before
Just purchased Tartarus Pro recently and got this issue as well. It's infrequent may be like once in a 2 hour session but it's still frustating.
I read on reddit some people mentioned that the problem doesn't affect them when using a usb A hub. anybody have tried this and confirm whether it's true? i only have access to usb c hub right now and can confirm that the problem still persists when using usb c hub.
Thank before
So i think I broke Razer Support team right now. They ‘escalated’ my case for the nth time, but this time, no more bots reminding me to *bump* every 3 days now. I had never felt so much inner peace in such a long time.
but the issue still persists, so I still trudge on.
@Razer.Speedcr0ss , we still waiting for your response.
but the issue still persists, so I still trudge on.
@Razer.Speedcr0ss , we still waiting for your response.
I'm going to pile on here. Tartarus Pro, same issue, super frustrating, just fix it already. My Tartarus Pro is sitting in a drawer while I bring back my Nostromo. Can you do all those pesky customers a favor and fix your synapse software so that the premium device that they paid for can actually work as intended?
Rodorn
Yes, thank you, that helps. A follow up question. Did you just uninstall synapse or the drivers as well?
... But when I was deep in the weeds of troubleshooting ...?? Is that what you meant? ... If so, then yeah: I uninstalled Synapse as well as the drivers as well as alllllll trace files in all folders, every time.
Rodorn
Yes, thank you, that helps. A follow up question. Did you just uninstall synapse or the drivers as well?
I only logged out and exited Synapse -- I didn't uninstall it entirely.
(although, when I was particularly frustrated, it was very tempting to uninstall it! haha!)
... I still keep it around, but I only launch it periodically to briefly check if there's any updates to apply. Deep down (waaaay deep down), I'm an optimist ... I keep hoping that Razer will provide an update/patch/driver update which will fix everything. :wink_:
Page 6 / 20
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.