This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
I am trying to use my Xbox 360 Wireless Racing Wheel in Windows 7 using the Wireless Gaming Receiver to connect it to my PC.
It connects fine and I can use the wheel in games, but I'm not getting any force feedback and I don't see it mentioned in the device configuration in the control panel.
This page: http://www.xbox.com/en-gb/hardware/x/xbox360wirelessgamingreceiver/ specifies that the wheel should have drivers available for Windows Vista in the future (I am guessing this page is well out of date) with force feedback but I can't find mention of these drivers anywhere.
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.
Technically, this is a Windows 7 Driver Support question on when then Wireless Gaming Receiver drivers will be updated to provide force feedback support as was promised in the URL the previous poster provided.
I to would be interested in if this work is progressing. If it has been cancelled you may wish to notify marketing and get them to update the page in question.
Cheers.
Hi! I am another customer fooled by Microsoft.
I was searching around in order to understand how hard would be to enable the FFB feature of the wheel on Windows.
So, here are my impressions...
Microsoft introduced a new input library called XInput specifically for Xbox 360 controllers (gamepad, wheel, guitar, fightstick, and etc.). Currently, this library is officially implemented for Windows (supporting DirectX 9 or later) and Xbox 360. Thus, on both platforms, any game supporting the Xbox 360 controllers use this library.
Theoretically, since the same library is used in both platforms, the controllers should work on Windows as they work on Xbox 360. However, it seems like the XInput implementation for Windows is lacking the functions to access the FFB motor of the wheel (as suggested by "Core Driver" in Codemasters forums: http://community.codemasters.com/forum/grid-tech-support-1020/280028-no-love-xbox-360-wireless-racing-wheel.html). Give a look at the Windows XInput documentation (http://msdn.microsoft.com/en-us/library/ee417007(v=VS.85).aspx), there are only a function to access the vibration motors (the XInputSetState function).
Considering this lack, how the game developers would implement the FFB support!? Therefore, I believe that a driver update would not be enough to enable the wheel FFB feature. Microsoft should also update the XInput API for Windows with the FFB functions and the game developers should release patches for their games. Summarizing, even Microsoft updating the API and the driver, I think we will have to implore the game companies to update their racing titles in order to use the FFB functions.
Anyway, if Microsoft announced FFB support it must must be delivered. Otherwise, it is false advertising.
Sorry for my bad English.
Ok, I have been a loyal customer to Windows for awhile, every computer I've had has been equipped with Windows. It has been frustrating, annoying, and disheartening to read this post. I began with Xbox LIVE, transferred into PC racing, and now run both with my Xbox 360 racing wheel. iRacing as many SIM racers may know is a top notch physics-based racing sim that requires accurate controls. I'm decidedly on a budget and can't afford another wheel at this point and believe this has all the stuff (minus a clutch pedal :P) as far as hardware goes. All it needs is for the lazy ____ at MS to get their heads out of their ____ and help us out. They think we can't live without them, so they'll keep on going ignoring relatively small problems. Thing is, relatively small technical problems are the base of their hardcore buyers. They lose us, they lose a very large chunk of their audience. And just for reference I have attached a link to "How to Sue Someone for False Advertising", so if anyone feels like they have the time and the resources and the knowledge, take them the ____ out!!!!!!!!!!
http://www.ehow.com/how_2175318_sue-someone-false-advertising.html
i dont think they are compatible
Microsoft doesn't even know this thread is here. As far as I can tell, nobody from Microsoft reads these forums. It's outsourced to some Indian company.
They appear have absolutely no way of elevating technical issues to the correct department, as this thread demonstrates.
Microsoft seems to be ignoring the big elephant in the forum.
