Closed pablopsw closed 1 year ago
I have the same problem, I was on 1.8.3, I updated to 1.8.4 and it still doesn't work.
I've tried this now, to confirm. It's weird, but yeah it doesn't work.
I used the gc-controller-test app and it all looks right there, with merged triggers. I can't tell the difference in that app between wired gc controller and bluetooth one.
So I tested this myself in v1.8.4 with PS5, PS4, PS3 and Switch controllers. I had the merged trigger preset loaded and I was able to dash with R and also Slam the ground with A then R.
Can you guys run homebrew?
If so run this https://github.com/corenting/GC-Controller-Test/releases/tag/v1.2
and take a picture while you hold R to maximum and post here. I want to see the analog value.
It's the only game that happens to me. Thanks for your time.
@pablopsw base on screenshot of first post you don't have the merge trigger preset that the gamecube end trigger require.
With that preset the L & R end button will get pressed when the analog value reach >= 197
It worked! I needed to read a little more, thank you for answering me and solving the problem.
Closing as original author problem is fixed, but @kirimui & @rattboi feel free to post your analog value and screenshot of mapping.
BlueRetro firmware version
v1.8.4
BlueRetro firmware specification
HW1
BlueRetro firmware variant
System specific
BlueRetro hardware type
Internal install DIY
Manufacturer
Myself
System used
Nintendo GameCube
Bluetooth controller brand & name
Original Dualshock 3 and 4 controller
What is problem? (only list ONE problem per report)
R trigger does not work in gamecube game Wario World, I tried different settings in advanced settings, placing R trigger on other buttons and the problem persists.
What did you expect to happen?
that the trigger R worked
Attach files like logs or Bluetooth traces here
https://github.com/darthcloud/BlueRetro/assets/75383650/f4bd35ab-623d-41fb-8a48-67efabac34c0