LilyPad 0.10.0
(02-22-2017, 11:02 AM)awsdert Wrote: Okay I tried the rapid fire once more and it seems it is working but not as frequently as expected and feels somewhat buggy somewhere (can't really explain that part yet), I think besides adding the ability to configure the frequency of sending the button's input in milliseconds adding options to play activation/deactivation sounds or some other form of alerting the user to what state the button is being put in would also be appreciated.
That's because it could be triggered twice if you hold the buttons too long, making it seem like it doesn't always work. It worked fine when I did a quick test with the keyboard, but it might not work every time. It was a quick test build, it will work properly once it's added to PCSX2.

I tried using confirmation sounds but they can be inaudible at times due to in-game audio. So that's not the ideal solution.
Reply

Sponsored links

(02-22-2017, 09:48 PM)FlatOut Wrote: That's because it could be triggered twice if you hold the buttons too long, making it seem like it doesn't always work. It worked fine when I did a quick test with the keyboard, but it might not work every time. It was a quick test build, it will work properly once it's added to PCSX2.

I tried using confirmation sounds but they can be inaudible at times due to in-game audio. So that's not the ideal solution.

Okay thanks for the clarification, as for the being triggered twice thing I think that can be stopped if you just record the last time a button is released and compare against that while a button is being held down, the confirmation sounds is just a suggestion besides can just add an option for increasing the volume of those sounds to make sure they are audible or having them go through specific speakers (like headphones) only
Reply
(02-23-2017, 07:20 PM)awsdert Wrote: Okay thanks for the clarification, as for the being triggered twice thing I think that can be stopped if you just record the last time a button is released and compare against that while a button is being held down, the confirmation sounds is just a suggestion besides can just add an option for increasing the volume of those sounds to make sure they are audible or having them go through specific speakers (like headphones) only
Yes, I know how to add and check for things. Like I said it was a quick test build and it worked during a my test, so there was no need for it.

I definitely don't want to add audio settings to a control plugin, as that would inconvience many users and bloat the UI.
Reply
(02-23-2017, 08:04 PM)FlatOut Wrote: Yes, I know how to add and check for things. Like I said it was a quick test build and it worked during a my test, so there was no need for it.

I definitely don't want to add audio settings to a control plugin, as that would inconvience many users and bloat the UI.

A: That was just in case you were hurting for ideas on how to fix it so I was giving my food for thought.
B: The volume control was mearly anotther food for thought if you did go down that route (I myself am currently hurting for ideas of alternatives), since this is a forum we can always wait for a suitable idea from the community to pop up if niether one of us has a good idea. If the route were to be used then perhaps instead of it being added directly to Lily, PCSX2 could have related options added and then pass on pointers to Lily of functions called something like playActivateSound & playDeactivateSound which would then pass on the heavy work to the sound plugin in use.
Reply
Just bumping this in case anyone knows the solution:

Hey guys,
emulator recognizes the controller but I have 2 Nvidia Shield Controllers and for some reason I can't set them up as 2 different pads because they are recognized as the same controller which means 2 players doesn't work well.
Other emulators do recognize these controllers as separate. Might anyone know what's the problem?

Thanks !!

Here is the content of the LilyPad.ini:
Code:
[General Settings]
Last Config Path=D:\Games\PS2\Bios
Last Config Name=LilyPad.lily
Force Cursor Hide=0
Mouse Unfocus=1
Background=1
Multiple Bindings=1
DirectInput Game Devices=1
XInput=1
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=0
Close Hacks=0
Keyboard Mode=3
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
Binding 0=0x0004000D, 0, 19, 65536, 0, 1, 0
Binding 1=0x00040044, 0, 21, 65536, 0, 1, 0
Binding 2=0x00040053, 0, 22, 65536, 0, 1, 0
Binding 3=0x00040057, 0, 20, 65536, 0, 1, 0
Binding 4=0x000400A2, 0, 30, 65536, 0, 1, 0
[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_046D&PID_C232#2&33191fed&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 4]
Display Name=Raw KB: HID Keyboard Device
Instance ID=\\?\HID#VID_1B1C&PID_1B11&MI_00#8&3017fea4&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 5]
Display Name=Raw KB: HID Keyboard Device
Instance ID=\\?\HID#VID_1B1C&PID_1B11&MI_01&Col01#8&34db2f8c&0&0000#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 6]
Display Name=Raw KB: HID Keyboard Device
Instance ID=\\?\HID#virtualdevice&10&Col03#2&1f1ca0f9&0&0002#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 7]
Display Name=Raw KB: HID Keyboard Device
Instance ID=\\?\HID#virtualdevice&10&Col02#2&1f1ca0f9&0&0001#{884b96c3-56ef-11d1-bc8c-00a0c91405dd}
API=3
Type=1
[Device 8]
Display Name=Raw MS: HID-compliant mouse
Instance ID=\\?\HID#virtualdevice&10&Col04#2&1f1ca0f9&0&0003#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\HID\virtualdevice&10&Col04
API=3
Type=2
[Device 9]
Display Name=Raw MS: HID-compliant mouse
Instance ID=\\?\HID#virtualdevice&10&Col01#2&1f1ca0f9&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\HID\virtualdevice&10&Col01
API=3
Type=2
[Device 10]
Display Name=Raw MS: Evoluent VerticalMouse 4
Instance ID=\\?\HID#VID_1A7C&PID_0191#7&2d271fce&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\HID\VID_1A7C&PID_0191
API=3
Type=2
[Device 11]
Display Name=Raw MS: HID-compliant mouse
Instance ID=\\?\HID#VID_046D&PID_C231#2&1dd8bfaf&0&0000#{378de44c-56ef-11d1-bc8c-00a0c91405dd}
Product ID=\\?\HID\VID_046D&PID_C231
API=3
Type=2
[Device 12]
Display Name=Simulated Keyboard
Instance ID=Simulated Keyboard
API=3
Type=1
[Device 13]
Display Name=Simulated Mouse
Instance ID=Simulated Mouse
API=3
Type=2
[Device 14]
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
Binding 24=0x00040000, 1, 20, 65536, 0, 0, 0
Binding 25=0x00040001, 1, 22, 65536, 0, 0, 0
Binding 26=0x00040002, 1, 23, 65536, 0, 0, 0
Binding 27=0x00040003, 1, 21, 65536, 0, 0, 0
Binding 28=0x00040004, 1, 19, 65536, 0, 0, 0
Binding 29=0x00040005, 1, 16, 65536, 0, 0, 0
Binding 30=0x00040006, 1, 17, 65536, 0, 0, 0
Binding 31=0x00040007, 1, 18, 65536, 0, 0, 0
Binding 32=0x00040008, 1, 26, 65536, 0, 0, 0
Binding 33=0x00040009, 1, 27, 65536, 0, 0, 0
Binding 34=0x0004000C, 1, 30, 65536, 0, 0, 0
Binding 35=0x0004000D, 1, 29, 65536, 0, 0, 0
Binding 36=0x0004000E, 1, 31, 65536, 0, 0, 0
Binding 37=0x0004000F, 1, 28, 65536, 0, 0, 0
Binding 38=0x00200010, 1, 24, 65536, 0, 0, 1
Binding 39=0x00200011, 1, 25, 65536, 0, 0, 1
Binding 40=0x01020012, 1, 33, 65536, 0, 0, 13172
Binding 41=0x02020012, 1, 35, 65536, 0, 0, 13172
Binding 42=0x01020013, 1, 32, 65536, 0, 0, 13172
Binding 43=0x02020013, 1, 34, 65536, 0, 0, 13172
Binding 44=0x01020014, 1, 37, 65536, 0, 0, 13172
Binding 45=0x02020014, 1, 39, 65536, 0, 0, 13172
Binding 46=0x01020015, 1, 36, 65536, 0, 0, 13172
Binding 47=0x02020015, 1, 38, 65536, 0, 0, 13172
[Device 15]
Display Name=XInput Pad 1
Instance ID=XInput Pad 1
API=4
Type=3
[Device 16]
Display Name=XInput Pad 2
Instance ID=XInput Pad 2
API=4
Type=3
[Device 17]
Display Name=XInput Pad 3
Instance ID=XInput Pad 3
API=4
Type=3
[Device 18]
Display Name=DX Mouse
Instance ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B60-D5A0-11CF-BFC7-444553540000
API=1
Type=2
Binding 0=0x01010000, 0, 36, 65536, 0, 0, 13172
Binding 1=0x01010000, 0, 16, 65536, 0, 0, 13172
Binding 2=0x01010000, 0, 25, 65536, 0, 0, 13172
Binding 3=0x02010000, 0, 38, 65536, 0, 0, 13172
Binding 4=0x02010000, 0, 34, 65536, 0, 0, 13172
Binding 5=0x02010000, 0, 33, 65536, 0, 0, 13172
Binding 6=0x02010000, 0, 35, 65536, 0, 0, 13172
Binding 7=0x02010000, 0, 30, 65536, 0, 0, 13172
Binding 8=0x02010000, 0, 31, 65536, 0, 0, 13172
Binding 9=0x02010000, 0, 18, 65536, 0, 0, 13172
Binding 10=0x02010000, 0, 27, 65536, 0, 0, 13172
Binding 11=0x02010000, 0, 17, 65536, 0, 0, 13172
Binding 12=0x02010000, 0, 24, 65536, 0, 0, 13172
Binding 13=0x02010000, 0, 26, 65536, 0, 0, 13172
Binding 14=0x02010000, 0, 21, 65536, 0, 0, 13172
Binding 15=0x02010000, 0, 23, 65536, 0, 0, 13172
Binding 16=0x02010000, 0, 20, 65536, 0, 0, 13172
Binding 17=0x01010001, 0, 37, 65536, 0, 0, 13172
Binding 18=0x01010001, 0, 39, 65536, 0, 0, 13172
Binding 19=0x01010001, 0, 32, 65536, 0, 0, 13172
Binding 20=0x01010001, 0, 19, 65536, 0, 0, 13172
Binding 21=0x01010001, 0, 29, 65536, 0, 0, 13172
Binding 22=0x01010001, 0, 28, 65536, 0, 0, 13172
Binding 23=0x01010001, 0, 22, 65536, 0, 0, 13172
Binding 24=0x01010001, 0, 17, 65536, 0, 0, 13172
[Device 19]
Display Name=DX Keyboard
Instance ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
Product ID=6F1D2B61-D5A0-11CF-BFC7-444553540000
API=1
Type=1
[Device 20]
Display Name=DX Corsair K95 RGB Gaming Keyboard
Instance ID=C0DE3E70-B0D2-11E6-8001-444553540000
Product ID=1B111B1C-0000-0000-0000-504944564944
API=1
Type=3
[Device 21]
Display Name=DX Corsair composite virtual input device
Instance ID=C0E36E90-B0D2-11E6-800A-444553540000
Product ID=1BF01B1C-0000-0000-0000-504944564944
API=1
Type=3
[Device 22]
Display Name=DX Audio Controls
Instance ID=C0E36E90-B0D2-11E6-800B-444553540000
Product ID=0A1F046D-0000-0000-0000-504944564944
API=1
Type=3
[Device 23]
Display Name=DX Controller
Instance ID=ECBB3D3D-C2EA-4861-983F-B3E15BDC6C52
Product ID=B4000955-0000-0000-0000-504944564944
API=1
Type=3
Email PM Find Edit Reply Quote Report

Enter Keywords
 Search Thread
« Next Oldest | Next Newest »
Reply
(02-27-2017, 12:48 AM)Garzen Wrote: Other emulators do recognize these controllers as separate. Might anyone know what's the problem?
Here is the content of the LilyPad.ini:
Code:
[General Settings]
Multiple Bindings=1
DirectInput Game Devices=1
XInput=1
DualShock 3=0
Multitap 1=0
Multitap 2=0
To me these particular settings look to be the problem (on the other hand I've never looked at Lily's INI settings before)
Try changing them to:
Code:
Multitap 1=0
Multitap 2=1
Reply
(02-27-2017, 12:48 AM)Garzen Wrote: Just bumping this in case anyone knows the solution:

Hey guys,
emulator recognizes the controller but I have 2 Nvidia Shield Controllers and for some reason I can't set them up as 2 different pads because they are recognized as the same controller which means 2 players doesn't work well.
Other emulators do recognize these controllers as separate. Might anyone know what's the problem?

Thanks !!
I looked into the issue but I've yet to find a solution. It seems several games had the same issue with the controller. It might be a good idea to update the drivers if possible and try using http://www.x360ce.com/ to workaround the issue.


@awsdert Enabling multitap is a bad idea unless you want to play a game(which supports multitap) with 3-4 players. Turning it on will not recognize more controllers.
Reply
(02-27-2017, 04:24 PM)FlatOut Wrote: @awsdert Enabling multitap is a bad idea unless you want to play a game(which supports multitap) with 3-4 players. Turning it on will not recognize more controllers.

Okay, I did say that I've never looked at the INI settings before so it should have been clear from that that it was just a guess based on the name of the parameter
Reply
(02-27-2017, 04:24 PM)FlatOut Wrote: I looked into the issue but I've yet to find a solution. It seems several games had the same issue with the controller. It might be a good idea to update the drivers if possible and try using http://www.x360ce.com/ to workaround the issue.


@awsdert Enabling multitap is a bad idea unless you want to play a game(which supports multitap) with 3-4 players. Turning it on will not recognize more controllers.

Oh that's too bad. Thanks a lot for looking into it though !! Smile
Reply
hello i want to report an issue with 8bitdo nes30 pro, almost all buttons binds to "brake- or brake+ or accelerator"
i noticed in test page that the correct keys switch to "1" but brake too switch to "1" so it seems that 2 contemporary buttons are pressed and lilypad accept only the first voice (brake or accel)
manually setting the bindings WORK
i would suggest an (hack) option, for example "8bitdo nes30 pro" when selected, Lilypad completely ingores BRAKE and ACCELERATOR so other keys can bind correctly Smile
here my manual bindings (still missing L2 and R2 because i have problems finding them Laugh  )
Code:
Binding 0=0x03100000, 0, 20, 65536, 0, 0, 13172, 1, 1
Binding 1=0x04100000, 0, 21, 65536, 0, 0, 13172, 1, 1
Binding 2=0x05100000, 0, 22, 65536, 0, 0, 13172, 1, 1
Binding 3=0x06100000, 0, 23, 65536, 0, 0, 13172, 1, 1
Binding 4=0x01020005, 0, 38, 65536, 0, 0, 13172, 1, 1
Binding 5=0x02020005, 0, 36, 65536, 0, 0, 13172, 1, 1
Binding 6=0x01020002, 0, 37, 65536, 0, 0, 13172, 1, 1
Binding 7=0x02020002, 0, 39, 65536, 0, 0, 13172, 1, 1
Binding 8=0x01020001, 0, 34, 65536, 0, 0, 13172, 0, 1
Binding 9=0x02020001, 0, 32, 65536, 0, 0, 13172, 0, 1
Binding 10=0x01020000, 0, 33, 65536, 0, 0, 13172, 0, 1
Binding 11=0x02020000, 0, 35, 65536, 0, 0, 13172, 0, 1
Binding 12=0x01020006, 0, 41, 65536, 0, 0, 13172, 1, 1
Binding 13=0x02020006, 0, 41, 65536, 0, 0, 13172, 1, 1
Binding 14=0x80020007, 0, 41, 65536, 0, 0, 13172, 1, 1
Binding 15=0x00040000, 0, 29, 65536, 0, 0, 0, 0, 1
Binding 16=0x00040001, 0, 30, 65536, 0, 0, 0, 0, 1
Binding 17=0x00040003, 0, 28, 65536, 0, 0, 0, 0, 1
Binding 18=0x00040004, 0, 31, 65536, 0, 0, 0, 0, 1
Binding 19=0x00040006, 0, 26, 65536, 0, 0, 0, 0, 1
Binding 20=0x00040007, 0, 27, 65536, 0, 0, 0, 0, 1
Binding 21=0x0004000A, 0, 16, 65536, 0, 0, 0, 0, 1
Binding 22=0x0004000B, 0, 19, 65536, 0, 0, 0, 0, 1
Binding 23=0x0004000D, 0, 17, 65536, 0, 0, 0, 0, 1
Binding 24=0x0004000E, 0, 18, 65536, 0, 0, 0, 0, 1
CPU: Intel I7 7700k @5ghz - Water cooled with Corsair H55
MB: Asus Rog Strix Z270I Gaming
RAM: G.Skill Trident Z RGB DDR4 4266MHz 16GB CL19 @4500Mhz
GPU: KFA2 GeForce® GTX 1070 OC Mini
CASE: Fractal Design Node 202
OS: Windows 10
Reply




Users browsing this thread: 4 Guest(s)