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 5 / 20
Good idea.
Today i will test with local account - 3 - 4 hours, tomorrow i convert local to microsoft account, and test it.
Today i will test with local account - 3 - 4 hours, tomorrow i convert local to microsoft account, and test it.
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 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.
So!
1.Disable any extraneous Windows services that are installed by third-party software that is not part of the OS.
2. Press the Windows key + R key combination. A menu will appear to enter https://i.imgur.com/sKSZ6YB.png
3.Write msconfig and click ok. The system setup application will open.
4. Go to the Startup tab and disable all applications from the list.
5.Next, go to the Services tab and check the box next to "Do not show Microsoft services", then click Disable all.
6. After these actions, click "ok", you will be prompted to restart your PC. Please reload it. After restarting, try starting the game without launching any programs.
1.Disable any extraneous Windows services that are installed by third-party software that is not part of the OS.
2. Press the Windows key + R key combination. A menu will appear to enter https://i.imgur.com/sKSZ6YB.png
3.Write msconfig and click ok. The system setup application will open.
4. Go to the Startup tab and disable all applications from the list.
5.Next, go to the Services tab and check the box next to "Do not show Microsoft services", then click Disable all.
6. After these actions, click "ok", you will be prompted to restart your PC. Please reload it. After restarting, try starting the game without launching any programs.
@the_novena Incredible summary you made there!
There are many more unsuccessful fixes outlined by many users in the pits of comments on the reddit post below, including forcing Tartarus v2/Pro to not be recognized by Synapse 3.0 while the program is running. (But it seems the driver is still running) I didn’t open this reddit post, so it is quite rough.
https://www.reddit.com/r/razer/comments/fn1iv3/tartarus_pro_movement_wasd_lock_occasionally_need/
@KAWAiiSONG The 3rd device i tested with, which is my work’s PC are mostly barebones and was running off a local account (not local admin account). Issue is still there.
I really need to emphasize that testing to replicate the issue takes time, weeks even. My longest time without issue was 2 weeks (Possibly with human error not noticing), my shortest time was 2 minutes (lol), and on average it is usually 2 hours.
There are many more unsuccessful fixes outlined by many users in the pits of comments on the reddit post below, including forcing Tartarus v2/Pro to not be recognized by Synapse 3.0 while the program is running. (But it seems the driver is still running) I didn’t open this reddit post, so it is quite rough.
https://www.reddit.com/r/razer/comments/fn1iv3/tartarus_pro_movement_wasd_lock_occasionally_need/
@KAWAiiSONG The 3rd device i tested with, which is my work’s PC are mostly barebones and was running off a local account (not local admin account). Issue is still there.
I really need to emphasize that testing to replicate the issue takes time, weeks even. My longest time without issue was 2 weeks (Possibly with human error not noticing), my shortest time was 2 minutes (lol), and on average it is usually 2 hours.
For me System File Checker did not help at all, found corrupted files and fixed them, but the problem continued. The only thing that helped (temporarily) was creating a new local account and playing on it. Or converting a microsoft account to a local account.
This is a bit strange as to why some solutions only work for a while. Nothing on my computer had changed in the meantime.
This is a bit strange as to why some solutions only work for a while. Nothing on my computer had changed in the meantime.
I can chime in,
I had performed System File Checker prior to converting my main admin account on my secondary device (which i use for testing nowadays) into a local admin account. While SFC has detected an error on my secondary device (log stated that it fixed a file related to Microsoft NET 4.5 distribute), and promptly fixed it, the Tartarus Pro issue stil crops up after 2 hours of testing.
In terms of softwares on my side, I can only think of ‘Discord’, ‘Nvidia Geforce Experience’, ‘Microsoft Office 2016’, ‘Microsoft OneDrive’, ‘Google Drive’, ‘Apple iCloud’, ‘Steam’ and ‘Google Chrome’ being the only softwares that are the same between my primary and secondary device, and are running on the background. Work PC (Tertiary drvice) only had Google Chrome.
Like @Seegeth, my systems has practically went unchanged for the past year except for updates on Windows, and Synapse.
I had performed System File Checker prior to converting my main admin account on my secondary device (which i use for testing nowadays) into a local admin account. While SFC has detected an error on my secondary device (log stated that it fixed a file related to Microsoft NET 4.5 distribute), and promptly fixed it, the Tartarus Pro issue stil crops up after 2 hours of testing.
In terms of softwares on my side, I can only think of ‘Discord’, ‘Nvidia Geforce Experience’, ‘Microsoft Office 2016’, ‘Microsoft OneDrive’, ‘Google Drive’, ‘Apple iCloud’, ‘Steam’ and ‘Google Chrome’ being the only softwares that are the same between my primary and secondary device, and are running on the background. Work PC (Tertiary drvice) only had Google Chrome.
Like @Seegeth, my systems has practically went unchanged for the past year except for updates on Windows, and Synapse.
I haven't tested it yet, but I think it might be a better lead. It is easier for me to believe that all this is the fault of some driver than e.g. windows account.
Userlevel 7
- Razer Support
- 7595 replies
-
19 January 2021
Hey everyone! I appreciate all the help. I suggested performing the SFC scan and creating a local Windows user account so it can help us isolate the issue. And yes, I agree that these steps are tedious. Keep in mind that this is not an official fix. By the way, the team is watching this thread and they're monitoring everyone's post. I appreciate the collation of data, video tutorial, and for everyone who tried the steps too. It's surprising that the issue is happening to another gaming keypad brand too. Our aim is to determine the cause of this and create a fix. I'll update this thread again once I got a follow-up from the team.
jhnclvr
... IMO Razer has great designs and hardware, but the software is terrible, and the issues are not limited to the Tartarus.
This pretty much sums it up fairly accurately. And true: it's not just the Tartarus's (Tartarii? lol). I've had it happen to my Black Widow Elite keyboard (once or twice). @KAWAiiSONG encounters it continuously on his Naga Pro mouse. And there have been two or three occasions where I think it may have happened to my own Naga mouse as well.
There is indeed something terrible going on with the software, but I also recognize that Razer is aspiring to greatness (and has indeed achieved greatness in so many other ways, with their designs and hardware, as pointed out!). The one thing we all have in common is that we all just want this to work as intended. I'm determined to try to contribute to that effort, and I genuinely appreciate everyone who is participating on this thread, towards that same effort!
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.
Orbweaver works great on Synapse 2.
Maybe the dev team could do some test drivers to run Tartarus on Synapse 2.
Maybe the dev team could do some test drivers to run Tartarus on Synapse 2.
Just bought Tartarus v2, 2 weeks ago. First time using a gaming keypad and I can say I love it so far. Also first time using a Razer product.
BUT...this issue is getting ridiculous. My character just keeps walking...At first, I thought I'm doing something wrong...and it wasn't happening that often, like once every 2-3 hours(definitely annoying, but manageable). But today it drove me mad. I've played wow for 3 hours, raiding, and it happened every 15-20 minutes. Even got kicked out of raids because I was randomly walking and pulling mobs
I've already spent half a day reading about this issue online and it seems it's quite old and there is no solution for it...
Should I return the product? Has anyone tried Tartarus Pro? All the people with this issue are on tartarus v2...maybe the pro version is working, I dunno.
BUT...this issue is getting ridiculous. My character just keeps walking...At first, I thought I'm doing something wrong...and it wasn't happening that often, like once every 2-3 hours(definitely annoying, but manageable). But today it drove me mad. I've played wow for 3 hours, raiding, and it happened every 15-20 minutes. Even got kicked out of raids because I was randomly walking and pulling mobs
I've already spent half a day reading about this issue online and it seems it's quite old and there is no solution for it...
Should I return the product? Has anyone tried Tartarus Pro? All the people with this issue are on tartarus v2...maybe the pro version is working, I dunno.
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.
I have tried the troubleshooting steps mentioned in this thread. The issue persists for me. After doing extensive research across the internet I'm convinced that:
1) it's wide spread and in fact experienced by all user
2) it's due to the synapse software (I've tried uninstalling synapse and the issue goes away)
I don't want to have to buy rewasd software because it costs money and I don't want to lose ability to map my scroll wheel.
Razer can you please address this?
1) it's wide spread and in fact experienced by all user
2) it's due to the synapse software (I've tried uninstalling synapse and the issue goes away)
I don't want to have to buy rewasd software because it costs money and I don't want to lose ability to map my scroll wheel.
Razer can you please address this?
Seegeth
I tried driver fix. (disable HID)
Works for one day. Now issue occur few times in hour.
Oh no... That is truly sad to hear. :< I wonder if there is a specific driver that I can delete so that I can install Synapse 3.0 to let me use my other devices in peace.
jjdenver
I have tried the troubleshooting steps mentioned in this thread. The issue persists for me. After doing extensive research across the internet I'm convinced that:
1) it's wide spread and in fact experienced by all user
2) it's due to the synapse software (I've tried uninstalling synapse and the issue goes away)
I don't want to have to buy rewasd software because it costs money and I don't want to lose ability to map my scroll wheel.
Razer can you please address this?
Welcome to the thread, @jjdenver ! I personally like reWASD software very much, but yeah, we shouldn't be relying on 3rd party software to retain 'most' of our product functionality. There is actually no need to 'uninstall' Synapse, just turn it off entirely, and the issue will go away temporarily for as long as the program is not running.
By all means keep a close tab on this thread, as we do various different methods of testing to check for a potential workaround while we wait for a proper driver/firmware fix from the developer team! (I am still eagerly awaiting good news, @Razer.Speedcr0ss !)
Seegeth
I tried driver fix. (disable HID)
Works for one day. Now issue occur few times in hour.
yeah mine started doing it again, :slightly_sad: it's like you need to repair the install ever 3-4 days it's annoying af ¬¬
and i think they should at least stop sales of the device till they fix this bug, because it's show how little f..s they give. because it will happen to everyone at some point, it just takes time. and for them to fix that i don't think they are going to leave the product in a pc for over a few weeks constant to see the bug appear, "we tested for like 2 days nothing happened"
when the problem occurs again, check the latest Synapse sync time with the cloud!I think it might be related!
olPiG
Whats the 3rd party solution?
reWASD
the_novena
Interesting suggestion, yeah! I wonder: is there anywhere we can find and see when the last sync time occurred, @Razer.SpeedCr0ss ?
I tried disabling the HID-compliant device. Sadly: no improvement at all. The issue was still occurring within a couple/few hours.
To be honest, the issue seems to be happening MORE frequently, and also seems to be affecting my mouse (Naga Trinity) more than ever, too. Although I've been blessed with an abundance of patience, I'm genuinely reaching my limits.
https://imgur.com/UtuNLpm
Update 3.6.130.11816
I have not heard from Razer support in about a month. So guess they stopped sending the automated "we have not heard from you in a while and want to see if you ware still having issues" email. I guess they got wise to my automated response saying I was still having the issue.
In any case, I don't know what (if anything) is being done to actually identify and correct the issue.
In any case, I don't know what (if anything) is being done to actually identify and correct the issue.
Userlevel 7
- Razer Support
- 7595 replies
-
1 February 2021
Hey everyone! The team is working on a fix for all of our reported Synapse-related issues. Please check your Razer Synapse's available updates from time to time. Let me know if there are changes or if it fixed your device's concern. Also, I'll report back once the team finalized the updates intended for Razer Tartarus V2/Pro.
waaaghmachine
This issue extends to the Razer Huntsman V2 Analog. I’ve been giving the same instructions on using different ports, using a clean version of Synapse, and then Razer suggested I return it to the retailer for another one. Maybe I had a defective keyboard? Well… I’m trying again, this is my third keyboard, and to nobodies surprise, it has the same “sticky” keys. If I log out of Synapse, the issues go away completely.
The only thing I get from Razer anymore is an RMA offer, zero solutions to their flagship new keyboard, which isn’t getting “reviewed” by many prominent youtubers who typically cover Razer products (Badseed, RandomFrankP, HardwareCanucks).
With reports affecting not only Tartarus v2 and Pro, but also including their other newer product lines like Huntsman V2 Analog, and Naga Trinity, this could be a sign for things to come. Perhaps this warrants a new thread to have everyone chime in to get noticed. What do you guys think?
I monitored the sync times closely, and although it was a good hypothesis, I'm afraid it appears to be unrelated. Between a 3:52pm sync-time yesterday afternoon, and the next sync time at 12:43am, the issue occurred about four or five times in between.
Glad to see there's a brand new update to Synapse; keeping my fingers crossed this solves it!!
Glad to see there's a brand new update to Synapse; keeping my fingers crossed this solves it!!
New threads generally only clutter the issue. I don't know if it would be worth it. I just asked for an update on my case, I think everyone who has not already, needs to open support cases and keep on top of them for updates.
Page 5 / 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.