A quick question out of curiosity…
In games that use a flickering shadow to simulate transparency, i.e. Neo Geo fighters, I understand how it works by syncing with the monitors refresh rate, but how come the FBA core pulls this off successfully, while on MAME I still get flickering shadows? (Standalone or using RetroArch core?
I’ve tried to adjust settings in MAME, but I still can’t get rid of the flickering shadows…
Is this just how it is?
Could be several things.
Citing Haze on MameTesters board:
MAME always has rasters enabled (display is updated on a scanline basis for all drivers all the time, the raster enable/disable stuff mentioned in Nebula / old MAME is a speed hack)
This is why MAME correctly emulates some of mid-screen tearing that occurs on real NeoGeo games, and other emulators don’t.
So there’s probably a difference between current Mame and FBA (based on an old version with a speedhack).
Or simply that Mame always have a strange timing with hiccups (like discussed here)
Or perhaps it will finally do better when tech like G-sync will allow the games to run at their real speed without tearing.
the other thing to point out, is that…
you can access the service menu on MAME (press L2) without needed to access the core settings through the RGUI (as like with FBA).