Announcement

Collapse
No announcement yet.

Can't remove native input from back paddles using Dualsense Edge in ER: Nightreign

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

  • Can't remove native input from back paddles using Dualsense Edge in ER: Nightreign

    Using default mapping in game itself and having no mapping on back paddles (like how it can be added via Playstation Accessories) causes game to register LeftPaddle and RightPaddle as square and X accordingly. Adding any combo to paddles in config leads player to use flask (LP) or jump (RP). My idea was to add skill combos such as triangle + L2 and triangle + O, but native input always registers first, with occasional custom combos going through only after.
    Attached Files

  • #2
    It's possible that your DualSense Edge has had its game profile changed via the PlayStation 5. You may need to connect the controller to the console to change the profile back to the default as described here.

    Comment


    • #3
      I mentioned that there is no action/button tied to back paddles, I checked it in Playstation Accessories app, default profile doesn't have paddle binds and using custom one with specifically turned off buttons doesn't change anything

      Comment


      • #4
        Originally Posted by Arty_2099 View Post
        I mentioned that there is no action/button tied to back paddles, I checked it in Playstation Accessories app, default profile doesn't have paddle binds and using custom one with specifically turned off buttons doesn't change anything
        At the same time, in reWASD, you also have nothing mapped on your paddles (based on the config you sent).

        Comment


        • #5
          yes, but game still triggers square on left paddle and cross on right one. I can add combos to them, but square and cross still trigger

          Comment


          • #6
            If you are playing through Steam, try disabling controller support in Steam settings.

            Comment


            • #7
              Problem was indeed in steam input, totally forgot about that, thanks

              Comment


              • #8
                Always happy to help

                Comment

                Working...
                X