Emuforums.com - View Single Post - LilyPad

**ChickenLiver** · April 9th, 2007

Hmm...That's funky. Are only the labels incorrect? That is, even with the wrong labels, does it still work? LilyPad won't let you bind axes to buttons, so despite the labels, looks like they're all correctly being detected as buttons. Those strings come from Direct Input; I don't generate them myself. If they don't work, could you please tell me which buttons do work (none/only properly labelled ones/etc)?

Another possibility: If you bind controls, then start running the emulator, then escape out, and then bind some more, bad things may happen. I don't think this will cause problems, but it might. If you didn't do that, this is obviously not the issue. If this is the issue, delete all your bindings, restart PCSX2, and rebind everything.

Alternatively, it could be some other issue I'm not thinking about...If this is the case, the buttons don't work correctly when pressed and possibility 2 isn't the issue. If this is the case, I've attached a special version of the dll. Put it in your plugins directory and it will create a file called debug.txt in the PCSX2 directory (You shouldn't have to do anything, just go to the plugin selection screen. I don't think you even have to select the plugin). Compress it and post it here. It just contains a list of all direct input devices, all their buttons/axes/etc, their names, and their types. It will clearly indicate if my first guess is correct, and if it's not, it'll at least give me a better idea of just where things are going wrong.

Edit: Do try the debug dll. It suddenly occurred to me that buttons and axes may be using the same object ids. The dll's output would let me verify that. As I record settings only by object id, and not by type, this would cause issues. I didn't think that sharing ids was permitted when I wrote my code, but it would explain exactly the behavior you're seeing (First 3 axes and first 3 buttons being confused. Not sure why the other one skips two buttons). If this is the case, should be an easy fix, though I'd like to verify it is before trying to fix it.

<Attachment removed, version in first post is more recent>

Last edited by ChickenLiver; April 24th, 2008 at 18:10.. Reason: ancient typo I just noticed

April 9th, 2007	#5 (permalink)
ChickenLiver Plugin author Join Date: Apr 2006 Location: Perdition Posts: 588	Hmm...That's funky. Are only the labels incorrect? That is, even with the wrong labels, does it still work? LilyPad won't let you bind axes to buttons, so despite the labels, looks like they're all correctly being detected as buttons. Those strings come from Direct Input; I don't generate them myself. If they don't work, could you please tell me which buttons do work (none/only properly labelled ones/etc)? Another possibility: If you bind controls, then start running the emulator, then escape out, and then bind some more, bad things may happen. I don't think this will cause problems, but it might. If you didn't do that, this is obviously not the issue. If this is the issue, delete all your bindings, restart PCSX2, and rebind everything. Alternatively, it could be some other issue I'm not thinking about...If this is the case, the buttons don't work correctly when pressed and possibility 2 isn't the issue. If this is the case, I've attached a special version of the dll. Put it in your plugins directory and it will create a file called debug.txt in the PCSX2 directory (You shouldn't have to do anything, just go to the plugin selection screen. I don't think you even have to select the plugin). Compress it and post it here. It just contains a list of all direct input devices, all their buttons/axes/etc, their names, and their types. It will clearly indicate if my first guess is correct, and if it's not, it'll at least give me a better idea of just where things are going wrong. Edit: Do try the debug dll. It suddenly occurred to me that buttons and axes may be using the same object ids. The dll's output would let me verify that. As I record settings only by object id, and not by type, this would cause issues. I didn't think that sharing ids was permitted when I wrote my code, but it would explain exactly the behavior you're seeing (First 3 axes and first 3 buttons being confused. Not sure why the other one skips two buttons). If this is the case, should be an easy fix, though I'd like to verify it is before trying to fix it. <Attachment removed, version in first post is more recent> Last edited by ChickenLiver; April 24th, 2008 at 18:10.. Reason: ancient typo I just noticed