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 11 / 20
Yes, it could work, but the situation would be like it is now, so it would only work in specific situations.
It might be okay for MMO, but for every shooter, any delay in "execution" could be a problem.
It might be okay for MMO, but for every shooter, any delay in "execution" could be a problem.
Daisame
So it did something a little different this time. Usually... when I get a 'stuck' input, hitting the 'stuck' key again will stop the input. This time, it did not. I was stuck running against a wall and had to actually kill the Synapse process to stop the input. Then... I could not get the keypad's buttons to work at all (01-19), but the d-pad and thumb button still worked. Even after rebooting my PC they would not work. Tried logging out and back into the Synapse software and STILL would not work. The only fix was to unplug the USB of the Tartarus and plug it back in. Then the keys started working agin. I am uninstalling the Synapse software and will buy that WASD software for $20. It is clunky and I should not have to buy it to use my $130 Tartarus Pro, but at this point I cannot use a keypad with buggy software that randomly has me stuck moving in a signle direction in games. Frankly I should just ask for a refund and go back to my G13 from Logitech. It is not as pleasant to use mecanically, but at least the software works.
This has happened to me once before sometime last year. It was an isolated incident where the device 'spazzed' out. I believe it is just an isolated incident tbh. No need to be too alarmed about it imho.
Thanks @NoahArk620
I hope you are right. I am just so gun-shy on this Synapse software. I just uninstalled Synapse, and bound keys to the defaults. I cannot use any macro or key combinations, but at least it does not 'stick' any more.
I hope you are right. I am just so gun-shy on this Synapse software. I just uninstalled Synapse, and bound keys to the defaults. I cannot use any macro or key combinations, but at least it does not 'stick' any more.
Seegeth
Yes, it could work, but the situation would be like it is now, so it would only work in specific situations.
It might be okay for MMO, but for every shooter, any delay in "execution" could be a problem.
Well, if it is something controlled through the Software, it could be a player controlled setting to have it either way...
This way, if the player was to play a game, for example a MMO, that would benefit from this, the player would make the change to the setting in the Software, otherwise, if the player was going to play another game, say a First Person Shooter, they would leave things as they are now and not make that adjustment....
Would this way be then something possible ?
arroz76
Well, if it is something controlled through the Software, it could be a player controlled setting to have it either way...
This way, if the player was to play a game, for example a MMO, that would benefit from this, the player would make the change to the setting in the Software, otherwise, if the player was going to play another game, say a First Person Shooter, they would leave things as they are now and not make that adjustment....
Would this way be then something possible ?
That would be the best solution.
So here's a strange thing that happened ... and I don't know if it's related so more testing will have to be done. My Tartarus Pro and Razer Keyboard were connected and Synapse software loaded. I played a few hours of Mortal Kombat 11. My character would randomly jump without input from my controller (controller is how I play the game). It might last about 5 seconds or so. There were about 4-5 cases of this within 3 or so hours. Going to try again in the next few days but this has otherwise never happened to me before. But I usually don't load Synapse either unless playing COD with the Tartarus Pro.
EDIT: Problem ensued without the software loaded. Even disconnected my Razer items but it didn't help. So nevermind, not a Razer issue causing this.
EDIT: Problem ensued without the software loaded. Even disconnected my Razer items but it didn't help. So nevermind, not a Razer issue causing this.
What kind of controller is it, @buzzGrizzlyEMERALD539 ? A Razer one, by any chance?
man I am hesitant. I've been itching the pull the trigger on either the V2 or the Pro. Is this problem accross the board for both ? or just on the pro ?
kevmanrazer
man I am hesitant. I've been itching the pull the trigger on either the V2 or the Pro. Is this problem accross the board for both ? or just on the pro ?
Sorry to be the bearer of bad tidings, but the issue is definitely affecting both models, kev. Until Razer is able to find a fix for their Synapse software, (or perhaps develop a new model that has on-board memory), I can't recommend their devices. If, despite this, the Tartarus is still tempting you with it's sexy design ... then be sure to budget an extra $20 for reWASD (very functional third party software to replace Synapse) and kiss your customizable RGB goodbye, along with a wee bit of functionality on any other Razer peripherals you might also own.
Honestly though, if you're prepared to pay $20 for reWASD, then I would urge you to consider some of the few other gaming keypads on the market. Save yourself a good pile of money by perhaps buying a cheaper one -- there's a few out there which are priced much lower because their key bindings are factory set and not customizable. ... but as soon as you buy reWASD then they will indeed be customizable!
At this point, with Synapse being what it is, it effectively neuters any capability to program your own customizable key bindings on the Tartarus, anyways. I strongly feel that this truly warrants a downward adjustment on their retail price, accordingly.
... With this being the case, there is little else to set it from the competition. Razer definitely makes the best looking device in my opinion, and I've always given them high marks for build quality and customer service. But hey, if I had to decide between a $30 off-brand model and $80 - $130 Tartarus -- neither of which can truly offer functionally programmable keys! -- then I might be inclined to sacrifice sexiness at the altar of cost effectiveness, and take a leap of faith on another manufacturer.
the_novena
Sorry to be the bearer of bad tidings, but the issue is definitely affecting both models, kev. Until Razer is able to find a fix for their Synapse software, (or perhaps develop a new model that has on-board memory), I can't recommend their devices. If, despite this, the Tartarus is still tempting you with it's sexy design ... then be sure to budget an extra $20 for reWASD (very functional third party software to replace Synapse) and kiss your customizable RGB goodbye, along with a wee bit of functionality on any other Razer peripherals you might also own.
Honestly though, if you're prepared to pay $20 for reWASD, then I would urge you to consider some of the few other gaming keypads on the market. Save yourself a good pile of money by perhaps buying a cheaper one -- there's a few out there which are priced much lower because their key bindings are factory set and not customizable. ... but as soon as you buy reWASD then they will indeed be customizable!
At this point, with Synapse being what it is, it effectively neuters any capability to program your own customizable key bindings on the Tartarus, anyways. I strongly feel that this truly warrants a downward adjustment on their retail price, accordingly.
... With this being the case, there is little else to set it from the competition. Razer definitely makes the best looking device in my opinion, and I've always given them high marks for build quality and customer service. But hey, if I had to decide between a $30 off-brand model and $80 - $130 Tartarus -- neither of which can truly offer functionally programmable keys! -- then I might be inclined to sacrifice sexiness at the altar of cost effectiveness, and take a leap of faith on another manufacturer.
thank you for this great detailed reply. I may hold off for a bit.
Update 3.6.331.31613, no improvement 
Seegeth
Update 3.6.331.31613, no improvement :slightly_sad:
Thanks man, now I don't need to test it for myself.
Same -- updated to 3.6.331.31613 ... issue persists.
My new Tartarus V2 has the same issue with Synapse 3.6.331.31613
I've collected multiple logs before sending the device back to get a refund. Maybe the logs help the devs.
I've collected multiple logs before sending the device back to get a refund. Maybe the logs help the devs.
@Razer.Speedcr0ss Has the technician succeeded in replicating the "problem"?
Hey guys,
same problem here... I've got the third Tartarus V2 now and still same problems. Tried the Pro version, same problem... Tried different USB ports, USB hub with power supply, reinstalled the software (with deleting all file and config stuff in Windows) and still: same error.
The support asked me several times to close all Synapse Apps and to test ingame if the error still occures - but I've never got an answer how to test the stick without the possibility of binding a profile to the device without the necessery software...
Even if the Razer support is fast and friendly but: the problem still persists...
Wondering if there will EVER be a solution for it, waintig for six month now...
@Razer Support, my ticket numbers: 210215-000039, 210223-002818, 210323-000814 and the collection of tickets is growing.... In the past, for me Razer hardware and software was a synonym for quality!
Cheers
same problem here... I've got the third Tartarus V2 now and still same problems. Tried the Pro version, same problem... Tried different USB ports, USB hub with power supply, reinstalled the software (with deleting all file and config stuff in Windows) and still: same error.
The support asked me several times to close all Synapse Apps and to test ingame if the error still occures - but I've never got an answer how to test the stick without the possibility of binding a profile to the device without the necessery software...
Even if the Razer support is fast and friendly but: the problem still persists...
Wondering if there will EVER be a solution for it, waintig for six month now...
@Razer Support, my ticket numbers: 210215-000039, 210223-002818, 210323-000814 and the collection of tickets is growing.... In the past, for me Razer hardware and software was a synonym for quality!
Cheers
Same here, problem persists even after update.
Razer support has given up on solving this issue. After they RMA'ed my Tartarus pro, the issue persisted. They made me open a new case. For some reason the existing case "confused" them. So I opened a new case, referenced the old case. And the first thing the new case wanted, was to re-run ALL the previous troubleshooting and information gathering steps again. Which there are A LOT.
When I said I was not going to run them again, and to just look at all the previous data I sent them, they responded with this:
"Good day!
We would like to inform you that we will be closing the case and you may contact Razer support from this link for further assistance: https://support.razer.com
Thank you so much for having business with Razer and have a wonderful day!
Sincerely,
Ronnie
Razer Customer Service"
It appears Razer has no interest in solving this problem. I offered to work with them to run any debugging software or mode of Synapse so they could hopefully identify the issue and correct it. That did not seem to appeal to them at all. I would highly recommend returning any Tartarus products or anyting that may rely on Synapse 3's key mapping abilities. Or... buy some third party app, if you truly must use a Razer product.
When I said I was not going to run them again, and to just look at all the previous data I sent them, they responded with this:
"Good day!
We would like to inform you that we will be closing the case and you may contact Razer support from this link for further assistance: https://support.razer.com
Thank you so much for having business with Razer and have a wonderful day!
Sincerely,
Ronnie
Razer Customer Service"
It appears Razer has no interest in solving this problem. I offered to work with them to run any debugging software or mode of Synapse so they could hopefully identify the issue and correct it. That did not seem to appeal to them at all. I would highly recommend returning any Tartarus products or anyting that may rely on Synapse 3's key mapping abilities. Or... buy some third party app, if you truly must use a Razer product.
It's beyond obvious this is a software issue and not a hardware issue and they know this, those RMA's and 'troubleshooting' methods are just to get us discouraged to take any more steps. Also i don't believe this "Razer.Speedcross' guy that has been posting here and claims he has been reporting our problems to his so called 'team'. He is just trying to keep us occupied by making us believe they are working on the problem, when they are clearly not.
To the ones reading this thread and are considering to purchase a Razer Tartarus (v2, Pro, or any), be smart and don't waste your money!
To the ones reading this thread and are considering to purchase a Razer Tartarus (v2, Pro, or any), be smart and don't waste your money!
This is getting very annoying now.
Recently, the problem was once an hour, now it happens several times an hour.
I already wrote about it some time ago, but can't the dev team really sacrifice one person to write some driver to be able to use Synapse 2 with basic functions like binding keys.
It's not a perfect solution, but it's a good way to wait and see if it's a Synapse 3 problem.
It would also be nice if there was more information about what is being done.
Recently, the problem was once an hour, now it happens several times an hour.
I already wrote about it some time ago, but can't the dev team really sacrifice one person to write some driver to be able to use Synapse 2 with basic functions like binding keys.
It's not a perfect solution, but it's a good way to wait and see if it's a Synapse 3 problem.
It would also be nice if there was more information about what is being done.
Yes, we must forget about fix.
Razer turns profitable in 2020, posts $1.2b in revenue
https://www.techinasia.com/razer-turns-profitable-2020-posts-12b-revenue
Why spend money on fixing synapse, if stupid children buy no matter what. More important add a lot bells and whistles.
Not only keyboard, even mice are affected
https://old.reddit.com/r/razer/comments/i75uyk/razer_naga_trinity_stuck_buttons/
/huntsman-v2-analog-ascend-to-analog.69792/page-3#post-735615
and so on
Razer turns profitable in 2020, posts $1.2b in revenue
https://www.techinasia.com/razer-turns-profitable-2020-posts-12b-revenue
Why spend money on fixing synapse, if stupid children buy no matter what. More important add a lot bells and whistles.
Not only keyboard, even mice are affected
https://old.reddit.com/r/razer/comments/i75uyk/razer_naga_trinity_stuck_buttons/
/huntsman-v2-analog-ascend-to-analog.69792/page-3#post-735615
and so on
man am i happy that i just paid the £5 to use rewasd. just thought i would come in here and see if they have fixed their cruddy bloat/spyware yet. ofc not because there is money to be made and they have already got all off ours, so why spend r n d time on this when you can release more products. which will will also still have the same problem but hay we are "for the gamer" glad i have seen through that lie now, not so glad it cost £130
Is rewasd working with Tartarus?
I am using Synapse 3 to control all my LEDs - Razer, ASUS and DIYHUE... I think I'll give OpenRGB another chance, it did not support all my devices last year. Someone told me, Aquasuite made by Aquacomputer will control "all" LED devices (MSI, ASUS, Razer...) in the future.
For me, it was the last Razer product I've bought... Possible that I'll sell all that Razer trash and buy some working stuff... I think Razer has forgotten, that many disappointed gamers know many other gamers how would like to buy new gear - and I will NOT recommend them to buy any Razer product because it only looks nice but don't work. Btw, my newest support ticket is three days old and I did not get an answer yet. Maybe Razer support has closed because of wealth
About 15 years gaming with Razer will end like that...
I am using Synapse 3 to control all my LEDs - Razer, ASUS and DIYHUE... I think I'll give OpenRGB another chance, it did not support all my devices last year. Someone told me, Aquasuite made by Aquacomputer will control "all" LED devices (MSI, ASUS, Razer...) in the future.
For me, it was the last Razer product I've bought... Possible that I'll sell all that Razer trash and buy some working stuff... I think Razer has forgotten, that many disappointed gamers know many other gamers how would like to buy new gear - and I will NOT recommend them to buy any Razer product because it only looks nice but don't work. Btw, my newest support ticket is three days old and I did not get an answer yet. Maybe Razer support has closed because of wealth
About 15 years gaming with Razer will end like that...
Today there was another update, this time probably Tartarus itself, because the Synapse 3 version is the same, but I don't know how to check the firmware versions.
I will test in the evening in games to see if anything has changed.
@WhiteFox935 rewsad works but not fully, you cant bind wheel and control rgb
I will test in the evening in games to see if anything has changed.
@WhiteFox935 rewsad works but not fully, you cant bind wheel and control rgb
Seegeth
Today there was another update, this time probably Tartarus itself, because the Synapse 3 version is the same, but I don't know how to check the firmware versions.
I will test in the evening in games to see if anything has changed.
@WhiteFox935 rewsad works but not fully, you cant bind wheel and control rgb
It is probably the same version being redistributed at a later date. Mine showed up as being released on 24th March.
Page 11 / 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.