Groovymame with lag reduction ON still feels like it has about 4-5 frames of lag on my PC. This is quite noticeable when I play DFK BL, for example. It feels about the same as the lag in the SDOJ port. This is a big improvement over how MAME used to feel -- I mean, it felt like 6-8 frames before for me -- but it doesn't come close to the PCBs or the good X360 ports.
4-5 frames, getting that with a 2 frames source like cv1k sounds typical of broken settings, meaning the lag reduction isn't working. Maybe 9 in 10 new users experience that as I've witnessed (typically they changed settings in the mame.ini they shouldn't have, or introduced another parameter that's breaking everything, like misconfigured multi-monitors, or they downloaded the wrong build, etc)
There is a quick configuration guide which has crucial info but the site is currently down so check later.
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=433When you use lag reduction (frame delay slider from the UI menu)
you're supposed to see tearing appear, that means the feature is active, and as you increase the frame delay level you'll get where it affects performance negatively (frame/sound drops)
[often this is where users go and mess with sync settings and make a fatal mistake]Set at a stable level before it, like if 7 is too much set 6 or even 5.
On my PC with cv1k games I can set 5 for global cv1k stability. 7~8 is better of course but it's really heavy on the CPU and GPU at times. and yes with Groovy the GPU matters a bit too, in particular with high-res displays like full-hd, wqhd, 4k, so I wouldn't trust much things like Intel iGPUs)
tip: keep an eye on F11 when you set frame delay, make sure the meter stays at 100%.
Then create a specific .ini file for a game, for instance
pinkswts.iniin it write:
vsync_offset 250and drop it into the 'ini' folder.
That 250 value is just for illustration, you may need a much lower or higher one, play the game to see if it
gets rid of the tearing.
typically this takes a few tries to get right.
Note higher values can mean it's too tight for your hardware and you should maybe drop frame delay 1 level then try a different offset value.
tip: the higher resolution your display, the greater values you'll need, think about your monitor's vertical resolution, you're moving the tearing line up and down it.
Alternatively you can use a single ini named
cv1k.ini, and drop it into a 'source' subfolder in the 'ini' one.
but using a single offset value for all games don't always work perfect...
Anyway if you did that right you now have your vsynced and lag-reduced video working the way it should, tear-free butter-smooth scrolling and low lag close to that of the pcb (2~3 frames)
Levels of frame delay kinda represent setting chances of occurences of having no unwanted lag
at all, it's not really a percentage but you could picture it like with 7 you have 70 chances of an input being lagless within the targeted frame time.
It's more subtle than that but Calamity would explain better.
For the CPU slider, remember there's ten steps in between each % , hence the slowness, and that's not visible from the UI (go to each game's individual .cfg file, open and witness your CPU setting on a 1000 scale to be absolutely sure of the slider position, eventually edit manually there if that's your thing)
As I've said before, even 0.1% can matter in places, some in-game behaviours will trigger or won't by a hair.
If nobody watches this, then 10 people who've set for instance 50% could have 10 different set values without knowing it.
I don't know why you're experiencing a game missing the CPU slider, I'd have to know everything about your setup, build, settings, roms, etc but I won't really go and ask that then provide the inevitable hours of support like I did tens of times on the farm and other places, paraphrasing the official guide(s) with additional explanations, because it's led to people most times failing, essentially because they were very uncooperative and a few other reasons, and I've worked my ass for nothing. I would maybe for you EOJ but there are people here I really don't like and I don't want to help them along.
You can ask anything in private though.
PS: about Calamity, few people who would really have benefited from his help actually went and asked at BYOAC (el_rika gave the link), and those who did often wouldn't bother producing a log file like Calamity demands so he can provide efficient help.
For anyone who's having trouble with Groovy that's the place to go and where to receive support, in fact this is where all the ppl serious about this current topic should go now, start a thread similar to this one and get aid from the most skilled people there along Calamity's.
That would be the smarted and most valuable move, much, much better than going for the dead-end made with old builds and retroarch trash.
However you know the situation right now, and he's in Spain (ouch), so it's possible there won't a be a response before long (plus he was already often absent from the forum even before that)
pps: oh and if you need fresh roms go to r.e.t.r.o.r.o.m.s , besides the 'dome' it is the
only place carrying up-to-date rom sets, which is absolutely crucial these days the way modern MAME works, and therefore for Groovy too (wrong/old roms = some things might not work properly if at all)
Recent Posts
Be sure to enable nobuffer patch in mame settings/cfg, it should cut an extra frame of lag.