Software Support > PowerMAME

PowerMAME - New Derivative Build

(1/45) > >>

RobotronNut:
(I'm belatedly renaming this thread, to reflect the bulk of the discussion...)


--- Quote from: Xiaou2 on February 01, 2006, 06:12:26 am ---I dont think it would be a problem to allow more than one way to set up a driver.  For example, to allow the current method of shifting, and adding an optional method which mimmics the arcade hardware with constant hold down.

The problem mostly lies is submissions.  Nobody seems to know how to write code that the mame devs consider clean enough to be [acccepted]..  at least, thats how it appears to me.

--- End quote ---

this is an interesting new perspective on the discussions of the last few days. it struck me as oddly bureaucratic of the MAMEdevs to be so resistant to supporting multiple input devices, even in some cases controls that allow the games to be played as they were in the original arcade machine, even if the code is conditionally compiled and not in their official builds.

is the real issue merely good software design?

would any MAMEdevs listening in care to comment on this?

Tiger-Heli:
How many threads do you plan to start on the same subject?  (I think this makes #4).

Silver:
If you want to speak to mamedevs or get them to comment, IMHO, you need to go to mame.net forums or mamedev.org.

This is not the best place to speak to mamedev...

RobotronNut:
well, in my previous threads, i was trying to work out specific solutions to specific problems for the mame system i'm constructing, but they all seemed to end up in the MAMEdev vs. arcade control discussion. even when i've said, "can we get back to the subject i originally asked about," everyone seems mainly to want to talk about this subject.

this is obviously a huge sore spot, of which i was unaware, since i'm a new-comer to arcade emulation.  however, i do have something to say about good software design. i've been passionate about good, clean C code for decades, since i worked on the Unix kernel at Bell Labs in the late 70's and led teams designing large system software projects in the 80's and 90's.

if the MAMEdevs' main concerns are NOT an unwillingness to allow arcade control support into the core MAME code, but simply a resistance to what they consider poor implementations of that support, then maybe we can make everybody happy by submitting modest, "squeaky clean" changes which, over time, bring in support for most of the devices we care about, while keeping mame clean and maintainable.

Flinkly:
the problem with mamedevs is that they (seem to) care about documenting these old games and not making them playable on your computer.

while the argument stands that you should be able to use the original controls, most of us are plugging our controls into interfaces, then to the computer, so it's not like your pluging your controller straight to the computer where mame grabs that raw info and uses it to control the game. 

we are all sending interfaces our raw info, and they turn it into windows stuff(keypresses, mice, etc) and then windows passes it to mame who has to decode and then the game re-encodes it in your game.

Navigation

[0] Message Index

[#] Next page