Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Games can use Scepad.dll to natively communicate with a PS4 controller. They also continue to see your PS4 controller as a PS4 controller if they use HID. There might be problems with games that only use DirectInput, but I don't know how many of these exist in the wild. My experience has been that games with support for DualShock button prompts will use HID to identify the controller, and Steam doesn't mess with that.
I do not have any of the aforementioned 3rd party programs (DS4Windows or otherwise) installed. Which games specifically do you have in mind that use HID and therefore do not revert to Xbox button prompts? If what you say is in fact the problem, it would be good to know of some games that use HID in case I end up buying any of them.
Many other games use texture mods to give you your buttons, which you're probably familiar with ;)
It's interesting that you mention The Witcher 3, because that was one of the ames that I had this problem with. I'll double check sometime tomorrow, but I think it did.
To give you proper context, allow me to display the button icons in their full glory :)
http://steamcommunity.com/sharedfiles/filedetails/?id=1118727969
I've moved my mouse over the Xbox prompts. Very easy to mistake Steam for Xbox.
In any case, this problem is due to The Witcher 3 adding Steam controller detection early in the lifecycle. There are better ways through SteamAPI of detecting a Steam controller now that CD Projekt should be using. As soon as you turn the custom mapping off, The Witcher 3 immediately recognizes the PlayStation controller icons again.
Right, which was my problem to start with. I suppose there're too many factors involved for it to be given a simple fix.
But I have to admit, I misunderstood your problem because you originally mentioned Xbox buttons. The game's not confusing your controller for an Xbox controller, it's confusing it for a Steam controller and you're seeing the similar buttons and calling them Xbox :)
I don't think there's a vey distinct difference. The Steam controller is set up just like an Xbox controller, which came first. Dualshock controllers and nintendo controllers have very different designs. Steam and Xbox controllers are very similar. I'm just nitpicking, though :p
I did mention that my problem was that enabling Configuration support made games recognize my Ps4 controller as a Steam controller, too.
Thanks for the help, in any case.
Do I have to make a specific setting?
As addition I try to play through Steam Link. Both PC and Steam Link are connected with wires.
The games I want to play are Rocket League and Mad Max.
When I am on the PC I get the PS button prompts. When I start Big Picture on the PC they change to the ♥♥♥♥♥♥♥ A/X/Y/B buttons. So it must be a problem with Big Pictures.
Can someone help me?
If the game supports the current version of SteamInput natively, then the game WILL use the correct button prompts.
If it supports the steam controller directly, but not the new SteamInput, and you run it with configuration, Steam Big Picture will remap your ps4 controller into a steam controller, with it's prompts. This is the Witcher III problem. it's advertising steam controller support specifically.
If the game supports neither, steam will try to impersonate an xbox controller, using it's prompts.
if the game has native ps4 controller support (using libscepad.dll) then if you DISable steams control configurator, it will see your DS4 fine, and if it's programmed to use rumble with the native support, it will work, and if not, it won't. That's not steam's fault.
The problem is if you use big picture controller configuration with a game that does NOT natively support SteamInput, then it will pick a controller type that the game is known to support to impersonate. If it's impersonating another controller, you get the button prompts that belong to the impersonated controller.
What can be improved.
1) have the launcher check the game directory for libscepad.dll. if it's there, AND your controller is indeed a DS4, be nice and shut yourself off, so the program will detect your DS4 properly.
2) if a game supports mutiple controller types, have the option to select how your controller is presented to the game, instead of it always using xinput or steam controller if the game supports it.