Wednesday, January 04, 2006
post://113641699941941700/
Follow-up to the XBox story:
I've contacted the PR agency regarding the functionality of the XBox Controller "for Windows XP".
I hope to get to the bottom of things, since the Tech support can't seem to get their heads around this.
If it's an intention to not have the rumble work, there's a problem.
If they did intend to have the rumble work, there's still a problem.
Case 1) They have created a controller that works for both their Microsoft designed XBOX 360 "computer" and conventional PCs running WinXP. However, they apparently did not speak with their DirectX crew regarding how to make ForceFeedback work via DirectInput. The whole point of DirectX is to make it easy on developers and hardware manufacturers so they can easily create a device that is "Plug & Play" with Windows. Conundrum anyone?
Case 2) They fully intended to create ForceFeedback, but somewhere along the lines they put out the wrong driver, or (in traditional Microsoft style) they didn't have it ready for launch. The driver I have was dated Sept 27th. The initial launch date? Can anyone help me out here?
I would like an answer. I was told by XBox tech support: "Oh, yeah... the rumble doesn't work on PC"
I want to know why hackers can put together a driver that rumbles when Microsoft can not. You
wrote DirectX! You
created ForceFeedback (v2 now?), and still... your own hardware device lacks? For SHAME! (
prove me otherwise)
I need to set the record straight, for all you tearing your hair out just like me.
This guy blamed his PC and
Matt's site has got a whole bunch of people with the same issue. Amazingly enough they all want to play Need for Speed Most Wanted with rumble! It seems to be a driving force (no pun intended, honestly!) behind this. A major game developer (Electronic Arts) too! It's not some podunk little game company trying to get Force Feedback to work, EA's done it before. I had NFS 3 and it supported Force Feedback, I think they know how to code it correctly!
They have a down and dirty way to get it to work. First you have to get XBCD - an XBox controller to USB driver utility, then download the "profile" - essentially a .sys file (driver) and .inf (pointer to the driver) that tells XBCD how to speak 360. Once that's done... Nirvana:
Lots O options... and... RUMBLE!
Of course I want to be using the WHQL drivers, but why, oh why don't they rumble?!!
To be continued...
posted @ 18:11
-x-
(0) comments |
Post a Comment