MAME mapdevice support for multicades?

[megashub]

I have a lot of different controllers, mice, joysticks, spinners, etc built into my multicade arcade cabinet. Those are in addition to the digital pinball plunger (zebsboards in my case) with its associated buttons.

I'm noting that motion from my analog joysticks (Ultimarc Ultrastik 360s) are being interpreted by pinmame as nudges. So, I need a way to only map devices to pinmame that I want it to listen to, and ignore the rest. In normal standalone MAME, this is accomplished easily by creating a custom ctrlr file with explicit mapdevice parameters.

I see no reference to this same capability in pinmame.

see also: https://docs.mamedev.org/advanced/devicemap.html

Does it exist and I just didn't find the right KBs? If it doesn't exist, can it please be added as a feature enhancement request?

[wiesshund]

You would do it through VPX as far as changing/adjusting the controls And i think you want the zebs board tagged as controller 1 in windows

[megashub]

You would do it through VPX as far as changing/adjusting the controls

Why though? Why wouldn't you want to do it the same as MAME does it? No sense reinventing the wheel, is there?

And i think you want the zebs board tagged as controller 1 in windows

Please elaborate further.

[wiesshund]

MAME is MAME VpinMAME is a helper app, VpinballX is the controlling app VpinMAME does what ever VPX says, how ever VPX says, regardless of what you set in VpinMAME i can set VpinMAME to use some other control for a function, and it will proceed to absolutely ignore it when VPX is running because VPX tells it otherwise, the VPX prefs and through VPMKeys.vbs

Windows Control Panel Devices and Printers Zebs controller Advanced

http://images.akamai.steamusercontent.com/ugc/578993823828898331/C54A459E2664171039B9E91C1CB0D2B33C24E1EB/

[megashub]

MAME is MAME VpinMAME is a helper app, VpinballX is the controlling app VpinMAME does what ever VPX says, how ever VPX says, regardless of what you set in VpinMAME i can set VpinMAME to use some other control for a function, and it will proceed to absolutely ignore it when VPX is running because VPX tells it otherwise, the VPX prefs and through VPMKeys.vbs

Thanks. This is helpful detail. In that case, I need a way to only map devices to VPX that I want it to listen to, and ignore the rest. In normal standalone MAME, this is accomplished easily by creating a custom ctrlr file with explicit mapdevice parameters. How is this accomplished in VPX? If it can't be done today, is there a code repo or feature request queue I can submit this to?

Windows Control Panel Devices and Printers Zebs controller Advanced http://images.akamai.steamusercontent.com/ugc/578993823828898331/C54A459E2664171039B9E91C1CB0D2B33C24E1EB/

Thanks. I'll try this. How does making this change modify VPX's behavior?

[wiesshund]

I am not sure if that 100% made sense? MAME is the app in that when you run mAME, you run MAME, you interact with MAME directly PinMAME only functions as a controller app and you interact with VPX

To the best of my knowledge VPX only looks at controller 1 If i plug in 4 gamepads, VPX only responds to the one designated as controller 1 MAME will respond to any valid controller on any ID, which is normal considering a 4 player cab is most likely 4 controllers with players 3 and 4 probably being simple encoders and players 1 and 2 being 1 or more controllers depending on spinner and trackball set up etc, plus say a steering wheel controller or anything else one might plug into a cab

PinMAME will probably technically respond to anything but since VPX actually handles and interprets what is going on it kind of becomes moot.

[droscoe]

Considering the age of this request, I recommend either assigning a status for future work, or closing it.

[wiesshund]

It can be closed. The request was mistakenly put in VPinMAME github, but should have been put in VpinballX section instead as the feature is required of VPX, not VpinMAME

[droscoe]

It can be closed. The request was mistakenly put in VPinMAME github, but should have been put in VpinballX section instead as the feature is required of VPX, not VpinMAME

That's cool. I had closed one that I opened, and he said it wasn't really a big deal to have these remain open anyway. Disregard.

[toxieainc]

Related to #67 and #140