[Xbox Mapper For Mac
Ainoha Sistek
I tried to connect my xbox controller to my MacBook, even though the controller is registered in bluetooth setting, but it doesn't function at all.Have anyone met the same problem and if there's a fix for this problem
We appreciate your feedback in the Developer Forums. We believe this issue is already resolved in macOS 12.3.1. If you are still seeing this issue, please submit a feedback report to ensure the issue can be investigated by the relevant engineering teams. You can do so from the Feedback Assistant app or Feedback Assistant website.
I'm not entirely sure why this happens, it happens intermittently for me. The last attempt I took was Delete the controller, Turn off Bluetooth, Restart, Reconnect Controller- but while I was reconnecting there was a phantom controller that popped up that showed the original controller connected, but I could not disconnect it through the Mac, I turned the controller off and the phantom controller popped back down to the unknown devices and upon entering bluetooth mode on my ps4 controller the phantom controller was identified as a ps4 controller and I was able to connect and use the controller again to play games. I hope this helps!
I still have a weird issue, but like I said on my iPhone, my Xbox controller will connect, and then make the Virtual Controller disappear indicating that the Controller is connected (at least). But nothing functions from the Xbox controller. Then turn off controller and Virtual Controller comes back on... (the controller is there in the debug info, Mac too if I am not mistaken).
Also experiencing the same issue. My Nimbus + Controller won't work with Apple Arcade after updating to Monterey 12.3. I'm able to connect via bluetooth, but none of the buttons work. I'm sure there are a lot of Mac Gamers with the same issue and hopefully Apple fixes this soon.
Looks like two games I tested have broken controller support. Both of them are Unity games using the InControl framework. I tried three controllers with each: An Xbox Series X controller, a DualShock 4 controller, and a Stadia Pro controller connected via USB, which appears as a generic controller with vaguely Xinput like features.
Just adding my experience to the list in the hopes this gets addressed. I have tried three different bluetooth controllers (XBOX One, PS5 DualSense, Nintendo Switch Pro Controller) and the issue is the same across all 3. Bluetooth has no problem connecting the controllers to my M1 MacBook Pro, pressing the Home buttons on each controller brings up a game selection bar, and I can use the controller to select games. However, regardless of which game I select, once I am in-game, no controller input works except the Home button to bring the game selection menu back up. No issues prior to the Monterey 12.3 Update.
I tried to livestream the log through console. I am not a pro in IT but hope it helps. There are two findings. #1 When plugged in via USB cable and press the pairing button on my controller, console shows that the USB port read the signal and immediately disconnect shortly afterwards. #2 When pairing via bluetooth, message "configuring controller, will try again later" will nonstop pop up until Bluetooth stop trying to pair up with the controller.
I'm having same problem, noticed the ps4 controller is working fine with it but ps5 controller is not. The symbol/icon when i connect my ps5 controller vs my ps4 controller via bluetooth is different.The ps4 controller shows an ps4 controller icon and allows me to connect normally.The ps5 controller shows a normal bluetooth symbol (same as my iphone).When connected a monitor will show a monitor icon next to it, a mouse will have a mouse icon, a speaker shows a speaker etc... Somehow need to change how the mac bluetooth recognizes the controller.
Just adding that I'm having the same issue. I've tried Xbox One, PS4, and a generic controller that I used to use frequently and none have worked. I've tried all of them corded and Bluetooth with no luck. The game I've been trying to get it to work with is Final Fantasy XIV by Square Enix. I've been seeing advertisements for another new OS update, any word if we'll receive a fix before or even with the new update?
I am using a wired x box 360 afterglow controller. I plugged it in and installed xboxdrv. On the joystick pane all the buttons are mapped properly but when I load a game on steam several of the buttons don't work and the ones that do work are not mapped to what they actually are (right trigger is the start button etc..) i went into the steam controller setting and remapped everything there to the proper place. When I load up a game afterwards its the same thing. I am using ubuntu 14.04 and cannot seem to come up with a solution.
As much as you might think it would be a simple fix, it is absolutely not. The xbox adaptive controller can not be be rebound to oculus touch controller mappings without some serious firmware updates. the touch controlers have propietary mapping for the headset. The ammount of development it would take to have it all work seamless with touch controller and the specific app requires a lot of development.
Yep, I work in games and sometimes things that look really simple really aren't when you look under the hood. I think "effective" would've been a better word, because if Oculus made it possible to use game controllers and VR controllers at the same time, it would immediately help literally millions of people to use Oculus. Currently you can't even pair the Xbox Adaptive Controller with the headset (at least I couldn't), and there's really no excuse. To the best of my knowledge it sends all the same stuff an ordinary gamepad does.
I actually bought a nice set of straps from VR Cover. They are really useful for preventing flying controllers when playing Beat Saber, but unfortunately they make using the buttons even harder for me. My issue is that my finger movement is very limited, so my hands have pretty much only two modes: open or closed. On a good day I can do the grab thing if I hold the controllers just so, but it's very slow, awkward and error prone, which sucks out all the fun. Just being able to map the triggers to foot pedals would make a world of difference.
Hi, I have managed topper the Xbox Adaptive Controller with the Oculus Quest quite easily. You need to have XAC in pairing mode then in headset go to settings> experimental> bluetooth pair> The XAC shows up, pair and it's connected. This lets you use the headset gaze white dot to navigate and the controller to hit buttons to trigger. It works perfectly within the Oculus environment, but as soon as you go into games etc it doesn't work! Very frustrating! WalkinVR theoretically allows you to use an xbox controller in 'companion mode'....once I manage to download it, I'll let you know!
I actually have WalkinVR installed and waiting for a deep dive. Now that I tried it in No Man's Sky and Tabletop Simulator, the "co-pilot" using an ordinary Xbone gamepad kind of worked. I could move and turn using the sticks, but the controller buttons with the trigger and grab functionalities didn't do anything, and the movement was super choppy. Anyway, it does have potential for helping with certain PC games.
Having trouble with a Facebook or Instagram account? The best place to go for help with those accounts is the Facebook Help Center or the Instagram Help Center. This community can't help with those accounts.
I've gone through this dance three times now. So I'm going to document it this time and hopefully save some other poor souls some effort. It's loosely Arduino related in that a lot of people like to control things with these controllers.
You have to get rid of xpad for xboxdrv to work. You can:
sudo rmmod xpad
every time you want to use the xbox controller or you can go into /etc/modprobe.d/blacklist.conf and add:
blacklist xpad
to the end of that file. You'll need root privileges to modify it.
So you go to /etc/udev/rules.d and you create a new rule in that directory. You create a filename with xx-someName.rules where xx is a number above 50 that isn't already used in that directory and someName is whatever you want to name it.
Now when you run xboxdrv without sudo you see that it finds a uinput device but you don't have permission to use it. So use usermod to add yourself to the plugdev and input groups. Now restart and you should be able to run xboxdrv without sudo and see output from the controller.
Fact is the only reason I downloaded this game again was because I had recently bought this controller and thought I'd give DA:I another go again, because the controls were absolutely horrendous playing with keyboard and mouse.
I guess I will simply have to uninstall the game again even though I haven't finished it, because I don't think I could stand to attempt another playthrough with these terrible, blatantly console oriented controls
Edit: I don't know if controls have been patched or not, but they're not as bad as I remember them. Still, they are quite clunky and I would love to be able to play with a controller (a modern one, at that).
It turns out this is a shortcoming on Microsoft's side. It is a known issue that Xbox One Elite Controllers can simply stop working in games for no apparent reason whatsoever. The controller works just fine in Windows 10 and joy.cpl, but it fails to work in games in general.
I'm not sure if this has to do with any controller updates (seeing as there are none, Windows 10 has the latest Xbox One (Elite) Controller drivers built-in, rather it would seem this is due to a, as far as anyone can tell, random change drivers.
The frustrating thing about this whole ordeal is that the controller worked just before I started playing Inquisition again so I just assumed it was working with all other games. and so I blamed this on BioWare. Strange thing is, Origin or Inquisition were the only things I updated/changed and I have a hard time believing any of those would incite this change in hardware drivers.
795a8134c1