Problem dpad

[Anths2016]

Don't works configuring dpad "right". I can't get it to fit when I reconfigure the keys.

[npwoods]

Any chance you could be more specific? What device are you trying to configure? Which MAME drivers and which input are you trying to configure?

My trusty Microsoft Sidewider Wingman from 10 years ago has a d-pad, and it worked for me, but its not surprising that someone may have problems with something else.

[Anths2016]

Everything works, except the "right" button on the dpad. I use the Hori Fighting commander.

[npwoods]

This is going to be obnoxious to diagnose, because I suspect that while there is likely a legitimate bug in play, without access to that hardware I can't debug it.

I'm assuming that you can successfully configure this device in normal MAME?

Also, if you're brave it would be helpful if you could try running MAME in a standalone fashion, but with the "worker_ui" LUA plugin that is used to interface with BletchMAME. You should be able to do this with the command line mame64 xyz -plugin worker_ui once you have paths set up.

When you run it, you will see a packet of XML that is used to emit information into BletchMAME, looking like this:
https://imgur.com/a/X08AAja

If you could find the section pertaining to your controller and paste it here, it would help.

[Anths2016]

I can't. This is my setup, anyway ... :
https://imgur.com/rZPuPnp

[npwoods]

I'm not sure how to proceed here. We're piggybacking off of MAME, and if you can't successfully reconfigure this device in normal MAME, there probably isn't anything that BletchMAME can do.

That said, I can envision a type of error that happens with the BletchMAME integration, in which case I'd need to see the XML that the worker_ui LUA plugin returns.

[Anths2016]

https://imgur.com/OAqtswh

[npwoods]

Looking at this, I see all of the other DPAD directions (Up/Down/Left) but not Right.

Based on what I'm seeing I would expect normal MAME to not recognize the DPAD Right button. Is that the case? If so, this should be reported as a normal MAME issue.

[Anths2016]

No, Mame sees it.

https://imgur.com/K5fIVNr

[npwoods]

Interesting.

If I saw this on my machine, my next step would be to debug MAME itself. Is this something that (by any chance) is an option for you? I'm assuming not but I may as well ask.

[Anths2016]

Help!! libwinpthread-1.dll was not found Il domenica 29 novembre 2020, 14:37:24 CET, npwoods ***@***.***> ha scritto: Interesting. If I saw this on my machine, my next step would be to debug MAME itself. Is this something that (by any chance) is an option for you? I'm assuming not but I may as well ask. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[Anths2016]

Il domenica 29 novembre 2020, 14:37:24 CET, npwoods ***@***.***> ha scritto: Interesting. If I saw this on my machine, my next step would be to debug MAME itself. Is this something that (by any chance) is an option for you? I'm assuming not but I may as well ask. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[npwoods]

Ugh this is a stupid oversight. I put a lot of effort into cutting down on unnecessary dependencies. Something tells me that BletchMAME 2.8 is coming out soon :-|