On Windows, the GameCube controller adapter will need a custom driver to let Dolphin detect it and use it, Zadig can help you with it. Sudo chown -R root:wheel /Library/Extensions/SmashEnabler.kextįor questions on any of these macOS installation techniques, please see the forum thread. Sudo cp -r ~/Downloads/SmashEnabler.kext /Library/Extensions/SmashEnabler.kext Installing the SmashEnabler standalone kexts must be done via Terminal.
#Project 64 emulator controller setup install#
Standalone kext for older versions of macOS Terminal Install Installer package for older versions of macOS See this StackExchange thread for more details. This will lessen security, and is not recommended. The only workaround is to disable kernel-extension signing verification, which can be done in macOS Recovery Mode. On El Capitan (10.11) and later, the unsigned Kernel Extension will fail to load. Standalone kext for macOS El Capitan (10.11) and later System Integrity Protection (SIP) Installer package for macOS El Capitan (10.11) and later Older versions of macOS can be supported by installing SmashEnabler. This method does not require disabling System Integrity Protection (SIP). GCAdapterDriver is an open source project for enabling adapter usage under macOS. GCAdapterDriver Installer Packages for macOS High Sierra (10.13.6) and later 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. Thus in order to use adapters on macOS, a driver needs to be installed that simply grabs and ignores the adapter, and permits a lower-level connection (like the one Dolphin makes). Since the adapter does not supply a valid report descriptor, this makes the IOKit driver useless for direct communication. If you want to change the rule, links for instructions are available on the libusb FAQ.ĭue to the nature of Apple's HID implementation, all HID devices (including non-standard ones) are intercepted by IOKit's HID driver. Dolphin should now detect it in the controller settings (refer to #Dolphin Setup below). Paste the following in the /etc/udev/rules.d/les file (/lib/udev/rules.d/les if making a package): However, a udev rule must be created to allow access to the device. Linux support does not require any special drivers, as long as Dolphin was built with libusb support. 1.2.2.1.1 System Integrity Protection (SIP).There is a control in the options labeled “Z trigger”, and it registers the Z trigger as being pressed, but in the game (Super Mario 64) the Z trigger does nothing. I tried setting the Z trigger individually to L2, and I tried setting it to R2 as well, but L2 wouldn’t come up unless I set controls a control for L2. I know that it does work, I used it with another game. I was able to set up all the buttons, but I can’t get the Z trigger to work.
Put that into your N64 config override and it will switch the buttons around whenever you load an N64 game. R2 does a weird button shuffle thing (it’s a hack we had to add to make the N64 core work with the touchscreen overlay system you don’t really need to know the details), so don’t map it to anything. Everything else is where you would expect (that is, L-button is L1, R-button is R1, B is retropad-Y, A is retropad-B). The default mappings are similar to the Wii Classic Controller mapping for Virtual Consoles games, with the C-buttons on the right analog stick and Z-button on L2. Then, you’re going to need to do a config override for the N64 core that maps the retropad inputs differently. If you’re going to be using any other cores, go ahead and get your retropad mappings set up properly.