An issue I also had with SR3

SketchSlayer

SketchSlayer

For some unknown reason legitimate versions of both 3 and 4 on my machine mess up controller input in a big way, right stick being fully inverted left b being a etc, and I checked breifly with a pirate version which didn't seem to have the issue (maybe due to being an earlier version or something).

So I'm more confused about this than I used to be since I had assumed the pushy "your controller has issues response" was right since it is from an old 360 that has since passed on due to rrod and a few other issues that controllers have with some games have shown (mostly fixable like the sleeping dogs double input) had shown up with it.

Is there any changes to win 7 that could cause this kind of issue or anything that was changed in the newer patches of sr4 (and possibly 3, never checked if early versions of that worked).

I have heavily customized what win 7 runs and how it displays some things for the sake of preformance and pesonal taste so I figure there is a chance that the way the game takes controller input is somehow linked to something i have disabled or otherwise changed.
 
This sounds like a strange case. Perhaps the game isn't detecting the controller through xinput and is using directinput.

Make sure you don't have any other gamepad devices connected. Also, when some they reported control issues with SR3, a couple of users had success by uninstalling drivers for other control devices (Logitech, Razer, Belkin, anything) and/or reinstalling their 360 controller drivers.
 
Would there be any way to force xinput?
Does sound like that is a possibility since the fix for say sleeping dogs is a directinput8.dll file which limits those games to detecting it once.
Also the only controller drivers i have are the 360 pad ones and removing them and reinstalling did nothing so I assume the drivers are as they should be.
 
Last edited:
Yeah, decided to post in that thread since the other guy might still not have found any solution.
Best I can tell the cause is either a feature of windows people disable that actually has a use or a registery screw up somewhere.
If I knew much abouthow 360 input works and how games recieved the info from them I would attempt to look further into it as there will be a simpler way of fixing it but not one I have a clue about.

And reinstalling windows isn't that major of a thing on a gaming pc since you can keep the steam library and such on a non system drive and just reinstall steam and chuck them back in provided you don't have too many random programs you run (which case reinstalling would be a nightmare).
Or you can do an extremely messed up install as I did by not really reinstalling things but chucking the previous installs versions on and hoping they work (only did this since I'ma be reinstalling again when I get my new mobo) steam itself fixes this because it notices what has been done.
 
Last edited:
You must log in or register to reply here.
Back
Top