LilyPad - new pad plugin with a lame name

[ChickenLiver]

What do you have mouse mode set to? What is the exact behavior you're experiencing? "Can't seem to get it to configure" tells me nothing... Well, I suppose it's a little better than "It doesn't seem to work."

[odin607]

Screenshot of configs:
http://img507.imageshack.us/img507/5...lconfigfy3.jpg

I ment it really just wasnt responding... (lack of behavior? lol)

if i click Vert axis, it moves the curser, then i move mouse up, and nothing happens.

Though i did get horizontal to work.. once >.>...

same dealio with M4/M5.. they just doesnt do respond/do anything

oh and ive toggled allow binding axes to buttons off/on so thats not an issue

ZEE MOUZE MOVEMENTZ
ZEY DO NOTHINGZ!

[ChickenLiver]

Ok... So buttons 1-3 are working fine, but you can't bind the axes or buttons 4 and 5? Or can you bind the axes, but they aren't working in-game? Might come as a surprise, but knowing what works when is more useful than knowing that something doesn't work at some point. And what does worked once mean? Was it the first time, a random time, after fighting with it for a while, or what?

For the axes: Have you tried Windows Messaging mouse mode? What GS plugin are you using (If you can bind, but they don't work in game)?

With M4/M5, the SetPoint driver generally handles them and does funky stuff with them. What do you have them mapped to there? If you map them to normal keystrokes, they should work fine (Though they'll be bound as keys). If you map them to something funky, no way for me to get the message, as there is no message sent anywhere. If you have them bound to something only moderately funky, suppose Windows Messaging keyboard mode might work as well.

[bimbaa]

Hi guys, I'm back after some time, formatted my PC. I can now configure Lilypad just fine, but I have a new problem. As you can probably guess, I'm a newbie at this and I don't know much about what I'm doing. Anyways, I'm using the newest version of Lilypad and (I'm using PS2 dualshock 2 pad) managed bind the buttons and the analog sticks (btw, is it possible to bind the directional buttons on the left?) so Lilypad recognized the buttons just right and I then proceeded to play Persona 3.

To my surprise it seems like the emu doesn't understand that I'm using the analog sticks as it doesn't react when I use them. I tried megapad plugin but I had some sensitivity problems there so I decided to try Lilypad again. So if anyone has time to help me with this, please do so Thanks.

[ChickenLiver]

Do the analog sticks work on other games for you? Have you tried turning on/off the auto analog button (It's the only option in LilyPad that may require you to restart the emulator, by the way)?

To bind the d-pad, just press the vertical d-pad axis button and press up/down. That's in the docs.

[bimbaa]

Doh so that's what D pad means..

I tried Kingdom Hearts, the directions don't work in that one either.

I guess they don't work in any game.

[ChickenLiver]

Odd that you can bind them fine but they don't work in game... Problem is generally the other way around. Does the d-pad work fine in-game?

Enable logging, start either game, and go to a point where the analog sticks should be responding but aren't. Just the main menu would be fine. Then hold down an analog stick (Say, hold up on the left stick. Doesn't really matter, but I want to know which should be down) and quit the game. Post the resulting PadLog.txt (It'll be in the PCSX2\logs directory) and your LilyPad.ini and I'll see if I can figure out what's going on. If you compress the log file, it'll be small enough to attach to a post here.

[bimbaa]

Ok here's the log.

E: And no, D-pad doesn't work either.

[bimbaa]

And the .ini ...

[ChickenLiver]

Your binding's completely messed up. You have up and down bound to the same thing, effectively canceling each other out.. First, delete your old ini. Go into LilyPad's config screen and leave multiple binding diabled. Bind the buttons as before. Then press, in LilyPad: Vertical axis under left-stick. Then press your left analog stick up. Press horizontal axis,also under left stick, then press your left stick right (or left. Doesn't matter). Then do the same for the right stick. Then press D-pad vertial, and press your d-pad up.

Do not touch the up/down/left/right buttons in the interface. Those are for binding buttons, not binding axes. The first line of the troubleshooting section, at the top of my post, says, in bold, to use the axis buttons to bind axes. Don't know how I could make this any clearer.

[bimbaa]

Ok, thanks for the thorough explanation. I did try to read the troubleshooting last night, but for some reason didn't understand it correctly. Anyways, it works now. Perfectly. Big thanks

[odin607]

Originally Posted by ChickenLiver

Ok... So buttons 1-3 are working fine, but you can't bind the axes or buttons 4 and 5? Or can you bind the axes, but they aren't working in-game? Might come as a surprise, but knowing what works when is more useful than knowing that something doesn't work at some point. And what does worked once mean? Was it the first time, a random time, after fighting with it for a while, or what?

For the axes: Have you tried Windows Messaging mouse mode? What GS plugin are you using (If you can bind, but they don't work in game)?

With M4/M5, the SetPoint driver generally handles them and does funky stuff with them. What do you have them mapped to there? If you map them to normal keystrokes, they should work fine (Though they'll be bound as keys). If you map them to something funky, no way for me to get the message, as there is no message sent anywhere. If you have them bound to something only moderately funky, suppose Windows Messaging keyboard mode might work as well.

nah nothing on the mouse works, under any. I got it to recognize vert axis.. once... again... just once though, tried to redo and got nothing lol -_-;

and i dont remember first time, but this time it worked the first time after i changed to windows mess... so probably worked the first time i changed some setting (sorry dont remember at this point.)

tell me some stuff to just try, to slim list down of possibilities or somin

troubleshooting=fail imo.

[ChickenLiver]

There's not much difference between troubleshooting and trying to locate and fix a bug I'm not running into locally. If Windows Messaging worked, it'd probably be an issue with Direct Input. Now it's sounding like an issue with my mouse code. The more information I have, the more likely I am to be able to figure out the issue, and the less time it'll take me to do so. Working only the first time implies there's something wrong with either how I stop listening to the mouse, or start listening to it again.... Useful information, no? Reduces the relevant code to less than 50 lines. If it were a Direct Input problem, would be more than 5 times that much.

Edit: Think I fixed it. Was one of those aforementioned stupid bugs due to last minute changes. Confident enough that I'm releasing a new version (With another slight improvement to how the save/load stuff works. It now remembers the last file touched, other than the ini). Check first post for a new release (0.9.1).

[Mr. Killjoy]

It's me or force feedback ins broken in the latest version? I have a Saitek P2500, previous versions of the plugins worked fine (at least FF test in the config panel did) but now with the same config on 0.9.1 it doesn't seem to work at all...

Beside that it's a nice plugin, I like not having to move the mouse every once in a while to prevent my screensaver to pop up ^^

[ChickenLiver]

That's mighty odd. The only difference in force feedback is that I now create forces with 0 force in all other directions (like (0,1,0) for a force in the y-direction). I used to create single direction forces (like (1), and specifying I'm only using the y-direction). This fixed an issue GiGaHeRz was having due to buggy drivers not handling single direction forces in different directions properly. Sounds like your drivers are buggy, but have trouble in the exact opposite situation. Might have to add a toggle between the two methods or something. Maybe I'll just create another screen with complete force configuration.

Thanks for the info.

Anyone else have force feedback issues with 0.9.1 but not 0.8.4?

[Mr. Killjoy]

"Sounds like your drivers are buggy"
Tried both with and without drivers, and it worked in the 0.8.x so you most likely broke something ^^' We'll see what others say... meanwhile I'll play wiht that feature, it's not that important in FFX2

[ChickenLiver]

Try this. Should use the old method. Two whole lines are changed. If this works, it indicates that the issue is just what I said it is (That is, your drivers don't like multiple direction forces, at least when the force is 0 in all but one direction).

[Mr. Killjoy]

Works just like it did before your previous changes

[alexxb]

I need help please. The D-pad and Analog doesn't work. How can I fix this??

[ChickenLiver]

If reading the first line in the trouble shooting section at the top of the first post doesn't help you, I need more information.

What are you trying to bind? Game controller? Keyboard? Mouse? Networked toaster? What does "Doesn't work" mean? You can't bind them at all? It doesn't work in game? You have a broken controller?