Important Information These are community forums and not official technical support. If you need official support: Contact Us
The following comments are owned by whoever posted them. We are not responsible for them in any way.
Back to Threads Reply to Thread
I’m having trouble with my Xbox 360 controller on macOS Tahoe using CrossOver 25.1.0. The controller works perfectly on macOS 15.5 and also works fine with other apps like ShadPS4 emulator, so the hardware itself isn’t the issue.
The problem is only with CrossOver, it detects the controller but doesn’t map the buttons correctly.
Has anyone faced this issue or knows how to manually map the controller in CrossOver so it works properly? Any help would be appreciated!
Yep facing same frustrating,
Raised a ticket lets see if team has any fixes :)
I also face the same issue :(
Tried reinstalling and following reddit guide but no luck T-T
Same. On MacOS 26 now. I deleted all the old Crossover files and installed the regular version of Crossover, then tried the Preview version, but no luck.
Same issue...
Really surprised they couldn't diagnose this and fix it during the whole MacOS 26 beta period
Having the same issue with my Nimbus+ controller for all previously supported Steam games. As a workaround I am currently connecting the controller via Steamlink and can play games that way with some very minor latency.
team says bug filed, but might need a apple Mac os update, so i guess we have to wait until then
Might need a MacOS update?
Why would they say that considering the controller works fine in MacOS native steam?
Having same issue after latest Tahoe update ...
I’m running CrossOver 25.x on macOS 15 ("Tahoe") with an Apple Silicon Mac. My controller is an 8BitDo Ultimate 2
macOS side:
• The controller is fully detected in System Settings → Game Controller.
• Browser testers (hardwaretester.com) and a Swift probe using Apple’s GameController framework show correct extended gamepad events (sticks, triggers, ABXY, menu/options).
• Wired USB enumerates under IOUSBHostDevice; Bluetooth path goes through gamecontrollerd (AppleSyntheticGameController).
CrossOver/Wine side:
• CrossOver detects "a controller" in some cases but no button or axis events register in games or in wine control → Game Controllers (joy.cpl).
• Sometimes it doesn’t enumerate the controller at all.
• CrossOver ships with libSDL2-2.0.0.dylib, but runtime logs show no SDL joystick events, suggesting Wine on macOS is not actually using SDL2’s GameController backend.
Hypothesis:
Apple has shifted gamepad input to the GameController framework, hiding or restricting raw HID/hidraw access that Wine traditionally uses. Because CrossOver/Wine isn’t integrating SDL’s GameController API path on macOS, controller events never reach Windows applications.
Evidence:
• Swift GameController probe shows full extended events.
• CrossOver’s joy.cpl shows no movement.
• Wired USB and Bluetooth both fail inside Wine despite working in macOS.
I've been running betas, and this just started for me after the latest update ... though I have the 8BitDo controller .. what I did notice is previously I wasn't able to 'customize' the controller in MacOs settings ... after the latest update I am able to, though it no longer works with crossover .. looks like they (apple) has been adding controls to some firmware list (guess) and porting them into their gamecontroller api, which is bypassing hidraw or sdl or some other hardware controller wine uses.
Am I right to assume that this issue only relates to xbox 360 wired controllers? The bluetooth controllers from the xbox one and further do work, or are all controllers in general not working anymore?
with best regards
Xbox One wired and wireless controllers are broken, too. MacOS changed how it reads game controllers as far as I can tell, wine/CX hasn't made the change yet. Assuming they can.
Yeah, my wired xbox 360 controller works totally fine on the native steam app and native steam games.
Crossover detects the controller, but when I check DInput or XInput it is completely unresponsive to my inputs.
I just downloaded a 140GB game. If I downgrade crossover to an earlier version, will uninstalling crossover delete that bottle and I'll have to download again?
If anyone’s still looking for solution
I removed the dongle for my controller snd reconnect while crossover is open
Earlier it would fail to recognise
But right now steam identifies this as a play station retrobit controller
And i had to remap the x y a b
Buttons and its working fine that way
I finally get to enjoy games again.
Ill be around here if anyone wants to try
I have an 8BitDo Pro 2 controller that was working perfectly under Mac OS 15 (Sequoia) as well as all iterations of Mac OS 26 (Tahoe) Beta and CrossOver 25.0.0 and 25.0.1. My controller stopped working after I upgraded CrossOver to 25.1 in August. In some bottles, the controller is recognized but is completely unresponsive as reported here, in other bottles it simply shows that I have no controller. I have not had any issues with the controller being recognized on the Mac side. I had previously reported this but of course was told that because I was using Tahoe beta, I was out of luck for the time being. Well Tahoe is no longer in beta and the problem still stands - yet this problem started with the CrossOver update and not with a change in Tahoe versions. If anyone else is using the same controller as me and has it working under CrossOver 25.1 or higher, please let me know if you have any insights. Thanks.
I'm having a similar problem. I'm using an 8bitdo, and I recognized the controller, but it doesn't input at all, and after a certain period of time, it doesn't even recognize it. It doesn't go through crossovers and it recognizes normally on the Mac or Steam
In earlier versions, erasing and reinstalling the bottle worked normally in this case, but not in this version
mrbeezwax wrote:
I have an 8BitDo Pro 2 controller that was working perfectly under Mac OS 15 (Sequoia) as well as all iterations of Mac OS 26 (Tahoe) Beta and CrossOver 25.0.0 and 25.0.1. My controller stopped working after I upgraded CrossOver to 25.1 in August. In some bottles, the controller is recognized but is completely unresponsive as reported here, in other bottles it simply shows that I have no controller. I have not had any issues with the controller being recognized on the Mac side. I had previously reported this but of course was told that because I was using Tahoe beta, I was out of luck for the time being. Well Tahoe is no longer in beta and the problem still stands - yet this problem started with the CrossOver update and not with a change in Tahoe versions. If anyone else is using the same controller as me and has it working under CrossOver 25.1 or higher, please let me know if you have any insights. Thanks.
Hi! Are you using steam? If so try enabling steam input. ALSO if you have steam on your Mac and the games are the same install one and see if it works. If it work in steam on the Mac on the same game sounds like you may have duplicate controllers look in the menu for your launcher (steam, epic, etc..) on the right scroll dwwn if you have to and look for Game Controllers. Press that BUT FURST. Shut down crossover, Turn off your controller, Turn it BACK ON (Controller) then launch our game see if that helps that helped me once on an actual xbox controller. And seam sucks for input anya LOL I get so frustrated by the lag thats there sometimes...
Any word on this? It seems like the staff would be all over this bug. I ended up downgrading to macOS 15.7 to make the controller work again.
So I asked support for help with this issue, and they said it's a bug with Tahoe and that it won't be fixed without an update on Apple's end. They also told me downgrading my version of Crossover wouldn't fix the issue as it is an issue with Tahoe.
However, despite what they said, downgrading Crossover to 25.0.1 has indeed fixed the issue for me. I'm still using Tahoe. So I don't understand why they wouldn't be able to fix this without an update from Apple if the older version works, but what do I know?
JackBz wrote:
So I asked support for help with this issue, and they said it's a bug with Tahoe and that it won't be fixed without an update on Apple's end. They also told me downgrading my version of Crossover wouldn't fix the issue as it is an issue with Tahoe.
However, despite what they said, downgrading Crossover to 25.0.1 has indeed fixed the issue for me. I'm still using Tahoe. So I don't understand why they wouldn't be able to fix this without an update from Apple if the older version works, but what do I know?
Hi folks,
I'm the one that took Jack's ticket, and I'll share what I also shared with him. I was frankly surprised that CrossOver 25.0.1 is working better, but hey, I don't know everything, so that's great to know. CrossOver 25.0.1 does have many other controller issues, so while trying it out is obviously worthwhile, please be warned you might run into other issues. For this reason, simply updating CrossOver to revert to prior behavior isn't an appropriate fix. On the bright side, it is looking like Apple is looking into a fix.
Cheers,
Meredith
There is a lot of conflicting information regarding compatibility. I am prone to not upgrading to MacOS26 but also drawn to it because of DLSS...
It is very interesting to read the comments here and also the comments on reddit. I have the feeling that it also depends on hardware because some ppl have problems some don't. Some problems are resolved by reinitiating the controller some are not.
You can check out this reddit. it has some helpful tipps, maybe some problems are resolved with this:
https://www.reddit.com/r/macgaming/comments/1liqn67/do_not_update_to_macos26_tahoe_if_you_want_to/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Any updates on the status of this bug? Controller working perfect on Mac native games but not working at all on crossover, it recognizes it but I'm not able to use it, help please!
I updated to tahoe 26.1 beta release because apple mentioned a fix for controller but it still didn't work. Looks like this fix was for something else.
Just a tad bit of advice that if you are on a Beta OS you basically loose support with CO unless that's changed (Meredith?). I am using the latest retail version of Tahoe and Preview 26 of CO. I just tested on a few games and my xBox controller is working fine. I just was helping a user on discord last night with Borderlands 4 and I just now booted it up and the controller is fluid and moves as expected. Also works in D IV. As well as my indies like The Last Faith or Hades II.
Hopefully they find a fix for you guys. I'm not sure if it's because I've been using retail since prior to the MacOS release but 26 Preview was already into Tahoe. Strange all around...
Are you using wired connection ?, because I am facing this issue with wired connection on xbox controller on Tahoe
Varun Rawat wrote:
Are you using wired connection ?, because I am facing this issue with wired connection on xbox controller on Tahoe
No BT and as far as I know early on with one of the MacOS's they disabled wired but brought it back.
it should work with BT. I think the original post is also about wired connection
James Robertson wrote:
Varun Rawat wrote:
Are you using wired connection ?, because I am facing this issue with wired connection on xbox controller on Tahoe
No BT and as far as I know early on with one of the MacOS's they disabled wired but brought it back.
They haven't disbaled it in Tahoe, it works great on native steam and app store games for wired.
James Robertson wrote:
Just a tad bit of advice that if you are on a Beta OS you basically loose support with CO unless that's changed (Meredith?). I am using the latest retail version of Tahoe and Preview 26 of CO. I just tested on a few games and my xBox controller is working fine. I just was helping a user on discord last night with Borderlands 4 and I just now booted it up and the controller is fluid and moves as expected. Also works in D IV. As well as my indies like The Last Faith or Hades II.
Hopefully they find a fix for you guys. I'm not sure if it's because I've been using retail since prior to the MacOS release but 26 Preview was already into Tahoe. Strange all around...
I also use Tahoe 26.0.1 (not beta) and the latest CO Preview. My controller didn't work. Wired or BT. Both of them :(
But on native Mac, they work!! I already sent an email to the support but their response pretty much "wait for Apple to fix it". A bit disappointing :(
Dunno what to say then as I’m having no problems somehow it’s still working for me. And I know it works wired I said early on in MacOS they disabled wired but they brought it back ;)
I even made a new steam bottle to help a user with borderlands 4 and my controller worked just fine. I have no idea why but I’m not gonna poke the bear!
Hi folks,
We confirmed that Xbox controllers are working again as of macOS 26.1 beta 2 :) I am not encouraging anyone to install a beta macOS version, but wanted to let people know that there is a fix that should land in a release soon.
Link to the release notes: https://developer.apple.com/documentation/macos-release-notes/macos-26_1-release-notes
Best,
Meredith
On MacOS 26.1 now, controller still remains broken. Issue unresolved.
I would submit an official support ticket, esp if others are having the problem too. And share your findings here. I've not once in many versions of CO had BT XBox problems.
James Robertson wrote:
I would submit an official support ticket, esp if others are having the problem too. And share your findings here. I've not once in many versions of CO had BT XBox problems.
Not BT.
It's a usb wired xBox controller. Works fine with native Mac games, but not with CrossOver, since recent update.
Issue now solved with the latest November Preview release
1 to 37 of 37
Please Note: This Forum is for non-application specific questions relating to installation/configuration of CrossOver. All application-specific posts to this Forum will be moved to their appropriate Compatibility Center Forum.
CrossOver Forums: the place to discuss running Windows applications on Mac and Linux