The NEW Build Your Own Arcade Controls
Main => Software Forum => Topic started by: ncflagg on February 07, 2023, 02:03:47 pm
-
Looking for recommendations for specific emulator versions to run Killer Instinct. What is working for you? I don't mind running an older build as long as it runs well.
I'm building a fighter cab:
- CRT screen
- Windows 7 x64 & CRT EmuDriver
- HD 8490
- AMD Athlon64 x2 5000+ 2.6Ghz CPU
- SSD
Tried:
- haynor666's custom GroovyMame 0.229 build. Works ok in a match but certain transitions show infrequent pauses and audio pitch issues unrelated to the performance of my PC as far as I can tell (same issue on two PCs). http://forum.arcadecontrols.com/index.php?topic=154799.0 (http://forum.arcadecontrols.com/index.php?topic=154799.0)
- RetroArch: Mame2003 core. Performance was slow and stuttery, maxing out one of the CPU cores
- "Ultra64 Platinum Edition". Old DirectX 7 emulator which crashes and seems otherwise unfinished
- FinalBurn Neo dropped support for the KI games due to poor driver/emulation
The RetroArch: Mame2010 core is working the best for me currently though I've noticed a couple sound glitches while running the KI 1.5d rom. This core is also introducing screen tear in RetroArch for some reason.
-
Im using an old 1gb ddr3 amd hd 8750 card and have no problems that i cant tell using emudrivers and groovymame.
-
What groovymame version are you running?
-
228, but i never owned a real hardware so i couldnt tell if theres much diference, also i cant really catch any sound issues, it might be just me, that im dumb maybe.But yeah on certain mame versions , popeye has glitches, also tapper, so i think i i ever saw i glitch i would be able to spot it.
-
Thanks for that.
What CPU are you using?
-
Thanks for that.
What CPU are you using?
i5 3rd gen, 4gb ddr3 , vanilla win 7 x64 with the mods pposted from this same forum.
-
I found a solution. Using standard MAME 0.139, I am not hearing any sound issues on my Athlon64 CPU. Screen tearing can be fixed by enabling switchres and triplebuffering.
Mame 0.228/0.229 has the same audio-pitch-changing issue as GroovyMame on the older CPU with no obvious signs in task manager that the CPU is close to maxing out; no audio problems on my i7 CPU. Seems like the Mame code introduced some kind of bug/inefficiency sometime after Mame 0.139.