[Bug]: 8BitDo Micro - The d-pad options refuse to change when setting up the 8BitDo

[minimoth28]

Contact Details

Discord: @m1nimoth

Did you update to the latest plugin version?

• Updated RemNote

RemNote app version

version 1.22.75

Plugin version

0.4.5

What happened?

I am so sorry for all the edits and reopens and closes. I have truly no idea how this platform works.

The main issue is: when attempting to set controller bindings, all buttons on the 8BitDo Micro are willing to change except the D-pad. The screen got stuck looking as below, but I ended up finding your handy dandy button to reset all keybinds to default (God bless you and all you do. Thank you.) Would be great to be able to use the d-pad though!!

Also keep getting a message in the corner? It doesn't seem to change very much, but screenshotted and included nonetheless. Sorry for the frenzied updates, I feel bad for your email inbox if it's updating you every time I've twiddled with this!! Have a lovely rest of your day xx

SORRY. My last update. I swear. (I hope.) Another bug on here was about edit later which would be GREAT to be able to map, but I can't quite figure out how... would really appreciate your support :-) thankyousomuchsorryforbotheringyoubye

Relevant log output

Code of Conduct

• I agree

[coldenate]

No worries, not a bother at all! (my inbox is all good, GitHub is pretty conservative with notifications so you can edit all you need) I want this plugin to work for everyone, and it definitely needs a touch-up. Thank you for the kind messages!

• D-pad controller bindings not listening
• I will try my best to look into this. I don't own the specific controller you have.
• I may roll out an update with updated logs; I'll ask you to get the controller's D-pad to fail again and then I can take a better look. I'll reach out to you later.
• Sometimes GitHub issues can be annoying for back and forth conversation. Can I reach out to you over Discord, RemNote in-app support (probably the best), or email?
• If you chose Intercom, just send us a message on there and say "Please route me to Nate" + link this thread.
• Message in the corner
• That's the first clue! Make sure your controller is in controller mode. I developed that warning to complain when a controller is unique and not aligning with the general schema defined by the browser's gamepad API.

[minimoth28]

It's lovely to meet you, and thank you for your swift response - definitely relieving to know I haven't spammed your inbox! :-) A note on touch-up - while I agree that I can tell it’s in beta, the NESW buttons worked perfectly on my iPhone, iPad and PC (despite my ineptitude at finding the Omnibar on iPhone), so it’s doing its job!! Even worked during my commute with minimal service, which was cool because I’d seen someone raise that plugins aren’t supported offline.

Controller D-pad: Just let me know and I’m more than happy to do so. I did end up testing all the buttons on the remote via the site on the troubleshooting page, and all the buttons are definitely sending a signal if it helps!

Communication: Yes, of course! I’ll find you through the in-app support, and if I struggle, I’ll update here. (Update 1: All done.)

Controller mode: I’ll try and pair it on the “S” mode for Switch and update here once I’ve done so. It’s currently on “D” for direct input, and I skipped over “K”.

Any advice on the edit later button? Thanks so much!!