[MCPE-19712] R2 Trigger on Mi Pad doesn't work Created: 12/Jan/17  Updated: 15/May/17  Resolved: 15/May/17

Status: Resolved
Project: Minecraft (Bedrock codebase)
Component/s: None
Affects Version/s: 1.0.0, 1.0.2
Fix Version/s: None

Type: Bug
Reporter: Martin Gunther
Resolution: Duplicate Votes: 0
Labels: None

Attachments: PNG File Screenshot_20170112-125501.png    
Issue Links:
Duplicate
duplicates MCPE-14363 R2 button on a gamepad doesn't work Resolved
Confirmation Status: Unconfirmed
Platform: Phone - Android - Samsung Other (Specify in description)

 Description   

Galaxy S7 Edge phone.

This is a duplicate of MCPE-14363 and MCPE-13494 (and others linked), but I couldn't see how to re open it. So starting a new one for version 1. Just received a Xiaomi Mi Bluetooth Wireless Gamepad and it works brilliantly with MCPE, other than the R2 button. I assume it's meant to be "Trigger2" as a MCPE button. All other buttons, and sticks work, and the button works fine in other games, and the Bluetooh testing apps on Android.

It's sooo close to being lovely, and wanted to buy the Gear VR edition to use this with, but this button is kind of essential (well not, but it does take away from a very natural button to use to place/attack/destroy).

Thanks

Update: Still affects new 1.0.2 on Android. Really frustrating as it's such a useful button for attack when moving (using the front right button instead of trigger for the moment, but then can only scroll through to the left!)



 Comments   
Comment by [MCPE Mod] Celesian [ 15/May/17 ]

I have reopened MCPE-14363.

Comment by Martin Gunther [ 12/Jan/17 ]

That makes no sense? "Click tap right in list"? I can re assign buttons reset them etc. The trigger works perfectly in other games I've tried but it just doesn't register in mcpe? The default for attack destroy is trigger 2 but I cant assign it and it does nothing in game?

Comment by callumokane [ 12/Jan/17 ]

Open minecraft and select options,
Go to controller settings and click tap right trigger on list not controller,
then click the trigger on controller and it should work perfectly then!

Comment by Martin Gunther [ 12/Jan/17 ]

Screenshot of the affected button working in Bluetooth Gamepad tester

Comment by Martin Gunther [ 12/Jan/17 ]

Oh did want to add, that the button is reported in the Bluetooth testing app as key "313 BUTTON_R2 Key code 105".

We also have
key 310 BUTTON_L1 KC 102
key 311 BUTTON_R1 KC 103
key 312 BUTTON_L2 KC 104
key 312 BUTTON_THUMBL KC 106

All the other keys work, so shame 313/105 doesnt. Have attached screenshot of that app with the keycodes it's 105 that doesn't (highlighted)

Generated at Sat Jan 11 15:24:17 UTC 2025 using Jira 9.12.2#9120002-sha1:301bf498dd45d800842af0b84230f1bb58606c13.