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.