Build Your Own Arcade Controls Forum

Main => Software Forum => Topic started by: wallywalt on May 15, 2006, 01:08:30 am

Title: mame vs mame32 issues
Post by: wallywalt on May 15, 2006, 01:08:30 am
I thought they were basically the same when running roms, maybe it is my front end? Certain games will not load with mame, using mamewah frontend but will run using mame32.  Also other games run much faster in mame32 than when running mame.  Killer instinct for example runs smooth with mame32 but is very choppy in mame.  Any ideas on why certain roms wont load with one but will with the other, and speed issues?
Title: Re: mame vs mame32 issues
Post by: Pi on May 15, 2006, 03:31:15 am
They behave the same only if 1) you're using the exact same version, and 2) they have exactly the same settings. The second is harder than you'd say, because MAME32 has a few defaults different than vanilla MAME. Autoframeskip is disabled by default in one of them, as well as RDTSC (or whatever the spelling is). RDTSC affects performance on all games, it should be toggled to see which setting works for you. For some computers, RDTSC doesn't work. Autoframeskip should be disabled in framebuffer-based games like KI to avoid choppy performance.

About games not loading in one, it's either a rom path configuration issue (again, you should use the same configuration), or you're not using the exact same version.
Title: Re: mame vs mame32 issues
Post by: wallywalt on May 15, 2006, 04:35:17 am
autoframeskip turned off helped a ton, but i can't seem to find the RDTSC setting you talk of.  What category is it under in the .ini? Still working on why certain games won't work, its mainly 1 game...marvel vs capcom won't work in mame while it runs fine in mame32. I'm gonna keep tinkering to see if i can get it up.
Title: Re: mame vs mame32 issues
Post by: Minwah on May 15, 2006, 05:12:38 am
autoframeskip turned off helped a ton, but i can't seem to find the RDTSC setting you talk of.  What category is it under in the .ini?

It is under 'windows misc options' (between 'sleep' and 'high_priority').

On the subject make sure you set 'sleep 0' and 'high_priority 1'.
Title: Re: mame vs mame32 issues
Post by: Pi on May 15, 2006, 05:18:04 am
I wouldn't really advice to turn on high_priority. If you have other things running, then you want them running, or you'd close them before playing MAME. MAME with high_priority on will make those things crawl, so it will do no good to them. Even with old games, MAME is really an application which wants the puter exclusively for itself.

About the problem you have with Marvel vs. Capcom, "won't work" is not a problem we could help you with. Try to be more specific and we could actually provide you with a solution.
Title: Re: mame vs mame32 issues
Post by: Minwah on May 15, 2006, 11:37:49 am
I wouldn't really advice to turn on high_priority. If you have other things running, then you want them running, or you'd close them before playing MAME. MAME with high_priority on will make those things crawl, so it will do no good to them. Even with old games, MAME is really an application which wants the puter exclusively for itself.

In a cabinet though, most people don't want other stuff running so it is generally ok to do this IMO.
Title: Re: mame vs mame32 issues
Post by: Pi on May 15, 2006, 12:40:34 pm
But if you don't have other things running, why would you want high priority ;D

Now seriously, SMF mentioned a couple of times that he added high_priority to fix some problems with certain laptops or similar stuff. I really see no reason to have it high_priority.
Title: Re: mame vs mame32 issues
Post by: Minwah on May 16, 2006, 04:40:06 am
But if you don't have other things running, why would you want high priority ;D

Now seriously, SMF mentioned a couple of times that he added high_priority to fix some problems with certain laptops or similar stuff. I really see no reason to have it high_priority.

Good point...but I suppose it doesn't do any harm either.  To be honest I'm sure there isn't any noticable speed difference, I just it like that anyway.