+- Dolphin, the GameCube and Wii emulator - Forums (https://forums.dolphin-emu.org)
+-- Forum: Dolphin Emulator Discussion and Support (https://forums.dolphin-emu.org/Forum-dolphin-emulator-discussion-and-support)
+--- Forum: Controllers (https://forums.dolphin-emu.org/Forum-controllers)
+--- Thread: GCPad R and L button issues? (/Thread-gcpad-r-and-l-button-issues)
GCPad R and L button issues? - ajko - 04-21-2012
For some reason, every game I load onto Dolphin won't let my Xbox360 controller pick up the "click" that is on the GC controller. For example, I cannot strafe manually in Metroid Prime 1 or 2, and I have issues with some AR codes that require these buttons to be fully pressed. Is there something I am doing wrong?
RE: GCPad R and L button issues? - AnyOldName3 - 04-21-2012
(04-21-2012, 02:18 PM)ajko Wrote: For some reason, every game I load onto Dolphin won't let my Xbox360 controller pick up the "click" that is on the GC controller. For example, I cannot strafe manually in Metroid Prime 1 or 2, and I have issues with some AR codes that require these buttons to be fully pressed. Is there something I am doing wrong?
Just use this general purpose profile. It should work for anything. Paste it into notepad, then changed the extension to .ini when saving it, and put it in user/config/profiles/gcpad.
[Profile]
Device = XInput/0/Gamepad
Buttons/A = Button A
Buttons/B = Button X
Buttons/X = Button B
Buttons/Y = Button Y
Buttons/Z = Shoulder R
Buttons/Start = Start
Main Stick/Up = Left Y+
Main Stick/Down = Left Y-
Main Stick/Left = Left X-
Main Stick/Right = Left X+
Main Stick/Modifier = LSHIFT
Main Stick/Modifier/Range = 50.000000
C-Stick/Up = Right Y+
C-Stick/Down = Right Y-
C-Stick/Left = Right X-
C-Stick/Right = Right X+
C-Stick/Modifier = LCONTROL
C-Stick/Modifier/Range = 50.000000
Triggers/L = Shoulder L
Triggers/L-Analog = Trigger L
Triggers/R-Analog = Trigger R
Rumble/Motor = Motor L|Motor R
Rumble/Motor/Range = 96.000000
D-Pad/Up = Pad N
D-Pad/Down = Pad S
D-Pad/Left = Pad W
D-Pad/Right = Pad E
RE: GCPad R and L button issues? - Billiard26 - 04-22-2012
I would recommend not using AnyOldName3's config, it looks bad (no offense). It does not appear to map either trigger in a sane manner.
ajko, You will most likely want Both L and L-Analog set to your 360 controller's left trigger. (the same for R/R-Analog and the right trigger)
(I think this has been asked/answered on the forums many times.)
RE: GCPad R and L button issues? - AnyOldName3 - 04-22-2012
I'm wondering if you own an XBox controller, or have seen one, or even would be able to tell one apart from a brick. The analogue triggers on the XBox pad have been mapped to the analogue triggers on the GameCube pad, and the left bumper on the XBox pad, which doesn't have an equivalent button on the GameCube pad has been paired with the digital representation of the left analogue trigger. The only potential issue is that I could have paired the stick modifiers on the GC pad to the stick clicks on the XBox pad. The reason why I don't have the non analogue version of the triggers set to the analogue triggers is that it decides that the triggers are in all the way as soon as they are in 1% of the way if you set it up like that, defeating the object of having analogue triggers.
RE: GCPad R and L button issues? - Jimmy Smits - 04-22-2012
I had the same problem with my X360 controller. Billiard26's solution worked perfectly.
RE: GCPad R and L button issues? - Billiard26 - 04-22-2012
(04-22-2012, 08:12 AM)AnyOldName3 Wrote: The reason why I don't have the non analogue version of the triggers set to the analogue triggers is that it decides that the triggers are in all the way as soon as they are in 1% of the way if you set it up like that
No it doesn't. That "1%" is controlled by the threshold setting which is 90% by default.
RE: GCPad R and L button issues? - AnyOldName3 - 04-22-2012
I haven't changed it, but that's what it does. Maybe I'll manually have to do that, but I've never had any issue with it as it is.
RE: GCPad R and L button issues? - ajko - 04-23-2012
Thanks guys, ironically, as soon as I posted this I found the issue. Apparently, having the threshold on 0 disables the "click" function. I bumped it up to 90, it works fine now.