LilyPad - new pad plugin with a lame name

[alexxb]

Its a game controller and the controller is not broken (just bought it like 2 hrs ago). I can't bind/set any of the analog or D-pad buttons. When I move the analog (or D-Pad) it doesn't do anything. I didn't see/try the troubleshoot part so I will try and let you know.

Edit:

No, the first line doesn't help.

[ChickenLiver]

Ok, so you are using the bind axis buttons. Pressing bind d-pad horizontal axis button, etc. Do the axes work in the Direct Input device test windows? (Select the device on the first page and press test devices, anf move the d-pat/sticks around to make sure it's reading them right)

Edit: If it's not reading them, try rebooting if you haven't already. Also, if there are any drivers that came with it that you didn't install, try installing them.

[alexxb]

Its reading them. I have everything working except the D-Pad now. It appears to only have the option of vert or hort. I want/need to pick both but it only lets me pick one.

[ChickenLiver]

From first post:

To map a POV object (Better known as a "hat". They are objects that only provide a direction. D-pads are hats on many pad controllers), press an axis button and move the slider in the direction you want to bind to it. Binding one direction to a d-pad/analog stick axis will automatically bind the other direction to the perpendicular axis. As POV objects only report a direction, they have no sensitivity; however, their axes can be flipped independently.

[alexxb]

Thanks for your help. My game pad/controller is now working perfect. Now, to get that DVI to HDMI Cable....

[vafel]

I'm trying to configure my new SG PS2 guitar using the latest lilypad release.
I marked "guitar" under the general tab and it also automatically marks the "allow binding axes to buttons".

My problem is that I can't configure any leys becase something called "axis 6" is being recognized as being pressed and so every key I try to bind is being binded to "axis 6".

When I turn "allow binding axes to buttons" off the problem doesnt accure, but then I lost the ability to use the guitar setting.

any suggestions?

[ChickenLiver]

Sounds like a bug to me. I'll look into it later the week, when I have a chance.

Edit: Until then, you can bind the guitar buttons on the non-guitar screen if you want. There's a post somewhere on this forum (PS2 plugins forum) with a list of how to bind things for Rockband (Not the Guitar Hero 2 binding info in the main forum, even if you're playing GH2). You could also download the last test version in that thread, which I don't believe locks the checkbox.

Locking the "allow binding axes to buttons" setting is because on the Xbox 360 guitar, tilt is an axis, while it's a button the PS2 guitars, and I didn't want people repeatedly asking about it. Sick of people asking about pressing the bind axis button to bind analog sticks and d-pads, and didn't want to create another issue that'd result in tons of repetitive questions. Just letting the user disable it would get around the issue you're running into, but sounds like there's a bug involved, too, which would be best to fix.

[vafel]

thanks for the quick reply.
Seeing I'm the only one who suffers this issue its probably a bug on my side, I just asked in the slight chance its not and that I'm not the only one experiencing this bug.

I'll be sure to check the reccomended thread, thanks alot for a great plugin anf for your help

[Time Master]

Hey I would want to ask something, I read somewhere that ps2 supports the Logitech G25 Wheel, I was wondering if this could be used with the emu. I'm asking because I have one I bought for my PC racing games but it would be great if it was compatible with the emu/pad plugin. Just thinking about playing gran turismo at high res with it... I suppose it isn't possible (yet) but I don't loose anything for asking... :P

Thanks!

[ChickenLiver]

LilyPad should support any standard control (POV control, axis (absolute, relative, 1-direction or 2), and button) on any Direct Input device. I'd imagine a wheel is just a standard axis and foot peddles are just single-dimension axes (Or you could call them pressure sensitive buttons, sliders, whatever). Regardless, they should work with LilyPad, though you'll have to configure everything so it's all mapped to the corresponding PS2 controller buttons.

[khangenghis]

cant seem to get the small motor to work with an Xbox360 controller with Morii drivers.
Large motor + Constant = no problem
Small motor + Ramp = same as large motor vibrating
The small motor works when testing it in the Control Panel game controller setup.
XBCD has no problem with the small motor.

[ChickenLiver]

The Constant/ramp/etc only matters for some PS2 controller drivers, as far as I know. I have them all set up to give a constant force, but some drivers map them to different motors. You need to pick different motors in the axis drop down just above that.

[khangenghis]

I've already tried all the different motors and the small motor still isnt working right. I've resorted to reducing the force feedback value for the time being.

[ChickenLiver]

No clue what's the issue, then. Unless I can reproduce it, doubtful that I'll be able to fix it.

[khangenghis]

probably just the way morii drivers are written. i still like this driver compared to xbcd though. just wanted to report this small hitch

[ChickenLiver]

Thanks for reporting it. One last thought: you are using the dll attached to the first post, and not the dll attached to a post a page back, right? Regardless of which you're using, you could try the other.

Also, does Microsoft's DirectInput sample work with both motors? It's attached below.

[khangenghis]

should be the one in the first post, will try the sample later when i get back

[girolamo5]

I have a problem, not sure if it's a plugin problem, when I try to run PCSX2 with lilypad it crashes, also crashes with megapad, only with mtgs disabled it works.
Tried different games, but nothing. The same games works fine with the twinpad plugin and the keyboard, but not with the gamepad.

Running on a core 2 duo E6300 in windows xp.

[ChickenLiver]

Does it happen with both GSDX and ZeroGS? I've heard about similar crash issues before. I suspect it's some sort of nasty DirectX/DirectInput multithreading issue, so it's rather difficult to figure out what's going on, especially if I can't reproduce it, unfortunately.

If you disable game devices and just use the keyboard (In either DirectInput or Windows Messaging mode), does it not crash?

[Mr. Killjoy]

Well I dunno if he's got the same problem, but I have crashes too sometimes. Mostly happens when I try to resize the GSDX window or when it comes back on focus after switching back from another window (I play windowed so I can talk on MSN, keep an eye on my temps, etc, at the same time). It never happened with SSSpsx pad, which btw also makes resizing the window much faster, I don't really know why it's slow with yours.

/me will see if it works better with Windows messaging (only used Dinput and Raw 'till now, same problem in both modes)


Another thing, while I was trying to walk in FFX2 instead of running, I noticed the sensitivity wasn't the same on all directions. For exemple, a very slight pressure to the left makes me run, but the same (and even a bit more) on the right makes me walk as expected. I dunno if it's a problem in the plugin or in the pad's autocalibration (the calibration monitor showed perfect centers on both sticks).
I dunno how to fix it, if the problem is plugin side, it would be nice being able to customize dead-zone threashold, sensitivity curves (AFAIK, the slider only multiplies sensitivity by x, right?) or something like that. But it's maybe too much to ask, I'll take any workaround you want ^^'