..:: PCSX2 Forums ::..

Full Version: LilyPad 0.10.0
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
I've looked through this thread in particular but haven't seen an answer. I am using an arcade stick that is mapped like a keyboard. There are only 4 buttons, which are mapped to the main 4 buttons, so I was trying to find a way to simulate "L1" by pressing 2 buttons. Just an example "O" is triangle, "V" is x. Is there a way to make "O+V" = "L1"?
No, that currently isn't possible with LilyPad.

I think the TwinPad plugin does offer this through the combo feature: http://forums.pcsx2.net/Thread-TwinPad-v0-9-25
(07-23-2016, 06:09 PM)FlatOut Wrote: [ -> ]No, that currently isn't possible with LilyPad.

I think the TwinPad plugin does offer this through the combo feature: http://forums.pcsx2.net/Thread-TwinPad-v0-9-25

Thank you. It didn't work for what I needed but it will help for FFX lol.
(07-18-2016, 11:17 AM)FlatOut Wrote: [ -> ]If your controller has motion controls you need to keep the controller still and upright when pressing any buttons, or it will always detect the accelerator input.

I am having this same exact issue with the Matricom G-Pad XYBA.  I don't believe this device even has any accelerometers in it.  Anyway, keeping it still and/or upright doesn't help the situation.

Any other ideas anyone?
(10-02-2016, 03:08 PM)thepod Wrote: [ -> ]I am having this same exact issue with the Matricom G-Pad XYBA.  I don't believe this device even has any accelerometers in it.  Anyway, keeping it still and/or upright doesn't help the situation.

Any other ideas anyone?
Have you set the controller to PC mode (X + M buttons)?
(10-02-2016, 04:42 PM)FlatOut Wrote: [ -> ]Have you set the controller to PC mode (X + M buttons)?

Yes, but that appears to be "wired mode". I'm trying to use this controller wirelessly. Actually, Bluetooth connects when I use the X + Home buttons, but I then get a "driver error" and it disconnects.

I should note that when I connect using A + Home, it works well with other games/emulators, and everything appears normal in the "USB Gamepad" Windows control panel. I speculate that the LilyPad driver has the ability to look for accelerometers, which the other games/emulators do not, which may be contributing to the problem.
well right now I am dealing with a issue i have discovered that several others have with this plugin. It seems to cause buttons and stick controls to overlap in certain games like Castlevania: Curse of Darkness. Right now my right stick also acts as if it is a set of buttons. My d-pad does the same. I cannot select any of the Innocent Devil's special abilities so i am stuck in the Temple right now.
(10-07-2016, 01:26 AM)shatterhand Wrote: [ -> ]well right now I am dealing with a issue i have discovered that several others have with this plugin. It seems to cause buttons and stick controls to overlap in certain games like Castlevania: Curse of Darkness. Right now my right stick also acts as if it is a set of buttons. My d-pad does the same. I cannot select any of the Innocent Devil's special abilities so i am stuck in the Temple right now.
Can you post the contents of your LilyPad.ini file (it can be found in the My Documents\PCSX2\inis folder)?
(10-07-2016, 11:59 AM)FlatOut Wrote: [ -> ]Can you post the contents of your LilyPad.ini file (it can be found in the My Documents\PCSX2\inis folder)?

Here ya go:

[General Settings]
Last Config Path=C:\PCSX2 1.4.0
Last Config Name=LilyPad.lily
Force Cursor Hide=0
Mouse Unfocus=0
Background=1
Multiple Bindings=0
DirectInput Game Devices=1
XInput=0
DualShock 3=0
Multitap 1=0
Multitap 2=0
Escape Fullscreen Hack=0
Disable Screen Saver=0
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=1
[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
[Device 2]
Display Name=WM Mouse
Instance ID=WM Mouse
API=2
Type=2
[Device 3]
Display Name=Raw KB: HID Keyboard Device
Instance ID=\\?\HID#VID_413C&PID_2111&MI_00#7&30f84754&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 4]
Display Name=Raw MS: HID-compliant mouse
Instance ID=\\?\HID#VID_046D&PID_C408#6&34497429&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\HID\VID_046D&PID_C408
API=3
Type=2
[Device 5]
Display Name=Simulated Keyboard
Instance ID=Simulated Keyboard
API=3
Type=1
[Device 6]
Display Name=Simulated Mouse
Instance ID=Simulated Mouse
API=3
Type=2
[Device 7]
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, 87183, 0, 0, 13172
Binding 17=0x02020012, 0, 35, 87183, 0, 0, 13172
Binding 18=0x01020013, 0, 32, 87183, 0, 0, 13172
Binding 19=0x02020013, 0, 34, 87183, 0, 0, 13172
Binding 20=0x01020014, 0, 37, 87183, 0, 0, 13172
Binding 21=0x02020014, 0, 39, 87183, 0, 0, 13172
Binding 22=0x01020015, 0, 36, 87183, 0, 0, 13172
Binding 23=0x02020015, 0, 38, 87183, 0, 0, 13172
FF Binding 0=Constant 0, 0, 0, 0, 65536, 1, 0
FF Binding 1=Constant 0, 1, 0, 0, 0, 1, 65536
[Device 8]
Display Name=XInput Pad 1
Instance ID=XInput Pad 1
API=4
Type=3
Binding 0=0x00040000, 1, 20, 65536, 0, 0, 0
Binding 1=0x00040001, 1, 22, 65536, 0, 0, 0
Binding 2=0x00040002, 1, 23, 65536, 0, 0, 0
Binding 3=0x00040003, 1, 21, 65536, 0, 0, 0
Binding 4=0x00040004, 1, 19, 65536, 0, 0, 0
Binding 5=0x00040005, 1, 16, 65536, 0, 0, 0
Binding 6=0x00040006, 1, 17, 65536, 0, 0, 0
Binding 7=0x00040007, 1, 18, 65536, 0, 0, 0
Binding 8=0x00040008, 1, 26, 65536, 0, 0, 0
Binding 9=0x00040009, 1, 27, 65536, 0, 0, 0
Binding 10=0x0004000C, 1, 30, 65536, 0, 0, 0
Binding 11=0x0004000D, 1, 29, 65536, 0, 0, 0
Binding 12=0x0004000E, 1, 31, 65536, 0, 0, 0
Binding 13=0x0004000F, 1, 28, 65536, 0, 0, 0
Binding 14=0x00200010, 1, 24, 65536, 0, 0, 1
Binding 15=0x00200011, 1, 25, 65536, 0, 0, 1
Binding 16=0x01020012, 1, 33, 87183, 0, 0, 13172
Binding 17=0x02020012, 1, 35, 87183, 0, 0, 13172
Binding 18=0x01020013, 1, 32, 87183, 0, 0, 13172
Binding 19=0x02020013, 1, 34, 87183, 0, 0, 13172
Binding 20=0x01020014, 1, 37, 87183, 0, 0, 13172
Binding 21=0x02020014, 1, 39, 87183, 0, 0, 13172
Binding 22=0x01020015, 1, 36, 87183, 0, 0, 13172
Binding 23=0x02020015, 1, 38, 87183, 0, 0, 13172
FF Binding 0=Constant 1, 0, 0, 0, 65536, 1, 0
FF Binding 1=Constant 1, 1, 0, 0, 0, 1, 65536
[Device 9]
Display Name=XInput Pad 2
Instance ID=XInput Pad 2
API=4
Type=3
[Device 10]
Display Name=XInput Pad 3
Instance ID=XInput Pad 3
API=4
Type=3
[Device 11]
Display Name=DX Mouse
Instance ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
API=1
Type=2
[Device 12]
Display Name=DX Keyboard
Instance ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
API=1
Type=1
[Device 13]
Display Name=DX HID-compliant consumer control device
Instance ID=C25E59B0-5AF8-11E4-8003-444553540000
Product ID=DEEFFEEB-0000-0000-0000-504944564944
API=1
Type=3
[Device 14]
Display Name=DX USB Vibration Joystick
Instance ID=D46DB110-24B3-11E1-8001-444553540000
Product ID=00060079-0000-0000-0000-504944564944
API=1
Type=3
Binding 0=0x01020001, 0, 34, 65536, 0, 0, 13172
Binding 1=0x02020001, 0, 32, 65536, 0, 0, 13172
Binding 2=0x01020000, 0, 33, 65536, 0, 0, 13172
Binding 3=0x02020000, 0, 35, 65536, 0, 0, 13172
Binding 4=0x00040000, 0, 28, 65536, 0, 0, 0
Binding 5=0x00040001, 0, 29, 65536, 0, 0, 0
Binding 6=0x00040002, 0, 30, 65536, 0, 0, 0
Binding 7=0x00040003, 0, 31, 65536, 0, 0, 0
Binding 8=0x00040004, 0, 24, 65536, 0, 0, 0
Binding 9=0x00040005, 0, 25, 65536, 0, 0, 0
Binding 10=0x00040006, 0, 26, 65536, 0, 0, 0
Binding 11=0x00040007, 0, 27, 65536, 0, 0, 0
Binding 12=0x00040008, 0, 16, 65536, 0, 0, 0
Binding 13=0x00040009, 0, 19, 65536, 0, 0, 0
Binding 14=0x0004000A, 0, 17, 65536, 0, 0, 0
[Device 15]
Display Name=DX Dell
Instance ID=6056C180-3847-11E5-8001-444553540000
Product ID=A503413C-0000-0000-0000-504944564944
API=1
Type=3
[Device 16]
Display Name=DX Dell USB Wired Entry Keyboard
Instance ID=9387DE80-A049-11E5-8001-444553540000
Product ID=2111413C-0000-0000-0000-504944564944
API=1
Type=3
[Device 17]
Display Name=DX Dell USB Wired Entry Keyboard
Instance ID=938AC4B0-A049-11E5-8002-444553540000
Product ID=2111413C-0000-0000-0000-504944564944
API=1
Type=3


Thank you for any help you can give me in advance.
(10-07-2016, 05:41 PM)shatterhand Wrote: [ -> ][Device 14]
Display Name=DX USB Vibration Joystick
Instance ID=D46DB110-24B3-11E1-8001-444553540000
Product ID=00060079-0000-0000-0000-504944564944
API=1
Type=3
Binding 0=0x01020001, 0, 34, 65536, 0, 0, 13172
Binding 1=0x02020001, 0, 32, 65536, 0, 0, 13172
Binding 2=0x01020000, 0, 33, 65536, 0, 0, 13172
Binding 3=0x02020000, 0, 35, 65536, 0, 0, 13172
Binding 4=0x00040000, 0, 28, 65536, 0, 0, 0
Binding 5=0x00040001, 0, 29, 65536, 0, 0, 0
Binding 6=0x00040002, 0, 30, 65536, 0, 0, 0
Binding 7=0x00040003, 0, 31, 65536, 0, 0, 0
Binding 8=0x00040004, 0, 24, 65536, 0, 0, 0
Binding 9=0x00040005, 0, 25, 65536, 0, 0, 0
Binding 10=0x00040006, 0, 26, 65536, 0, 0, 0
Binding 11=0x00040007, 0, 27, 65536, 0, 0, 0
Binding 12=0x00040008, 0, 16, 65536, 0, 0, 0
Binding 13=0x00040009, 0, 19, 65536, 0, 0, 0
Binding 14=0x0004000A, 0, 17, 65536, 0, 0, 0
These are the bindings for your controller. As you can tell by looking at the default bindings(XInput Pad 0 and 1) above it, it doesn't have bindings for all buttons(14 instead of 23). Only the left stick, face buttons, shoulder buttons and select and start are assigned. So your d-pad and right stick aren't assigned at all. So this issue should affect all other games as well, not just Castlevania.

I did see some other people mentioning a driver issue for your controller that causes the d-pad and right analog stick to be recognized as different buttons. So that would mean it's not a LilyPad issue, but a driver issue instead.