Software Support > GroovyMAME
GroovyMAME and vector games
Calamity:
Hi krick,
According to your logs, the mode that's 50 Hz and looks good it's also on the lower Hfreq range around 15.70 kHz, so both things should be considered. With the new patch (014) you can create two ranges in order to have separate settings for progressive and interlaced games:
crt_range0 15625.00-16670.00,49.50-65.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,192,288,0,0
crt_range1 15625.00-16000.00,49.50-65.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,0,0,448,576
Here crt_range1 is just for interlaced modes, and I'm lowering HfreqMax to a more conservative value. Another option is to limit the vertical frequency to, say: 50-55 Hz:
crt_range1 15625.00-16670.00,50.00-55.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,0,0,448,576
krick:
Had some time to experiment with this tonight and I'm seeing odd behavior.
If I make a single line for both progressive and interlaced games like this, it works just like the h9110 preset...
crt_range0 15625.00-16670.00,49.50-65.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,192,288,448,576
...and tempest runs at 768x512@60 (interlaced) like normal
But if I split it into two lines, both with the same settings with one each for progressive and interlaced like this...
crt_range0 15625.00-16670.00,49.50-65.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,192,288,0,0
crt_range1 15625.00-16670.00,49.50-65.00,2.000,4.700,8.000,0.064,0.160,1.056,0,0,0,0,448,576
...then tempest runs at 344x256@60 (progressive)
It doesn't make any sense. I would expect it to run at the same exact resolution/refresh as the first one. Am I doing something wrong?
I was trying to establish a baseline before I started making frequency modifications, but it doesn't behave the way I expected.
Calamity:
No, it shouldn't work like that, definitely. I'll need to have a look to it.
Calamity:
Ok, just tested here and it's working fine regarding the different ranges, etc. I've attached my mame.ini and two logs, one with HfreqMax of the interlaced range set as 16.20 kHz, the other as 16.67 kHz. You can see how different resolutios are selected in either case due as an attempt to achieve 60 Hz as vertical refresh rate.
EDIT: I'm thinking you probably left one "crt_range1 auto" line uncommented, that might be the issue.
krick:
--- Quote from: Calamity on January 28, 2013, 01:04:15 pm ---EDIT: I'm thinking you probably left one "crt_range1 auto" line uncommented, that might be the issue.
--- End quote ---
/facepalm
Yep. That's exactly what I did. Once I comment that out, it works fine. Sorry to waste your time on a goose chase.
With it working, I'm not entirely pleased with the results though, and I expect that there's not really anything that can be done.
Reducing the horizontal frequency range forces the game to run at 640x480@60, but it still has the problem that I can't adjust the monitor to vertically to fill the screen without getting that doubling effect again.
Reducing the vertical frequency forces the game to run at a low-res progressive resolution (I didn't take note of which one) but that's not appealing either.
So in the meantime, I'll just use the default h9110 preset and live with the smaller image at the higher resolution. Eventually, I'm going to have to do a cap kit on this monitor and maybe (hopefully) it will fix the problem.