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 17 / 20
I was really looking into buying Tartarus but this thread disgusts me. Stucking of keys is really a serious issue for such expensive product marketed towards gamers.
I'm sorry, I got a bit lost, did the "Hid Compliant Game Controller" solution help you all or not?
TL;DR: There will be no changes, till this problem is mentioned in the main (hardware) media with a title like 'Razer faces random stucking key problems for over a year'. So, swarm out. Inform your local media about this mess.
Let’s point out some facts, guys. Cause in my opinion this rules out a lot of theorys on how to fix this without the support of Razer. First fact: We are facing a problem specific with the key_up-Event that - more or less randomly - is missing or got lost. This leads to the noticing of stucking keys. Second fact is, they are obviously physically not stucking. As alexxedo in post #364 pointed out, the key_up frame is already missing on USB level. I'll take this as fact three. Another - interesting but maybe overseen - point from him is the fact that the communication changes when Synapse is started (go back and read his post again!). And this makes even more sense, as we already knowing, that the behavior goes away, when we close Synapse (fact four).
What does fact four mean? Why does the behavior change? And what does this mean? Well, as background knowledge you must know that USB-2 has (to simplify it) two modes: Slow and Fast. Slow is usually enough speed for a typical keyboard. When Synapse is not open our Tartarus' stay in this default mode acting as a (kind of) normal keyboard. So why the change when Synapse is started? In my opinion is has mainly to do with latency. Fast mode has (for this kind of application) a lot less latency. (Latency = The time between when a key is pressed physically and when the computer is notified about that.) Using Fast-Mode lowers the latency on this part by the factor of 10 or so, making you feel the input as 'more direct'. (Which is also the selling point of the Tartarus Pro: again lower latency.) So using ReWASP or making the Tartarus as 'default HID device' (HID = Human Input Device) lets you not only loose the lighting but also the latency decrease.
So, where could be the root cause of this problem. Is it in the Tartarus firmware? Or a Driver/Synapse-Problem? Or could it even be a hardware combo problem, that it is specific to the USB-Port you are using? The last theory - in my opinion - can be ruled out for the most of us. It can be true that this is true for a tiny minority, but not for the most of us. The problem of the missing key_up event is waaaaay to specific for that. Or does a majority notifies missing key press events (you press a key and nothing happens)? In my case it is >always<, without any miss, key_up/stuck key. So problem must be in the firmware or the driver? And I would guess - based of alexxedo findings - that it is the firmware. Which leads me to 'Why does Razer doesn't fix it'? Well, usually you do not code a firmware – line by line - from scratch. You use librarys from your chip supplier. Razer is not a chip company, they pretty sure using librarys. And if there is a >hard to replicate< bug in a library, you must put a lot of effort in convincing your supplier to fix it. You, by yourself, couldn't do this, because you have no access to the library code.
So, is this good? No. And there will be no changes, till this problem is mentioned in the main (hardware) media with a title like 'Razer faces random stucking key problems for over a year'. So, swarm out. Inform your local media about this mess. Then - and only then - there is maybe enough pressure that this problem is getting fixed.
Let’s point out some facts, guys. Cause in my opinion this rules out a lot of theorys on how to fix this without the support of Razer. First fact: We are facing a problem specific with the key_up-Event that - more or less randomly - is missing or got lost. This leads to the noticing of stucking keys. Second fact is, they are obviously physically not stucking. As alexxedo in post #364 pointed out, the key_up frame is already missing on USB level. I'll take this as fact three. Another - interesting but maybe overseen - point from him is the fact that the communication changes when Synapse is started (go back and read his post again!). And this makes even more sense, as we already knowing, that the behavior goes away, when we close Synapse (fact four).
What does fact four mean? Why does the behavior change? And what does this mean? Well, as background knowledge you must know that USB-2 has (to simplify it) two modes: Slow and Fast. Slow is usually enough speed for a typical keyboard. When Synapse is not open our Tartarus' stay in this default mode acting as a (kind of) normal keyboard. So why the change when Synapse is started? In my opinion is has mainly to do with latency. Fast mode has (for this kind of application) a lot less latency. (Latency = The time between when a key is pressed physically and when the computer is notified about that.) Using Fast-Mode lowers the latency on this part by the factor of 10 or so, making you feel the input as 'more direct'. (Which is also the selling point of the Tartarus Pro: again lower latency.) So using ReWASP or making the Tartarus as 'default HID device' (HID = Human Input Device) lets you not only loose the lighting but also the latency decrease.
So, where could be the root cause of this problem. Is it in the Tartarus firmware? Or a Driver/Synapse-Problem? Or could it even be a hardware combo problem, that it is specific to the USB-Port you are using? The last theory - in my opinion - can be ruled out for the most of us. It can be true that this is true for a tiny minority, but not for the most of us. The problem of the missing key_up event is waaaaay to specific for that. Or does a majority notifies missing key press events (you press a key and nothing happens)? In my case it is >always<, without any miss, key_up/stuck key. So problem must be in the firmware or the driver? And I would guess - based of alexxedo findings - that it is the firmware. Which leads me to 'Why does Razer doesn't fix it'? Well, usually you do not code a firmware – line by line - from scratch. You use librarys from your chip supplier. Razer is not a chip company, they pretty sure using librarys. And if there is a >hard to replicate< bug in a library, you must put a lot of effort in convincing your supplier to fix it. You, by yourself, couldn't do this, because you have no access to the library code.
So, is this good? No. And there will be no changes, till this problem is mentioned in the main (hardware) media with a title like 'Razer faces random stucking key problems for over a year'. So, swarm out. Inform your local media about this mess. Then - and only then - there is maybe enough pressure that this problem is getting fixed.
Strange thing, I started my computer normally today, as always, after logging into windows, the synpase 3 installer popped up.
I turned it off and went back to work.
In the evening, I uninstalled reWASD and installed Synapse 3.
I don't know if my keypad has broken or if it has been updated, but my scroll has stopped working.
But after 2.5 hours of game, no problems (no sticking keys).
Maybe it's a coincidence that my Tartarus Pro broke down (scroll) and Synapse worked normally for 2.5 hours.
P.S. All HID drivers are enabled.
I've reinstalled Synapse twice, my scroll still doesn't work.
I turned it off and went back to work.
In the evening, I uninstalled reWASD and installed Synapse 3.
I don't know if my keypad has broken or if it has been updated, but my scroll has stopped working.
But after 2.5 hours of game, no problems (no sticking keys).
Maybe it's a coincidence that my Tartarus Pro broke down (scroll) and Synapse worked normally for 2.5 hours.
P.S. All HID drivers are enabled.
I've reinstalled Synapse twice, my scroll still doesn't work.
Seegeth
I'm sorry, I got a bit lost, did the "Hid Compliant Game Controller" solution help you all or not?
Seems to not fix the issue for me.
Looks like the scroll wheel has broken.
Tartarus is still sticking up.
I am going back to reWASD.
Tartarus is still sticking up.
I am going back to reWASD.
bizBarnRedsource043
I was really looking into buying Tartarus but this thread disgusts me. Stucking of keys is really a serious issue for such expensive product marketed towards gamers.
Don't waste your money!
OK here is my Theory on this... we are missig the keyUp events due to interference.
What points would support it?
- The USB connection behaves differently when Synapse is started, which could be because it increases the Bandwidth the Keyboard is communicating to reduce latency.
- We know that higher bandwidth requires better quality cables. I Have some First hand expirience with bad HDMI cables that were not up to the spec causing Frame dropping and flickering.
- I had problems with the Tartarus Pro like every 1-2 hours. My tatarus pro was cable-managed together close to my pc's power cable. Then i tried the Taratus V2 with cable just thrown off the desk and it worked. Then i switched back with the Pro with the same cable route as the v2 had and its working for 2 days now.
- Razer has hard time reproducing it - which could be because of the nature of interferrence that is very specific to the gaming setup.
- Razer points out to not use switches and USB extenders and use the USB ports on the back of the PC. The whole reason behind this is to get a as-clean-as-possible communication channel between the keyboard and the PC.
- After RMA with new hardware, the problems seems to stay (because the cable type and route is the same).
- The Problem seems to appear at a different rate (times per hour) to different users - with the possibe explanation that the inteferrence is unique to the user.
What points would speak against it?
- Looks like only the KeyUp-Event is affected and interferrence would affect all events.
- Possible Explanation for the Pro: having it using analoge switches would mean that there are multiple key-down events with different pressure depths, and this redundancy counters the loss of a single event.
How to Fix/Confirm:
- Try a different route of the Cable to your Pc, as far away from other cables, especially the 110/220/230V AC power line ones, but also speaker and other usb cables.
- If you have the expirience with dissassebly and soldering, you could solder a new cable to the unit that has better shielding. If you do, please report back if it fixes the Problem!
- Just a guess as im not an electric engeneer: Adding an ferrite core could help, but i have not tried it.
What points would support it?
- The USB connection behaves differently when Synapse is started, which could be because it increases the Bandwidth the Keyboard is communicating to reduce latency.
- We know that higher bandwidth requires better quality cables. I Have some First hand expirience with bad HDMI cables that were not up to the spec causing Frame dropping and flickering.
- I had problems with the Tartarus Pro like every 1-2 hours. My tatarus pro was cable-managed together close to my pc's power cable. Then i tried the Taratus V2 with cable just thrown off the desk and it worked. Then i switched back with the Pro with the same cable route as the v2 had and its working for 2 days now.
- Razer has hard time reproducing it - which could be because of the nature of interferrence that is very specific to the gaming setup.
- Razer points out to not use switches and USB extenders and use the USB ports on the back of the PC. The whole reason behind this is to get a as-clean-as-possible communication channel between the keyboard and the PC.
- After RMA with new hardware, the problems seems to stay (because the cable type and route is the same).
- The Problem seems to appear at a different rate (times per hour) to different users - with the possibe explanation that the inteferrence is unique to the user.
What points would speak against it?
- Looks like only the KeyUp-Event is affected and interferrence would affect all events.
- Possible Explanation for the Pro: having it using analoge switches would mean that there are multiple key-down events with different pressure depths, and this redundancy counters the loss of a single event.
How to Fix/Confirm:
- Try a different route of the Cable to your Pc, as far away from other cables, especially the 110/220/230V AC power line ones, but also speaker and other usb cables.
- If you have the expirience with dissassebly and soldering, you could solder a new cable to the unit that has better shielding. If you do, please report back if it fixes the Problem!
- Just a guess as im not an electric engeneer: Adding an ferrite core could help, but i have not tried it.
shouldn't you be able to shield the cable externally without soldering then? that should be enough to prove the theory
@edit
from my side i can confirm that it helps to connect the cable directly to motherboard, i was using usb hub before and was getting the error every 5-10 minutes, now im sticking about 3x daily, still not perfect tho.
@edit
from my side i can confirm that it helps to connect the cable directly to motherboard, i was using usb hub before and was getting the error every 5-10 minutes, now im sticking about 3x daily, still not perfect tho.
Hi,
I have this exact same problem as well.
Razer Tartarus Pro
My serial number is: PM1947F36300746, I have just opened a case, with number:
210805-002921.
I do not believe it is the synapse software at all, I have had this issue from day 1, been waiting for a firmware or software update to fix it and nothing until now. It is too frustrating to play like this. I bought mine from amazon UK.
This is what i have tried:
Total removal of synapse and re install no difference.
I tried the reWASD software fix but this is only a partial fix, when I use the reWASD indeed it does not get stuck until you press the same key again but instead gets stuck for around 1 second? 2 at most then will release by itself.
I have tried USB 2 and USB 3 ports, I also recently upgraded my pc completely, new motherboard, processor memory everything.
its a 10700k Intel I7, motherboard is Asus Z490F.
I also got a new SSD did a clean install of windows to see if maybe my windows was dodgy, downloaded fresh install from the internet microsoft website.
I installed only graphics drivers and motherboard software, also updated motherboard firmware.
Installed fresh synapse same problem.
I did notice though if i set the dpad to work as a joystick using synapse I get the same result as with reWASD it will only stick for 1 to 2 seconds then release but it is enough to cause havoc ingame. This happens in multiple games but the ones I play most and notice is wow and FFXIV.
It really is a pity as it is a good device and I am super happy with it besides this issue which makes it unusable really..
In relation tot he last post my cable runs clear to the PC nothing that should interfere with it at all, connected to front USB case ports Thermaltake 71 TG RGB and i connected directly to motherboard USB at the back. when in the front only other cable near it is for my mouse, no power cables or anything crazy that should be able to cause any kind of interference.
I also feel this is hardware/firmware issue. My Device is clean and no dirt or dust under the keys.
Can anyone else confirm the 1 to 2 second stuck key using reWASD?
I have this exact same problem as well.
Razer Tartarus Pro
My serial number is: PM1947F36300746, I have just opened a case, with number:
210805-002921.
I do not believe it is the synapse software at all, I have had this issue from day 1, been waiting for a firmware or software update to fix it and nothing until now. It is too frustrating to play like this. I bought mine from amazon UK.
This is what i have tried:
Total removal of synapse and re install no difference.
I tried the reWASD software fix but this is only a partial fix, when I use the reWASD indeed it does not get stuck until you press the same key again but instead gets stuck for around 1 second? 2 at most then will release by itself.
I have tried USB 2 and USB 3 ports, I also recently upgraded my pc completely, new motherboard, processor memory everything.
its a 10700k Intel I7, motherboard is Asus Z490F.
I also got a new SSD did a clean install of windows to see if maybe my windows was dodgy, downloaded fresh install from the internet microsoft website.
I installed only graphics drivers and motherboard software, also updated motherboard firmware.
Installed fresh synapse same problem.
I did notice though if i set the dpad to work as a joystick using synapse I get the same result as with reWASD it will only stick for 1 to 2 seconds then release but it is enough to cause havoc ingame. This happens in multiple games but the ones I play most and notice is wow and FFXIV.
It really is a pity as it is a good device and I am super happy with it besides this issue which makes it unusable really..
In relation tot he last post my cable runs clear to the PC nothing that should interfere with it at all, connected to front USB case ports Thermaltake 71 TG RGB and i connected directly to motherboard USB at the back. when in the front only other cable near it is for my mouse, no power cables or anything crazy that should be able to cause any kind of interference.
I also feel this is hardware/firmware issue. My Device is clean and no dirt or dust under the keys.
Can anyone else confirm the 1 to 2 second stuck key using reWASD?
yeah I think I know the fix. the previous temp fix is to use rewasd to remap the keys. first you need to understand that rewasd allows you to emulate a controller with mouse and keyboard. this means that your mouse and keyboard will have aim assist on fps games.
Most pc games don't allow you to use BOTH mnk and controller. if you turn 1 on, the other one shuts down. it looks like the joystick on the tartarus is somehow based on controller input while the rest of the device is mouse and keyboard input. if you use your joystick, certain games will think you are using a controller and will shut your mouse and keyboard down, and vice versa.
the fix is to entirely remove the joystick and make it mechanical like how it is on a keyboard, and to make the joysticks input a keyboard, don't make it's input a controller joystick.
Most pc games don't allow you to use BOTH mnk and controller. if you turn 1 on, the other one shuts down. it looks like the joystick on the tartarus is somehow based on controller input while the rest of the device is mouse and keyboard input. if you use your joystick, certain games will think you are using a controller and will shut your mouse and keyboard down, and vice versa.
the fix is to entirely remove the joystick and make it mechanical like how it is on a keyboard, and to make the joysticks input a keyboard, don't make it's input a controller joystick.
Well i have returned mine to amazon, got a new one and problem persists.
using rewasd and setting as keyboard is the standard I still have the issue where it will be stuck for around a second. not wasting more time on this.
I am giving up on the razer shit honestly they don't seem to care.
Even when you open a case with them it still seems they have never heard of this.
I have pre ordered an azeron cyborg waiting on that then I will return this pile of crap and never again.
I will also never recommend a razer product again. there are other good options out there.
using rewasd and setting as keyboard is the standard I still have the issue where it will be stuck for around a second. not wasting more time on this.
I am giving up on the razer shit honestly they don't seem to care.
Even when you open a case with them it still seems they have never heard of this.
I have pre ordered an azeron cyborg waiting on that then I will return this pile of crap and never again.
I will also never recommend a razer product again. there are other good options out there.
Hello. i ve got the same issue with my tartarus v2: random key stuck and i must press the key again to stop the strange behavior.
it works perfectly on my Latop and on my "old" i7 computer. I have the issue on my new Ryzen Computer.. with a fresh windows install.
any news for this bug ?
too bad, i really enjoy the Tartarus....
it works perfectly on my Latop and on my "old" i7 computer. I have the issue on my new Ryzen Computer.. with a fresh windows install.
any news for this bug ?
too bad, i really enjoy the Tartarus....
meanwhile, i have tried another tartarus pro, brand new and the issue persists. i have bought an pci usb adapter as i thought it may be a problem with the usb chipset, but that did not change a thing. i have a new ryzen 5900x system with x570 mainboard.
i also tried adding ferrite belts to the cable, did also change nothing.
i have read somewhere that a user on reddit was able to resolve the problem by using an usb hub. this is what i test now.
i also tried adding ferrite belts to the cable, did also change nothing.
i have read somewhere that a user on reddit was able to resolve the problem by using an usb hub. this is what i test now.
friends, remember, the problem is in Synapse
KAWAiiSONG
friends, remember, the problem is in Synapse
Im not really sure on this. In this thread there was a user stating that as soon as synapse is installed, the keypad behaves differently, like it goes from "normal basic keyboard" to "low latency full feature" mode or from digital to analog or something. Also some user used an usb debugger and said that the keyup signal does not reach the pc - so its not the synapse software that ignores it.
while it is clear that removing synapse "fixes" the problem, we are an minority. Obviously, most users do not have this Problem.
We also know that its not related to the individual keypad hardware, as every report i have read said "got a new one, problem stays".
If we accept all this as proven (where the usb debug thing is a single source, and im not sure if it was hardware- or software debugging), it must be something that happens between the keypad and the os usb stack or/and synapse and it has to be something that is not keypad-hardware-related and only applies to a minority of users.
- some setting in synapse or key bindung that tiggers a firmware bug on the keypad that only we have set - and re-set everytime we try a new keypad - and we even do when resetting the synapse profile.
- maybe the keypad does not 100% implement the usb specification or our usb chipset does not.
- something related to our windows installation or a tool we all have installed that interfers with the usb. maybe we have a similar usb driver version or antivirus installed. maybe we have other usb devices or internal devices that cause problems.
- interference in the usb cable caused by other cables, wireless stuff, microwaves or similar, possibly paired with weak signaling of the keypad so it is affected while other hardware is not.
i only game on one pc. Can someone who switches between two pcs tell how it goes? same problem on both? same synapse profile? same settings?
IVoidWarrenties
meanwhile, i have tried another tartarus pro, brand new and the issue persists. i have bought an pci usb adapter as i thought it may be a problem with the usb chipset, but that did not change a thing. i have a new ryzen 5900x system with x570 mainboard.
i also tried adding ferrite belts to the cable, did also change nothing.
i have read somewhere that a user on reddit was able to resolve the problem by using an usb hub. this is what i test now.
i've tried the usb hub thing and the problem persists. have tried usb c hub and also usb a hub, don't know whether that makes a difference tho
I hafe the Tartarus now for 2 Weaks and the Sticky issue happend to me too 3 times now.. its NOT OK and its not with the DPAD only im using WASD still so i walk with the buttons not the dpad
I suppose it is worth adding my two cents. I am having this same issue with a huntsman mini keyboard, even after an RMA. Noticeable when play tac fps games, a number of situations I have found that I have physically released WASD but my character continues to move in game.
Note this is on my second huntsman mini - both keyboards have suffered the same issue.
Note this is on my second huntsman mini - both keyboards have suffered the same issue.
Tartarus Pro and Brand new Naga pro also have sticking key glitch clear reinstall \\ pc switch \\ usb switch connection type switch etc. nothing helps
lezt get thiss treight they hafe a bug which literly makes some razer parts unusabel incompetetiv games and they dont care?
For the love of Pete! could they just fix the Issue already! or stop selling broken equipment that does not work with their software.
Being a firm believer in Logitech, I thought to myself, well why not just try out razer and go for something which I believed was a premium product from a known "top" company, so I bought a Razer Tartarus Pro, quite an expensive piece.
The first week, this problem occurs, searched the Internet and would you look at that, Almost everyone is having this issue.
Until they actually fix this problem, I will never ever buy another Razer product in my life, will not recommend it to anyone, and steer people away from them. if they do not even care enough about their customers to help them out with what I have come to believe, a software problem, then what quality can you actually expect from them.
I am disgusted.
Being a firm believer in Logitech, I thought to myself, well why not just try out razer and go for something which I believed was a premium product from a known "top" company, so I bought a Razer Tartarus Pro, quite an expensive piece.
The first week, this problem occurs, searched the Internet and would you look at that, Almost everyone is having this issue.
Until they actually fix this problem, I will never ever buy another Razer product in my life, will not recommend it to anyone, and steer people away from them. if they do not even care enough about their customers to help them out with what I have come to believe, a software problem, then what quality can you actually expect from them.
I am disgusted.
2 days ago I got this from help desk:
I started to test it today on various games. Now I have 6 hours of gaming without the sticky key issue and synapse is running.
If you do not trust the links (which are official Razer short links) try to ask them for "PID0266MW_v0.1.4.092113.exe" patch.
1st link is EXE, 2nd and 3rd are registry keys to enable key logging... Dunno if they are needed. After more hours of test I'll revert the registry changes back to original.
- Clean reinstall Synapse 3 and make sure to use latest installer from the webpage
- Make sure keyboard is detected in Synapse 3 - update and restart where necessary
- “Exit all apps” from system tray
- Stop “Razer Synapse Service” from Task Manager
- Install the patches below in order
- https://rzr.to/MBvxKG
- https://rzr.to/ERJ1nS
- https://rzr.to/oJ1uz7
- Restart “Razer Synapse Service” from Task Manager
- Start Synapse 3 and log in to their account
- Test the keyboard again.
- If the issue persists, kindly compare the frequency of failure before and after installing the patch
I started to test it today on various games. Now I have 6 hours of gaming without the sticky key issue and synapse is running.
If you do not trust the links (which are official Razer short links) try to ask them for "PID0266MW_v0.1.4.092113.exe" patch.
1st link is EXE, 2nd and 3rd are registry keys to enable key logging... Dunno if they are needed. After more hours of test I'll revert the registry changes back to original.
i did a clean install and it happens only all 8 hours once its not like often
they need to understand that WASD (werever they are set ) are the most pressed keys and it will happen.... they need to find the bug ...
Page 17 / 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.