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 4 / 20
friends, remember, the problem is in Synapse
meanwhile, i have tried another tartarus pro, brand new and the issue persists. i have bought an pci usb adapter as i thought it may be a problem with the usb chipset, but that did not change a thing. i have a new ryzen 5900x system with x570 mainboard.
i also tried adding ferrite belts to the cable, did also change nothing.
i have read somewhere that a user on reddit was able to resolve the problem by using an usb hub. this is what i test now.
i also tried adding ferrite belts to the cable, did also change nothing.
i have read somewhere that a user on reddit was able to resolve the problem by using an usb hub. this is what i test now.
Hello. i ve got the same issue with my tartarus v2: random key stuck and i must press the key again to stop the strange behavior.
it works perfectly on my Latop and on my "old" i7 computer. I have the issue on my new Ryzen Computer.. with a fresh windows install.
any news for this bug ?
too bad, i really enjoy the Tartarus....
it works perfectly on my Latop and on my "old" i7 computer. I have the issue on my new Ryzen Computer.. with a fresh windows install.
any news for this bug ?
too bad, i really enjoy the Tartarus....
Well i have returned mine to amazon, got a new one and problem persists.
using rewasd and setting as keyboard is the standard I still have the issue where it will be stuck for around a second. not wasting more time on this.
I am giving up on the razer shit honestly they don't seem to care.
Even when you open a case with them it still seems they have never heard of this.
I have pre ordered an azeron cyborg waiting on that then I will return this pile of crap and never again.
I will also never recommend a razer product again. there are other good options out there.
using rewasd and setting as keyboard is the standard I still have the issue where it will be stuck for around a second. not wasting more time on this.
I am giving up on the razer shit honestly they don't seem to care.
Even when you open a case with them it still seems they have never heard of this.
I have pre ordered an azeron cyborg waiting on that then I will return this pile of crap and never again.
I will also never recommend a razer product again. there are other good options out there.
yeah I think I know the fix. the previous temp fix is to use rewasd to remap the keys. first you need to understand that rewasd allows you to emulate a controller with mouse and keyboard. this means that your mouse and keyboard will have aim assist on fps games.
Most pc games don't allow you to use BOTH mnk and controller. if you turn 1 on, the other one shuts down. it looks like the joystick on the tartarus is somehow based on controller input while the rest of the device is mouse and keyboard input. if you use your joystick, certain games will think you are using a controller and will shut your mouse and keyboard down, and vice versa.
the fix is to entirely remove the joystick and make it mechanical like how it is on a keyboard, and to make the joysticks input a keyboard, don't make it's input a controller joystick.
Most pc games don't allow you to use BOTH mnk and controller. if you turn 1 on, the other one shuts down. it looks like the joystick on the tartarus is somehow based on controller input while the rest of the device is mouse and keyboard input. if you use your joystick, certain games will think you are using a controller and will shut your mouse and keyboard down, and vice versa.
the fix is to entirely remove the joystick and make it mechanical like how it is on a keyboard, and to make the joysticks input a keyboard, don't make it's input a controller joystick.
Hi,
I have this exact same problem as well.
Razer Tartarus Pro
My serial number is: PM1947F36300746, I have just opened a case, with number:
210805-002921.
I do not believe it is the synapse software at all, I have had this issue from day 1, been waiting for a firmware or software update to fix it and nothing until now. It is too frustrating to play like this. I bought mine from amazon UK.
This is what i have tried:
Total removal of synapse and re install no difference.
I tried the reWASD software fix but this is only a partial fix, when I use the reWASD indeed it does not get stuck until you press the same key again but instead gets stuck for around 1 second? 2 at most then will release by itself.
I have tried USB 2 and USB 3 ports, I also recently upgraded my pc completely, new motherboard, processor memory everything.
its a 10700k Intel I7, motherboard is Asus Z490F.
I also got a new SSD did a clean install of windows to see if maybe my windows was dodgy, downloaded fresh install from the internet microsoft website.
I installed only graphics drivers and motherboard software, also updated motherboard firmware.
Installed fresh synapse same problem.
I did notice though if i set the dpad to work as a joystick using synapse I get the same result as with reWASD it will only stick for 1 to 2 seconds then release but it is enough to cause havoc ingame. This happens in multiple games but the ones I play most and notice is wow and FFXIV.
It really is a pity as it is a good device and I am super happy with it besides this issue which makes it unusable really..
In relation tot he last post my cable runs clear to the PC nothing that should interfere with it at all, connected to front USB case ports Thermaltake 71 TG RGB and i connected directly to motherboard USB at the back. when in the front only other cable near it is for my mouse, no power cables or anything crazy that should be able to cause any kind of interference.
I also feel this is hardware/firmware issue. My Device is clean and no dirt or dust under the keys.
Can anyone else confirm the 1 to 2 second stuck key using reWASD?
I have this exact same problem as well.
Razer Tartarus Pro
My serial number is: PM1947F36300746, I have just opened a case, with number:
210805-002921.
I do not believe it is the synapse software at all, I have had this issue from day 1, been waiting for a firmware or software update to fix it and nothing until now. It is too frustrating to play like this. I bought mine from amazon UK.
This is what i have tried:
Total removal of synapse and re install no difference.
I tried the reWASD software fix but this is only a partial fix, when I use the reWASD indeed it does not get stuck until you press the same key again but instead gets stuck for around 1 second? 2 at most then will release by itself.
I have tried USB 2 and USB 3 ports, I also recently upgraded my pc completely, new motherboard, processor memory everything.
its a 10700k Intel I7, motherboard is Asus Z490F.
I also got a new SSD did a clean install of windows to see if maybe my windows was dodgy, downloaded fresh install from the internet microsoft website.
I installed only graphics drivers and motherboard software, also updated motherboard firmware.
Installed fresh synapse same problem.
I did notice though if i set the dpad to work as a joystick using synapse I get the same result as with reWASD it will only stick for 1 to 2 seconds then release but it is enough to cause havoc ingame. This happens in multiple games but the ones I play most and notice is wow and FFXIV.
It really is a pity as it is a good device and I am super happy with it besides this issue which makes it unusable really..
In relation tot he last post my cable runs clear to the PC nothing that should interfere with it at all, connected to front USB case ports Thermaltake 71 TG RGB and i connected directly to motherboard USB at the back. when in the front only other cable near it is for my mouse, no power cables or anything crazy that should be able to cause any kind of interference.
I also feel this is hardware/firmware issue. My Device is clean and no dirt or dust under the keys.
Can anyone else confirm the 1 to 2 second stuck key using reWASD?
shouldn't you be able to shield the cable externally without soldering then? that should be enough to prove the theory
@edit
from my side i can confirm that it helps to connect the cable directly to motherboard, i was using usb hub before and was getting the error every 5-10 minutes, now im sticking about 3x daily, still not perfect tho.
@edit
from my side i can confirm that it helps to connect the cable directly to motherboard, i was using usb hub before and was getting the error every 5-10 minutes, now im sticking about 3x daily, still not perfect tho.
OK here is my Theory on this... we are missig the keyUp events due to interference.
What points would support it?
- The USB connection behaves differently when Synapse is started, which could be because it increases the Bandwidth the Keyboard is communicating to reduce latency.
- We know that higher bandwidth requires better quality cables. I Have some First hand expirience with bad HDMI cables that were not up to the spec causing Frame dropping and flickering.
- I had problems with the Tartarus Pro like every 1-2 hours. My tatarus pro was cable-managed together close to my pc's power cable. Then i tried the Taratus V2 with cable just thrown off the desk and it worked. Then i switched back with the Pro with the same cable route as the v2 had and its working for 2 days now.
- Razer has hard time reproducing it - which could be because of the nature of interferrence that is very specific to the gaming setup.
- Razer points out to not use switches and USB extenders and use the USB ports on the back of the PC. The whole reason behind this is to get a as-clean-as-possible communication channel between the keyboard and the PC.
- After RMA with new hardware, the problems seems to stay (because the cable type and route is the same).
- The Problem seems to appear at a different rate (times per hour) to different users - with the possibe explanation that the inteferrence is unique to the user.
What points would speak against it?
- Looks like only the KeyUp-Event is affected and interferrence would affect all events.
- Possible Explanation for the Pro: having it using analoge switches would mean that there are multiple key-down events with different pressure depths, and this redundancy counters the loss of a single event.
How to Fix/Confirm:
- Try a different route of the Cable to your Pc, as far away from other cables, especially the 110/220/230V AC power line ones, but also speaker and other usb cables.
- If you have the expirience with dissassebly and soldering, you could solder a new cable to the unit that has better shielding. If you do, please report back if it fixes the Problem!
- Just a guess as im not an electric engeneer: Adding an ferrite core could help, but i have not tried it.
What points would support it?
- The USB connection behaves differently when Synapse is started, which could be because it increases the Bandwidth the Keyboard is communicating to reduce latency.
- We know that higher bandwidth requires better quality cables. I Have some First hand expirience with bad HDMI cables that were not up to the spec causing Frame dropping and flickering.
- I had problems with the Tartarus Pro like every 1-2 hours. My tatarus pro was cable-managed together close to my pc's power cable. Then i tried the Taratus V2 with cable just thrown off the desk and it worked. Then i switched back with the Pro with the same cable route as the v2 had and its working for 2 days now.
- Razer has hard time reproducing it - which could be because of the nature of interferrence that is very specific to the gaming setup.
- Razer points out to not use switches and USB extenders and use the USB ports on the back of the PC. The whole reason behind this is to get a as-clean-as-possible communication channel between the keyboard and the PC.
- After RMA with new hardware, the problems seems to stay (because the cable type and route is the same).
- The Problem seems to appear at a different rate (times per hour) to different users - with the possibe explanation that the inteferrence is unique to the user.
What points would speak against it?
- Looks like only the KeyUp-Event is affected and interferrence would affect all events.
- Possible Explanation for the Pro: having it using analoge switches would mean that there are multiple key-down events with different pressure depths, and this redundancy counters the loss of a single event.
How to Fix/Confirm:
- Try a different route of the Cable to your Pc, as far away from other cables, especially the 110/220/230V AC power line ones, but also speaker and other usb cables.
- If you have the expirience with dissassebly and soldering, you could solder a new cable to the unit that has better shielding. If you do, please report back if it fixes the Problem!
- Just a guess as im not an electric engeneer: Adding an ferrite core could help, but i have not tried it.
bizBarnRedsource043
I was really looking into buying Tartarus but this thread disgusts me. Stucking of keys is really a serious issue for such expensive product marketed towards gamers.
Don't waste your money!
Looks like the scroll wheel has broken.
Tartarus is still sticking up.
I am going back to reWASD.
Tartarus is still sticking up.
I am going back to reWASD.
Seegeth
I'm sorry, I got a bit lost, did the "Hid Compliant Game Controller" solution help you all or not?
Seems to not fix the issue for me.
Strange thing, I started my computer normally today, as always, after logging into windows, the synpase 3 installer popped up.
I turned it off and went back to work.
In the evening, I uninstalled reWASD and installed Synapse 3.
I don't know if my keypad has broken or if it has been updated, but my scroll has stopped working.
But after 2.5 hours of game, no problems (no sticking keys).
Maybe it's a coincidence that my Tartarus Pro broke down (scroll) and Synapse worked normally for 2.5 hours.
P.S. All HID drivers are enabled.
I've reinstalled Synapse twice, my scroll still doesn't work.
I turned it off and went back to work.
In the evening, I uninstalled reWASD and installed Synapse 3.
I don't know if my keypad has broken or if it has been updated, but my scroll has stopped working.
But after 2.5 hours of game, no problems (no sticking keys).
Maybe it's a coincidence that my Tartarus Pro broke down (scroll) and Synapse worked normally for 2.5 hours.
P.S. All HID drivers are enabled.
I've reinstalled Synapse twice, my scroll still doesn't work.
TL;DR: There will be no changes, till this problem is mentioned in the main (hardware) media with a title like 'Razer faces random stucking key problems for over a year'. So, swarm out. Inform your local media about this mess.
Let’s point out some facts, guys. Cause in my opinion this rules out a lot of theorys on how to fix this without the support of Razer. First fact: We are facing a problem specific with the key_up-Event that - more or less randomly - is missing or got lost. This leads to the noticing of stucking keys. Second fact is, they are obviously physically not stucking. As alexxedo in post #364 pointed out, the key_up frame is already missing on USB level. I'll take this as fact three. Another - interesting but maybe overseen - point from him is the fact that the communication changes when Synapse is started (go back and read his post again!). And this makes even more sense, as we already knowing, that the behavior goes away, when we close Synapse (fact four).
What does fact four mean? Why does the behavior change? And what does this mean? Well, as background knowledge you must know that USB-2 has (to simplify it) two modes: Slow and Fast. Slow is usually enough speed for a typical keyboard. When Synapse is not open our Tartarus' stay in this default mode acting as a (kind of) normal keyboard. So why the change when Synapse is started? In my opinion is has mainly to do with latency. Fast mode has (for this kind of application) a lot less latency. (Latency = The time between when a key is pressed physically and when the computer is notified about that.) Using Fast-Mode lowers the latency on this part by the factor of 10 or so, making you feel the input as 'more direct'. (Which is also the selling point of the Tartarus Pro: again lower latency.) So using ReWASP or making the Tartarus as 'default HID device' (HID = Human Input Device) lets you not only loose the lighting but also the latency decrease.
So, where could be the root cause of this problem. Is it in the Tartarus firmware? Or a Driver/Synapse-Problem? Or could it even be a hardware combo problem, that it is specific to the USB-Port you are using? The last theory - in my opinion - can be ruled out for the most of us. It can be true that this is true for a tiny minority, but not for the most of us. The problem of the missing key_up event is waaaaay to specific for that. Or does a majority notifies missing key press events (you press a key and nothing happens)? In my case it is >always<, without any miss, key_up/stuck key. So problem must be in the firmware or the driver? And I would guess - based of alexxedo findings - that it is the firmware. Which leads me to 'Why does Razer doesn't fix it'? Well, usually you do not code a firmware – line by line - from scratch. You use librarys from your chip supplier. Razer is not a chip company, they pretty sure using librarys. And if there is a >hard to replicate< bug in a library, you must put a lot of effort in convincing your supplier to fix it. You, by yourself, couldn't do this, because you have no access to the library code.
So, is this good? No. And there will be no changes, till this problem is mentioned in the main (hardware) media with a title like 'Razer faces random stucking key problems for over a year'. So, swarm out. Inform your local media about this mess. Then - and only then - there is maybe enough pressure that this problem is getting fixed.
Let’s point out some facts, guys. Cause in my opinion this rules out a lot of theorys on how to fix this without the support of Razer. First fact: We are facing a problem specific with the key_up-Event that - more or less randomly - is missing or got lost. This leads to the noticing of stucking keys. Second fact is, they are obviously physically not stucking. As alexxedo in post #364 pointed out, the key_up frame is already missing on USB level. I'll take this as fact three. Another - interesting but maybe overseen - point from him is the fact that the communication changes when Synapse is started (go back and read his post again!). And this makes even more sense, as we already knowing, that the behavior goes away, when we close Synapse (fact four).
What does fact four mean? Why does the behavior change? And what does this mean? Well, as background knowledge you must know that USB-2 has (to simplify it) two modes: Slow and Fast. Slow is usually enough speed for a typical keyboard. When Synapse is not open our Tartarus' stay in this default mode acting as a (kind of) normal keyboard. So why the change when Synapse is started? In my opinion is has mainly to do with latency. Fast mode has (for this kind of application) a lot less latency. (Latency = The time between when a key is pressed physically and when the computer is notified about that.) Using Fast-Mode lowers the latency on this part by the factor of 10 or so, making you feel the input as 'more direct'. (Which is also the selling point of the Tartarus Pro: again lower latency.) So using ReWASP or making the Tartarus as 'default HID device' (HID = Human Input Device) lets you not only loose the lighting but also the latency decrease.
So, where could be the root cause of this problem. Is it in the Tartarus firmware? Or a Driver/Synapse-Problem? Or could it even be a hardware combo problem, that it is specific to the USB-Port you are using? The last theory - in my opinion - can be ruled out for the most of us. It can be true that this is true for a tiny minority, but not for the most of us. The problem of the missing key_up event is waaaaay to specific for that. Or does a majority notifies missing key press events (you press a key and nothing happens)? In my case it is >always<, without any miss, key_up/stuck key. So problem must be in the firmware or the driver? And I would guess - based of alexxedo findings - that it is the firmware. Which leads me to 'Why does Razer doesn't fix it'? Well, usually you do not code a firmware – line by line - from scratch. You use librarys from your chip supplier. Razer is not a chip company, they pretty sure using librarys. And if there is a >hard to replicate< bug in a library, you must put a lot of effort in convincing your supplier to fix it. You, by yourself, couldn't do this, because you have no access to the library code.
So, is this good? No. And there will be no changes, till this problem is mentioned in the main (hardware) media with a title like 'Razer faces random stucking key problems for over a year'. So, swarm out. Inform your local media about this mess. Then - and only then - there is maybe enough pressure that this problem is getting fixed.
I'm sorry, I got a bit lost, did the "Hid Compliant Game Controller" solution help you all or not?
I was really looking into buying Tartarus but this thread disgusts me. Stucking of keys is really a serious issue for such expensive product marketed towards gamers.
Userlevel 2
Katyblossym
Hey guys, just another quick check in - after hours and hours of gaming on my Tartarus Pro this week, with the driver that I had previously mentioned disabled, I have had maybe... 3 instances of a key sticking once or twice in a gaming session. I was on vacation this week, so I put in probably about 60 hours of game time while my partner was at work. That means that the probability for failure on this device is extremely low, and I am not sure exactly why that is.
During the times that I have had an issue, it cleared up pretty much instantly. Just to be sure, I would do a reboot of my machine when I hit a quiet moment in the game I was playing. I have a really strong hunch that this is not just Synapse itself... during the times I have had the issue, I am pretty sure that when I experienced the issue, some other device I use that had to communicate with Windows did it's thing with its driver and cause Synapse to flip out (probably another Razer device, because I have a crap ton of them - my bet is my Blackshark v2 Pro because I had it communicating wirelessly via the dongle *secretly hates that word). Further credence to this theory is that the very first time I had an issue with this new Tartarus Pro is when I plugged in a Basilisk v2 while playing a game).
With my previous Tartarus v2, I would often open Notepad and just play with the dpad with WSAD mapping and just type with it. No matter how much I moved the dpad around and typed, I could never replicate the issue, yet when I went into a game, I would instantly start having issues. More food for thought - Synapse recognizes the games we play, obviously... we see images for the latest games we are playing when we click the Synapse icon in our System Tray. Synapse doesn't notice Notepad as a game, so maybe that ties into all of this too. I can see the dots on the map, I just can't figure out how to string them together (starting to feel like Charlie on Sunny in Philadelphia).
My professional life deals in the IT world, previously as a system/network admin and now an IT Operations Manager (I tell you this because my crazy theories and hunches have led me to some great successes with tech issues and that I am not just pulling stuff randomly out of the air). What I don't know is how to ping anybody in Razer to get them to notice my testing I have done.
This is the kind of stuff razer should be begging for to help solve the issue instead of burying their heads in the sand and saying "blow under the keys, pm me, locking thread"
Tachyana1
I've been disabling the "Hid Compliant Game Controller" that razer installs since the original synapse software came out. It has always caused problems with windows. I've been using the Tartarus since the very first one came out.
I never had the "D-Pad Glitch" AKA Stuck auto moving in one direction until you hit that key again, until I finally replaced my Tartarus with the newer version 2.
The new Synapse 3 is far superior in gathering data and sending it home but much worse at actually doing what we need it for, gaming :slightly_sad:
Razers psuedo joystick idea has never worked right. If you want sticks that work get an xbox controller. I recently got an MSI brand controller for my kid and not only does it work really good, it's well built and it works with xbox, pc, playstation, and android.
Thanks Katyblossym for reminding me to look in the device manager for that crap driver Razer has never been able to get to work right. Since disabling it I've had no more problems. I had hoped that since it has caused problems ever since Razer first released synapse, that they had actually done something to fix it. Silly me, they put all their effort into gathering our personal information instead. If they would just be content with profiting off the products they sell instead of making us their product, maybe they could get the sfotware to work right.
Disabling it means you can no longer use the D-Pad on the Tartarus as fake joystick. But I don't see a problem with that because inside, there are just 4 switches, not 8 switches, and definitely not 2 axis.
Software to make windows think the Tartarus is what it is not just doesn't work.
Thanks for the shoutout! I'm always trying to help where I can, even if it doesnt always lead to a fix!
Hey guys, just another quick check in - after hours and hours of gaming on my Tartarus Pro this week, with the driver that I had previously mentioned disabled, I have had maybe... 3 instances of a key sticking once or twice in a gaming session. I was on vacation this week, so I put in probably about 60 hours of game time while my partner was at work. That means that the probability for failure on this device is extremely low, and I am not sure exactly why that is.
During the times that I have had an issue, it cleared up pretty much instantly. Just to be sure, I would do a reboot of my machine when I hit a quiet moment in the game I was playing. I have a really strong hunch that this is not just Synapse itself... during the times I have had the issue, I am pretty sure that when I experienced the issue, some other device I use that had to communicate with Windows did it's thing with its driver and cause Synapse to flip out (probably another Razer device, because I have a crap ton of them - my bet is my Blackshark v2 Pro because I had it communicating wirelessly via the dongle *secretly hates that word). Further credence to this theory is that the very first time I had an issue with this new Tartarus Pro is when I plugged in a Basilisk v2 while playing a game).
With my previous Tartarus v2, I would often open Notepad and just play with the dpad with WSAD mapping and just type with it. No matter how much I moved the dpad around and typed, I could never replicate the issue, yet when I went into a game, I would instantly start having issues. More food for thought - Synapse recognizes the games we play, obviously... we see images for the latest games we are playing when we click the Synapse icon in our System Tray. Synapse doesn't notice Notepad as a game, so maybe that ties into all of this too. I can see the dots on the map, I just can't figure out how to string them together (starting to feel like Charlie on Sunny in Philadelphia).
My professional life deals in the IT world, previously as a system/network admin and now an IT Operations Manager (I tell you this because my crazy theories and hunches have led me to some great successes with tech issues and that I am not just pulling stuff randomly out of the air). What I don't know is how to ping anybody in Razer to get them to notice my testing I have done.
During the times that I have had an issue, it cleared up pretty much instantly. Just to be sure, I would do a reboot of my machine when I hit a quiet moment in the game I was playing. I have a really strong hunch that this is not just Synapse itself... during the times I have had the issue, I am pretty sure that when I experienced the issue, some other device I use that had to communicate with Windows did it's thing with its driver and cause Synapse to flip out (probably another Razer device, because I have a crap ton of them - my bet is my Blackshark v2 Pro because I had it communicating wirelessly via the dongle *secretly hates that word). Further credence to this theory is that the very first time I had an issue with this new Tartarus Pro is when I plugged in a Basilisk v2 while playing a game).
With my previous Tartarus v2, I would often open Notepad and just play with the dpad with WSAD mapping and just type with it. No matter how much I moved the dpad around and typed, I could never replicate the issue, yet when I went into a game, I would instantly start having issues. More food for thought - Synapse recognizes the games we play, obviously... we see images for the latest games we are playing when we click the Synapse icon in our System Tray. Synapse doesn't notice Notepad as a game, so maybe that ties into all of this too. I can see the dots on the map, I just can't figure out how to string them together (starting to feel like Charlie on Sunny in Philadelphia).
My professional life deals in the IT world, previously as a system/network admin and now an IT Operations Manager (I tell you this because my crazy theories and hunches have led me to some great successes with tech issues and that I am not just pulling stuff randomly out of the air). What I don't know is how to ping anybody in Razer to get them to notice my testing I have done.
I've been disabling the "Hid Compliant Game Controller" that razer installs since the original synapse software came out. It has always caused problems with windows. I've been using the Tartarus since the very first one came out.
I never had the "D-Pad Glitch" AKA Stuck auto moving in one direction until you hit that key again, until I finally replaced my Tartarus with the newer version 2.
The new Synapse 3 is far superior in gathering data and sending it home but much worse at actually doing what we need it for, gaming :(
Razers psuedo joystick idea has never worked right. If you want sticks that work get an xbox controller. I recently got an MSI brand controller for my kid and not only does it work really good, it's well built and it works with xbox, pc, playstation, and android.
Thanks Katyblossym for reminding me to look in the device manager for that crap driver Razer has never been able to get to work right. Since disabling it I've had no more problems. I had hoped that since it has caused problems ever since Razer first released synapse, that they had actually done something to fix it. Silly me, they put all their effort into gathering our personal information instead. If they would just be content with profiting off the products they sell instead of making us their product, maybe they could get the sfotware to work right.
Disabling it means you can no longer use the D-Pad on the Tartarus as fake joystick. But I don't see a problem with that because inside, there are just 4 switches, not 8 switches, and definitely not 2 axis.
Software to make windows think the Tartarus is what it is not just doesn't work.
I never had the "D-Pad Glitch" AKA Stuck auto moving in one direction until you hit that key again, until I finally replaced my Tartarus with the newer version 2.
The new Synapse 3 is far superior in gathering data and sending it home but much worse at actually doing what we need it for, gaming :(
Razers psuedo joystick idea has never worked right. If you want sticks that work get an xbox controller. I recently got an MSI brand controller for my kid and not only does it work really good, it's well built and it works with xbox, pc, playstation, and android.
Thanks Katyblossym for reminding me to look in the device manager for that crap driver Razer has never been able to get to work right. Since disabling it I've had no more problems. I had hoped that since it has caused problems ever since Razer first released synapse, that they had actually done something to fix it. Silly me, they put all their effort into gathering our personal information instead. If they would just be content with profiting off the products they sell instead of making us their product, maybe they could get the sfotware to work right.
Disabling it means you can no longer use the D-Pad on the Tartarus as fake joystick. But I don't see a problem with that because inside, there are just 4 switches, not 8 switches, and definitely not 2 axis.
Software to make windows think the Tartarus is what it is not just doesn't work.
Katyblossym
Go into device manager, and under View, change it to Devices by container. Scroll to Razer Tartarus V2, and expand it. Look for HID-compliant game controller, right click and Disable device. See if you have any issues after that.
I will post an image here. I have no idea if this will help any of you all now that I am on the Pro, but I still am curious to see if this has any benefit. If not, oh well, but as we seem to be our own tech support, it wouldn't hurt to give it a try. Please don't kill the messenger if you still have issues, I just want to try and help.
After 1h sticks again for me.
skylaar
I picked up a Tartarus V2 recently (before seeing this post) and have the same problems experienced here with different keys sticking at random. I remap most of my keys because I play with ESDF. Once you close Synapse 3.0, then no issue at all but I lose my key map. I have used an Orbweaver for years with no problems at all but it runs on Synapse 2.0 and I wanted to avoid having both installed along with the Orbweaver showing some wear. To say the least, this is disappointing. I am looking into alternative software to remap my Tartarus keys and control the lights.
reWASD works fine. (but only controls, no rgb, no scroll)
I picked up a Tartarus V2 recently (before seeing this post) and have the same problems experienced here with different keys sticking at random. I remap most of my keys because I play with ESDF. Once you close Synapse 3.0, then no issue at all but I lose my key map. I have used an Orbweaver for years with no problems at all but it runs on Synapse 2.0 and I wanted to avoid having both installed along with the Orbweaver showing some wear. To say the least, this is disappointing. I am looking into alternative software to remap my Tartarus keys and control the lights.
Katyblossym
Hey all I promised I would post back with my results with the Tartarus Pro and in two days I haven't had any issues at all. I plugged it into the same port as the v2 was, and I copied my v2 profiles into the Pro.
However, before I began using it, I was aware that the Pro will sometimes show up as a phantom xbox controller. I looked up some instructions on how to fix that before I even began using it, and I am wondering if it had anything to do with why my Pro is working without issue so far. I was hoping some of you all may try testing this and seeing what results you all get:
Go into device manager, and under View, change it to Devices by container. Scroll to Razer Tartarus V2, and expand it. Look for HID-compliant game controller, right click and Disable device. See if you have any issues after that.
I will post an image here. I have no idea if this will help any of you all now that I am on the Pro, but I still am curious to see if this has any benefit. If not, oh well, but as we seem to be our own tech support, it wouldn't hurt to give it a try. Please don't kill the messenger if you still have issues, I just want to try and help.
This doesn't seem to fix the issue for me
Still getting those sticking keys
Katyblossym
Follow up: I know I am posting a lot here, but MAYBE I am doing some good. Not trying to be annoying or anything.
My Tartarus Pro has continued to operate without issue, EXCEPT for one singular moment.
I was playing Destiny, and I use a Naga as my mouse. I decided to plug in my Basilisk v2 while playing (leaving the Naga plugged in as well) just to see if it felt more comfortable playing.
Windows did its whole "installing device" sound (Destiny was in the foreground so I couldn't see anything happening on my desktop, and a few moments later, I got stuck moving to the left on my Tartarus Pro Dpad. I then unplugged the Basilisk, and continued to play. After the mission I was in, I restarted my computer and I have had no further issues.
Something happening simultaneously between the Windows driver install Synapse caused the Tartarus to bug out. Probably been said a million times before but I have a very strong feeling that this has something to do with drivers Windows is using for our devices and how Synapse reacts to them. Maybe when the driver activates or has to perform a function?
Just ideas from what I am seeing.
Not annoying at all. I'm following this thread closely with great interest. I wish Razer would too :)
I've had the sticky button issue forever. I've tried a lot of things and by now i'm so used to it in games that i automatically cancel the stuck button by pressing it again pure by muscle memory
. I would love to see this fixed tho because it still gets u in awkward situations in games.
I will try disabling the HID controller like u said and report back if i feel its fixed for at least a while.
gl with testing.
Follow up: I know I am posting a lot here, but MAYBE I am doing some good. Not trying to be annoying or anything.
My Tartarus Pro has continued to operate without issue, EXCEPT for one singular moment.
I was playing Destiny, and I use a Naga as my mouse. I decided to plug in my Basilisk v2 while playing (leaving the Naga plugged in as well) just to see if it felt more comfortable playing.
Windows did its whole "installing device" sound (Destiny was in the foreground so I couldn't see anything happening on my desktop, and a few moments later, I got stuck moving to the left on my Tartarus Pro Dpad. I then unplugged the Basilisk, and continued to play. After the mission I was in, I restarted my computer and I have had no further issues.
Something happening simultaneously between the Windows driver install Synapse caused the Tartarus to bug out. Probably been said a million times before but I have a very strong feeling that this has something to do with drivers Windows is using for our devices and how Synapse reacts to them. Maybe when the driver activates or has to perform a function?
Just ideas from what I am seeing.
My Tartarus Pro has continued to operate without issue, EXCEPT for one singular moment.
I was playing Destiny, and I use a Naga as my mouse. I decided to plug in my Basilisk v2 while playing (leaving the Naga plugged in as well) just to see if it felt more comfortable playing.
Windows did its whole "installing device" sound (Destiny was in the foreground so I couldn't see anything happening on my desktop, and a few moments later, I got stuck moving to the left on my Tartarus Pro Dpad. I then unplugged the Basilisk, and continued to play. After the mission I was in, I restarted my computer and I have had no further issues.
Something happening simultaneously between the Windows driver install Synapse caused the Tartarus to bug out. Probably been said a million times before but I have a very strong feeling that this has something to do with drivers Windows is using for our devices and how Synapse reacts to them. Maybe when the driver activates or has to perform a function?
Just ideas from what I am seeing.
Hey all I promised I would post back with my results with the Tartarus Pro and in two days I haven't had any issues at all. I plugged it into the same port as the v2 was, and I copied my v2 profiles into the Pro.
However, before I began using it, I was aware that the Pro will sometimes show up as a phantom xbox controller. I looked up some instructions on how to fix that before I even began using it, and I am wondering if it had anything to do with why my Pro is working without issue so far. I was hoping some of you all may try testing this and seeing what results you all get:
Go into device manager, and under View, change it to Devices by container. Scroll to Razer Tartarus V2, and expand it. Look for HID-compliant game controller, right click and Disable device. See if you have any issues after that.
I will post an image here. I have no idea if this will help any of you all now that I am on the Pro, but I still am curious to see if this has any benefit. If not, oh well, but as we seem to be our own tech support, it wouldn't hurt to give it a try. Please don't kill the messenger if you still have issues, I just want to try and help.
However, before I began using it, I was aware that the Pro will sometimes show up as a phantom xbox controller. I looked up some instructions on how to fix that before I even began using it, and I am wondering if it had anything to do with why my Pro is working without issue so far. I was hoping some of you all may try testing this and seeing what results you all get:
Go into device manager, and under View, change it to Devices by container. Scroll to Razer Tartarus V2, and expand it. Look for HID-compliant game controller, right click and Disable device. See if you have any issues after that.
I will post an image here. I have no idea if this will help any of you all now that I am on the Pro, but I still am curious to see if this has any benefit. If not, oh well, but as we seem to be our own tech support, it wouldn't hurt to give it a try. Please don't kill the messenger if you still have issues, I just want to try and help.
Page 4 / 20
Sign up
Already have an account? Login
Log in with Razer ID to create new threads and earn badges.
LOG INEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.