Software Support > PowerMAME
PowerMAME - New Derivative Build
Silver:
Outstanding idea. Good for you for going for it. There is already a bunch of tweaks/additions out there that people may wish to have added (author permitting of course).
One suggestion/though that I'm sure you already have covered - do you plan to set out a form of 'rules' or guidelines for what you do or don't want to include? such as will you just want to add 'extra' features like led-whiz support based around inputs or do you want any additions to mame?
MikeQ:
I think we will look at all suggestions and the prioritize them based on feedback from the community. It seems right now a hot topic is fixing broken controls so that will probably be where we start. Something I'd also like to see get looked at is adding the "save state" stuff that Aaron wants. He hinted that we will lose hiscores.dat at some point and if someone implements "save state", then this will give us a better and permanent solution. But no, I don't think we will rule out any change. I think the MAMEdevs goal should be to document and lay down the framework. Our goal should be to make things more playable and more interesting. We should also make it more product like. For instance with the LED-WIZ stuff, the code will be their to support and LED-WIZ but if and LED-WIZ isn't found when Power**** is run, then it won't be used. We won't expect the user to set something in a makefile and recompile.
Tiger-Heli:
First, if official MAME loses hiscore.dat, we could still keep it in PowerMAME - but then you get into who is going to maintain the .dat file once official MAME abandons it.
Silver also has a valid point on coming up with guidelines for what will/won't be accepted. One example I can think of is coin counters - I think Youki added it to Atomic. Lots of people on here might like it in at least the MAME32 version - but the devs definitely don't like it, because it could be most likely used in a for-profit arcade cab environment. And incorporating that MIGHT jeopardize the usage of PowerM*** in the name. FWIW. . .
MikeQ:
--- Quote from: Tiger-Heli on February 02, 2006, 04:54:40 pm ---First, if official MAME loses hiscore.dat, we could still keep it in PowerMAME - but then you get into who is going to maintain the .dat file once official MAME abandons it.
Silver also has a valid point on coming up with guidelines for what will/won't be accepted. One example I can think of is coin counters - I think Youki added it to Atomic. Lots of people on here might like it in at least the MAME32 version - but the devs definitely don't like it, because it could be most likely used in a for-profit arcade cab environment. And incorporating that MIGHT jeopardize the usage of PowerM*** in the name. FWIW. . .
--- End quote ---
True about the coin counters. I don't know that we need a bunch of guidelines but surely if it pisses of the MAMEdevs, it probably shouldn't be considered. One of the goals of this little experiment is to try to build a better dialog with them anyway. However if it seems like we are just banging our heads into a wall everytime we interface with them, we might have to rethink that goal. We will just have to see.
Crazy Cooter:
What I'd like to see (and hopefully be able to contribute... I have this burning desire to get deeper in the code :'()
1) Easy compatibility with a FE.
2) Controls for playability with integrated CP viewer/Johnny/whatever stuff.
3) Bells & whistles - LED stuff.
I'd say the only rule would be to maintain the program well within the guidelines set by the mamedevs. The three things I listed is enough to keep an army busy for quite some time, no need to push the interpretation of the EULA for MAME. AFAIK, the controls project still needs info, and a FE still needs to integrate the pause/controls functions. But I've been kind of asleep for a bit on another project, so maybe it's easier than I think.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version