Hi! Will someone be so kind as to explain how I can get a per driver .ini in MAME to work.
In RGUI, in seems like I can have it read my own MAME.ini, but I cannot seem to get it to work anymore.
Ideally, I want to set up the Neo Geo driver to force a 60hz refresh rate instead of the default 59.xxx to get rid of those flickering transparency effects caused by having the refresh rate different than my TV
Thanks in advance for any and all help!
MAME saves cfg files per game by default, but for some reason they have decided to not allow saving overclocking or video refresh rate. In any case you should be able to set MAME.ini writeconfig to 1 (dunno why it isn’t a core option I’m pretty sure I removed it for a reson), then MAME will save per game ini files.
It’s reading the ini correctly here so it’s probably in an incorrect location
RetroArch already handles this itself by adjusting the core’s audio rate to allow vsync to match your display. This wasn’t working in the MAME core previously due to it incorrectly reporting 60.0Hz for all games to RetroArch, but now it reports a correct refresh rate for each game/driver and RetroArch is able to do the correct adjustments. Neo Geo should work flawlessly since it’s only slightly off from 60Hz, as should things like CPS2 and CPS3, but for larger differences you may need to increase the maximum audio timing skew in audio settings for those to be adjusted, and they will have more noticeable pitch and speed deviations.
Also, I noticed MAME’s throttle option sometimes interferes with RetroArch’s rate control, so you should disable that.
[quote=“Monroe88”]
RetroArch already handles this itself by adjusting the core’s audio rate to allow vsync to match your display. This wasn’t working in the MAME core previously due to it incorrectly reporting 60.0Hz for all games to RetroArch, but now it reports a correct refresh rate for each game/driver and RetroArch is able to do the correct adjustments. Neo Geo should work flawlessly since it’s only slightly off from 60Hz, as should things like CPS2 and CPS3, but for larger differences you may need to increase the maximum audio timing skew in audio settings for those to be adjusted, and they will have more noticeable pitch and speed deviations.
Also, I noticed MAME’s throttle option sometimes interferes with RetroArch’s rate control, so you should disable that.[/quote]
Mame in RetroArch has never worked correctly for me regarding NeoGeo games… A good example would be Samurai Shodown. If you watch the intro attract screen, the lanterns have that uneven flickering effect, and the shadows underneath the fighters feet also flicker unevenly…
I can fix this by pressing ‘L2’ and calling up the MAME menu and adjusting the refresh rate up a bit.
Final burn Alpha doesn’t exhibit this behavior.
I’ve never been able to fix this in RetroArch MAME. If you could help me solve the flickering transparencies, I’d be most appreciative
RetroArch already handles this itself by adjusting the core’s audio rate to allow vsync to match your display. This wasn’t working in the MAME core previously due to it incorrectly reporting 60.0Hz for all games to RetroArch, but now it reports a correct refresh rate for each game/driver and RetroArch is able to do the correct adjustments. Neo Geo should work flawlessly since it’s only slightly off from 60Hz, as should things like CPS2 and CPS3, but for larger differences you may need to increase the maximum audio timing skew in audio settings for those to be adjusted, and they will have more noticeable pitch and speed deviations.
Also, I noticed MAME’s throttle option sometimes interferes with RetroArch’s rate control, so you should disable that.[/quote]
Mame in RetroArch has never worked correctly for me regarding NeoGeo games… A good example would be Samurai Shodown. If you watch the intro attract screen, the lanterns have that uneven flickering effect, and the shadows underneath the fighters feet also flicker unevenly…
I can fix this by pressing ‘L2’ and calling up the MAME menu and adjusting the refresh rate up a bit.
Final burn Alpha doesn’t exhibit this behavior.
I’ve never been able to fix this in RetroArch MAME. If you could help me solve the flickering transparencies, I’d be most appreciative[/quote]
Final Burn Alpha didn’t exhibit this because it reported its refresh rate accurately to RetroArch, while MAME didn’t before. In the latest nightly builds, this has been resolved and the MAME-libretro core is flawlessly adjusted to your display. I just tested that game and RA’s dynamic rate control handles it flawlessly on my end and the flickering is 100% even.
So be sure and update to the latest nightly builds of RetroArch and MAME-libretro, ensure the refresh rate setting in Settings>Video Options is accurate to your display (it’s used for calculating the audio adjustment), and disable the throttle core option in MAME, and the flickering will be even.
Nightly builds are located here:
I’m using the Dec. 06 build…
I’ll set the refresh rate to 60hz in settings and see if it makes a difference for me.
Thanks for the help!
That is ancient by now, 1.0.0.3 is waaaay better, and even that’s outdated now.
I thought DEC 6 as in last year… my bad…
I can honestly say that with using the Dec 07 2014 build, I still have these refresh rate issues. RetroArch reports my televisions refresh rate at 59.950, changing it to 60.0 made no difference. Neo Geo games run slightly below that, so I get that flickering effect and the only way I can fix it is by bumping up the refresh rate in MAME itself (which we all know doesn’t stick in the settings; you have to do it every time)
Any additional suggestions to finally fix this for me?