> What .diffs ? There aren't any, GM stopped at 0.171 and it's not my fault Calamity > isn't giving any signs of life. > 'be patient people have lives' sure, that's fine we all understand, we can wait. > But prolonged silence isn't right, you have to chime in once in a while to tell > people it's not dead and they'll have to wait more. > > Long silence plus a mamedev coming and and saying there's "no problem" and dropping > the $1000 solution, it's hard not to think the matter has been sidelined. > > Then uman, for someone who's had the build he's contributing to nealy disappear you > should be more understanding. > As for ego please, I've seen you enough bitch on these very forums. > > @anikom15: congratulation on demonstrating you're a cunt.
Why are you crying rivers here? The .diff files are on the very first page of the GroovyMAME thread: http://forum.arcadecontrols.com/index.php/topic,135823.0.html They are like a patch and alter the files of a source. In fact, thats how GroovyMAME is made of. Get familiar with a compiler and create a GroovyMAME 0174 version on your own. There are many tutorials, how to do this, even on this site.
Lets not hope that something bad has happen to Calamity, but you are assuming that the mame-devs are guilty for his absence, which is 100% not the case. I believe that Calamity is more a person, who dont like to speak so much of "coming soon". He is rather someone who do his work silently and surprise people, if things are ready and final.
There are also solutions, that cost at most 50$... buy a CRT or TV . B2K24´s monitor was a example, not a must. He fairly well explained to you, what is a possible cause for tearing in MAME.
Index 
Flat 
Re: Is there any way to effectively reduce screen tearing/flickering?
Reply
. B2K24´s monitor was a example, not a must. He fairly well explained to you, what is a possible cause for tearing in MAME.
