Even when many controllers are supported in other platforms, for the Wii the approach is a bit different, we need add a driver for each of them. Nice you have the usbgecko, I would love one for debugging. You definitely have to recompile your cores! It should detect it, configure it and allow to use it. But the hat and button bytes never change when doing the same for them. Let do something… maybe there is an issue on the bytes it is reporting that were read. Could you please confirm what are you tring to achieve:
|Date Added:||12 January 2007|
|File Size:||62.69 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
You definitely have to recompile your cores! No, the hidtool may be displaying different of bytes depending its packet size, but as you are showing only showing 20 for your control. The GC adapter may be already supported.
Switching between modes only affects the stick, buttons still do not work in analog mode. Physically inaccessible Right Stick Vertical Byte Now, please the current driver got the GC adapter only supports the first controller. It should detect it, configure it and allow to use it. Thanks for the reply netux Thanks so much for your fast help: Physically inaccessible Hat Byte Can I be sure that the files are changed for compilation as soon as I change them in the toolchain have only been compiling the salamander-file, no cores?
Per the data shown I think yes there is an issue with the data, not sure if your controller may need a startup sequence to start sending the button data like the PS3 controller … but that would be more difficult to track from my side.
Sure compare the following uncompleted. It works now, what was missing were the autoconfig files.
GTC Ribbon Drivers Download
But the hat and button bytes never change when doing the same for them EDIT: Nice you have the usbgecko, I would love one for debugging. I had finally the time to check your code and jostick what, it seems correct to me… you did the correct changes to make it work and also your autoconfig seems ok! Apr 20 I was kinda running out of ideas, aswell. Let do something… maybe there is an issue on the bytes it is reporting that were read.
That would be much appreciated. I will suggest that you try that way first… I mean, forget for a moment the HAT stuff and check that the bytes from the buttons actually have values… I may say that if it actually works and shows something with the nintendont tool it should work with Retroarch as it uses the same process to get the data… Just be sure you use the same info that this tool provides… something weird I noticed in your comments is that RA returns 8 as the size and at the very beginning I see you put the data from the hidtool and see 20 bytes… be sure it is 20 bytes or 8 bytes… regularly it is 8 bytes for standard controllers.
So yes, you may be able to get them working but you will need to create the driver and then recompile it all and maybe share your driver so it can be used by someone else with the same controller. I may need the physical controller and obviously that it not possible. Using the info you provided I created the connect file but it seems practically the same as your… try it also and see the results. I saw that here: Could you please confirm what are you tring to achieve:.
inch LCD Nokia LCD Module [GTC NOKIA DISPLAY RED BOARD] Communica Online
Any help is appreciated. I downloaded them and put them on the SD like you described. I downloaded the autoconfig files and set autoconfig directory to where the files are in retroarch. Sure, here you go: After changing the driver to hid my controller works perfectly now.
I remember you mentioned it was 8 but hopefully it is larger. All of this did work flawlessly in the Windows version of RA using udev as input driver though. You may be right about it needing a startup sequence, this comment from the PS3 driver does sound a lot like my problem:.