forums.marpirc.net

Guess this is as good a place to mention one plan I have.

What I'd like to do is possibly produce a version of WolfMAME with many extra features, which would be fixed at a set MAME version, so that work can be focused on that, without having to worry whenever Aaron decides to re-write something. It'd probably all start as just a MAME frontend, probably GTK+ based (for easier compatibility with other OSes), and eventually tie it all together, perhaps even having it all integrated together (a la MAMEUI). I'd probably use no later than 0.116, due to INP playback issues with the re-written Neo Geo driver. None of this would affect the usual WolfMAME release for each major MAME release, either.

This is all still in the fairly distant future, though, I'm still working on MESS for now, and I'd like to get back to my other emulation project that I've neglected for the past 18 months, too.

yeah, I had the automatic off in my ini.

For those CLI and GUI challenged, from the same folder your mame executable is in, find the mame.ini file. Match up these lines...
this makes sure you are always drawing all frames....if you then have speed issues(less than 100%)...then you can increase frameskip value but you definitely want to keep autoframeskip set to 0.

Update to the plan:

I've made a very basic start (early UI design is about it really) to my new frontend.
I think I'll stick with using Visual C# Express and .NET, seeing as I now know that .NET applications can be run on other OSes (albeit, only up to .NET 2.1). It'll make it easier to write than with C++/GTK+, although I'm still learning C#, so it'll probably still be quite some time until anything usable is ready for general use, depending on time and interest. Especially if I suddenly decide to do something daft like write an FM Towns driver for MESS.