as far as i know, all xbox controllers work with any microsoft usb gaming receiver. i couldnt tell you if there is differences in software between all the versions of gear that has come out, but i dont think they ever abandoned the original way they are communicating.
amazon is about the best place to get the set. its not cheap at $48 shipped, but they last a lifetime. http://www.amazon.com/Microsoft-Xbox...p_ob_e_title_2
just curious, did you get paid yet? do i need to update the front page?
finally I made it work, but I changed something in the chatpad_config to this:
CHATPAD_KEY_W + CHATPAD_ORANGE = KEYBOARD_KEY_UP
#CHATPAD_KEY_A + CHATPAD_ORANGE = KEYBOARD_KEY_LEFT
#CHATPAD_KEY_S + CHATPAD_ORANGE = KEYBOARD_KEY_DOWN
#CHATPAD_KEY_D + CHATPAD_ORANGE = KEYBOARD_KEY_RIGHT
but it does'nt work anyone can help me out how to change keys ty
trader007, as far as I know, all the prize money went direct to a children's hospital charity (with matching money from Microsoft). :) And thanks for the link! I should probably order a few things on Amazon.
rjan22, I still don't see the controller itself on that device list. :/ The game controller should show up somewhere, and have 2-3 nodes on it saying something like XBox 360 game controller. I think the problem is that the control utility is not finding the device.
First off, you know that if a line has # in front of it then it will be a comment, right? Your W + orange mapping should work though.
If it does not, you may need to look for where the orange chatpad key is mapped. There should be some examples in the file of using the orange modifier. If you are still stuck then I will try to put together an example and test myself. :madgrin:
how did you get microsoft to match that? i thought they might not like us hacking their stuff... are they going to help you get the wireless drivers done?
I'd just like to say great work :)
I can't wait for drivers for the wireless controller!
It should be straightforward to allow a configurable trigger point for each trigger, ie. integers of 0-255 in the config file. I was thinking that it might need checks to make sure that the specified values don't cause the triggers to be always clicked, and if the triggers aren't calibrated properly (not sure what the trigger values would be in that situation).
In chatpad_filter.inf, you might want to change the last line:
ClassName="XBox 360 Controller Chatpad"
ClassName="XBOX 360 Peripherals"
which is the ClassName that Microsoft uses in Device Manager in XP and WHS. You might be able to omit the line from the INF file and then it uses the default ClassName (I'm not 100% sure about this, but I think that's what you did for the HID keyboard and mouse drivers). Otherwise it clobbers the device category heading that Microsoft uses in Device Manager, and after deinstalling the chatpad driver, the entry for the Microsoft controller driver is restored but the category heading remains "Xbox 360 Controller Chatpad" even though there are no chatpad devices, only XBOX controllers and receivers.