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
Aside that all you can really do is try to run it with a cable. It does perform better this way. The sony controllers are proprietary tech so this can often happen.
Also, I don't know if you have the option to do otherwise on Mac, but when you pair the controller put it into pairing mode and then choose to connect it via BT menu.
-----
An M1 or Intel?
On either you can use the Steam Input Configurator and map the pad to KB controls.
If an Intel, then Steam's gamepad driver can be installed and Steam can emulate an Xbox 360 controller. As far as I know the driver is still not compatible with M1's.
To map the pad to KB controls:
1. Enable Steam Input/PlayStation Configuration Support
View > Settings > Controller > General Controller Settings > enable PlayStation Configuration Support
2. Right-click the game in Steam Library > Manage > Controller configuration
3. (You can use the gamepad or mouse or kb here) Click a gamepad control > select keyboard key to map it to. If it's a group (like the face buttons), choose the group, then the button, then the key to map it to. Select Back and continue same process with next gamepad control.
4. Done
It's likely someone will already have made a configuration mapped to keyboard for Brawlhalla that you can just apply instead of creating it yourself. You can check like this:
Go to the controller configuration for Brawlhalla, choose Browse Configs > Community > see if any config there mentions mapped to KB in name or description > highlight it > Import Config > Apply Configuration > Done
Update: I checked it out and configuration named Brawlhalla PS4 (by Magmirian) is mapped to KB. KungFuDynamite also has one with the same name but their KB mapping is a little different.
I think that will cover it so see how that goes.
When I can I'll check Brawlhalla with my controller in PS mode and see how things go on my end.
Update: So tested it on Windows and the game works with my controller in PS mode over BT. I believe doing the stuff at the top will be enough for you on Mac as it was for me on Windows since the game natively supports the DS4 in it's DirectInput state.
Thanks! This helped, but right after I mapped the pad to KB using either my own or Magmirian's, whenever I input a direction, it just scrolls fast, which I think is called stick drift. I don't believe it's a problem of the stuff (like dirt) inside the controller, because when I used the ps4 controller recently with a cable, it doesn't have the same problem (the cable isn't working right though, that's why I'm trying to resort to BT).
Update: oh wait, it might really be the controller itself
If it feels like it's not just the gamepad check this:
Under detected controllers does Steam also list Xbox controllers? There is a Steam bug that looks like the controller it creates gets fed back into it or something. I was helping someone else and they found that inputting a direction would result in auto-scroll.
They used this process to hide Steam's virtual controller from itself:
https://steamcommunity.com/discussions/forum/2/3198119849656535195/#c3198119849666679596
If the controller_blacklist entry doesn't exist, check the post below that one for info.
To undo the blacklisting, select the option Unhide Devices on the Controller Settings screen or follow process but revert changes.
It's likely not so much stick drift, if it ain't worn.
It's likely to be your deadzones aren't sett correctly.
These are the dead spots where the sticks rest when idle. Typically they will show SOME signal residually, so you need to change that if you can to give it a bit of a wider berth before it activates.
i've no idea whether it's in your settings, but that's what you should be looking for I guess.