Razer Tartarus V2 controller D-pad sticking / glitch | Razer Insider

Razer Tartarus V2 controller D-pad sticking / glitch



Show first post
This topic has been closed for comments

490 Replies

Yes, thank you, that helps. A follow up question. Did you just uninstall synapse or the drivers as well?
No, @Rodorn ... Over the last few months on this thread (somewhere back around page 12-15), a few of us have tried disabling the HID (Human Interface Device) for the Tartarus alone, to see if that would make a difference, but no ... it ultimately didn't work. The problem continued to return.

As for running both Synapse 3 and reWASD simultaneously, no ... it isn't really possible/advisable; you will end up with conflicts between the two.

For me, I am using reWASD only for the Tartarus.

I don't need to use reWASD for my mouse because my Razer Naga Trinity and my Logitech G600 mouse both have onboard memory. (use Synapse 3 or Logitech G-Hub initially to set up all your mouse button key-bindings, then they will be stored to onboard memory. So from then on, they will work without needing their native software running in the background).

I don't need to use reWASD for my Blackwidow keyboard, because I never made any customized key-bindings on my keyboard; I've always just used it at the factory defaults.

It is worth noting however that reWASD is capable of managing a few/several devices at once. This includes most gaming mice, keyboards, and controllers, if/when you ever want it to. I personally only need it to manage my Tartarus, ... but it's nice to know that it can manage more if I ever need it to.

As for the RGB lighting, the bad news is: no -- you won't be able to customize that lighting in reWASD like you can in Synapse. This sacrifice is a bummer. Now that I've divorced myself from Synapse 3, my Razer devices just cycle through the different colours at a slow/gradual cycle, which I think is the factory default. Even slightly more sad: the cycle on all three devices are not even synchronized, lol. So, my desktop doesn't LOOK as pretty as I would like it to ... but at least it finally WORKS again, which is what's most important.

I ended up going with the $20 version for two reasons:
(1) My frame of mind was just that frustrated. I was just, like, "take all my money; solve all my problems!" lol!
(2) I need a couple buttons to do macros; not just single keybinds. Macros are part of the premium package.
I don't regret a penny of it, but if all you need are single keybinds (which is fine for many/most users) then you'd probably be able to get away with just the $6 version.

My best advice here would be to just try the free trial. They will let you trial the basic version for two weeks free of charge, AND ... they will allow you to individually add in the premium features too, so that you can test drive them for three days free of charge.

Hope this helps!
the_novena
Sooo many of us have tried to provide everything they've asked for, numerous times ... followed all kinds of trouble shooting steps; collected and submitted Synapse log files; sent units back for further tech inspection, etc, etc, etc ... soooo many efforts to "help them help us" ... and still no satisfactory results.

When it became clear to me that Razer has given up on this issue, I was within inches of giving up on them.

THEN, a whole new issue: my Naga Pro developed issues of the left mouse button generating a double-click when only a single click was pressed. Sent it back on RMA but bought a Logitech G600 to use while I waited for a new Naga Trinity replacement. Razer's replacement arrived and I'm saving it (brand new in box) in case I ever have problems with the new Logitech G600. ... The mouse issue is off-topic from the Tartarus issue this thread is based upon, so I won't go off on a tangent, but suffice to say, this was my breaking point.

I paid for reWASD, and have enjoyed flawless gaming ever since. If anyone is on the fence about this third party software, honestly just choke up the small cost and do it -- it will save you a whooooole lot of grief!



Hi mate, I started having this issue just now, sent it to RMA as I suspect hardware fault as well, I will look into reWASD when it comes back. A quick question tho. Were you able to somehow disable it the keypad in razer synapse so you still had keyboard/mouse in synapse but keypad in reWASD? Or at least make lightning work without synapse?

And also what version did you buy? The basic 6 USD one or premium?
Sooo many of us have tried to provide everything they've asked for, numerous times ... followed all kinds of trouble shooting steps; collected and submitted Synapse log files; sent units back for further tech inspection, etc, etc, etc ... soooo many efforts to "help them help us" ... and still no satisfactory results.

When it became clear to me that Razer has given up on this issue, I was within inches of giving up on them.

THEN, a whole new issue: my Naga Pro developed issues of the left mouse button generating a double-click when only a single click was pressed. Sent it back on RMA but bought a Logitech G600 to use while I waited for a new Naga Trinity replacement. Razer's replacement arrived and I'm saving it (brand new in box) in case I ever have problems with the new Logitech G600. ... The mouse issue is off-topic from the Tartarus issue this thread is based upon, so I won't go off on a tangent, but suffice to say, this was my breaking point.

I paid for reWASD, and have enjoyed flawless gaming ever since. If anyone is on the fence about this third party software, honestly just choke up the small cost and do it -- it will save you a whooooole lot of grief!
Daisame
Razer support asked me to send my PC motherboard, CPU, and GPU Make and Model as well as the RAM. I told them I would but asked if they wanted it for the three different machines that experienced the issue. It surely is not tied to one hardware setup. It happened on 100% of the machines I have used. Although I have not tried it on my new laptop yet, so I could give them 4 different machine specs.

So after all these efforts to help them help you did you get any results????
Daisame


My Tweet to Razer and Razer Support

I do not see any signs of Razor actually caring about this problem. But I am also learning that the Tech world is not one to be praised for their communication skills. Good luck getting a fix.
I am definitely debating changing out the dpad for the Arduino/Thumbstick mod. I doubt this will be getting fixed in any of the current iterations of the Tartarus.


My Tweet to Razer and Razer Support
I have an old Logitech G13 that I can use, but prefer the keys and layout of the Tartarus. I loved the old Belkin Nostromo that this is based on. I just wish Razer's Synapse software was not such crap. I have been dabating paying the $20 for the reWASD software. It is an extra expense and pretty clunky, but it at least works. Which is more than can be said for Razer's software. I just want to hold Razer accountable for producing a working product, but it is exhausting going through the steps over and over again with each new support person. They need to get a Project Manager to lead this effort, collect all the reports, get a tiger team on their dev team and identify and solve this like the real problem that it is.
CptCraptacular
i think someone linked a video on youtube on here at some point just use that one for proof of "hardware problems" because if they can notice multiple people use the same video then maybe there is some hope they can fix the problem


Razer has let us down, they must know by now it is not a hardware glitch and yet straight faced they lie to us causing us to suffer hours of attempted fixes when it is all them. Angered that I died so many times due to the V2 and losing street cred and team mates that I have bought a new game pad. It is saving me time, memory, and grief. The Red Dragon DITI is working great for me right out of the box, with more buttons and cost less, does not have to update ever thus far, and is more comfortable for me. Good luck dealing with them.
Razer support asked me to send my PC motherboard, CPU, and GPU Make and Model as well as the RAM. I told them I would but asked if they wanted it for the three different machines that experienced the issue. It surely is not tied to one hardware setup. It happened on 100% of the machines I have used. Although I have not tried it on my new laptop yet, so I could give them 4 different machine specs.
Seegeth
Until this moment I tried

b. Connect the Tartarus to a different USB port or computer.
d. Repair Razer Synapse 3.0
e. Clean reinstall Razer Synapse 3.0


Nothing helped

I tried all these things also and finally after getting no help found a for sure fix for almost everyone. I just posted it, titled. How I fixed Tartarus V2 sticking keys.
No worries but thanks for the update. I've recently started using an Azeron but the jury is still out on whether it's going to be a workable solution (steep learning curve). If it doesn't work out, at least I'll have this as a fallback.
dfscott
To clarify the workaround: does reWASD let you map the thumbpad to keystrokes as well (e.g., wasd for movement) or do you lose that functionality as well? I could live without the scroll wheel but moving with the thumbpad is the main reason I use keypads.


Yes. Just remap the arrow keys, and it should take an effect. Give the trial a go before you make the decision to purchase the software.

Also, sorry for the late reply. There is quite literally no news on my end. The troubleshooting steps i mentioned (no brightness, default green static lighting, default keymapping) does not work on my end either, so we can still safely assume it is not related with Chroma SDK.
To clarify the workaround: does reWASD let you map the thumbpad to keystrokes as well (e.g., wasd for movement) or do you lose that functionality as well? I could live without the scroll wheel but moving with the thumbpad is the main reason I use keypads.
I was finally able to submit a video of the issue. You can all see it here :

I sent this to Razer support and they claim it is a hardware issue... again. 😞

I then asked them to please send as many units as it would take to rule this out as a hardare issue (being this is already the second unit I have tried) and I would try them one at a time until they all failed, or one worked. I think one of the other posts is right. They just try to wear down the resolve of their customers until we just forget about it or let it go.

Why is the community aparently working harder to solve this problem than Razer? The Tartarus Pro would be incredible if not for the POS Synapse software.
I have this issue as well with not only the D-Pad any longer. It seems the whole keypad now gets stuck at times. Happens a few times a gaming session on Warzone now. Really annoying when I aim down sight at it stays aimed down site when I'm walking in the open. Or when I have to do a full 360 click on the d-pad to unstick. Used to happen every once in a while and now seems to happens more and more often. Please fix this Razer. I love the Tartarus but this is really becoming annoying. I don't want to move my character with WASD. I want to move my damn character with my THUMB which is why I got the Tarturus.
Razer support wants a video again and run through the same steps as before with using a different cloud account. I am truly amazed at how Razer continues the same old script over and over again, seemingly without realizing it makes them look extremely foolish. I regret the day I bought the Tartarus Pro. I think I need to just give up on Razer ever taking this issue seriously and use a third party's key-remapping software and just never buy from Razer again. They will not get the picture until they stop selling product. And it seems like they would be clueless as to why their products don't sell any longer.
CptCraptacular
i think someone linked a video on youtube on here at some point just use that one for proof of "hardware problems" because if they can notice multiple people use the same video then maybe there is some hope they can fix the problem

I did that actually, Support did not 'want' a copy of someeone else's video. Unless they just want me to PROVE I am having the problem, there is literally no value to record a seperate video showing the exact same symptom. It should be very clear what the symptoms are at this point. Now we just need devs to look over debugging logs to find what is causing it and fix it.
That is 'hopefully' what their Log File Collector app does. You start this debugging program... play a game and duplucate your isssue, then stop the program to collect the logs. I did that and sent it in. I can only hope it has some sort of valuable data in those logs that can point to a problem.
Daisame
I sent the Razer Collector Logs to the support team after reproducing the issue on my Tartarus pro. However, I don't have ANY confidence that anyone is looking at it because the support person from my second case (because the initial case somehow confused them) is having me go through all the same steps over again. (Groan). They want a video of the issue happening... as if that is somehow going to magically tell them what the problem is with Synapse. They think it is STILL a hardware issue, after RMAing the last unit, and the issue not occuring when Synapse is not installed. This would be funny if it was not so frustrating.

It seems that the support team and development teams may not be communicating, or else they would not be asking us to do the same redundant troubleshooting steps over and over again. Or asking repeatedly for video of the issue.

i think someone linked a video on youtube on here at some point just use that one for proof of "hardware problems" because if they can notice multiple people use the same video then maybe there is some hope they can fix the problem
Daisame
I sent the Razer Collector Logs to the support team after reproducing the issue on my Tartarus pro. However, I don't have ANY confidence that anyone is looking at it because the support person from my second case (because the initial case somehow confused them) is having me go through all the same steps over again. (Groan). They want a video of the issue happening... as if that is somehow going to magically tell them what the problem is with Synapse. They think it is STILL a hardware issue, after RMAing the last unit, and the issue not occuring when Synapse is not installed. This would be funny if it was not so frustrating.

It seems that the support team and development teams may not be communicating, or else they would not be asking us to do the same redundant troubleshooting steps over and over again. Or asking repeatedly for video of the issue.


Anytime I do anything that involves troubleshooting for support where random is the problem effect it becomes an infinite, unresolvable communication problem with support. Had a similar issue with an AMD 290x video card randomly producing bizarre graphics effects in Fallout 4. Hundreds, probably thousands of people were having the same random effects. Never solved. I stopped using AMD cards as a result. This issue, for me and for others I see as I read through, is random. I presume for you too. So, how do you consistently reproduce random for support teams to look at? After the latest Synapse 3 update I played for two days and it didn't happen, then it did, though less consistently than it had been. The game I was in I tried reprogramming the movement keys for controllers, just to see if that might be the clue. Worked beautifully for walking and running, unfortunately vehicles wouldn't drive, had to switch to the keyboard wsad keys (mine's a Cynosa Chroma). Never stuck, but with random, who knows if that will be a forever fix?
I sent the Razer Collector Logs to the support team after reproducing the issue on my Tartarus pro. However, I don't have ANY confidence that anyone is looking at it because the support person from my second case (because the initial case somehow confused them) is having me go through all the same steps over again. (Groan). They want a video of the issue happening... as if that is somehow going to magically tell them what the problem is with Synapse. They think it is STILL a hardware issue, after RMAing the last unit, and the issue not occuring when Synapse is not installed. This would be funny if it was not so frustrating.

It seems that the support team and development teams may not be communicating, or else they would not be asking us to do the same redundant troubleshooting steps over and over again. Or asking repeatedly for video of the issue.
Wish I'd found this thread before I bought my Tartarus Pro a few weeks ago. Along with the sticking direction keys, I discovered yesterday in an experiment to see how it works in other games, that in two games (both Bethesda games, Skyrim SE and Fallout 4) the programming recognizes the Tartarus Pro as a controller. That recognition completely kills all controls at the startup menu. Editing the prefs.ini files in both games to change controller from 1 to 0 is a fix, both games. I'm now curious to see if the Tartarus Pro keys stick in those games.

Possibly the relationship is between the optical analog keys and the controller confusion that seems to be taking place with the Tartarus Pro, don't know anything about the Tartarus V2 mecha membrane keys. I notice my Cyberpunk 2077 game now shows controller config is loaded in a little pop up screen as it starts. That screen does not pop up if Tartarus Pro is unplugged. I also had noticed some help screens called for controller buttons instead of keyboard buttons. What that could possibly have to do with keys staying randomly stuck on I can't imagine, but that's there and that's all new with the Tartarus. I was running my Orbweaver Chroma before. Who knows what else is waiting in other games.
Glad I found this thread, was about to order a Huntsman Mini and a Tartarus Pro, I don't think I will now until this issue is fixed.