Cyberpunk 2077

Cyberpunk 2077: Cyberpunk 2077 Analog Movement with Wooting Keyboard Guide, Updated for Patch 2.12

Posted on

Welcome to our updated guide on setting up analog walking and driving for Cyberpunk 2077 using a Wooting Keyboard (or any other analog-capable keyboard). With the analog capability of the Wooting Keyboard’s magnetic switches, you can now customize your walking and driving speeds based on how much pressure you apply to the keys. This guide serves as an update to the previous one, which was written 3 years ago and now has outdated mappings/keybindings. Additionally, the original guide set up both walking and driving on one joystick, which can cause issues as explained below. Let’s get started!

Why two joysticks?

It is much easier to setup the movement for walking and driving to only use the left joystick, but there is a downside. If you are driving a vehicle, and you accelerate (Right Trigger via the W key), and try to turn left or right at the same time (left joystick left / right via the A / D key), you will find that you will only be able to make very wide turns, despite pressing the A / D key to the maximum. This is because, due to the setup for walking, the W key not only activates Right Trigger as needed for vehicle acceleration, but also moves the left joystick up so that you can walk forward.

This means that you unintentionally move the left joystick up as you accelerate, which limits how much the left joystick is able to move left or right, as its range is confined to a circle.

The first pictures show the wheel and left joystick when you only press the W key (aka accelerate)

The second pictures show the wheel and left joystick when you press both the W and D key (aka accelerate + turn right)

The third pictures show the wheel and left joystick when you only press the D key (aka turn right)

The fix for this that I found, as the gamepad tester screenshots imply, is to set the steering control to the right joystick instead of the left joystick, and leave the left joystick solely for walking. This is done specifically by setting the “LeftX_Axis_Vehicle” mapping/keybind to use the “IK_Pad_RightAxisX” controller input instead of “IK_Pad_LeftAxisX”.

This setup assumes that you will use the analog controls for walking and driving (+ a few minor things like extra photo-mode control) and regular keyboard input for everything else, preserving the use of the regular WASD keys.

WOOTING / KEYBOARD SETUP

First, in the main Wootility settings, enable the Xbox Controller:

Make a new profile dedicated to this game, then setup the following advanced keys in the “Advanced Keys” section:

Then make sure the settings are set like this in the “Gamepad Mapping” section:

You may change the curve in “Analog Curve” but I cannot recommend a specific curve to follow

CYBERPUNK SETUP

Right click on the game in your steam library, hover over “Manage” and click on “Browse local files” to open the game’s directory folder:

While you’re here, also make sure steam input is enabled for Cyberpunk 2077, by instead clicking on “Properties…” and going to the following setting:

Once you’re in the “Cyberpunk 2077” folder, open the “r6” folder, then open “config”, then either replace the inputUserMappings.xml file with the one provided or open it with a text editor and make the changes listed below.

Here’s the file with all of the edits implemented, rename the file to remove the “.Analog.txt” part before replacing it with the one in the game folder: https://pastebin.com/L7swPDVv

Otherwise, here are the changes you will need to make in the file. Beware, its a big list…

THE CHANGES

1. For: <mapping name=”LeftX_Axis” type=”Axis” >
Remove:

<button id=”IK_A” val=”-1.0″ overridableUI=”left”/>
<button id=”IK_D” val=”1.0″ overridableUI=”right”/>

2. For: <mapping name=”LeftY_Axis” type=”Axis” >
Remove:

<button id=”IK_W” val=”1.0″ overridableUI=”forward”/>
<button id=”IK_S” val=”-1.0″ overridableUI=”back”/>

3. For: <mapping name=”RightX_Axis” type=”Axis” >
Remove:

<button id=”IK_Pad_RightAxisX” />

4. For: <mapping name=”FreeCam_RightX_Axis” type=”Axis” >
Remove:

<button id=”IK_Pad_RightAxisX” />

5. For: <mapping name=”Acceleration_Axis” type=”Axis” >
Remove:

<button id=”IK_W” val=”1.0″ overridableUI=”vehicleAccelerate”/>

6. For: <mapping name=”Deceleration_Axis” type=”Axis” >
Remove:

<button id=”IK_S” val=”1.0″ overridableUI=”vehicleDecelrate”/>

7. For: <mapping name=”Acceleration_Axis_Tank” type=”Axis” >
Remove:

<button id=”IK_W” val=”1.0″ overridableUI=”vehicleAccelerate”/>
<button id=”IK_S” val=”-1.0″ overridableUI=”vehicleDecelrate”/>

8. For: <mapping name=”QuestLeft” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftAxisX” />

9. For: <mapping name=”QuestBack” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftAxisY” />

10. For: <mapping name=”RangedAttack_Button” type=”Button” >
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

11. For: <mapping name=”RangedADS_Button” type=”Button” >
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.1″ thresholdRelease=”0.05″ />

12. For: <mapping name=”MeleeAttack_Button” type=”Button” >
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.2″ thresholdRelease=”0.55″ />

13. For: <mapping name=”MeleeBlock_Button” type=”Button” >
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.01″ thresholdRelease=”0.05″ />

14. For: <mapping name=”ThrowNPCAlt_Button” type=”Button” >
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

15. For: <mapping name=”BraindancePlayForward_Button” type=”Button” >
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.1″ thresholdRelease=”0.05″ />

16. For: <mapping name=”BraindancePlayBackward_Button” type=”Button” >
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.1″ thresholdRelease=”0.05″ />

17. For: <mapping name=”InspectionZoom” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftTrigger” />

18. For: <mapping name=”UI_vehicle_customization_mode_prev_Button” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

19. For: <mapping name=”UI_vehicle_customization_mode_next_Button” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

20. For: <mapping name=”LeftX_Axis_Vehicle” type=”Axis” >
MODIFY:

<button id=”IK_Pad_LeftAxisX” />

INTO:

<button id=”IK_Pad_RightAxisX” />

And remove:

<button id=”IK_D” val=”1.0″ overridableUI=”vehicleSteerRight”/>
<button id=”IK_A” val=”-1.0″ overridableUI=”vehicleSteerLeft”/>

21. For: <mapping name=”LeftY_Axis_Vehicle” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftAxisY” />

22. For: <mapping name=”LeftY_Axis_Vehicle_RockFB” type=”Axis” >
Remove:

<button id=”IK_W” val=”1.0″ overridableUI=”vehicleAccelerate”/>
<button id=”IK_S” val=”-1.0″ overridableUI=”vehicleDecelrate”/>

23. For: <mapping name=”Vehicle_Shoot_Primary” type=”Button”>
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

24. For: <mapping name=”Vehicle_Shoot_Secondary” type=”Button”>
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

25. For: <mapping name=”Dialog_LeftY_Axis” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftAxisY” />

26. For: <mapping name=”AimWithSniperNest_Button” type=”Button”>
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

27. For: <mapping name=”prior_sub_menu” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

28. For: <mapping name=”next_sub_menu” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.5″ thresholdRelease=”0.55″ />

29. For: <mapping name=”right_stick_x” type=”Axis” >
Remove:

<button id=”IK_Pad_RightAxisX”/>

30. For: <mapping name=”left_trigger” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftTrigger”/>

31. For: <mapping name=”right_trigger” type=”Axis” >
Remove:

<button id=”IK_Pad_RightTrigger”/>

32. For: <mapping name=”video_next” type=”Button” >
Remove:

<button id=”IK_Pad_RightTrigger”/>
<button id=”IK_Pad_RightAxisX” thresholdPress=”0.2″ thresholdRelease=”0.5″/>

33. For: <mapping name=”video_prior” type=”Button” >
Remove:

<button id=”IK_Pad_LeftTrigger”/>
<button id=”IK_Pad_RightAxisX” thresholdPress=”-0.2″ thresholdRelease=”-0.5″/>

34. For: <mapping name=”ep1_cyberware_perk_details_forward” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_RightAxisX” thresholdPress=”0.3″ thresholdRelease=”0.5″/>

35. For: <mapping name=”ep1_cyberware_perk_details_back” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_RightAxisX” thresholdPress=”-0.3″ thresholdRelease=”-0.5″/>

36. For: <mapping name=”sub_option_switch_next” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_RightTrigger” />

37. For: <mapping name=”sub_option_switch_prev” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_LeftTrigger” />

38. For: <mapping name=”option_switch_next_settings” type=”Button” SIEJADependent=”true” >
Remove:

<button id=”IK_Pad_RightTrigger” thresholdPress=”0.1″ thresholdRelease=”0.05″ />

39. For: <mapping name=”option_switch_prev_settings” type=”Button” SIEJADependent=”true”>
Remove:

<button id=”IK_Pad_LeftTrigger” thresholdPress=”0.1″ thresholdRelease=”0.05″ />

40. For: <mapping name=”PhotoMode_CraneDown_Axis” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftTrigger” />

41. For: <mapping name=”PhotoMode_CraneUp_Axis” type=”Axis” >
Remove:

<button id=”IK_Pad_RightTrigger” />

42. For: <mapping name=”minigame_LeftX_Axis” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftAxisX” />

43. For: <mapping name=”minigame_LeftY_Axis” type=”Axis” >
Remove:

<button id=”IK_Pad_LeftAxisY” />

44. For: <mapping name=”shooter_minigame_prone” type=”Button” SIEJADependent=”true”
Remove:

<button id=”IK_Pad_LeftAxisY” thresholdPress=”-0.1″ thresholdRelease=”-0.05″ />

45. For: <mapping name=”tank_minigame_attack” type=”Button” >
Remove:

<button id=”IK_Pad_LeftTrigger” />

Here is a backup of the original file if you messed up or wish to undo these changes (or you can delete the file from the game folder and verify integrity of game files thru steam): https://pastebin.com/cpFyp39k

CONCLUSION

That is all that is to it! While the original guide said to change the keybinds for walking / driving to something other than the WASD keys ingame, this seems to be unnecessary as the setup still works despite not changing them.

Issues:

  • WASD (aka left joystick) still moves the cursor in the game settings / inventory, I found that none of the mappings control it. Only an issue if for instance you liked to use A and D to navigate submenus, etc.
  • The game will rapidly switch between displaying keyboard icons and controller icons on your HUD, as of course it is detecting both keyboard and controller inputs at the same time. Wish there was a fix for this but I have not found any

Note: This mappings setup may become invalid (like in the original guide) if an update changes everything again, but I bet that will not be the case since the game has probably already received most of the updates it was going to get

Thanks for reading, let me know of any suggestions or issues

And that wraps up our share on Cyberpunk 2077: Cyberpunk 2077 Analog Movement with Wooting Keyboard Guide, Updated for Patch 2.12. If you have any additional insights or tips to contribute, don’t hesitate to drop a comment below. For a more in-depth read, you can refer to the original article here by Urinalism, who deserves all the credit. Happy gaming!

More Cyberpunk 2077 Guides

Tags: ,

Leave a Reply

Your email address will not be published. Required fields are marked *