Main > Main Forum
MAME causing monitor to go whacky
codeena:
Hey mvolke1,
Have you tried unchecking the "triple buffering" if checked? How about lowering resolution? Choosing a lower sound sample rate? Using Direct Draw and not Direct3D? Have you tried scanlines ir adjusting the frame rate settings? Just throwing out idears that I've tried. Good luck!
TOK:
The sound stutters are a classic symptom of the processor being too slow. You said you're running MAME32, but what actual revision?
I'd also add the RAM to your system, but the first thing I'd do is go backwards on the MAME revision. Version .99 had support for Golden Tee and was a lot more streamlined than current builds. If you're willing to ditch the Golden Tee support, or run two builds of MAME, you can go back even further.
I stopped at .99 because the .1 and later builds of MAME haven't added anything I need and have also really ramped up the system requirements as well as messing up some of the older games. I think it's become pretty common for people to use the oldest version of MAME they can get away with.
RayB:
RAM isn't going to do jack-all here. 128 is PLENTY for the kinds of games that a 1.0 ghz system is able to play (ie: mid-90's and earlier-- NO CHD games, NO 3D)
I'd recommend ditching MAME32 and using Windows command line version, in order to get best performance (or even DOS), and he'll have to turn off special graphics filters (scanlines etc).
For my 1.0 system, I use DOS mame 0.78 (though Windows command line version seems to run just as fast, without the need to set up sound and mouse drivers)
Havok:
Yup - your Mame version is the problem. Go with a pre 100 build, although if you are a Phoenix fan, you need 104: they finally got the sound almost perfect...
mvolke1:
Thanks for the advice, gents. I'm going to try it out and let you know how it goes. I think I'll try .99 first, and go from there.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version