> > Are you going to add support for console stuff or are you actively trying to avoid > > that? > > I'm considering the option to enable "old MESS" stuff. Not because I'm afraid of not > being able to continue to call my derivative version MAME, but simply because there's > an increasing request about it. Though, and this is for clarify one time for all, > there will be no software lists support directly from the GUI. You will be able to > select C64 PAL and then you'll have to use the Internal MAME Interface (TAB key) to > setup the machine and load a game from, for example, a D64 image. > > Or, last option, I could stop releasing my build forever and continue to live happy. > My users base doesn't use MAME for play (this is only an example) C64 games. They use > VICE. I verified this a lot of times. Though, as I already said, I'm seriously > ponderating what could be the best choice.
C64 is a poor example as the driver isn't very good, but an increasing number of people are using MAME for common systems where our emulation is 'good enough' for them (even if we're not best in field)
From the dev point of view the problem is that we advertise MAME as having x new features or improvement to driver y, people download a version of MAME and can't find them because they ended up downloading UIFX which has half the content missing. UIFX doesn't really represent where MAME is going, hence what I said about use of the trademark.
It also doesn't work in your favor, as once they find out they end up ditching UIFX.
I do hope that the various plans discussed for filters end up turning out as well as they sound on paper, as you could ship a 'default.lua' filter for your build that hides anything that has no coin slots / has no screen by default and get a list similar to what your users would be expecting, but without crippling the build (they could disable the filter if they wanted and have full functionality back)
|