Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Controller input problem.
#1
Games that work well:

Batman: Arkham Asylum
Tony Hawk's Pro Skater 2
Tony Hawk's Pro Skater 3


Games that don't work well:

PCSX2
Dolphin
Project64
1964

http://www.youtube.com/watch?v=26cSUs28YtY&fmt=18

----------

For games that work well, the analog sticks are flawless with no problems at all where as with the games that don't work well, Up-Right, Down-Right and Down-Left don't register properly resulting in the main character moving very slowly. Upping the sensitivity a good deal fixes it but negates the effectiveness of moving slowly in games.

Project64 and 1964 don't require much of a boost to sensitivity to rectify the problem while Dolphin and PCSX2 do require a massive boost.

How do I fix this? Someone suggested changing the shape of the dead zone but I don't think such an option is available.




Edit: Xbox360 controller with latest controller software from MS.
Computer specifications:
Windows 10 x64 | Intel Core i7 @ 2.66GHZ | ASUS P6T | Gigabyte Windforce x3 Geforce  760 4GB | 8GB DDR3 1600MHZ RAM | Integrated Audio
Reply

Sponsored links

#2
have you tried XBCD, a custom driver for XBOX 360 controller (not wireless) which utilizes Direct input instead of Xinput which means you can configure your controller a great deal more
http://redcl0ud.1.forumer.com/index.php?showtopic=2155

you can also configure your trigger as buttons and the controller will use force feedback, if a game which does not use Xinput supports it
Chicken is not Vegan?

NO VEGAN DIET NO VEGAN POWERS!!!!

http://www.flixxy.com/my-blackberry-is-not-working.htm
Reply
#3
(11-14-2010, 01:02 PM)kabooz Wrote: have you tried XBCD, a custom driver for XBOX 360 controller (not wireless) which utilizes Direct input instead of Xinput which means you can configure your controller a great deal more
http://redcl0ud.1.forumer.com/index.php?showtopic=2155

you can also configure your trigger as buttons and the controller will use force feedback, if a game which does not use Xinput supports it

How do you select it in the emulator once installed?

edit: Oh am I to go to Device Manager and change the driver there after installation?
Computer specifications:
Windows 10 x64 | Intel Core i7 @ 2.66GHZ | ASUS P6T | Gigabyte Windforce x3 Geforce  760 4GB | 8GB DDR3 1600MHZ RAM | Integrated Audio
Reply
#4
Which emulator/plugin version are you using?
I also have an x360 and using latest 9.7 with included lilypad I dont have this problem and no custom drivers needed. Actually no custom drivers have been needed since 9.5 I believe.
Specs:
CPU: C2D E8400 @ 3.6
GPU: GTX 560Ti 2Gb
MOB: Asus P5QL
RAM: Crucial 4Gb
OS: Windows 7 64bit/XP 32bit
Reply
#5
It is installed and the driver has loaded. I copied the xinput1_1.dll, xinput1_2.dll, xinput1_3.dll, xinput9_9_1_0.dll files and x360ce.ini to the same folder as PCSX2.exe. How do I configure the emulator to take advantage of this new driver?
Computer specifications:
Windows 10 x64 | Intel Core i7 @ 2.66GHZ | ASUS P6T | Gigabyte Windforce x3 Geforce  760 4GB | 8GB DDR3 1600MHZ RAM | Integrated Audio
Reply
#6
Bump tried various API's (Raw Input, XInput, Direct Input) with both the official driver and the XBCD one and the same issue is present in both. Presumably XBCD reroutes all the other API's to DirectDraw right?

I can solve it by bumping the sensitivity like I originally suspected but PCSX2 doesn't seem to require as drastic a buff as Dolphin. I only had to buff it to 1.01 for all axis. I did mention that I hate using sensitivity to counter the problem so am still open to other suggestions.
Computer specifications:
Windows 10 x64 | Intel Core i7 @ 2.66GHZ | ASUS P6T | Gigabyte Windforce x3 Geforce  760 4GB | 8GB DDR3 1600MHZ RAM | Integrated Audio
Reply




Users browsing this thread: 1 Guest(s)