#KIGB WONT RECOGNIZE 360 CONTROLLER DRIVERS#
#KIGB WONT RECOGNIZE 360 CONTROLLER DRIVER#
#KIGB WONT RECOGNIZE 360 CONTROLLER PC#
#KIGB WONT RECOGNIZE 360 CONTROLLER DOWNLOAD#

So, is this the same method used to play 2 players in gamecube too? Was looking 4 a way to play 2p from long time. So if you want to change the buttonmapping of the controller you have to use xpadder. See here īut since you want multiple X360 pads connected you can't use that either.

#KIGB WONT RECOGNIZE 360 CONTROLLER DRIVER#

There is also another driver that supports the wireless pad but you can only connect one at a time. But XBCD doesn't support the wireless Xbox 360 pad. XBCD has a wrapper that converts dinput to xinput. You will face similar problems with N64 emulators.Ī solution to this is to use alternative drivers, not made by Microsoft, like XBCD. The xinput plugin for Dolphin doesn't allow a reconfiguration at this time.

#KIGB WONT RECOGNIZE 360 CONTROLLER DRIVERS#

The reason why you can't use the Xbox 360 Wireless controller like a normal gamepad and configure it in the emulator and therefore need Xpadder is because the X360 Pad drivers by Microsoft don't support directinput very well, they use xinput.

I also attached an image of my 360 Controller you will need it to create a setup in xpadder

#KIGB WONT RECOGNIZE 360 CONTROLLER DOWNLOAD#

To use the 360 controller as a Wii Classic Controller, download xpadder and set the X360 controller keys to keyboard keys, the X360 Controller will then act like a keyboard.īut since all games that use the Wii Classic Controller also should be able to use the Gamecube controller, I don't think this will be necessary. You will need a second program if you want to change its configuration. WiiMote1Plugin = Plugins/Plugin_Wiimote.dllĪlso in the controller plugin you need to enable the x360 pad(red circle), you can't configure the Xbox 360 wireless controller in this menu. Pad4Plugin = Plugins/Plugin_PadSimple.dll Pad3Plugin = Plugins/Plugin_PadSimple.dll Pad2Plugin = Plugins/Plugin_PadSimple.dll You can't really mess anything up since you can reenable anything you disable just be careful to not uninstall drivers or something.Pad1Plugin = Plugins/Plugin_PadSimple.dll So if installing the drivers themselves doesn't work you might have to play around with the Device Manager like I did. I basically disabled one and since haven't had issues at all with my controller. After I got it installed (maybe with a reset, too, I forget since this is something I did way back in the day for another game that had similar problems) I went to the Windows' Device Manager and saw that there were two separate entries for HID Compliant Devices (Microsoft Common Controller should be its own category so that's the one thing in the device manager you don't touch). Beyond installing additional drivers what I ended up having to do was disable another driver that automatically loads up when you connect your controller.įirst I installed the official Xbox 360 Controller Drivers via.

#KIGB WONT RECOGNIZE 360 CONTROLLER PC#

On my PC the issue was conflicting drivers. I noticed this when I wanted to change radio stations which is kind of a hassle on the controller. The keyboard doesn't work if you have any of the controls pressed on the gamepad and vice-versa. That could imply that the game makes a substantial distinction between 'controller mode' and 'keyboard/mouse mode,' as opposed to games that recognize controller inputs but still show a mouse cursor and keyboard prompts. One of the things that I noticed (and appreciated, since it doesn't seem as common a feature as it should be) was that as soon as I started to use my controller while on the main menu, the mouse cursor disappeared. This is problematic for a variety of reasons, but it especially effects games like Saints Row that support both mouse/keyboard and controller, and that pay attention to the most recent device to generate input since the mouse is constantly generating input, the controller gets shouted down.) (There are a few mice that constantly generate mouse-moved events in Windows, rather than only sending events when the mouse actually moves. Other than that, I don't know what to tell you, unless you have a chatty mouse. One of the FAQs suggests unplugging and replugging the controller while the game is running.

Kigb wont recognize 360 controller