**Update 7/12/18 - 3rd device just failed with same issue (d-pad button). See my new post below for the details.**
Hi - I'm not certain if this is the right place to post this, but I'm hoping to bring attention to a quality control issue on the new Tartarus V2 Chroma d-pad switches in the hopes that it will get fixed in a new revision of the product.
TLDR: the d-pad micro-switches are failing way too fast (~1-2 months of use).
After a bit of research, I'm 99% certain I found the switches that are being used (http://www.kailh.com/en/Products/MS/MN/389.html), which claim to be rated for 3 million clicks. There are 4 of these switches (one for each direction on the d-pad) on a little daughter board inside the device.
- First Failure (JAN '18 - mid FEB '18, ~1.5 months) - the "right / east" d-pad button fails. Switch starts to stick in-game and loses it "clicky" sound. Received a replacement device in early MAR '18
- Second Failure (MAR '18 - mid APR '18, ~1.5 months) - this time, the "down / south" d-pad button failed, but in the exact same way. The microswitch just physically dies and stops 'clicking'. You can see a video I uploaded to the support team below to see / hear what I mean. Received replacement device near end of APR '18, early MAY '18.
- Third Failure (MAY '18 - mid JUL '18, ~2.5 months) - same failure, this time back to the "right / east" d-pad button. Going through RMA process, yet again...and hoping to find a way to bring this to an actual product designer / engineer's attention to see if they can improve switches or product design.
- Fourth Failure (JUL '18 - NOV '18, ~4 months) - same failure, this time the "right/east" d-pad button (which I use for "move forward" so gets used the most). I haven't started the RMA process yet, but will do so later today.
Latest Failure Video (Failure #4, 11/15/2018) -- notice how it's a different D-pad switch this time (right/east button).
I use the d-pad as my main movement keys in games, replacing my WASD...so they do get a lot of continuous use. That said, I've always played this way and my previous Tartarus / Nostromo devices have never had this issue. I've been using these gamepads for over a decade, since the original Belkin days and have owned ~9-10. I was super excited when Razer announced the new Tartarus V2, especially since it went back to the old d-pad style instead of the single "cylinder" approach, which isn't as accurate for movement. I actually love this new device, but I'm afraid the switches they chose for the d-pad...or perhaps the design itself...needs to be looked at a.s.a.p. for failure modes. I've had two fail, in the same way, in under 4 months...and have never had a single previous device fail in over a decade's worth of use.
*edit: cleaned up YouTube link*
*edit #2: added details of 3rd failure (7/14/18)
*edit #?: added details for 4th failure and new video (11/15/18)
Would be fine to get an official statement from Razer, if it`s a geneal problem, or only a specific charge, or ....
Did/Will Razer change something in production ?
(I know, it's difficult for the company, but would increase reputation).
I'm hoping razer comes up with a quick solution, I've had the same keypad since the old Belkin days as well.
I'm sure I'll have to go through the whole return process again and upload a new video, etc. When I do, I'll update this post with the new vid & any details of the experience.
I wish I could just buy a few of these switches myself and fix it (it's a simple daughter board and solderable). If anyone knows how to find the switches I linked above, LMK .
Unfortunately, there are actually no alternative keypad's in market. I'm in the same situation as you, totally disappointed by quality of Razer hard- and especially software. I fear, we have to switch to playing with keyboard and (MMO)mouse, as all the others do.
I have more bad news for you. I'm guessing since these things are failing left-and-right, they are not able to keep them in stock for RMA's. I'm still waiting to even be notified of a replacement option since my third one failed (since 7/12, it's now 8/5). When I responded to my support case asking for more info / details, I was quoted this:
I would really just like a response from a Razer Product Manger, Engineer, or someone other than a helpdesk tech that they are aware of this issue and are working on a updated version of this product.
I hate that all my posts here are negative because of shortcomings of the tartarus V2 and the synapse 3 crapware. Its really sad because it could be a really good product. I really wish we could get some kind of word on if its going to be resolved.
In this situation, we cannot have hope for an official reaction, nore an improvement. Over is over.
I was over the moon when the Tartarus V2 was announced, a clear upgrade from my trusty Nostromo. Wow, what a disappointment mine has turned out to be. Got straight onto eBay and picked up two extra pre-owned Nostromos, enough now for a lifetime. They never break.
I've had the exact same problem, I contacted Razer support because I assumed it was a bug with the Synapse 3 software fighting for processing power and freezing up for a few seconds, but I was just playing Prey earlier today and the D-pad stopped working literally in the middle of playing a game, I would have bought the Orbweaver bit it's almost twice the price
Same, only problem I ever had on the N52 from Belkin was I wore the faces off the keys... That thing was a tank.
I use the "Left" on the D-Pad for jumping and my ~ 2 month old Tartarus V2 D-Pad left just went to mush as OP described. This thread is super disheartening...
Edit to add video of symptom - same as OP other than my left failed:
First it would be necessary to know, what exactly is failing: the micro switches or the conducting pathes.
But whatever it is, best is to refund, if possible, or not use it.
I don't think there will be a solution, as Razer wraps in silence.
I've just had mine replaced since it's covered by warranty for 2 years, so I'm planning on just getting a replacement every time it breaks until the warranty runs out, then I might look into getting an Orbweaver or something, assuming it doesn't have the same problems
I've now ordered a replacement, which will be available on monday (I've bought via amazon). In the meantime a second switch has stopped working (forward, right), i'm not able to play with this product anymore. If the replacement breaks too, i will ask if its possible to get some kind of voucher because I'm tired of replacing the tartarus all the time.
Thanks for your answers!
Some of us don't want to wait a couple weeks to play games
After contacting Amazon support, I had a replacement delivered within a few days
Yes, but if the replacement breaks again? I'll have a look on my replacement, if this one breaks again, reading the comments here I guess it will, I will try to get a voucher or somenthing like this. What do you do if the warranty is over? If this is a lack in design it will break again and again. I really hope that this two broken switches in my tartarus v2 are a coincidence, but if not I don't want to replace it once in two months.
When its out of warranty Razer Support will send you this:
Thank you for contacting Razer Peripherals Support.
We understand the need for a replacement but as much as we would like to assist you further, the device is already outside of warranty.
For more information, you can visit our warranty page at https://www.razer.com/warranty
All the best,
Razer Peripherals Support
I had a Razer Tartarus and I barely used it over the past year since i use it for design softwares and not hard core gaming and it mysteriously died on me. Surprisingly, just after the warranty got over and just after their Synapse software updated and what I can recall the software was always asking me to sign in very frequently. I wont buy any Razer produtcs that needs to communicate online to sync and no option of keeping profiles offline or working without accounts and due to quality control or design or manufacturing faults.
Was thinking of the Tartarus V2 but when saw that some online store was giving heavy discounts on it gave me hint that that batch or model might have high replacement and also many users reporting this issue so no V2 for me.