LilyPad - new pad plugin with a lame name - Page 4

Brandestoch · July 3rd, 2007

Quote:

Originally Posted by ChickenLiver

I'm sorry, I'm having trouble understanding you. So the d-pad and some other control (A slider of some sort? The "Discar" and "Controle de rolagem" things? I've never used an Xbox controller) does not work? And it doesn't work when you select both motors together?

Here's a version with an attempt to fix the issue with the d-pad (It now polls devices that report that they don't need to be polled...Might be causing the problem, might not be), and a fix for an issue when both small and big motors are configured to cause the same actuators to vibrate.

Tell me if this fixes any of your issues.

Excuse me if I didn't more specify. I would like configures R1 and L1 or R2 and L2, but the plugin doesn't get to recognize dialing or the snowballing control in this buttons. however the plugin seems to recognize usually when I configure like R1/L1 buttons. D-pad works fine. With this fix seemingly the problem with the motors was solved but I didn't only get to check if they are working in an independent way. The problem with the buttons dial and snowballing control continues.

Last edited by Brandestoch; July 8th, 2007 at 03:31..

**ChickenLiver** · July 3rd, 2007

I don't know what you mean by "buttons dial" or "snowballing control". I had assumed "dial" referred to the d-pad, as a number of people have had issues with it, and it is a directional control (Hence a dial). Are they the black and white buttons on the xbox controller?

Brandestoch · July 4th, 2007

Quote:

Originally Posted by ChickenLiver

I don't know what you mean by "buttons dial" or "snowballing control". I had assumed "dial" referred to the d-pad, as a number of people have had issues with it, and it is a directional control (Hence a dial). Are they the black and white buttons on the xbox controller?

No, they are the equivalent buttons to R1 and L1 of Playstation

**ChickenLiver** · July 4th, 2007

Hmm...That's the first I've heard of a problem with buttons. Looks like I'm detecting them ("L Trigger" and "R Trigger"). I'll look into it, but no promises. Hard to debug a problem you can't replicate.

Brandestoch · July 4th, 2007

Quote:

Originally Posted by ChickenLiver

Hmm...That's the first I've heard of a problem with buttons. Looks like I'm detecting them ("L Trigger" and "R Trigger"). I'll look into it, but no promises. Hard to debug a problem you can't replicate.

OK. Maybe this helps to fix this. Tries to see how the buttons R1/L1 or R2/L2 or R3/L3 get to recognize usually but not the buttons R1, L1, R2, L2.

**ChickenLiver** · July 4th, 2007

There's no special code for them. The same DirectInput code handles any key on the keyboard, mouse buttons, and all buttons on any other device. As long as they are normal button objects (And assuming they are the "L trigger" and "R trigger", they are normal button objects), there's no reason I can think of that they wouldn't be working. As this code works for every button on every device I've ever tried it on, and no one else has reported any bugs with it, I have absolutely nothing to go on.

The only other thing I could think of is they they're actually the "Discar" and "Controle de rolagem" axis objects (Not speaking Portuguese (?), I can't make sense of either name), rather than buttons. In which case, I have no clue what their behavior is if it doesn't work with the "L1/R1 axis" options and such.

Brandestoch · July 4th, 2007

Look at the image
The green and blue bars are respectively the buttons in subject.

Attached Images

xbox.gif (94.9 KB, 57 views)

**ChickenLiver** · July 4th, 2007

Ok...So we are talking about the "Discar" and "Controle de rolagem" axis objects. Great, that explains it completely. They aren't officially "buttons", then, but rather axes. Buttons can only be up or down, while axis objects provide a position along an axis.

So the green and blue bars are each single pressure-sensitive buttons? That is, you want (for example) the green bar to be L1 and the blue bar to be R1 (As opposed to one bar being L1 when empty and R1 when full, which is what the "L1/R1 axis" option does)?

Last edited by ChickenLiver; July 4th, 2007 at 17:37..

Brandestoch · July 4th, 2007

Quote:

Originally Posted by ChickenLiver

Ok...So we are talking about the "Discar" and "Controle de rolagem" axis objects. Great, that explains it completely. They aren't officially "buttons", then, but rather axes. Buttons can only be up or down, while axis objects provide a position along an axis.

So the green and blue bars are each single pressure-sensitive buttons? That is, you want (for example) the green bar to be L1 and the blue bar to be R1 (As opposed to one bar being L1 when empty and R1 when full, which is what the "L1/R1 axis" option does)?

Yes, green bar is Left or "discar" and blue bar is Right or "Controle de rolagem" pressure-sensitives "Triggers".

It's exactly what I need, the green bar as L1 or L2 and the blue bar as R1 or R2 buttons.

**ChickenLiver** · July 5th, 2007

See if this version lets you do what you want. First check "Allow binding axes to buttons" on the first page, then bind the buttons. It's disabled by default so people don't accidentally bind, e.g., a left-right axis to left or right accidentally. Figure not a lot of people will run into your issue, in general.

<Attachment removed. New version released - see first post>

Last edited by ChickenLiver; July 5th, 2007 at 12:04..

Brandestoch · July 5th, 2007

Quote:

Originally Posted by ChickenLiver

See if this version lets you do what you want. First check the "Allow binding axes to buttons" on the first page, then bind the buttons. It's disabled by default so people don't accidentally bind, e.g., a left-right axis to left or right accidentally. Figure not a lot of people will run into your issue, in general.

Great, everything works now, thanks for fix that for me and for your efforts and patience. Thank you very much.

**ChickenLiver** · July 5th, 2007

Bump for new release (0.7.0).

Brandestoch: Glad to hear it. 0.7.0 lets you adjust sensitivity for pressure sensitive buttons, too (In addition to a bunch of other minor other fixes).

Brandestoch · July 6th, 2007

Quote:

Originally Posted by ChickenLiver

Bump for new release (0.7.0).

Brandestoch: Glad to hear it. 0.7.0 lets you adjust sensitivity for pressure sensitive buttons, too (In addition to a bunch of other minor other fixes).

Wow, it's perfect for me now. tks.

Edit:I executed the bios for testing a memorycard, but the control not work inside the bios. I tried to execute with the plugin GSdx9 but not work too.

Last edited by Brandestoch; July 6th, 2007 at 12:02..

**ChickenLiver** · July 8th, 2007

Back up your LilyPad.ini and delete it (Or just rename it). Can you bind your controls again? If so, do they work? On an unrelated note, is the scroll bar supposed to look like that? (Note - this was in response to the post about it not working at all for you, which you have since deleted)

Edit: Also, are you loading states immediately when the game starts or not? Are you using any of the new options on the first page?

Edit 2: BIOS works fine for me, with both GS plugins. Is LilyPad not working at all for you with GSdx9 or only in the BIOS?

Last edited by ChickenLiver; July 8th, 2007 at 04:02..

Brandestoch · July 8th, 2007

Quote:

Originally Posted by ChickenLiver

Back up your LilyPad.ini and delete it (Or just rename it). Can you bind your controls again? If so, do they work? On an unrelated note, is the scroll bar supposed to look like that? (Note - this was in response to the post about it not working at all for you, which you have since deleted)

Edit: Also, are you loading states immediately when the game starts or not? Are you using any of the new general options on the first page?

Edit 2: BIOS works fine for me, with both GS plugins. Is LilyPad not working at all for you with GSdx9 or only in the BIOS?

I have marked the option Disable in "Other Devices", for that he not work. Now I marked Uses Directimput and it is working fine now. It's works fine in Bios too. Excuse me, the mistake was mine.

**ChickenLiver** · July 8th, 2007

That'll do it. Glad you figured it out on your own. Maybe I'll hide or gray out disabled controls in a future version.

Edit: Aforementioned future version released.

Last edited by ChickenLiver; July 9th, 2007 at 04:41..

**refraction** · July 23rd, 2007

added to the official site with a news post

PCSX2.net - News

let me know when you update it and ill update the download section.

__________________

http://www.generalemu.net/
Intel Core 2 Quad Q6600 @ 3.4Ghz (425x8), Leadtek GTX 280 1Gb, 1.8Tb HDs, 2Gb Corsair DDR2-800 @ DDR2-1020 5-5-5-18 Dual Channel
Dont PM me for help, use the forums, thats what its for!

juampo · July 30th, 2007

I have the new version, 0.7.1., but when I configure it, I can't set the D-Pad. Please help.
I have a Logitech Rumble Pad 2, working properly in all windows games.

**ChickenLiver** · July 30th, 2007

Have you installed Logitech's drivers? I have a Rumble Pad 2 as well, and it works perfectly.

Also, in the diagnostics window (Double click on the device's name on the General tab at the bottom), does it display the state of the D-Pad accurately as you move it around?

PCXL-Fan · October 13th, 2007

I had trouble with my d-pad when I first used your plug-in but, then I realized I had set the horizontal as vertical. So I went back and on the 'Vert Axis' button I pressed either Up or Down.

I actually prefer your plug-in better to the built in one since the analog seems to be more sensitive. In FFX when using the other controller plugin you can't walk since the controls are to sensitive (for me at least). With your its difficult but possible to walk by finding a sweet spot pushing the analog. This is using an X-box controller with a usb adapter.

July 23rd, 2007	#77 (permalink)
refraction PCSX2 Coder $refraction's Avatar$ Join Date: Jan 2004 Location: Plymouth, UK Posts: 9,822	added to the official site with a news post PCSX2.net - News let me know when you update it and ill update the download section. __________________ http://www.generalemu.net/ Intel Core 2 Quad Q6600 @ 3.4Ghz (425x8), Leadtek GTX 280 1Gb, 1.8Tb HDs, 2Gb Corsair DDR2-800 @ DDR2-1020 5-5-5-18 Dual Channel Dont PM me for help, use the forums, thats what its for!
$refraction is offline$

October 13th, 2007	#80 (permalink)
PCXL-Fan Heroes Might& Magic Champ Join Date: Oct 2007 Location: Beating Gladiator@ over the head with my Retail box of Heroes of Might and Magic 1,2,3,4 & 5 Posts: 4,412	Can't get controllers working either I had trouble with my d-pad when I first used your plug-in but, then I realized I had set the horizontal as vertical. So I went back and on the 'Vert Axis' button I pressed either Up or Down. I actually prefer your plug-in better to the built in one since the analog seems to be more sensitive. In FFX when using the other controller plugin you can't walk since the controls are to sensitive (for me at least). With your its difficult but possible to walk by finding a sweet spot pushing the analog. This is using an X-box controller with a usb adapter.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

July 3rd, 2007	#62 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	I don't know what you mean by "buttons dial" or "snowballing control". I had assumed "dial" referred to the d-pad, as a number of people have had issues with it, and it is a directional control (Hence a dial). Are they the black and white buttons on the xbox controller?

July 4th, 2007	#64 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	Hmm...That's the first I've heard of a problem with buttons. Looks like I'm detecting them ("L Trigger" and "R Trigger"). I'll look into it, but no promises. Hard to debug a problem you can't replicate.

July 4th, 2007	#66 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	There's no special code for them. The same DirectInput code handles any key on the keyboard, mouse buttons, and all buttons on any other device. As long as they are normal button objects (And assuming they are the "L trigger" and "R trigger", they are normal button objects), there's no reason I can think of that they wouldn't be working. As this code works for every button on every device I've ever tried it on, and no one else has reported any bugs with it, I have absolutely nothing to go on. The only other thing I could think of is they they're actually the "Discar" and "Controle de rolagem" axis objects (Not speaking Portuguese (?), I can't make sense of either name), rather than buttons. In which case, I have no clue what their behavior is if it doesn't work with the "L1/R1 axis" options and such.

July 4th, 2007	#68 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	Ok...So we are talking about the "Discar" and "Controle de rolagem" axis objects. Great, that explains it completely. They aren't officially "buttons", then, but rather axes. Buttons can only be up or down, while axis objects provide a position along an axis. So the green and blue bars are each single pressure-sensitive buttons? That is, you want (for example) the green bar to be L1 and the blue bar to be R1 (As opposed to one bar being L1 when empty and R1 when full, which is what the "L1/R1 axis" option does)? Last edited by ChickenLiver; July 4th, 2007 at 17:37..

July 5th, 2007	#70 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	See if this version lets you do what you want. First check "Allow binding axes to buttons" on the first page, then bind the buttons. It's disabled by default so people don't accidentally bind, e.g., a left-right axis to left or right accidentally. Figure not a lot of people will run into your issue, in general. <Attachment removed. New version released - see first post> Last edited by ChickenLiver; July 5th, 2007 at 12:04..

July 5th, 2007	#72 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	Bump for new release (0.7.0). Brandestoch: Glad to hear it. 0.7.0 lets you adjust sensitivity for pressure sensitive buttons, too (In addition to a bunch of other minor other fixes).

July 8th, 2007	#74 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	Back up your LilyPad.ini and delete it (Or just rename it). Can you bind your controls again? If so, do they work? On an unrelated note, is the scroll bar supposed to look like that? (Note - this was in response to the post about it not working at all for you, which you have since deleted) Edit: Also, are you loading states immediately when the game starts or not? Are you using any of the new options on the first page? Edit 2: BIOS works fine for me, with both GS plugins. Is LilyPad not working at all for you with GSdx9 or only in the BIOS? Last edited by ChickenLiver; July 8th, 2007 at 04:02..

July 8th, 2007	#76 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	That'll do it. Glad you figured it out on your own. Maybe I'll hide or gray out disabled controls in a future version. Edit: Aforementioned future version released. Last edited by ChickenLiver; July 9th, 2007 at 04:41..

July 30th, 2007	#78 (permalink)
juampo Registered User Join Date: Aug 2006 Location: SPAIN Posts: 1	I have the new version, 0.7.1., but when I configure it, I can't set the D-Pad. Please help. I have a Logitech Rumble Pad 2, working properly in all windows games.

July 30th, 2007	#79 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	Have you installed Logitech's drivers? I have a Rumble Pad 2 as well, and it works perfectly. Also, in the diagnostics window (Double click on the device's name on the General tab at the bottom), does it display the state of the D-Pad accurately as you move it around?