You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2024. It is now read-only.
I recently purchased a DualSense Edge controller for my PC. When I first started using the controller with DS4, it had no problem! Was able to map keyboard/controller inputs to the Fn buttons and back paddles on the controller and all of the mappings worked in-game (Warzone) until I accidently press Fn+Triangle, which enabled the onboard default profile, making all of binds within DS4 not work anymore. Does anyone know a fix around this issue?
Steps to reproduce the behavior:
Plug a new DualSense Edge Controller and map buttons to the back paddles and Fn buttons within DS4Windows
Test to see if all the binds work from DS4 alone
Press Fn+Triangle to access the default profile on the controller
No longer able to use binds that were configured within DS4
The text was updated successfully, but these errors were encountered:
I would think that loading the default profile would be what is required to get bindings to work within DS4Windows. I obviously do not own a DualSense Edge controller so I have no clue what mode you need to be in to get the controller to work in DS4Windows again.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey everyone,
I recently purchased a DualSense Edge controller for my PC. When I first started using the controller with DS4, it had no problem! Was able to map keyboard/controller inputs to the Fn buttons and back paddles on the controller and all of the mappings worked in-game (Warzone) until I accidently press Fn+Triangle, which enabled the onboard default profile, making all of binds within DS4 not work anymore. Does anyone know a fix around this issue?
Steps to reproduce the behavior:
The text was updated successfully, but these errors were encountered: