(11-24-2013, 02:05 PM)JimPhreak Wrote: [ -> ]How does this help the fact that 4.0 won't even detect that my controller is there? I can't even reconfigure it from scratch because when I press any of the buttons on the controller 4.0 Doesn't detect anything as if the controller isn't even plugged in.
You might need to press the Default button in the GC Pad configuration before re-configuring the controller.
(11-24-2013, 11:27 PM)ulao Wrote: [ -> ]Did you install a driver for that adapter? On the may flash site they have a list of updated drivers for there products. I know it seems like its a dolphin issue but I work with so many adapters and dolphin is really good at supporting them all. I dont know if they still support that model but look here.
http://www.mayflash.com/Support/Download/
How can it be a driver issue if it works on the same computer with Dolphin 3.5? Windows detects the adapter fine.
(11-25-2013, 08:40 AM)skid Wrote: [ -> ]You might need to press the Default button in the GC Pad configuration before re-configuring the controller.
Pressing default just sets the Device to the Keyboard and Mouse.
Quote:How can it be a driver issue if it works on the same computer with Dolphin 3.5? Windows detects the adapter fine.
That is the very nature of how drivers suck. Very often times software changes ( for better or worse ) and expects the drive to do what it right. Just because the older drivers worked does not mean its correct. When you have issues like this its bets not to assume anything and try many things. Updated a drive is always a good idea. Arguing all and any advice you are given is not.
(11-25-2013, 04:30 PM)skid Wrote: [ -> ]Some people have had issues with SDL2. Try replacing the SDL2.dll in the dolphin folder with this one:
http://www.libsdl.org/release/SDL2-2.0.1-win32-x64.zip
I will try this when I get home tonight. Thanks.
(11-25-2013, 10:40 PM)ulao Wrote: [ -> ]Quote:How can it be a driver issue if it works on the same computer with Dolphin 3.5? Windows detects the adapter fine.
That is the very nature of how drivers suck. Very often times software changes ( for better or worse ) and expects the drive to do what it right. Just because the older drivers worked does not mean its correct. When you have issues like this its bets not to assume anything and try many things. Updated a drive is always a good idea. Arguing all and any advice you are given is not.
I tried the driver from the link you provided (thanks for that btw) last night to no avail.