Announcement

Collapse
No announcement yet.

Not all keyboard buttons mapped to my controller (DS4 or Flydigi Vader 4 Pro)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Not all keyboard buttons mapped to my controller (DS4 or Flydigi Vader 4 Pro)

    New user here. I am trying to map keyboard buttons to my Flydigi Vader 4 Pro to play Valorant. I downloaded Rewasd a few days ago (V 9.1.2.10339). I set the Vader 4 Pro to Dinput mode and Rewasd detects it as a Vader 4 Pro. I proceed to configure my controller mapping. When I press on any button on the Vader, Rewasd sees the press. After configuring the mapping, I clicked "Apply to Slot 1" and I get the yellow pop-up notification saying 'Valorant: [controller name] is active in Slot 1'.

    I load the game and the only buttons/controls that work on the Vader 4 Pro is the left joystick, X, and B buttons. I tried connecting my Dualshock 4 and i get the same results. Only the left joystick, X and B buttons worked on the DS4.

  • #2
    Hi. Valorant works with only one keyboard and mouse input. In order for the game to see the input from the remapped stick, the mappings should be emulated on behalf of your physical devices. Right now, this behavior only affects the mouse, but you can choose both to be sure that everything works perfectly with this or upcoming game’s versions.

    So, to resolve the issue you need the following steps:
    - Go to Preferences (gear icon at the bottom right) → Input Devices tab
    - Choose the physical devices you are currently playing with in the drop-down lists (1) and click Apply (2):
    - Apply your Valorant config (or choose one of those we have in our community and play.
    - You can also check 'Do not create Virtual Input Device for reWASD' (3) after you have chosen the physical devices. This will help avoid the issues with Valorant that may use the mouse exclusively and doesn't let it work in Windows.

    Click image for larger version

Name:	image.png
Views:	22
Size:	155.4 KB
ID:	245951​​

    Comment


    • #3
      this worked. thank you!

      Comment

      Working...
      X