Huntsman V2 Analog bugs | Razer Insider
Skip to main content
I recently bought a new Huntsman V2 Analog and wanted to try out the analog wasd key feature. It looks like many or maybe just some games are having big issues with this. While the movement mostly works fine, other inputs start to fail.

I couldn’t test a lot of games but here are some that had these issues:

-in Resident Evil games (tested the rework of RE 2 and RE 7) while moving I can't use my mouse to look around

-it’s even worse in Middle-Earth: Shadow of Mordor. It looks like the game switches to XBOX controls when I move and back to Mouse/Keyboard whenever I use one of those. It does that so badly that the game becomes unplayable

-in Cyberpunk 2077 it were just some minor movement controls not working e.g. evading to the sides (normally done by double tapping a or d)

All of those games are having full controller support.

Furthermore I can’t write with the wasd keys when the analog mode is enabled but maybe there is a setting I haven’t found yet that prevents this.

Does someone else have those issues? Can I fix them? And is this a game or keyboard sided error? It would be a shame if such a great feature would be rendered useless because most games can’t use it properly.

Any help appreciated.
Regarding the WASD, they keys are switching to joystick functionality, not adding it, that's why you cannot use both, as far as I know, there are no games that recognize the analog keys and I'm hoping Razer make something like the chroma sdk so the games can see and use the analog keys properly.



So far I found some games where WASD (or any key) on controller functionality is working as expected:



-Overwatch: Best implementation, everything works plus you have the option to lock the keyboard UI so when using the WASD in joystick mode, it doesn't switch to controller buttons on UI.

-Gears 5, TitanFall 2, HellBlade, Rise of the Tomb Rider, Death Stranding, Wolfestein: YoungBlood, The Division 2, FarCry 5, Red Dead Redemption II and StarWars Jedi Fallen Order: Just the small issue of the UI switch to controller and KB depending on what you press/move.

-StarWars Battlefront II: It works but cannot use the mouse additional buttons when pressing the WASD.



The main issue is how the games handle the input, yes Huntsman V2 will work with all the games that have controller support, but not all of those support kb/mouse and gamepad input at the same time. I see there are more and more users adopting the analog keyboards and hopefully developers start supporting it.



So far I haven't found a solution when the game doesn't support mixed input, any additional info/software/recommendation will be appreciated.
freshMauveplane258
I recently bought a new Huntsman V2 Analog and wanted to try out the analog wasd key feature. It looks like many or maybe just some games are having big issues with this. While the movement mostly works fine, other inputs start to fail.

I couldn’t test a lot of games but here are some that had these issues:

-in Resident Evil games (tested the rework of RE 2 and RE 7) while moving I can't use my mouse to look around

-it’s even worse in Middle-Earth: Shadow of Mordor. It looks like the game switches to XBOX controls when I move and back to Mouse/Keyboard whenever I use one of those. It does that so badly that the game becomes unplayable

-in Cyberpunk 2077 it were just some minor movement controls not working e.g. evading to the sides (normally done by double tapping a or d)

All of those games are having full controller support.

Furthermore I can’t write with the wasd keys when the analog mode is enabled but maybe there is a setting I haven’t found yet that prevents this.

Does someone else have those issues? Can I fix them? And is this a game or keyboard sided error? It would be a shame if such a great feature would be rendered useless because most games can’t use it properly.

Any help appreciated.




Hi there! Thanks for creating this thread. Allow me to forward this concern/feedback to our devs. Please send me the following:



a. Screenshot of System Information (Hit Windows+R to open the Run box. Type “msinfo32” into the “Open” field, and then hit Enter.)

b. Screenshot of Windows version (Hit Windows + R. Open the Run box with then type winver)

c. Screenshot of Synapse version (Click the gear/cog icon at the top right. For Synapse 3.0, click “About”).

d. Synapse 3.0 logs.

e. If it's feasible, a video showing the mentioned keyboard behaviors.



Save the compressed files via Google Drive or any online drive account, then paste the link in your PM. Let's continue from there.