> > > http://mamedev.emulab.it/etabeta/2016/06/06/time-is-ticking-out/
> >
> > This is so rad.
> >
> > Is the Xbox 360 Windows Pad's rumble implementation... considered non-standard? I
> > mean, the rumble bit could potentially be added to MAME, but I know that's
> > pad-specific, so I don't know if it's actually... you know, feasible. Especially
> > considering non-MS pad manufacturers don't get it to work the same way as the
> > original one does.)
>
> current approach is to let 3rd party applications to take care of redirecting the
> output to the appropriate controllers, so that OS-specific applications can exploit
> the corresponding APIs.
> right now, MAME output is being reworked so that this is probably not the best moment
> to tackle such a task, but the idea is that an external program shall listen for the
> output and redirect it to the controller...
Hm ok, but the only such external program I'm aware of is Windows-only, cumbersome to use, supports a limited set of MAME drivers since each needs to be individually added, and hasn't been updated in years. I realize SDL2 isn't the greatest API, but from what I understand it would at least allow for such functionality to be added directly to MAME in a platform-independent way without the need for such extra software.
I recall this being discussed as a long-term goal a while ago - has this changed, or is that what you mean by "MAME output is being reworked?" MAME's direct support for rumble/ff has been a hope since OutRun was added to MAME back in the .3X days, and was only realistic since the recent update from SDL1 > SDL2, or so I had thought..
Anyway, what you are doing with the GBA is really cool regardless, certainly a nice surprise to catch all the new developments there. 
|
Index 
Flat 
Re: etabeta: Time is ticking out…
Reply
