Wolverine v3 tournament edition back buttons causing slowed aim rate | Razer Insider
Skip to main content
Question

Wolverine v3 tournament edition back buttons causing slowed aim rate

  • December 15, 2024
  • 1 reply
  • 313 views

leetBallBlueboard817

I just got a wolverine v3 pro about 4 days ago, hoping that I could easily transition from xbox to pc and vise versa. I started to use this new one from my old scuf, and am noticing that when i press M3 (binded to B) or M4 (binded to A) it slows my right stick down a TON like i’m using it for the aim slow-down rate.

i even tried assigning another button to the aim slow-down rate so maybe it would trick the controller to not use M¾ as the slow down buttons… didnt work.

i have tried it both on xbox and pc. same problem… its like the default out-of-the-box settings won’t go away after clearing it and adding new binds.>

any help would be appreciated. I love this controller and don’t want to have to get rid of it

Did this topic help you find an answer to your question?
This topic has been closed for comments

1 Reply

Razer.Aero
Forum|alt.badge.img
  • Razer Support
  • 3222 replies
  • December 17, 2024

Hello leetBallBlueboard817,

 

Thank you for escalating this issue to us. I understand you are having an issue with your Razer Wolverine V3 Pro, particularly related to the M3 and M4 button assignments affecting your right stick's responsiveness. Here’s a couple of steps you can take to troubleshoot and possibly resolve the problem:

  1. Ensure the cable connection from your controller to the console or PC is secure.
  2. Update the firmware version for your controller. 
  3. Disconnect the controller, then press and hold the power button for about 10 seconds to power it down completely. Reconnect it and see if this resolves the issue.
  4. Revisit the controller settings and ensure the button mappings are set correctly. Sometimes resetting the settings to default and then remapping can help.
  5. If possible, try connecting your controller to a different PC or Xbox to see if the issue persists. This can help determine if the issue is with the controller itself or if it's related to a specific device.

 

If the same problem persists, send me the device serial number so I can check for other workarounds. All the best!


*Thread locked to curb conversation to PM.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings