XNA Game Studio 3.1 is a library for C# to create Windows, Zune, or Xbox games. It is not as you state to make games for Xbox on Windows, that is just one of three options. In the upcoming XNA Game Studio 4 it will be for Windows, Xbox and Windows Phone 4. There is no annual subscription. It is completely free. The only thing you would need to pay for is if you want to market your game for the Xbox, then it would cost you money depending if you went monthly, or annual. It is not always helpful to give inaccurate information. A Game such as Dishwasher the Dead Samurai was made in XNA Game Studio, a very popular and well made game. Please at least do a little research before stating 'facts'. Thank you.
Need Xbox 360 Chatpad driver
Hi,
one year ago i buy a Xbox 360 Controller Made by Microsoft Corporation and a Chatpad for it. on the box was info about use for Windows-based PCs but until now no driver... so i am here to ask for some help. For now i can turn the backlight on sending
ctrl 0x41 0x0 0x1f 0x02 # Init (without this, no led wil work)
ctrl 0x41 0x0 0x8 0x02 # capslock
ctrl 0x41 0x0 0x9 0x02 # square
ctrl 0x41 0x0 0xa 0x02 # circle
ctrl 0x41 0x0 0xb 0x02 # people
ctrl 0x41 0x0 0xc 0x02 # backlight
ctrl 0x41 0x0 0x11 0x02 # capslock
ctrl 0x41 0x0 0x12 0x02 # square
ctrl 0x41 0x0 0x13 0x02 # square and capslock
ctrl 0x41 0x0 0x14 0x02 # circle
ctrl 0x41 0x0 0x15 0x02 # capslock and circle
ctrl 0x41 0x0 0x16 0x02 # circle, square
ctrl 0x41 0x0 0x17 0x02 # circle, square, capslock
ctrl 0x41 0x0 0x1b 0x02 # makes led go on on keypress
ctrl 0x41 0x0 0x1e 0x02 # Init2 >>> Ep6: [5] { 0xf0, 0x03, 0x00, 0x01, 0x01 }
ctrl 0x41 0x0 0x1f 0x02 # Init (without this, no led wil work)
i also have acess to USB protocol analyzer (but it is not mine... sorry) to have the info that travell between the controller and the Xbox
also we can recive one key press but after it is dead.... and i dont know why... a lot of people are working on it but microsoft made it so at leas you can help us to try make a driver...
2nd byte flags:
shift/capslock = 0x01
square = 0x02
circle = 0x04
people = 0x08
3rd byte keycodes:
1 = 0x17
2 = 0x16
3 = 0x15
4 = 0x14
5 = 0x13
6 = 0x12
7 = 0x11
8 = 0x67
9 = 0x66
0 = 0x65
q = 0x27
w = 0x26
e = 0x25
r = 0x24
t = 0x23
y = 0x22
u = 0x21
i = 0x76
o = 0x75
p = 0x64
...
...
...
Windows for home | Previous Windows versions | Gaming
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
81 answers
Sort by: Most helpful
-
Anonymous
2010-09-03T01:36:39+00:00 -
Anonymous
2010-08-26T00:59:12+00:00 I would like to know if you could make an executable driver for this, I have a chatpad and wished for it to work even a little.
-
Anonymous
2010-07-30T10:52:21+00:00 I'm a bit confused as why this type of post is coming from a Microsoft employee. Are you familiar with the "Games for Windows" initiative? Do you know that to get a Games for Windows logo, a many types of games are encouraged/required to support the Xbox 360 Controller? Did you know that when I plug a headset into my Xbox 360 controller, it is recognized as a microphone by my PC? Why is the chatpad any different support wise on the PC than a microphone?
-
Anonymous
2010-07-28T13:12:32+00:00 ok, this may be regarded as a little off-topic (ish). But here's my reasoning. I'm not interested in a Windows Driver, but I am interested in the usb protocol used. Why? Well, I'm an embedded hardware engineer and I make "things" (not Windows software) that use all manner of Input/Ouput. The Xbox360 gamepad is a pretty useful input device for all manner of other things other than the Xbox360 or a Windows PC.
I have the protocol for the buttons, joysticks, triggers and LEDs. But the chatpad remains a mystery. Even with a USB protocol analyser trying to figure out keypress data on the chatpad is a chore that as yet eludes me. Now Micrsosoft may not want to bother writing a driver for the PC. I can see why they can't be bothered that much. But at least putting online somewhere the USB protocol for the gamepad would
a) allow others to write their own Windows Drivers if that's what they want to do OR
b) allow me to write code that makes use of the Xbox360 gamepad + chatpad in areas Microsoft don't even know exist! After all, if I make something that uses a gamepad as it's input device then Microsoft only benefit from more sales!
It's not hard to make available the protocol. I mean, I'm not asking for that part of the gamepad USB protocol regarding the security chip that identifies the gamepad as an authentic Microsoft product, I have no interest in that and wouldn't expect MS to publish that. But the generic portion of the USB protocol that anyone can use would be really useful in the public domain. It just means more sales for MS for people wanting to make use of the Gamepad as an input device.
The Xbox360 Gamepad+Chatpad is, "bang-for-buck" and size wise as really useful little device!
-
Anonymous
2010-07-18T19:27:43+00:00 I am surprised such an old topic is still being discussed, but more surprised at all the naysayers on the topic. Why would you want a mini keyboard on a pc with a full size keyboard? Why would you want to slouch over a desk rather than sit back with a controller in your hand? My back would love for this thing to work with the my pc. Not to mention all the people who would like it for their in-car pc systems and home theaters, it would make a brilliant solution if you could use the thumb sticks as the mouse and type with a chatpad. MS apparently doesn't care about this topic OR there is some horrible compatibility issue (though I don't see why there would be). If another company made a similar product for the pc I would likely buy it, but in the meantime, if you don't have anything to contribute to the discussion please don't even post on it or this will be a never-ending debate on whether or not original packaging was misleading 3 years ago rather than something productive.