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 15 / 20
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
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.
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_:
I just want a fix for this issue already...
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
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
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
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.
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.
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.
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...
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?
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.
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.
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!
Has the Razer team left the chat? Why is there such silence on their part? the problem has not gone anywhere !!!
Ive come here to add that I just bought a tartarus v2 and started playing Apex with it. My movement keys WASD stick 2-3 times per game and thought it was a windows issue.. but now that i see this, its pretty obvious i bought a defective piece of hardware that razer has yet to fix.
bgzgamer
Ive come here to add that I just bought a tartarus v2 and started playing Apex with it. My movement keys WASD stick 2-3 times per game and thought it was a windows issue.. but now that i see this, its pretty obvious i bought a defective piece of hardware that razer has yet to fix.
The device is fine, the problem is in the Synapse 3.0 software
KAWAiiSONG
Has the Razer team left the chat? Why is there such silence on their part? the problem has not gone anywhere !!!
My Razer Support ticket has gone silent, and they closed it. So there won’t be any more news coming from them anymore now. @Razer.Speedcr0ss is the only hope we have now, but he has gone radio silent too.
Ok it seems we aren't gonna see any fix soon...
I don't understand why they do not want to fix this issue.
Are others peripherals than the tartarus line concerned by the problem ?
The other solution would be to wait for the guys of openrazer to release a windows version of their soft even if they aren't supporting the Tartarus pro yet.
I think I'll let a review on Amazon where I bought the product to warn other consumers so they don't buy it.
That's such a shame to have this bug, I bought a redragon K585 keypad and it does not match the tartarus in term of comfort and design.
I don't understand why they do not want to fix this issue.
Are others peripherals than the tartarus line concerned by the problem ?
The other solution would be to wait for the guys of openrazer to release a windows version of their soft even if they aren't supporting the Tartarus pro yet.
I think I'll let a review on Amazon where I bought the product to warn other consumers so they don't buy it.
That's such a shame to have this bug, I bought a redragon K585 keypad and it does not match the tartarus in term of comfort and design.
alexxedo
Ok it seems we aren't gonna see any fix soon...
I don't understand why they do not want to fix this issue.
Are others peripherals than the tartarus line concerned by the problem ?
The other solution would be to wait for the guys of openrazer to release a windows version of their soft even if they aren't supporting the Tartarus pro yet.
I think I'll let a review on Amazon where I bought the product to warn other consumers so they don't buy it.
That's such a shame to have this bug, I bought a redragon K585 keypad and it does not match the tartarus in term of comfort and design.
Yes, other devices also lag, I have a Razer Naga Pro and she does it too! however, I have a guess that there is something else besides Razer, my friend has a mouse G 600 and it also sticks with him! maybe Razer and Windows have a problem at the same time and they need to solve it together! We are waiting for the Windows 21H1 update
KAWAiiSONG
Yes, other devices also lag, I have a Razer Naga Pro and she does it too! however, I have a guess that there is something else besides Razer, my friend has a mouse G 600 and it also sticks with him! maybe Razer and Windows have a problem at the same time and they need to solve it together! We are waiting for the Windows 21H1 update
I don't think Windows has anything to do with this. Handling standard input of a mouse or a keyboard is the 101 of an operating system especially with input coming from a human user which is pretty damn slow. However if manufacturers implements faulty drivers of software this kind of things can happen.
Maybe the logic in Synapse is not processing the USB frames coming from the keyboard resulting in overwrites and then ignoring key release or the Firmware of the device is bugged when behaving in Synapse mode.
Going silent and not showing interest into solving the issue is maybe the worst thing they can do. It hurts their brand image a lot.
alexxedo
Going silent and not showing interest into solving the issue is maybe the worst thing they can do. It hurts their brand image a lot.
I don't think so, keypads are a very niche product and Razer has many other more popular products.
The problem has been known for a long time and has not been fixed until then. If they knew how to fix it, they would have done it.
The only chance is that it will accidentally be fixed during the Synapse 3 update.
In general, you have to accept that the situation will not change and use third-party programs or hide the keypad in the drawer and that's it.
Was almost gonna buy this, hope there is a fix soon.
Tartarus looks really good, sucks that it unusable right now.
Tartarus looks really good, sucks that it unusable right now.
Seegeth
I don't think so, keypads are a very niche product and Razer has many other more popular products.
The problem has been known for a long time and has not been fixed until then. If they knew how to fix it, they would have done it.
The only chance is that it will accidentally be fixed during the Synapse 3 update.
In general, you have to accept that the situation will not change and use third-party programs or hide the keypad in the drawer and that's it.
Others products seems to have the issue they have to fix it in the end.
Meanwhile this experience means the tartarus is going to be my last razer product. And I am going to advice my friend to avoid the brand in the future.
Page 15 / 20
Sign up
Already have an account? Login
Log in with Razer ID to create new threads and earn badges.
LOG INEnter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.