How to use the Official GameCube Controller Adapter for Wii U in Dolphin: Difference between revisions

no edit summary
(Switched to the capitalization of UsbDk that seems to be official)
No edit summary
Line 19: Line 19:
If you want to change the rule, links for instructions are available on the [https://github.com/libusb/libusb/wiki/FAQ#Can_I_run_libusb_applications_on_Linux_without_root_privilege libusb FAQ].
If you want to change the rule, links for instructions are available on the [https://github.com/libusb/libusb/wiki/FAQ#Can_I_run_libusb_applications_on_Linux_without_root_privilege libusb FAQ].


== OS X ==
== macOS ==
Due to the nature of Apple's HID implementation, ''all'' HID devices (including non-standard ones) are intercepted by IOKit's HID driver. Since the adapter does not supply a valid report descriptor, this makes the IOKit driver useless for direct communication.
Due to the nature of Apple's HID implementation, ''all'' HID devices (including non-standard ones) are intercepted by IOKit's HID driver. Since the adapter does not supply a valid report descriptor, this makes the IOKit driver useless for direct communication.


Line 38: Line 38:
Once installed, Dolphin should be able to recognize that the adapter has been plugged in. You do not need to configure the controllers manually within Dolphin's controller settings but any controllers plugged into the adapter should work immediately.
Once installed, Dolphin should be able to recognize that the adapter has been plugged in. You do not need to configure the controllers manually within Dolphin's controller settings but any controllers plugged into the adapter should work immediately.


For questions on any of these OS X connection techniques, please see the [https://forums.dolphin-emu.org/Thread-os-x-gcn-adapter-kext-testers-wanted forum thread].
For questions on any of these macOS connection techniques, please see the [https://forums.dolphin-emu.org/Thread-os-x-gcn-adapter-kext-testers-wanted forum thread].


==== OS X with System Integrity Protection (SIP) ====
==== macOS with System Integrity Protection (SIP) ====
 
For newer versions of macOS, the unsigned Kernel Extension will fail to load.
For newer versions of OSX, the unsigned Kernel Extension will fail to load.
The only current workaround is to disable kernel-extension signing verification, which can be done in OSX Recovery Mode.
The only current workaround is to disable kernel-extension signing verification, which can be done in OSX Recovery Mode.
This will lessen security, and is not recommended.  
This will lessen security, and is not recommended.