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.
I am in complete agreement, this is now false advertising and I feel I have wasted a lot of money (relative to my income).
I feel disgusted and betrayed by Microsoft, they have gone back on a promise made in black and white across all there marketing material. Does anybody here know of a good channel to start escalating this through. Several hundred of us have now tried independantly through MS official support.
hello Saulo and wills,
just an update the registry settings were a remenants of some driver files i was testing from a japanese guy this was just for the vibration feedback also though so sorry if there was any false hope :( here is the link with drivers for xinput, windows wireless receiver and others as well i used google translator to translate what they werehttp://www.katch.ne.jp/~morii/index.html
as you have said they have already implemented on xbox 360 surelt then most of the work has been done and they need tweaking for windows? i am glad there are more people getting on board regarding this, as i believe we have a very case for false advertising if they don't deliver on these drivers also.
what do think should be a next course of action as i have already sent emails made phone calls and nothing is happening, any suggestions as i am not going to let this drop...
Saulo your English is very good :)
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.
Humm, interesting. I'll take a look when my wireless adapter comes. Where exactly was the registry key in question? HKLM/..?
