Archive. This is an archive of the Apple Support Community. Discussions are being restored and soon you will be able to read and post here again.
kingrurik
User level: Level 1 (4 points)

DualSense controller inputs not registering on MacBook Pro M2 after Golden Gate update

I'm using a Macbook Pro 13-inch M2 2022, currently running Golden Gate 27.2.


Since updating to Golden Gate a couple months ago, my Dualsense game controller hasn't been working properly. I didn't have any issues with my controller on Tahoe, but since updating I've had issues with inputs not going through- I press the button, and nothing happens. Which buttons work and don't work seems to be random, though it's primarily the d-pad and face buttons. The issue is very inconsistent, and comes and goes while I'm playing.


I've tested over bluetooth and a wired connection, and with another, much newer Dualsense controller, and the issue persists. It's not an issue with the games or software I'm using- even with all other applications closed, in the Game Controllers menu, the controller name normally lights up when any input is correctly registered, but I face the same issue- seemingly randomly, inputs will not register, and the controller does not light up when a button is pressed.



I've disabled location services and anything else I could think of that could be disrupting the connection, to no effect. I've tried resetting the controller, erasing all settings and reconnecting it, I'm genuinely out of ideas as to what I could possibly do just to make it work as well as it did a couple of months ago.

Posted on Nov 8, 2026 10:12 AM

4 replies

kaz-k
User level: Level 9 (53,902 points)

Nov 8, 2026 10:53 AM in response to kingrurik

Hi,

The macOS "Golden Gate" (macOS 27) update has introduced known compatibility and permission bugs that break DualSense controller inputs in emulators and streaming apps (such as OpenEmu, vAmiga, and Moonlight) even when macOS detects the device.


Known Workarounds & Troubleshooting Steps

  • Test Input First: Verify whether the controller registers on a web tester like Gamepad Tester or via Steam to see if the issue is system-wide or restricted to specific emulators/apps.
  • Bypass Bluetooth via USB: Connect the DualSense Wireless Controller directly to your MacBook Pro M2 using a USB-C cable, as wired connections frequently bypass Bluetooth-layer input drops in newer macOS versions.
  • Erase Controller Settings:
    1. Go to System Settings > Game Controller.
    2. Select Erase Controller Settings if available.
    3. Go to System Settings > Bluetooth, forget/remove the DualSense device, and re-pair it by holding the PS + Create (Share) buttons until the light bar flashes.
  • Check App Permissions: For streaming or remote tools (like Moonlight), ensure Local Network and relevant input permissions are granted under System Settings > Privacy & Security.
  • Use Steam Input: If playing games through Steam for Mac, enable PlayStation Configuration Support in Steam Controller Settings and force Steam Input for the specific game.


kingrurik Author
User level: Level 1 (4 points)

Nov 8, 2026 2:17 PM in response to kingrurik

Granting System Settings Local Network permissions does seem to have helped- though that could be circumstantial. The issue still persists, though mostly when pressing multiple buttons at once, or when pressing buttons in quick succession.


This is obviously still an issue for a lot of games, but at least at the moment it seems to be resolving more quickly- the controller will miss an input, but become responsive again after a few seconds, where before it could take minutes, multiple resets, and pure random chance to get anywhere near functional.


The issue persists whether connected via USB or Bluetooth, but does seem similarly improved either way.

kingrurik Author
User level: Level 1 (4 points)

Nov 8, 2026 11:10 AM in response to kaz-k

Yes, these are all things I've tried. The issue persists in Gamepad Tester, Steam, and even just in the System Settings > Game Controllers menu- this menu doesn't show which buttons are being pressed like Gamepad Tester does, but the controller name lights up when it reads an input, and the issue persists here even when all other apps are closed.


USB Connection didn't solve the issue.


Erasing all controller settings and re-pairing seemed promising, but ultimately didn't fix the issue.


All relevant apps (steam, moonlight) have Local Network permissions. I tried adding System Settings to the list, and at least in the short term things seem to be working consistently? Though given the inconsistent nature of the problem, that could be coincidental. I will report back if the issue recurs.


Steam Input and PS Config Support are enabled.

kingrurik Author
User level: Level 1 (4 points)

Nov 8, 2026 5:44 PM in response to kingrurik

Not too surprisingly, the d-pad is acting up again, so any improvement was likely coincidental.

Originally posted at discussions.apple.com/thread/256390906