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 7 / 20
side note if you press the same key on your other keyboard it also stops the the input, just thought i would try it earlier when it happened
also tried dcing other keyboard. that did not change anything either
also tried dcing other keyboard. that did not change anything either
Thanks for the idea. I never hit a key on my keyboard at the same time as a key on the Tartarus. I do though click mouse buttons at possible the same time. But not often.
I just had it happen a couple of times in the last hour in Space Engineers. There was no other input but perhaps more than one key on the Tartarus itself. It certainly does happen dozens of times per hour, but probably once every hour or two. So if there was some debugging, they SHOULD be able to see it happen. I could probably do it on a word processor and see it 'stick' after an hour or two. As much as it happens, I would think Razer would be able to find it. This is a critical function of the Tartarus... so it needs to be identified and corrected. Razer should be applying reasonable resources to getting this fixed as quickly as possible.
I just had it happen a couple of times in the last hour in Space Engineers. There was no other input but perhaps more than one key on the Tartarus itself. It certainly does happen dozens of times per hour, but probably once every hour or two. So if there was some debugging, they SHOULD be able to see it happen. I could probably do it on a word processor and see it 'stick' after an hour or two. As much as it happens, I would think Razer would be able to find it. This is a critical function of the Tartarus... so it needs to be identified and corrected. Razer should be applying reasonable resources to getting this fixed as quickly as possible.
spent a bit more time looking into the razer mini and well i have no hope now.
July 14 2020 was the release date for the huntsman mini
firmware to fix the bug was released on 24 Sep 2020
so yeah over a year for the tartrus . When it took them 72 days to fix the problem FROM the release of the product. not the first topic on the fault, so it prob took them lets say 40-50 days max to fix. now that is kind of crazy, kind of shows how little they care about this product if they can fix the same fault on that so fast
it's the firmware if you wanted to see for yourself
https://mysupport.razer.com/app/answers/detail/a_id/3609/
July 14 2020 was the release date for the huntsman mini
firmware to fix the bug was released on 24 Sep 2020
so yeah over a year for the tartrus . When it took them 72 days to fix the problem FROM the release of the product. not the first topic on the fault, so it prob took them lets say 40-50 days max to fix. now that is kind of crazy, kind of shows how little they care about this product if they can fix the same fault on that so fast
it's the firmware if you wanted to see for yourself
https://mysupport.razer.com/app/answers/detail/a_id/3609/
It did it a couple more times just now, and then a few minutes later Synapse software crashed, making all inputs cease, since even detault keystrokes don't work when the software crashes aparently.
The issue is Synapses software. If you use the the damn thing with out the software and map the tarturas from the games instead of the synapses you get no issues. Unfortunately most of us are invested with alot of mapped key through synapses so re doing all of this in game sucks hard but it will get rid of the issue. well at least for me. havent tried the reWASD yet because i often use the scroll wheel mapping, but will give it a go.
I agree. I tweeted at Razer today and they had me 'update' the Razer Synapse software. This is a brand new install on a brand new PC. And it did it on my old rig too. So definitely local to the keybad or software. I have not tried to do without the software. I may try that next, since they don't seem to care about fixing their software.
There are some other software to control separate devices other then rewasd. Scroll is configurable too.
Hid macros
HidKeySequence
KeytoKey keytokey-dev.net/
OpenRGB for backlit. But it cant into per profile or per keymap lighting. Only once and for all
Hid macros
HidKeySequence
KeytoKey keytokey-dev.net/
OpenRGB for backlit. But it cant into per profile or per keymap lighting. Only once and for all
I sent my device for a RMA. I have very low expectations that it will help, but I want to be sure that I have done everything I could.
Seegeth
I sent my device for a RMA. I have very low expectations that it will help, but I want to be sure that I have done everything I could.
I did the same last year in November, I still have the same problem, haha.
I hate to be the bearer or bad news but I would not hold my breath on a fix anytime soon. This exact problem has persisted even prior to Synapse being released and goes at least as far back as the software that was used to control the old nostromo keypads. I have tried absolutely every fix under the sun on every software version they have released and on several different keypads and the only thing I have learned is that it is absolutely a software issue but must be deep deep in the code somewhere for it to persist as it has. The only fix i have found is to not use synapse and use reWASD to remap....you lose some functionality but at least you will stop uncontrollably running out into the open and getting your ass shot off
here ya go, this seem familiar to everyone? This is from 2012....
(*Omitted)
(*Omitted)
For the past few years, I have used the Razer Orbweaver which uses Synapse 2, and I've never had this problem. Unfortunately, the Razer Orbweaver is hard to buy now, so I bought the Razer Tartarus.
pulseinteractive043
here ya go, this seem familiar to everyone? This is from 2012....
*Omitted /QUOTE]
I remember this video from ages back, which makes me hesitant on buying a gaming keypad from Razer for a very long time. But just reading through the comments now, it suggests that Razer do release software driver fixes for it later down the line.
pulseinteractive043
I hate to be the bearer or bad news but I would not hold my breath on a fix anytime soon. This exact problem has persisted even prior to Synapse being released and goes at least as far back as the software that was used to control the old nostromo keypads. I have tried absolutely every fix under the sun on every software version they have released and on several different keypads and the only thing I have learned is that it is absolutely a software issue but must be deep deep in the code somewhere for it to persist as it has. The only fix i have found is to not use synapse and use reWASD to remap....you lose some functionality but at least you will stop uncontrollably running out into the open and getting your ass shot off
can vouch for rewasd been great since using that. Will prob just pay the £5 for the software as it's cheap, also they are working on putting extra features in the software for this keypad. they will, probably have rgb full macro etc working before razer get's anywhere at this point
I have been trying to work through Razer support through twitter, since they don't seem to have an actual support page here (asside from these forums, that don't seem to get any responses from Razer staff). They want a video. I don't have equipment to make a video, not that I understand what possible use a video would be. This is not a difficult concept to understand how it is described. Maybe I should just send them that Battlefield video from 2012.
Twitter support is now saying that if I don't have a video of the issue, they cannot support me. WTF!? I am asking if that other person's video from 2012 would suffice. Razer needs to have a note on all their product postings that users must be able to take video of any issues to get support.
I have the Logitech g13 and a Nostromo nut want to buy a new one since the ones I have are very dated. The Nostromo has 1 key that doesn't work altogether and 2 that stick, must be a on going issue with razer. The Logitech has a few minor issues but has be reliable for many years. Other than key sticking how is it and is it a mech keypad on the Tartarus?
Just to be clear. the keys on my unit don't ACTUALLY PHYSICALLY stick. THey just act as if they are. And it is not just the keys, the d-pad does the same. I love the layout of the Tartarus, and asside from the sticky inputs, the keys feel great. If it were not for the sticky input and the horrible customer service, I would highly recommend it. I used a Nostromo N52 when it was created by Belkin back in the day. Think I still have that pad somewhere. I have tried the Logitech keybpad but did not like it's layout nearly as much. I really wish they would fix the issue with the Tartarus because it would be awesome if not for this one issue.
Daisame
I have been trying to work through Razer support through twitter, since they don't seem to have an actual support page here (asside from these forums, that don't seem to get any responses from Razer staff). They want a video. I don't have equipment to make a video, not that I understand what possible use a video would be. This is not a difficult concept to understand how it is described. Maybe I should just send them that Battlefield video from 2012.
As similar as Nostromo’s issue is to the current Tartarus V2/Pro, you must focus on showing the video that is based on Tartarus V2/Pro. All you need to do is record the issue when it shows itself on your phone, and that is usually good enough.
topher82
I have the Logitech g13 and a Nostromo nut want to buy a new one since the ones I have are very dated. The Nostromo has 1 key that doesn't work altogether and 2 that stick, must be a on going issue with razer. The Logitech has a few minor issues but has be reliable for many years. Other than key sticking how is it and is it a mech keypad on the Tartarus?
Tartarus Pro uses their latest Analog Optical Switches which functions very similar to red cherry mx switches.
Userlevel 7
- Razer Support
- 7595 replies
-
13 February 2021
Hey everyone! Were you able to update your Razer Synapse to version 3.6.130.11816? Please let me know if it made an impact on your gaming keypad's performance. Our devs want to get feedback from this thread. I appreciate your PMs and responses.
NoahArk620
As similar as Nostromo’s issue is to the current Tartarus V2/Pro, you must focus on showing the video that is based on Tartarus V2/Pro. All you need to do is record the issue when it shows itself on your phone, and that is usually good enough.
The Problem with this request, is that it can be hard to record something that happens one every hour or so. I THOUGHT I was able to catch an incident last night, but my phone did not actually record it. The second problem with this request is that it should not make a difference. If they only want it to 'prove' that I have this issue, then fine, but it does not help anyone solve the problem. If they don't understand the problem, then ANY video that shows the same issue would suffice to show what the problem looks like.
Razer.SpeedCr0ss
Hey everyone! Were you able to update your Razer Synapse to version 3.6.130.11816? Please let me know if it made an impact on your controller's performance. Our devs want to get feedback from this thread. I appreciate your PMs and responses.
I already am running this version. Unless it updated this morning without me seeing it, I had the issue last night so it did not solve it.
Userlevel 7
- Razer Support
- 7595 replies
-
14 February 2021
Daisame
I already am running this version. Unless it updated this morning without me seeing it, I had the issue last night so it did not solve it.
Thanks for letting me know. Does the same behavior happen when it is connected to a different computer? By the way, when and where did you buy the mouse? If you are residing outside the US and bought it from a reseller, please contact the store and request a replacement. Otherwise, submit a case to our Support Team or send me a PM so I can assist you in creating one.
Razer.Speedcr0ss
Thanks for letting me know. Does the same behavior happen when it is connected to a different computer? By the way, when and where did you buy the mouse? If you are residing outside the US and bought it from a reseller, please contact the store and request a replacement. Otherwise, submit a case to our Support Team or send me a PM so I can assist you in creating one.
Cosnidering it happened on my old gaming rig and it happens on my new freshly installed system... yes. I also have a case opened with support. [Vorgang: *Omitted]
Do any Razer employees use there own products?
It seem hard to believe none of them have experienced this issue.
It does seem to be widespread.
Maybe someone at Razer should take one home, map the WSAD Keys to the d-pad and play any FPS for more then 1 hour.
It seem hard to believe none of them have experienced this issue.
It does seem to be widespread.
Maybe someone at Razer should take one home, map the WSAD Keys to the d-pad and play any FPS for more then 1 hour.
Page 7 / 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.