> > I'm using Direct3D, but this should still apply. I use a general 'raster' INI for
> > most arcade games and then for consoles I just do each console individually, even
> > though they all have the same settings generally. There aren't too many consoles so
> > this isn't a big deal.
> > MAME definitely should allow for more flexibility though. For example, a way to
> > settings for monochrome monitors, interlaced games, etc. or maybe even some way to
> > make custom categories.
> > The thing about UI design is MAME needs to be highly flexible to handle all the
> > different kinds of games out there. We can't just apply a single CRT shader because
> > not all games use the same type of CRT. Heck many of them don't even use CRTs.
> > never going to be able to have perfect simplicity with a complicated system without
> > sacrificing flexibility.
> I totally get where you're coming from, but 600 files or different persets as Ziggy
> suggests is far from this simplicity explained in one of your points.
> For now until something better is possible, I like having different shader chain
> files which are select-able in real-time. It's the easiest method for me to manage
> due to it's simplicity and versatility.
I don't think you will need 600. There are only a handful of consoles/computers most people need, raster.ini, vector.ini, vector-mono.ini can handle 99.9% of the arcade games you'll play, and then there are maybe a handful of others that are specialized (interlace, hi-res, rear projection). If you are smart about it, it's fine.