Pressing it again releases the old pad state, if the old pad state had any keys pressed. "Local volume control" uses Vista's per-app volume control to use volume control keyboard buttons or wheels to affect PCSX2's volume only. The default is high enough that relative axes (which are primarily used by mice) are generally either considered fully up or down. Some PSX emulators (At least PSXeven) require pad plugins to be named pad*.dll. Sensitivity sets how hard an axis or button is pressed. Shouldn't cause any issues in game, and crashing behavior should be consistent (either always does or never does).

You do not have to configure ignored keys again when you change the keyboard input mode. The slider sets the force used when an effect is triggered. Other devices (game devices, certain extended keyboard keys, etc) are only available through DirectInput, except Xbox controllers, which can work through XInput as well.

There's no reasonable workaround I can do for this, unless I learn how to convince GH2 I'm really a guitar. Even after enabling lilypad … Those of you using an Xbox 360 controller will need to select 'Xinput'. Not all games like the pad disabling code, no clue why. "Allow binding multiple PS2 controls to one PC control" is pretty self-explanatory. Allows one control to be bound to multiple commands. Note that though the binding appears on the page of a particular pad, pressing the button affects all mice. For other devices, to get some motors to work, previous motors much be disabled for that force. Pressing "Lock Input" when only half the input is locked (directions or buttons) will lock the other half, leaving the already locked half still locked, and in its old locked state. Any misattribution is accidental and largely due to there not being a First two motors are automatically enabled for any effect, only up to 6 motors will be displayed. Note that the small motor is only either off or on at max, while the big motor's vibration can be set from 0 to 255. It was implemented primarily to prevent passing F7 to the GS plugin, which I occasionally hit when playing with graphics options and can cause PCSX2 to crash. Multiple keys/buttons/axes can be bound to the same PS2 button, and one key/button/axis can be bound to multiple PS2 buttons. Note that you must start the game with the checkbox selected. Devices not currently enabled in the API selection list at the top are not displayed. First thing I did was load PCSX2 1.4 and connect my Xbox one controller via USB to it like I did my desktop.

Lilypad and Xbox One Controller. Vsync can cause PCSX2 to run ahead of the GS, so it appears input is lagged when it's actually the GS that's behind. This is handy for the lazy, who don't want to have to hit the analog button whenever they start the emulator for games that support but do not automatically enable analog mode, and for loading states in games that get upset when you load a state before the pad is initialized.

I want to play Gears of War 2 with an Xbox 360 controller in pcsx2. As a result, attempting to close the window while the emulator is not actively running still isn't a great idea. I don't know how to convince it I'm a real guitar. The "Lock Input" button locks the current state of the pad.

If you really need to use two different pad plugins for some reason, and one is LilyPad, disable LilyPad's keyboard handling so that the F-keys, used to control the emulator, don't behave as if you always press them twice. May be removed in a future version, as it's no longer too useful. I'm still waiting for a response to issue I thought the Kung Fu Panda issue was fixed ?