If you'd like to try the 0x01 0x02 bytes with your controller, I uploaded a Win7 64-bit control utility build with only those bytes changed:
http://code.google.com/p/chatpad-sup...trol_test3.exe
Grumbel: Could you please post the X8***** serials of your controllers (mention wireless or not please)?
I'm testing your Linux driver on 10.10 32bit, just installed the boost libs, now building it
-edit: built completed, from the GIT version...
did what you wrote in previous post > now when i run it:
unrecognized option '--chatpad'
did you commit to github?
If you'd like to try the 0x01 0x02 bytes with your controller, I uploaded a Win7 64-bit control utility build with only those bytes changed:
http://code.google.com/p/chatpad-sup...trol_test3.exe
Bingoits fully working!
Gafblizzard and Grumble please come to Grumble's own channel on IRC FREENODE
#xboxdrv
Sorry to spam this thread so much...I went to http://webchat.freenode.net/ and #xboxdrv but don't see anyone. Is that the right place? *edit* Yes, looks like it is.
Great work GAF! I have been following this since the contest was posted. Your dedication and progress in getting this working is greatly appreciated! And don't apologize for 'spamming' this thread!! You OWN this thread and any update no matter how small is welcomed!
I would love to help you test this initial version but I'm in the wireless camp, don't have a wired controller.
Great work!
Happy New Year ppl
I only noticed it happen after about 20-30 minutes of use, and I think there is a possibility that it is registering while decompressing the key, I guess an easy way to test this would be to do fast single key presses and slow key presses, I'll give it a shot today since i didn't really think about it yesterday haha
One piece of good news: supporer and a guy on another forum weren't able to use the chatpad with my driver even though everything seemed to install correctly. Once I gave them test binaries that used the 0x01 0x02 initialization sequence, it works for supporer and the other guy. So far we have:
Hardware version 1.10, uses 0x01 0x02 for init.
Hardware version 1.14, uses 0x09 0x00 for init.
The versions are in the USB report and one can see them using something like lsusb (in Linux) or UsbView (in the WinDDK Debuggers directory, under Windows, if you have the WinDDK installed). I don't know what hardware version this other person has, but the test program worked for him.
Bookmarks