New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
⚠️ READ BEFORE POSTING - BigSur / M1 / Intel / Errors with Driver #1139
Comments
Thanks, so this works on M1 Big Sur?? |
|
Xbox series controller works after firmware update on windows or on the xbox |
@Johnth10 |
Sorry for not being precise. Answers to your questions : Read this : #1119 |
thanks for clearing that up, this is good to know! I will add this to the main post once I clean up the markdown formatting a bit to make it easier to read. I also update my xbox one controller firmware and can confirm even on Intel macs it works for both bluetooth and wired with no issues. 👍 |
Good to know. Thank you for your work. |
I tried my Xbox controller on Parallels and it worked with a wire which is kind of odd. But now it doesn't work. |
I have had nothing but nightmares in past attempts to use virtualization software to play games; which is why its not a listed option. yeah, it might have worked for a moment but this is something ive found to not go away. which is why boot camp is a more stable option. this issue it’s beyond my scope, so if your determined maybe you can google for some answers. only hint i can tell you is to shut down the emulation and check out your settings for Usb/accessories. best i can tell ya. |
The problem is that I'm on the M1 Mac and it runs ARM processors so it doesn't work. Parallels have a beta which makes Windows 10 work but it could run into issues maybe that's why. But, if Bootcamp comes with support I'd switch to it. Thanks! |
oh right forgot about that. well someone was able to make bootcamp work on the M1. they did something with the arm build for windows microsoft has. um i saved it i will look it up for you maybe it might help you. |
okay here are two links that might help. [1st person to run windows on M1] [using parallels to run windows on M1] |
Thanks, I'm currently using Parallels now and it is fast. |
@L0VEFIRE |
How? |
he is using a Intel Processor hence the mac model he is using. |
this might be worth looking into if you haven’t read it already, but i would read it very carefully, a lot of important steps that must be followed for it to work correctly. |
Aren’t those steps for BlueTooth though? My controller doesn’t have BlueTooth. Thanks anyway man! |
@FatSandwich what version of xbox controller are you using by chance.? full name and model (should be on back) |
Model: 1537 Also, what's weird is that in the device's settings in Windows 10 it shows "Controller - Connected". But, when I go to https://gamepad-tester.com/ it says "No Gamepad Detected". Another weird thing is when I first connected my Xbox controller to my M1 mac it worked flawlessly in Parallels and I could even use it to play games, but now it just doesn't work! Thanks for your help! |
I have a similar issue to But they didn't seem to fix the issue. |
reference this link go to method 1 uninstalling the driver. see if that helps. but i will say windows 10 on its own has issues with pairing xbox controllers. yours is wired so maybe a different cable,. see if uninstalling helps if so might be on to something |
I tried uninstalling the driver but that didn't work either. At this point, I'll try reinstalling Windows 10. |
IT WORKED!!! REINSTALLING WINDOWS 10 WORKED!!! I should have tried it before! Thank you so much for your help man! |
And now it's not working again!!!!! It did the same thing as last time!!! |
@FatSandwich
This is interesting, that removing the driver did nothing yet re-installing the OS made it work again. It must have cleared something that was present, that is getting stuck or something when you connect your control. I wonder if this is a M1 thing.
I would strongly suggest you join the conversation on parellels fourms and also start a support ticket to get his looked into.
Here is the Fourm for M1
https://forum.parallels.com/forums/parallels-desktop-16-for-m1-mac-technical-preview.786/
Here is the main support page.
https://www.parallels.com/support/
I really wish i had an M1, so i could look into this more. I hope in time someone can answer you question once you post your issues and get help.
… On Jan 18, 2021, at 7:35 PM, FatSandwich ***@***.***> wrote:
And now it's not working again!!!!! It did the same thing as last time!!!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Yeah I hope so! Thank you I will go the forums and ask them! |
You need to use the ARM64 compiled binary which is mentioned further up in the post. |
@mmg1988 can you please share your development instructions to compile on Apple Silicon? |
Where is it? |
Here https://github.com/360Controller/360Controller/files/9063388/Install360Controller.pkg.zip But I'm wondering if @mmg1988 can provide his build steps/process. I just want to ensure I install safe code. |
@mmg1988 also kindly ask to provide build instructions for Apple Silicon as readme says the XCode 6.4 is needed to build the project, the one that can't be installed on Ventura. |
Still desperate to know now to build it for M1. But thanks to this thread, this build from @mmg1988 https://github.com/360Controller/360Controller/files/9063388/Install360Controller.pkg.zip (it's alpha5) and instructions from #1227 I was able to connect 8bitdo Ultimate Wireless Controller with Charging dock (Bluetooth) in 2.4G mode and 8bitdo Ultimate C 2.4G wireless controller both wireless and wired on Ventura 13.4.1 MacBook Pro M1 2020. Everything works for both controllers except rumble feature. I added following lines inside installed kext in /Library/Extensions/360Controller.kext/360Controller/Info.plist to enable these two particular devices: BTW 8bitdo Ultimate Wireless Controller with Charging dock (Bluetooth) works natively in Bluetooth mode in Ventura: including rumble feature. But analog triggers are registered as full press at any press scale (so no Mario Sunshine in BT mode). |
@mmg1988 are you able to share your changes to get this compiled for Apple silicon? |
really insistent we are :))) as I understand anyone who has experience of porting legacy apps could build it, but me with no experience failed. There are instructions from @mmg1998 in one of comments actually but they are a little bit vague, so me myself failed at the first and the second try. Maybe we could collaborate somehow to try to build it in separate Issue thread and try to fix errors we encounter. The one thing to start from is that the version that was build by @mmg1988 is alpha5, not alpha6. I tried to build alpha 6 and failed. |
Just updated to Sonoma 14.0. Previously installed 360Driver is working. |
are you using a m1 mac ? because i can't reinstall it for me i said bad signature and i have done the whole thing we can read here |
Yes, Macbook Pro 2020 M1. 360Driver was installed and worked on Ventura 13.6, just updated to Sonoma 14.0 through System settings. No loss in functionality for the driver. Everything works as on Ventura. |
I was able to build with success the alpha 6 version like @mmg1988 did following his tutorial with some additional steps but when I install the package the receiver still not working. I have a Macbook M1 Pro with the latest MacOS. |
Now, after install my built package, when I run
|
I've realized that I'm having this error, even saying that built with success. For some reason, this file doesn't exist after the build inside the kext.
|
@luizgununes that's great news! Do you have a fork and/or list of exact steps that you can share here? |
@bryce13950 I don't remember having this error, so I can't help, sorry. @palmerj If I have success figuring out the error I've reported above, I can write a tutorial, but there is no mystery, just download the XCode, install the MacOS development package when suggested, open the latest source code folder downloaded here in this GitHub, remove the code mentioned here before, change the architecture to arm64 for each package inside the driver, change the signature method in all projects like mentioned before too, check the errors tab to solve additional errors, run chmod +x for ./build.sh before running with sudo to build and cross your fingers. I've also installed "Packages" with brew. PS.: I've downloaded a Windows 11 on Parallels and the Xbox 360 receiver magically worked. It's impressive. But I want to run native. |
Thanks that would be fantastic @luizgununes ! |
Any updates @luizgununes please ? |
Believe me or not, but suddenly, I've made it work. But it's not my credit. Days after my last post here, I deleted all files and gave up. But, a few weeks later, I searched again and found this link - one that I'm 100% sure I already tried to install before - and it worked! It gave an error during the installation, as always. But when I connected my controller, it appeared on the list (System Settings > Xbox 360 Controller) and the Enable Driver option works too! I don't know exactly what could have caused it to only work now, but I'm happy. Something that might have helped it work is that my Good luck! |
@luizgununes I'm still interesting in building from source so I can trust output (given you need to disable security on loading the module). Did you ever install the driver from a source build? If so can you share the full steps you took? For example I'm not 100% clear what you did for the comment you made above:
Thanks so much! |
@luizgununes You absolute legend - tysm !! |
Esse instalador com link é para processador da apple ou para intel? |
@jonasw8 buenas, no hablo portugués, solo español, pero el instalación trabajé para mí en mi M1 Mac, utilizando eso link. Buena suerte!! |
Acredito que para ambos, mas o meu processador é o M1 Pro. |
I don't know if you really need to disable crsutil, you can try without it. |
THANK YOU. Got it working on MacBook m3 Pro 14", Sonoma 14.4.1 with wired xbox 360 controller. I use the build from @mmg1988 (https://github.com/360Controller/360Controller/files/9063388/Install360Controller.pkg.zip) and run csrutil disable. |
The state of this repository (xbox driver) going forward
FranticRain:
(1) Uninstalling the Driver on Big Sur will give you an Error, the only way to uninstall it is manually.
(2) ONLY install the driver after you have followed the steps below in before installing section. It will still say "Installation Failed" this is normal ignore it. As long as you follow the terminal steps below, xbox controllers will worked again wired. Xbox One Controllers model 1708 will work via bluetooth after a firmware update.
(3) As of currently late January 2021, using Windows Parallels on an M1 Mac will not work for any controller, and will give you constant issues.
MANUALLY UNINSTALLING THE DRIVER
Goto the following locations and find the following files. Either drag them to the trash, or select them and press (Command+Delete)
_EMPTY THE TRASHCAN!!!
Use the check boxes for your convenience
Important - Before you can even access these files you need to gain access to your main drive which apple has disabled by default (thanks apple lol)
Summary of Steps to Enable Drive in Finder Sidebar:
(1) Click on the desktop or the finder on the dock
(2) click on "finder" in the menu bar
(3) click on preferences
(4) select the "sidebar" tab
(5) check the box for "your name"'s Macbook (whatever your devices is)
(6) exit this window and go to your finder window
(7) navigate to Macintosh HD (Follow steps below)
Steps to Uninstall the Driver
BEFORE INSTALLING THE DRIVER!!!
(1) Update your Controller Firmware
For Xbox Controllers this is done by either your Xbox through a wired conncetion or Windows 10 App from the app store called "Xbox Accessories" also a wired connected is needed. For all other controllers check you manufacture website for support.
(2) Manually adding driver support to Big Sur
In order for the Xbox driver to work this must be done First. Afterwards, like stated before insatlling the driver can be done, it will still fail but will not fucntion with wired controllers (not elite).
If you play on steam you will need to do these same steps before installing steams gamepad driver; just using steams dev id instead for step 2. The full post for the steam method on are located in this link if your curious. [Fix.for.game.controllers.on.Big.Sur.Steam.for.Mac.pdf] (https://github.com/360Controller/360Controller/files/5792061/Fix.for.game.controllers.on.Big.Sur.Steam.for.Mac.pdf)
STEPS:
spctl kext-consent add G947KKM5RL
kmutil trigger-panic-medic --volume-root "/Volumes/Macintosh HD"
(If driver name is different then replace “Macintosh HD” with whatever your drive is named; press Tab at the end of typing "/Volumes/" to get a hint).
sudo kmutil load -p /Library/Extensions/360Controller.kext
OTHER CONSIDERATIONS:
(1) Use Windows Bootcamp
Using bootcamp for Games instead has proven to be a useful alternative, and use macfancontrol to keep CPU cool via full blast.
(2) Advisory for Xbox Elite controllers
Elite Controllers generally will only work on Windows 10 or an Xbox Console; until it gets a firmware update and full support is added to big sur, steam, and games.
Currently, for steam after installing the “Big Picture gamepad driver” Elite controller will work via bluetooth only with limited support (only some games will work)
(3) Consider Downgrading to macOS Catalina
you can choose to do this on you main parition after you back it up, wipe your drive and re-install, or easier just install a second partition on your driver for Catalina just for games (also can use a NVME SSD for this as well via thunderbolt)
(4) Check your controller is compatible with this Driver
https://github.com/360Controller/360Controller/wiki/Compatible-controllers
(5) Using Controllers with STEAM®
Controllers will not work with steam on Big Sur, unless you have:
HOPE THIS HELPS
The text was updated successfully, but these errors were encountered: