PS5 controller connecting wireless gives in-game recognizing issues

[Domenco]

Hello,

Title is a bit vague but when you disable Playstation controller support and connect a PS5 controller through a WIRE, games will detect a PS Controller and use the correct button mapping in-game.

If you Enable Playstation support, games will show Xbox button mapping in-game.

If you Disable Playstation support and use your PS5 Controller WIRELESSLY, Playstation support gets forced ON even though it is disabled in the menu. Giving the problem that you get Xbox button mapping again.

Does anyone know a fix for this issue? I would like to use my Controller in FF7 remake and Eldenring with the correct button mapping wirelessly.

[Nx Machina]

Button mapping is set up by the developer and in general will always show Xbox prompts but some developers set up prompts based on the controller connected. Prey 2017 is one such example where the controller connected dictates then prompts shown.

[Domenco]

Ursprünglich geschrieben von Nx Machina:

Button mapping is set up by the developer and in general will always show Xbox prompts but some developers set up prompts based on the controller connected. Prey 2017 is one such example where the controller connected dictates then prompts shown.

Both mentioned games have native Playstation controller support. works wired but not wirelessly.

[Nx Machina]

Ursprünglich geschrieben von Domenco:

Both mentioned games have native Playstation controller support. works wired but not wirelessly.

I do not have either of those games but i was speaking from the perspective that most games support Xbox prompts only unless the developer also chooses to implement PS prompts as well.

Secondly that points it to been a Windows issue (although i may be wrong) rather than a Steam issue as Windows does not have native support for Playstation controllers.

Both DS4 and DSE controllers (wired) shows as a Wireless controller but do not function on Uplay Connect or Rockstar launcher. You have to use a 3rd party app such as DS4Windows (Ryochan7 version).

[Domenco]

Ursprünglich geschrieben von Nx Machina:

Ursprünglich geschrieben von Domenco:

Both mentioned games have native Playstation controller support. works wired but not wirelessly.

I do not have either of those games but i was speaking from the perspective of most games support Xbox prompts only unless the developer also chooses to implement PS prompts as well.

Secondly that points it to been a Windows issue (although i may be wrong) rather than a Steam issue as Windows does not have native support for Playstation controllers.

Wired it shows as a Wireless controller but does not function in for example Uplay Connect or Rockstar launcher. You have to use a 3rd party app such as DS4Windows (Ryochan7 version).

Ok thanks for trying to help, windows added support for wireless controllers (and specifically the PS5 controller) a while ago, even in non steam games, games can detect the controller.

This is 100% a steam problem and their implementation of the Playstation controller API. I described the problem thoroughly, Steam is messing with the wireless connection and forcing playstation controller support ON messing with everything.

[Nx Machina]

Ursprünglich geschrieben von Domenco:

Ok thanks for trying to help, windows added support for wireless controllers (and specifically the PS5 controller) a while ago, even in non steam games, games can detect the controller.

This is 100% a steam problem and their implementation of the Playstation controller API. I described the problem thoroughly, Steam is messing with the wireless connection and forcing playstation controller support ON messing with everything.

Windows 10 21H2 sees the DSE as a wireless controller but does NOT function in Uplay Connect or Rockstar Launcher as previously stated so the Windows support you stated was added is broken for those two clients. I have to use DS4Windows (Ryochan7 version) for those two clients.

[Domenco]

Ursprünglich geschrieben von Nx Machina:

Ursprünglich geschrieben von Domenco:

Ok thanks for trying to help, windows added support for wireless controllers (and specifically the PS5 controller) a while ago, even in non steam games, games can detect the controller.

This is 100% a steam problem and their implementation of the Playstation controller API. I described the problem thoroughly, Steam is messing with the wireless connection and forcing playstation controller support ON messing with everything.

Windows 10 21H2 sees the DSE as a wireless controller but does NOT function in Uplay Connect or Rockstar Launcher as previously stated so the Windows support you stated was added is broken for those two clients.

Because the clients don't have added support. The controller will still ping its ID as a Dualsense controller when asked by a program. As evident if you try to boot up Final Fantasy 7 Remake, which will detect the controller and change the input mapping accordingly.

But that is not the issue I am having, This is about steam. The controller works fine for anything else, even Emulators (some emulators even autodetect the controller).

[Nx Machina]

Ursprünglich geschrieben von Domenco:

Because the clients don't have added support. The controller will still ping its ID as a Dualsense controller when asked by a program. As evident if you try to boot up Final Fantasy 7 Remake, which will detect the controller and change the input mapping accordingly.

But that is not the issue I am having, This is about steam. The controller works fine for anything else, even Emulators (some emulators even autodetect the controller).

You stated Windows added support for the Dualsense which by definition would mean the controller functions irrespective of whether a client has controller support. The Xbox controller functions on both those clients so obviously Dualsense support is broken on Windows.

EDIT:

Just tested Prey 2017 both wired and wireless with Steam controller input plus Playstation support and PS prompts are shown for both the DS4 and DSE which suggests the issue for you is game related.