When I have a pro controller plugged in to the wiimote, USB Loader GX seems to code up upon start up or changing games. Can someone give me some insight into this issue. Much appreciated!
It is. I also have a hori fighting stick that does this as well, but only on the menu screen. I'll get a Nintendo CC and see how that goes. Thanks!A CC Pro? If it's causing a dump it must be a 3rd party one.

Yes!! Thank you!! Just trying to get my virtual arcade as smooth as possible and this would help a lot!it's fixable, and I remember @AbdallahTerro gave me a link to a patch (wiiflow sources, I think, or maybe it was libogc patch?), I never took time to add that fix.
I forgot where the link is, but with some active search, I could find it again. or maybe he will give us again as I just ping him![]()
This sounds a little out of my league, tbh. I was thinking maybe I'm just using an older version of USB Loader GX.You can patch libwiiuse (part of libogc) to ignore certain extension IDs but it won't make the controller work in the loader, just prevent the DSI exception.
It might be possible to wrap the register function to eliminate the need to recompile parts of libogc.
The latest versions of libogc already assume an unknown extension controller is a classic controller and try to register them as one.

Using an older one will have more issues and bug, because it was compiled using an old libogc and devkit version, etc.
Finding another controller is maybe easier. it might cost you a little to find/buy another, but it'll work.
try flea markets (it's the starting time in France, no idea if there's a trend in Spring in all countries)
