Perhaps more accurately, the World Map will not stop scrolling Southwards, since I plugged in my new Razer Huntsman v2 Analog keyboard.
I’ve actually experienced something similar previously, with an Xbox controller plugged in, but that was easily solved by wiggling the joysticks a bit, presumably getting them into their respective deadzones.
I’ve cleared the mappings on a new virtual Controller that appears to have been created and tried disabling the USB controller devices that have spawned in Windows, apparently as a result of plugging the keyboard in, but have yet to succeed in finding the culprit.
I understand that this will probably eventually need to go back to Razer, but I just wondered if anyone here had experienced anything similar with a keyboard and what the solution might have been?
Thank you for your post! Your topic has been moved to a sub-category of the User Support Hub
The General Discussion category is meant for discussions that fall outside of our other sub-categories.
If you would like other users to help you with an issue you are experiencing in the sim, consider these User Support Hub categories for your future post:
My previous post could, in no way, be considered a solution, but you should now be able to move that marker to this one.
It would appear that the Razer software, Synapse, that comes with the keyboard, might have initially installed itself in an odd state, as after I’d agreed to set bindings to the virtual xbox controller and then try the world map, pressing the “W” key stopped the movement and so far, that seems to be the solution. I have since cleared those virtual controller bindings and the world is still pleasantly still.
Well, it looks like my “solution” would be better termed a workaround, as the issue recurs each time I restart my PC. There is definitely an issue with the Razer profile and/or synapse, when it first starts up, that they’ll need to correct.
In the meantime, I’ve found a lasting solution, from the Razer Forum, that involves disabling the XBOX Controller for Windows, via device manager, and following a windows restart, the issue appears to be gone forever. Reassuringly, this solution also seems to leave my real xbox controller unaffected, when i plug it in and as I currently have no plans to use my keyboard as a controller, the solution will do just fine for now.
