Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Xbox 360 analog stick issue.
#1
I cannot get my analog sticks working, they worked fine before but after a reboot they stopped funcioning. all other buttons work just fine.

here's my settings
[Image: GIHTVck.png]

I've tried the following;
Reboot
Reinstall Controller drivers
Reinstall Lilypad
Reinstall PCSX2
Downgrade Lilypad
Downgrade PCSX2
Bind an analog key
Increase analog sensitivity
Test analog sticks outside of PCSX
Reply

Sponsored links

#2
Just use the xpad plugin for your xbox360 controller, no configuration required.
MB: Gigabyte GA-X79-UP4 - Intel® X79 Express Chipset
CPU: 1x Intel® Core™ i7-4820K CPU @ 3.70 GHz
WC: Swiftech H220, Watercooling Kit (Completely Modified)
RAM: 2x 8192 - 16 GB Corsair Vengeance® Pro Series CL11 PC3-17066
GFX: EVGA® Nvidia® GeForce™ GTX 780 Classified ACX - 3,000 GB GDDR5 (With Backplate)
OS - MS - Windows 7 - Professional - x64 - SP 1

Reply
#3
Same problem, All buttons work except the analog sticks. Controller works flawlessly outside of PCSX2.
Reply
#4
Please test your controller under devices and printers first to exclude a hardware defect.

EDIT:
[Image: gvi6.th.png]
MB: Gigabyte GA-X79-UP4 - Intel® X79 Express Chipset
CPU: 1x Intel® Core™ i7-4820K CPU @ 3.70 GHz
WC: Swiftech H220, Watercooling Kit (Completely Modified)
RAM: 2x 8192 - 16 GB Corsair Vengeance® Pro Series CL11 PC3-17066
GFX: EVGA® Nvidia® GeForce™ GTX 780 Classified ACX - 3,000 GB GDDR5 (With Backplate)
OS - MS - Windows 7 - Professional - x64 - SP 1

Reply
#5
(08-29-2013, 07:04 PM)Cole Wrote: Please test your controller under devices and printers first to exclude a hardware defect.

EDIT:
[Image: gvi6.th.png]

Already done, Troubleshooted and calibrated. No effect. It's literally just PCSX thats having this issue. It was working fine yesterday. I tried reinstalling and doing exactly what I did back then to no avail.
Reply
#6
(08-29-2013, 07:15 PM)Vuul Wrote: Already done, Troubleshooted and calibrated. No effect. It's literally just PCSX thats having this issue. It was working fine yesterday. I tried reinstalling and doing exactly what I did back then to no avail.

Try these settings

LilyPad.ini

Code:
[General Settings]
Last Config Path=inis
Last Config Name=LilyPad.lily
Force Cursor Hide=0
Mouse Unfocus=1
Background=1
Multiple Bindings=0
DirectInput Game Devices=1
XInput=1
DualShock 3=0
Multitap 1=0
Multitap 2=0
Escape Fullscreen Hack=1
Disable Screen Saver=1
Logging=0
Save State in Title=0
GH2=0
Turbo Key Hack=0
Vista Volume=1
Close Hacks=0
Keyboard Mode=2
Mouse Mode=0
Volume=100
[Pad 0 0]
Mode=1
Auto Analog=0
[Pad 0 1]
Mode=1
Auto Analog=0
[Pad 0 2]
Mode=1
Auto Analog=0
[Pad 0 3]
Mode=1
Auto Analog=0
[Pad 1 0]
Mode=1
Auto Analog=0
[Pad 1 1]
Mode=1
Auto Analog=0
[Pad 1 2]
Mode=1
Auto Analog=0
[Pad 1 3]
Mode=1
Auto Analog=0
[Device 0]
Display Name=Ignore Keyboard
Instance ID=Ignore Keyboard
API=7
Type=1
[Device 1]
Display Name=WM Keyboard
Instance ID=WM Keyboard
API=2
Type=1
Binding 0=0x00040041, 0, 40, 65536, 0, 0, 0
Binding 1=0x0004004D, 0, 15, 65536, 0, 0, 0
[Device 2]
Display Name=WM Mouse
Instance ID=WM Mouse
API=2
Type=2
[Device 3]
Display Name=Raw KB: Terminal Server Keyboard Driver
Instance ID=\\?\Root#RDP_KBD#0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 4]
Display Name=Raw KB: HID Keyboard Device
Instance ID=\\?\HID#VID_03F0&PID_0024#6&2e1d7234&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 5]
Display Name=Raw MS: Terminal Server Mouse Driver
Instance ID=\\?\Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\Root\RDP_MOU
API=3
Type=2
[Device 6]
Display Name=Raw MS: HID-compliant mouse
Instance ID=\\?\HID#VID_0461&PID_4D20#6&35d0c7fb&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\HID\VID_0461&PID_4D20
API=3
Type=2
[Device 7]
Display Name=Simulated Keyboard
Instance ID=Simulated Keyboard
API=3
Type=1
[Device 8]
Display Name=Simulated Mouse
Instance ID=Simulated Mouse
API=3
Type=2
[Device 9]
Display Name=XInput Pad 0
Instance ID=XInput Pad 0
API=4
Type=3
Binding 0=0x00040000, 0, 20, 65536, 0, 0, 0
Binding 1=0x00040001, 0, 22, 65536, 0, 0, 0
Binding 2=0x00040002, 0, 23, 65536, 0, 0, 0
Binding 3=0x00040003, 0, 21, 65536, 0, 0, 0
Binding 4=0x00040004, 0, 19, 65536, 0, 0, 0
Binding 5=0x00040005, 0, 16, 65536, 0, 0, 0
Binding 6=0x00040006, 0, 17, 65536, 0, 0, 0
Binding 7=0x00040007, 0, 18, 65536, 0, 0, 0
Binding 8=0x00040008, 0, 26, 65536, 0, 0, 0
Binding 9=0x00040009, 0, 27, 65536, 0, 0, 0
Binding 10=0x0004000C, 0, 30, 65536, 0, 0, 0
Binding 11=0x0004000D, 0, 29, 65536, 0, 0, 0
Binding 12=0x0004000E, 0, 31, 65536, 0, 0, 0
Binding 13=0x0004000F, 0, 28, 65536, 0, 0, 0
Binding 14=0x00200010, 0, 24, 65536, 0, 0, 1
Binding 15=0x00200011, 0, 25, 65536, 0, 0, 1
Binding 16=0x01020012, 0, 33, 65536, 0, 0, 13172
Binding 17=0x02020012, 0, 35, 65536, 0, 0, 13172
Binding 18=0x01020013, 0, 32, 65536, 0, 0, 13172
Binding 19=0x02020013, 0, 34, 65536, 0, 0, 13172
Binding 20=0x01020014, 0, 37, 65536, 0, 0, 13172
Binding 21=0x02020014, 0, 39, 65536, 0, 0, 13172
Binding 22=0x01020015, 0, 36, 65536, 0, 0, 13172
Binding 23=0x02020015, 0, 38, 65536, 0, 0, 13172
[Device 10]
Display Name=DX Mouse
Instance ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
API=1
Type=2
[Device 11]
Display Name=DX Keyboard
Instance ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
API=1
Type=1
[Device 12]
Display Name=DX Controller (XBOX 360 For Windows)
Instance ID=DAD335C0-E749-11E2-8001-444553540000
Product ID=028E045E-0000-0000-0000-504944564944
API=1
Type=3
[Device 13]
Display Name=DX SPEED-LINK DUAL SHOCK ADAPTER
Instance ID=E3A431B0-FDDB-11E2-8001-444553540000
Product ID=00030E8F-0000-0000-0000-504944564944
API=1
Type=3
MB: Gigabyte GA-X79-UP4 - Intel® X79 Express Chipset
CPU: 1x Intel® Core™ i7-4820K CPU @ 3.70 GHz
WC: Swiftech H220, Watercooling Kit (Completely Modified)
RAM: 2x 8192 - 16 GB Corsair Vengeance® Pro Series CL11 PC3-17066
GFX: EVGA® Nvidia® GeForce™ GTX 780 Classified ACX - 3,000 GB GDDR5 (With Backplate)
OS - MS - Windows 7 - Professional - x64 - SP 1

Reply
#7
Press the analog button? The one in the screenshot shown to be mapped as the "." key.

Since if you can remap the controller, including analogs, then the plugin does detect the analogs properly.
Reply
#8
(08-29-2013, 08:29 PM)Cole Wrote: Try these settings

LilyPad.ini

Code:
[General Settings]
Last Config Path=inis
Last Config Name=LilyPad.lily
Force Cursor Hide=0
Mouse Unfocus=1
Background=1
Multiple Bindings=0
DirectInput Game Devices=1
XInput=1
DualShock 3=0
Multitap 1=0
Multitap 2=0
Escape Fullscreen Hack=1
Disable Screen Saver=1
Logging=0
Save State in Title=0
GH2=0
Turbo Key Hack=0
Vista Volume=1
Close Hacks=0
Keyboard Mode=2
Mouse Mode=0
Volume=100
[Pad 0 0]
Mode=1
Auto Analog=0
[Pad 0 1]
Mode=1
Auto Analog=0
[Pad 0 2]
Mode=1
Auto Analog=0
[Pad 0 3]
Mode=1
Auto Analog=0
[Pad 1 0]
Mode=1
Auto Analog=0
[Pad 1 1]
Mode=1
Auto Analog=0
[Pad 1 2]
Mode=1
Auto Analog=0
[Pad 1 3]
Mode=1
Auto Analog=0
[Device 0]
Display Name=Ignore Keyboard
Instance ID=Ignore Keyboard
API=7
Type=1
[Device 1]
Display Name=WM Keyboard
Instance ID=WM Keyboard
API=2
Type=1
Binding 0=0x00040041, 0, 40, 65536, 0, 0, 0
Binding 1=0x0004004D, 0, 15, 65536, 0, 0, 0
[Device 2]
Display Name=WM Mouse
Instance ID=WM Mouse
API=2
Type=2
[Device 3]
Display Name=Raw KB: Terminal Server Keyboard Driver
Instance ID=\\?\Root#RDP_KBD#0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 4]
Display Name=Raw KB: HID Keyboard Device
Instance ID=\\?\HID#VID_03F0&PID_0024#6&2e1d7234&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 5]
Display Name=Raw MS: Terminal Server Mouse Driver
Instance ID=\\?\Root#RDP_MOU#0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\Root\RDP_MOU
API=3
Type=2
[Device 6]
Display Name=Raw MS: HID-compliant mouse
Instance ID=\\?\HID#VID_0461&PID_4D20#6&35d0c7fb&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\HID\VID_0461&PID_4D20
API=3
Type=2
[Device 7]
Display Name=Simulated Keyboard
Instance ID=Simulated Keyboard
API=3
Type=1
[Device 8]
Display Name=Simulated Mouse
Instance ID=Simulated Mouse
API=3
Type=2
[Device 9]
Display Name=XInput Pad 0
Instance ID=XInput Pad 0
API=4
Type=3
Binding 0=0x00040000, 0, 20, 65536, 0, 0, 0
Binding 1=0x00040001, 0, 22, 65536, 0, 0, 0
Binding 2=0x00040002, 0, 23, 65536, 0, 0, 0
Binding 3=0x00040003, 0, 21, 65536, 0, 0, 0
Binding 4=0x00040004, 0, 19, 65536, 0, 0, 0
Binding 5=0x00040005, 0, 16, 65536, 0, 0, 0
Binding 6=0x00040006, 0, 17, 65536, 0, 0, 0
Binding 7=0x00040007, 0, 18, 65536, 0, 0, 0
Binding 8=0x00040008, 0, 26, 65536, 0, 0, 0
Binding 9=0x00040009, 0, 27, 65536, 0, 0, 0
Binding 10=0x0004000C, 0, 30, 65536, 0, 0, 0
Binding 11=0x0004000D, 0, 29, 65536, 0, 0, 0
Binding 12=0x0004000E, 0, 31, 65536, 0, 0, 0
Binding 13=0x0004000F, 0, 28, 65536, 0, 0, 0
Binding 14=0x00200010, 0, 24, 65536, 0, 0, 1
Binding 15=0x00200011, 0, 25, 65536, 0, 0, 1
Binding 16=0x01020012, 0, 33, 65536, 0, 0, 13172
Binding 17=0x02020012, 0, 35, 65536, 0, 0, 13172
Binding 18=0x01020013, 0, 32, 65536, 0, 0, 13172
Binding 19=0x02020013, 0, 34, 65536, 0, 0, 13172
Binding 20=0x01020014, 0, 37, 65536, 0, 0, 13172
Binding 21=0x02020014, 0, 39, 65536, 0, 0, 13172
Binding 22=0x01020015, 0, 36, 65536, 0, 0, 13172
Binding 23=0x02020015, 0, 38, 65536, 0, 0, 13172
[Device 10]
Display Name=DX Mouse
Instance ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
API=1
Type=2
[Device 11]
Display Name=DX Keyboard
Instance ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
API=1
Type=1
[Device 12]
Display Name=DX Controller (XBOX 360 For Windows)
Instance ID=DAD335C0-E749-11E2-8001-444553540000
Product ID=028E045E-0000-0000-0000-504944564944
API=1
Type=3
[Device 13]
Display Name=DX SPEED-LINK DUAL SHOCK ADAPTER
Instance ID=E3A431B0-FDDB-11E2-8001-444553540000
Product ID=00030E8F-0000-0000-0000-504944564944
API=1
Type=3

Argh.. That didn't help either. Mellow
@ KrossX I made that binding because i thought maybe the analog sticks were disabled, pressing it did nothing.

I'm seriously confused guys, i have no clue what's causing this. The analogs work fine everywhere else. even lilypad can see the values change in the tests.

Thanks for you help, by the way.
Reply
#9
Try Xpad and see if it works. There's also a padtest ELF in this forum that you can use to test PCSX2 to see input information.

If padtest works fine, and the game is still troubled even when using xpad, then maybe you changed some game setting?
Reply




Users browsing this thread: 1 Guest(s)