Hello Steve

Hope minecraft was worth it xddd

not working hey

NICE!!

NOT WORK

is illegal guy

Not Working Anymore

Not Working

Awesome, thank you very much. I played the demo with the xbox controller so I was disappointed the game dropped the support so I shelved it. With your .ini I've dusted it of just in time to wet my appetite for Mass Effect 2.

I guess good things come to those who wait.:) Once you've mastered Xbox 360 controller in FPS it spoils you going back to keyboard + mouse. Plus its 2009 with so much to those from in the way of descent games you can afford to be fussy so I only try and play games with force feedback support.

However I must admit COD Modern Warfare 2 on the PC is occupying my dreams even though it doesn't have gamepad support !
Do you think you will be able to do anything with the .ini for it ( Modern Warfare 2 ) so we can use our Xbox360 controllers at least, if not also for feedback support?
Once again thank you for your Mass Effect .ini upload. :-)

Gears of War may require an XInput-compatible gamepad(in layman's terms, an Xbox 360 controller)to use rumble. Could be similar to why the Xbox 360 gamepad with MS drivers only rumbles in games with XInput support, and not all of the already-existing games that rely on DirectInput. I just wish that M$ wasn't so hell-bent on phasing out DirectInput in favor of XInput, from the look of things. For instance, I can't use my TM HOTAS Cougar in Crysis for aircraft unless I resort to keyboard emulation, in which case I might as well just use the keyboard(the whole point of using it is for analog movement and aiming!).NamelessPlayer

This is now getting complicated. Here is a quote from Wikipedia:

"XInput

XInput is an API for "next generation" controllers, and was introduced with the launch of the Xbox 360, allowing Xbox 360 controllers to be fully functional under Windows XP SP1 and up. XInput has the advantage that it is significantly easier to program with than DirectInput. XInput is compatible with DirectX 9 and up.

[edit]
DirectInput vs XInput

With DirectInput not having seen any major changes since DirectX 8, and XInput being introduced later in DirectX 9, there is some confusion on the current status and future of the two APIs. Currently, each have features the other doesn't, and neither had major updates with DirectX 10.

When using Xbox 360 Controller with their default Microsoft driver with DirectInput, there are the following limitations compared to with XInput:
The left and right triggers will act as a single axis, not as independent analog axes
The vibration effects will not be available
Querying for headset devices will not be available

According to MSDN, "the combination of the left and right triggers in DirectInput is by design. Games have always assumed that DirectInput device axes are centered when there is no user interaction with the device. However, the Xbox 360 controller was designed to register minimum value, not center, when the triggers are not being held." MSDN's 'solution' was to combine the triggers, setting one trigger to a positive direction and the other to a negative direction, so no user interaction is indicative to DirectInput of the 'control' being at center.[3]

The above, however, ignores the fact that many DirectInput controllers, such as game pads with dual analog sticks and racing wheel controller sets, already map triggers and pedals independently. In addition, many DirectInput devices also have vibration effects. There is at least one driver, XBCD, that gives the Xbox 360 controllers the vibration support, dead zones and (optionally) independent triggers through DirectInput. This indicates Microsoft's Xbox 360 controller driver intentionally has weaker DirectInput support, rather than due to any differences between DirectInput and XInput APIs.

The XInput API also currently has limits that DirectInput does not:
Supports only "next generation" controllers. This limits it basically to controllers for the Xbox 360 that also have windows drivers. Legacy windows controllers are not supported.
Maximum of four controllers at a time. This is an Xbox limit that is carried over to Windows. Although there are currently few PC games that need more than four controllers at once, this seems like an arbitrary restriction as DirectInput has no such limitation.
Does not support keyboards, mice, or mouse-type devices. While this mirrors Microsoft's recommendation not to use DirectInput with these devices, it is possible to use DirectInput with these devices.
Support for only 4 axes, 10 buttons, and 8-direction digital pad per controller, compared to DirectInput's support for 8 axes, 128 buttons, and full-range POV. (Incidentally, the number of axes and buttons XInput supports corresponds directly to the Xbox 360 controller.)

Currently, XInput is for XBox 360 controllers, while DirectInput is for any controller."

This seems to be saying that some people are trying to plug the hole that Microsoft have created with specialist drivers (see bold italic) so I'm better off with a DirectInput controller for the time being until this debarkle is sorted out, or am I reading the wrong?

I suppose it's too much to think that there is a controller that supports both DirectInput and XInput? I'm about to Google to see such a beast exists about post my results here obviously, but in the meantime if anybody with Gears of War for the PC and Xbox 360 controller and tell me for definite that the game doesn't support will speed back with that combination then it's one less thing I have to factor in my wireless rumble controller future purchase?

thank you once again for your input, it is much appreciated - Optical10

PS. - Is there a way to subscribe and get e-mail instant notification of replies to my posts?