Razer Wolverine V2 and V2 Chroma Deadzone Issue

I received this controller a few days ago, and I'm also experiencing dead zone issues. It's not fun. It's aggravating. When I go into the Razer app on the console, I can see that the app actually registers input from the thumb sticks without a dead zone. As soon as I apply any input in any direction, it registers that input immediately. However, in Destiny 2 for example, a dead zone is very noticeable. It takes more about a 1/4 of movement of the thumb stick to register the input. Most of the time this causes over aiming. D2 doesn't have custom dead zone settings. So what's causing this? Can this be fixed?

ComboKyle
I received this controller a few days ago, and I'm also experiencing dead zone issues. It's not fun. It's aggravating. When I go into the Razer app on the console, I can see that the app actually registers input from the thumb sticks without a dead zone. As soon as I apply any input in any direction, it registers that input immediately. However, in Destiny 2 for example, a dead zone is very noticeable. It takes more about a 1/4 of movement of the thumb stick to register the input. Most of the time this causes over aiming. D2 doesn't have custom dead zone settings. So what's causing this? Can this be fixed?

Nope, cannot be fixed as of rn, we'll have to wait on word from Razer themselves.

Hey I made the Fortnite video! The Japanese guy is a much more experienced reviewer , glad he was able to identify it with a video camera demonstration + the gamepadtester site. I will reference this thread in my support ticket, ty for finding the Japanese review with a better demo! For others reference, the Japanese video pulls up diagnostics around 9:37 into the video.

ZadiaSss
Hey I made the Fortnite video! The Japanese guy is a much more experienced reviewer , glad he was able to identify it with a video camera demonstration + the gamepadtester site. I will reference this thread in my support ticket, ty for finding the Japanese review with a better demo! For others reference, the Japanese video pulls up diagnostics around 9:37 into the video.

Yeah, I hope they can fix this issue ASAP. For some reason razer won't let me put a vid with timestamps and I get this error.

ZadiaSss
Hey I made the Fortnite video! The Japanese guy is a much more experienced reviewer , glad he was able to identify it with a video camera demonstration + the gamepadtester site. I will reference this thread in my support ticket, ty for finding the Japanese review with a better demo! For others reference, the Japanese video pulls up diagnostics around 9:37 into the video.

Also I'd be surprised if Razer doesn't do anything soon, bc there's 55K VIEWS on the Japanese dude's video.

iiiKariFPS
Also I'd be surprised if Razer doesn't do anything soon, bc there's 55K VIEWS on the Japanese dude's video.

I'm hearing from a reputable controller reviewer youtube that their v2 Chroma doesn't experience this issue, so hopefully an RMA will get us a device from a not so bad batch (I ordered it minutes after they listed it for sale on their site)

ZadiaSss
I'm hearing from a reputable controller reviewer youtube that their v2 Chroma doesn't experience this issue, so hopefully an RMA will get us a device from a not so bad batch (I ordered it minutes after they listed it for sale on their site)

Yea same, who was it from you? Mine was VCuda. I asked him what firmware he was running but he never responded.

So y'all are saying that reputable youtubers havent had this issue? Mine has it as well and is making me consider returning it sadly. It's an amazing controller and I assume this should be an easy firmware fix for razer. It seems like something vcuda would catch, I noticed it almost immediately.

I have the same Issue :( already wrote a ticket about it. Lets hope theyll fix it because besides that the controller is just great.

Made this thread on Reddit to reach a broader audience - https://www.reddit.com/r/razer/comments/q4st20/razer_v2_chroma_implicit_deadzone_issue_video/

ComboKyle
I received this controller a few days ago, and I'm also experiencing dead zone issues. It's not fun. It's aggravating. When I go into the Razer app on the console, I can see that the app actually registers input from the thumb sticks without a dead zone. As soon as I apply any input in any direction, it registers that input immediately. However, in Destiny 2 for example, a dead zone is very noticeable. It takes more about Indigo Card a 1/4 of movement of the thumb stick to register the input. Most of the time this causes over aiming. D2 doesn't have custom dead zone settings. So what's causing this? Can this be fixed?

Hello, This issue on the V2 was fixed. No longer an issue for the Razer Wolverine V2 and will not be an issue for Razer Wolverine V2 Chroma.

Matthewh06
Hello, This issue on the V2 was fixed. No longer an issue for the Razer Wolverine V2 and will not be an issue for Razer Wolverine V2 Chroma.

What software and firmware version are you running?

Matthewh06
Hello, This issue on the V2 was fixed. No longer an issue for the Razer Wolverine V2 and will not be an issue for Razer Wolverine V2 Chroma.

Just checked before heading out for work. There is no patch and the issue is still present. Razer has acknowledged our concern, and this is actually a feature of the controller to prevent users from experiencing drift. They have acknowledged that the more competitive players require drift to have better precision, and as a result will be implement a fix. No ETA on the fix though

ZadiaSss
Just checked before heading out for work. There is no patch and the issue is still present. Razer has acknowledged our concern, and this is actually a feature of the controller to prevent users from experiencing drift. They have acknowledged that the more competitive players require drift to have better precision, and as a result will be implement a fix. No ETA on the fix though

Any update on this information?

smartPaleBlueammo432
Any update on this information?

Still waiting :/

Hello, thanks for putting up all that info! I want to buy a V2 Chroma but I’m unsure right now if I should wait until they drop the firmware update? Is it 100% sure that it’s not a hardware issue? Thanks & BR

So I’m just getting mine from the RMA for my Wolverine ultimate and yes it still has the issue..

Wolverine V2. Forza Horizon 5 - same issue. Inner deadzone there is 50% or more (when I use this lower sensitivity feature the cars in the game have handling is totally gone). Also ingame settings working weird. - Inner deadzone from 0% to 50% - doesn't do anything. - Inner deadzone from 50% to 80% - works as intended. - Outer deadzone from 100% to 50% - works as intended. If you move outer deadzone slider to 50% or less - all your handling range from straight to full turn will be like half of millimeter stick movement. - Outer deadzone from 50% to 20% - keep steering range on this "half of millimeter" point and move INNER deadzone from 50% to 20%. This is really torture to play game like that. It's the same as if I would play game with keyboard and I didn't buy this wolverine V2 to play game keyboard style.

Following the thread. I was very close to ordering it, but I won't buy it until this issue gets fixed.

ma723
Hello, thanks for putting up all that info! I want to buy a V2 Chroma but I’m unsure right now if I should wait until they drop the firmware update? Is it 100% sure that it’s not a hardware issue? Thanks & BR

It is 100% a by-design feature. My guess is Razer wanted to eliminate complaints about drift for the casual gamers that care about drift. For example, on instagram I get ads for the v2 Chroma, and many comments complain about the controller exhibiting drift (these trolls are commenting based off previous Razer controllers, I assume, oh the irony). It is unfortunate that this is how joysticks work, and they pretty much all come from the same factory.. So what does Razer do after marketing studies the feedback in the public about their joysticks and drift? They work with developers to address the problem at its core and add a hard-coded deadzone via the software. My guess is that they aren't testing it to the limits of a typical competitive gamer. Maybe they do, I don't know.. don't quote me on that. But in trying to solve one problem, they did us competitive gamers dirty. I don't blame them, there are probably more casual gamers than competitive gamers. Customer support has escalated my ticket and they have acknowledged the desire to have a configurable deadzone in the Razer controller app, they have a new firmware version out by now probably, but have to wait for their Quality Assurance team to really test it out (these are the testers). On top of that since the "Razer Controller Setup For Xbox" application is an Xbox Store application, it must go through Xbox's Quality Assurance testers as well.. Software is a beautiful thing, but really easy to break when trying to make better, so I am thankful for the rigorous testing processes. I'm sure they are rushing as the holiday season is approaching, and this is an attractive controller and they probably don't want any more people upset. Consider this as facing the reality as an early adopter.. Although this issue has been present in the v2 non-chroma.. So it took a few back buttons for it to be identified by the public.. I am not surprised, it's the sweatier, try-hard competitive gamers like s that notice these flaws.

ArcticLimeboardgreat270
So I’m just getting mine from the RMA for my Wolverine ultimate and yes it still has the issue..

Good to know I can RMA my Wolverine Ultimate for a v2 Chroma.. I bought a new Wolverine Ultimate so I can game without my bumpers registering 2-3x clicks when I really only pressed it once. Normal wear and tear but covered under warranty, which means I'll get a spare v2 Chroma, maybe I can gift it this holiday season.

buzzShampooquick158
Wolverine V2. Forza Horizon 5 - same issue. Inner deadzone there is 50% or more (when I use this lower sensitivity feature the cars in the game have handling is totally gone). Also ingame settings working weird. - Inner deadzone from 0% to 50% - doesn't do anything. - Inner deadzone from 50% to 80% - works as intended. - Outer deadzone from 100% to 50% - works as intended. If you move outer deadzone slider to 50% or less - all your handling range from straight to full turn will be like half of millimeter stick movement. - Outer deadzone from 50% to 20% - keep steering range on this "half of millimeter" point and move INNER deadzone from 50% to 20%. This is really torture to play game like that. It's the same as if I would play game with keyboard and I didn't buy this wolverine V2 to play game keyboard style.

Thanks for sharing man! I don't play Forza but I'm sure it requires precision movements for the most enjoyable gameplay. Deadzones are often configurable by the game, and I understand why Razer put this on.. Make the current setting the default, sure, lemme have the option to turn it off! Name it a feature - "Drift Killer" and market that maybe, lol.

Multiate
Following the thread. I was very close to ordering it, but I won't buy it until this issue gets fixed.

If you want my honest opinion, I'd get it because I'm a Wolverine loyalist. But it'd be wise to wait until they fix it. But if you get a sweet Black Friday deal.. you make the call ;)

I kinda wish that we could run open-source software to configure our v2 Chroma, instead of proprietary Xbox Store apps available through the Microsoft Store.

I'm now speaking with Razer support team, and they asked me to record the issue. So here how it's work in Forza Horizon 5 (don't be afraid of Russian text in gamepad software. I explain what I'm doing in subs). For some reason it somehow got better and from around 50% moved to 20%-30% or so. Which is still weird and makes racing unplayable. https://www.youtube.com/watch?v=D-v24M9o1Dk

I just picked a new one up today and noticed it too has this issue. Software version is 1.7.34.0 with firmware version of 1.0.6.0. In my testing some games it is not too noticeable but others it really stands out but when using https://gamepad-tester.com/ or Steam's own calibration, it is registering movement across the entire range of the stick.

Hahaha, I'm out guys. 15~20% deadzone is just way too unusable and unacceptable for the price, and I see no concrete sign of being fixed any time soon. I ended up buying Victrix Gambit Dual Core controller as an alternative, which is reviewed by the same Japanese Youtuber on the thread.

There was a firmware update just pushed out bringing it to 1.0.90.0 but the issue still persists. I really like this controller but for the price this is unacceptable.