Quote:
Originally Posted by smf
MAME gets alot of critisism because it's fashionable & some because we don't implement every thing the users want.
What we see as worth supporting or not changes over time. Hiscore.dat got removed because even though everyone was told on mametesters that they shouldn't submit a bug report if they used it, there were a large number of people who kept "forgetting" and would submit bug reports that were specifically caused by it.
Overclocking/underclocking is there so users can try more correct cpu speeds without having to recompile and then feed back if they improve the emulation. If enough bugs were caused by it then I imagine it would get the boot too.
Cheating & save states are useful for testing.
Artwork is about preservation.
Scanlines is about trying to make it look more accurate on modern monitors. It's arguable whether the result is worthwhile.
Optimisations are always nice as they allow us to test games without having to wait for days for each screen refresh. Where speedups are proven to cause accuracy issues then they are removed (like in st-v).
For something to be added to MAME, you first need someone to care about doing it. Then they need to do it, then they need to get it passed other people on the MAME team. Sometimes ideas are abandoned, other times they are improved and expanded upon. But on most technical issues, what the users will think is generally not considered. Just take it as a side effect if it looks like we do.
|
Just a question. (this isn't meant as an insult in any way)
Rather than take the "Giving up" approach of just removing something if it doesn't work, why not keep at it until it works right?
I know some things may just never work as intended and maybe even be impossible to incorporate into your current system, however, I highly doubt that rule applys to everything though.
I know that sounded like an insult but it was the only way I could describe it while keeping my point.