Wolverine v3 tournament edition M1..Mx buttons' mappings are not persisting | Razer Insider
Skip to main content

I’ve been using this controller for some hours as it’s arrived today. I’ve got it updated to the latest firmware via the Xbox app.

However, I've got an issue where after mapping the additional buttons M1..Mx. When playing for sometime, they reset to the default ones. Especially, M2 M3 and M4 they reset by themselves. In order to try and fix it, I need to remap the buttons even though they are showing fine in the app. So, I enter to the only created profile I’ve got in the app and re-assign the mappings to the same ones I’ve had configured, not even changing anything and it works fine after clicking on OK. 

 

Then after sometime when playing the game, the issue starts again, so the mappings are not persisting. Which is of course, very frustrating and the controller isn’t doing what’s supposed to do.

 

Tried to contact the chat support, but it’s not working either… it says ‘something went wrong, try again’ I did it 3 times to reach the same level, so not even the chatbot is working. I’m thinking if I’m going to stay with this one or ask for a refund.

Further information

 


After mapping the M1..M6 buttons, then after sometime some of them are re-mapping themselves to anything. Sometimes it’s the M3 mapped to A button, sometimes it’s a directional pad arrow, etc. it’s happening randomly.


When using the headset, the volume goes up and down automatically with no other reason.

Disconnecting/Connecting the controller won’t help as this misconfiguration persists. The only way to fix it is to re-entering to the Razer app on Xbox; note that the original mapping is still shown, but not working, so I’ve got to re-map to the original configured button and it works… then after sometime of playing it fails again. So frustrating!

 


I did another test mapping the buttons without the razer app, I’ve used Function + Mx + Button to map and after playing, it’s failing with the same issue. So the problem is the firmware or something inside isn’t able to hold the mappings over the time


Reply