LilyPad - new pad plugin with a lame name

[ChickenLiver]

Yea, the slider only multiplies the values read directly from direct input. There's a small default dead zone based on sensitivity, though I don't scale things perfectly, so it goes directly from the deadzone to 2 or 4, can't remember which (Full range is -128 to 127 for analog, 0 to 255 for everything else, in DS2 native mode. I believe the 2-4 is on the 0 to 255 scale, but not positive). Main reason you can't set a dead zone at the moment is just that making an interface for it is a pain, particularly if I make it general enough to allow fixing of axes that aren't calibrated correctly.

I hadn't heard about the resizing issue before, but I just tried it and experienced the same thing (Very slow resizing with LilyPad, that is). No clue what causes it yet, but I should be able to fix that.

I generally play with it maximized (Not full screen), and often have it unfocused, but I have a dual monitor setup, so I have whatever else I'm doing on my other screen. Have yet to have a crash when focusing/unfocusing, but wouldn't be surprised if it's a related issue.

[Mr. Killjoy]

"wouldn't be surprised if it's a related issue."

I thought that too ^^

Well, back the the 1st problem, any idea for this weird asymmetrical sensitivity issue? It happens with both X and Y axies, a direction being more sensitive than its opposite. It's like if the origin had an offset. Maybe it's because 0 isn't exactly a perfect average for -128<->127. (I think it would be -0.5, but I guess you are restricted to integers)

[ChickenLiver]

PS2 controllers send a 1-byte value from -128 to 127. It's unclear exactly where the center is. I've seen claims it's exactly 0, claims it's exactly -1, and claims its in between. It might even depend on the game. I've tried all 3 and haven't noticed any difference. I'm currently using 0 because that's what the other pad plugins use.

Edit: Part of the problem could be I just use an integer cast to round, and it rounds positive and negative numbers slightly differently, I believe.

[Mr. Killjoy]

I just retried with SSS, sensitivity works fine on it. So after that I switched back to yours and deleted joysticks to remap them with an exact 1 for sensitivity (had to use 0.994 or 0.0127 previously cause the slider isn't accurate enough for small value changes). Then it worked just the same as on the other plugin, so it was prolly caused by strange floating point values screwing everything.

[girolamo5]

Does it happen with both GSDX and ZeroGS?

Yes

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

No if i disable the option "Game/Other Devices Mode" it works

[Time Master]

Originally Posted by 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?

Originally Posted by girolamo5

No if i disable the option "Game/Other Devices Mode" it works

Yeah, I had the same problem, you did some test versions for me but at last you said it was not a plugin problem. I had to reinstall my OS anyways so I did it and after that it worked perfect.

Most probably it's a conflict issue with directx, maybe because of installing a controller driver it doesn't like for some reason. I haven't installed my g25 wheel yet, it's possible the pcsx crashes after that since it's the only controller driver I haven't reinstalled yet after reinstalling my OS. I will try it soon and tell you something.

[ChickenLiver]

The resizing thing is caused by releasing and recapturing all input whenever the window is resized (For every frame of the resizing update). In Windows messaging and raw mouse modes, my mouse stuff needs to update whenever the window is resized (When I'm stealing the mouse, have to trap it inside the window.). Of course, when you're resizing the window, I'm not stealing the cursor anyways. Issue will be fixed with the next release (It'll only release/steal the mouse, and only when you're using Windows messaging or raw modes, and only when it was stealing the mouse before - should then run only when maximizing/unmaximizing the window, in theory. Could also only do it when you're done resizing, come to think of it), but for now, you can just set the mouse mode to disabled. Looks like it has nothing to do with whatever focus/unfocus crashes you're having.

[millhouse13]

I need a plugin that lets you map the analog stick axes to buttons, and lets you disable force sensitive buttons (so it will always press the buttons all the way down)...
this plugin seems to be the best one out there, but I can't possibly get it to work!!

somehow, the plugin will never display in the plugin list! I placed the two files lilypad.dll and lilypad64.dll in the pcsx2 AND the plugins folder, but it never displays the plugin in the controller plugin list!

I'm running 64bit vista, and I am ABSOLUTELY sure that I've got visual c++ redist installed...

so, what am I doing wrong? please help

[Mr. Killjoy]

Which version of PCSX2 are you running? If it's too old it may be the reason why it doesn't show

[millhouse13]

I am trying with svn351, but I've had that very same problem with every version I've tried to far, including 0.9.4, I just never had to use this plugin... now I have to, and I can't get it to work

[ChickenLiver]

You are running the 32-bit version of PCSX2, right? The 32-bit dll (lilypad.dll) shouldn't require anything extra, other than DirectX 8.0 or later (DirectX 9.0 didn't come with a new version of DirectInput). It was compiled with MSVC 6.0 (Released in 1998) to avoid any and all dll requirement issues.

If you're running the 64-bit version, you should probably switch to the 32-bit version, since it tends to be faster (And the latest version of GSDX is only released as a 32-bit dll). Otherwise, you could try installing both versions of the VC 2005 runtime (Both 2005 and 2005 SP1. Can't remember which I compiled it with. Think it's SP1, but I'm not positive).

Download details: Visual C++ 2005 SP1 Redistributable Package (x64). Can google for the other one... Again, this is only if you're running the 64-bit version of PCSX2. Not even sure the 64-bit bit version of PCSX2 is still available.

[millhouse13]

I have a feeling that last post was kinda copypasta...

there's a 64bit version of pcsx2? didn't one of the devs say that they wouldn't do that, because the slight speedup wouldn't be worth the pain?
well, anyways, I'm using running on vista 64bit, pcsx2 is 32bit, I have DX10 (using gsdx10, too, but it won't work with DX9 mode, either)

I already have the visual c++ redistributable installed, and I had that problem already when I tried the exact same plugin on Windows XP 32bit. so... what could be the problem?

what exactly do you have to do to get the plugin to work normally? just place the dlls in the pcsx2 or plugin folder, and that's it? well, I did that.

[ChickenLiver]

Yea, that's all you have to do. They only need to be in the plugins folder, btw, not the PCSX2 one. Dlls that plugins depend on need to the in the PCSX2 folder, because of how windows links things.

There is a 64-bit version of PCSX2. I believe it's still available on the sourceforge page, but I could be wrong. You should be using the 32-bit version, anyways, but I just wanted to make sure.

As you had the same problem with XP, I have absolutely no idea what the problem is. It depends on 7 dlls: kernel32.dll, user32.dll, comdlg32.dll, ole32.dll, dinput8.dll, comctl32.dll, and msvcrt.dll. You should have all of these on both OSes, even with a clean install (Vista 64 does support DirectInput 8, though it did drop support for vesions 7 and earlier, apparently).

[millhouse13]

ah, c*ap!!
well, if Ican't get it to work normally, then could you suggest any other controller plugin that let's me map directions on the analog sticks to buttons AND that pushes the X (O, square, etc.) button all the way down? I have the problem that MegaPad appears to only push the buttons a little, and I am playing gta. I can't drive any cars!

[ChickenLiver]

Don't think any pad plugin allows that.

I don't think LilyPad would do exactly what you want, either. While you could map the up axis (Or any other) to X with LilyPad, pressing down on the axis would correspond to not pressing x, and having the axis centered would correspond to having the button half down. Suppose you could reduce the sensitivity a bit, but not sure you could manage the behavior you're after.

[millhouse13]

argh, you didn't understand...

I need the plugin to be able to map the 4 directions of the analog stick to keyboard buttons (I.E. WASD)

then, something completely different: I need the plugin that (virtually) presses the X, square, O, and triangle button (on an actual PS2 controller, but emulated, know what I mean?) when I press the corresponding button on a keyboard...

(backstory: GTA vice city stories only lets you control you characters movement with the analog stick, but when I'm driving a car, the amount of pressure you normally apply on the X button controls how fast you go with the car. with the megapad plugin, I get the right analog stick mapping, but it seems that it only tips the buttons by default (X, O, square, and triangle), so when I enter a car, there's no reaction when I press X, because it thinks I don't press the button had enough)

[ChickenLiver]

Ahh...Yes, I completely misunderstood. LilyPad, MegaPad, and TwinPad should all allow that. As LilyPad and MegaPad aren't working for you, you should try TwinPad.

Would like to figure out what problem you're running into with LilyPad, but have no idea where to look.

[millhouse13]

ah, well, I tried getting TwinPad now, but all I got was a .dll (which I placed in both folders), and an .exe (which, apparently, doesn't work.), and it's not showing up in the plugins list, either... well, thanks for your help, I think it would now go too far away from LilyPad for this thread...

thanks again

[bositman]

Originally Posted by millhouse13

ah, well, I tried getting TwinPad now, but all I got was a .dll (which I placed in both folders), and an .exe (which, apparently, doesn't work.), and it's not showing up in the plugins list, either... well, thanks for your help, I think it would now go too far away from LilyPad for this thread...

thanks again

It's really weird you're getting so much trouble with detecting all plugins.I'd redownload the latest SVN beta (351) and do a fresh install (delete your old pcsx2 directory,reconfigure everything etc)

[girolamo5]

Ok now it works.
If i select Twinpad in the second controller of the pcsx2 config, and Lilypad in the first controller, pcsx2 always crash.
With any other controller selected as secondary controller works fine.