Emulator Issues #10029
closed
Can't L-target to strafe in Metroid Prime 1
0%
Description
Game Name?
[Metroid Prime]
Game ID?
[GM8E01]
MD5 Hash?
[737cbfe7230af3df047323a3185d7e57]
Playing Metroid Prime on GC, you have two functions for the L-trigger: the first will lock onto enemies (and scan them if the scan visor is enabled) and allow you to circle-strafe around them. This function works fine on Dolphin. The second function allows you to strafe without any enemies nearby. This is what's not working. It seems like it will only work sometimes, and I can't figure out what the conditions are for it to work. I'm using an official Xbox 360 controller, and I tied the strafe function (L-Analog) to the L-shoulder button (separate from the lock on function, which is still tied to L-shoulder), and that works. Binding both two the L-shoulder makes only enemy lock ons work, and strafing NEVER work. This leads me to believe that it's an issue with combining the "L" and "L-Analog" functions into one button.
I'm using Dolphin 5.0, and after doing some cursory research, it seems this problem was an issue in the past, but not on some versions of Dolphin.
I'm running Windows 7 Home Premium 64-bit with an intel i5-3470 CPU and a GTX 1070 GPU (full system information in screenshots).
This is the controller config where strafing only works sometimes (both binded to L-trigger): https://i.imgur.com/I6clZsB.png
This is the controller config where the strafing works, but is binded to a separate key: https://i.imgur.com/3Wbktfv.png
This is the controller config where strafing does not work, but lock on does (both binded to L-shoulder): https://i.imgur.com/2zzDqsb.png
This is my full system configuration: https://i.imgur.com/wqIYAY1.png
Updated by MayImilae over 8 years ago
- Status changed from New to Working as intended
The GameCube has the analog input then a digital click. Metroid Prime expects this - if the digital click and analog signal are activated at the same time (such as they are bound to the same analog axis of a 360 controller), then it will ignore the digital click.
This is a difference with how current controllers work versus how the GameCube controller works. There is nothing we can do about it, and you are already using the workaround we recommend to people (mapping the analog and digital trigger presses to separate keys). The only way to this properly is to have a controller with an analog trigger which then clicks a digital button when fully depressed. It works perfectly fine on the Steam controller or native GameCube controller!
Anyway, this is well known, and you are already doing the work around. There's nothing we can do.