Software Support > GroovyMAME

Nanao MS2930 settings

<< < (2/3) > >>

Calamity:
Ah I think I got it, the issue is with those monitor specs.

Recalculate the modelines changing this value:

monitor_specs_0 = "15450.00-16050.00, 54-65, 3.19, 4.75, 6.45, 0.826, 0.191, 1.462, 0, 0, 288, 448"

After that the 1234x256 resolution should exist in your system. That's the lower value for vfreq. If you know your monitor can actually handle lower values try lowering that one even more (50 Hz could be the lowest). That way you'll also get 288-line resolutions. Raising hfreqmax value (16050) a bit may help too, but just do it if you know it's safe (you can use Arcade_OSD to find your limits).

senorchris:
Awesome, thank you - that works perfectly!  First I reduced the min vfreq, and mk2 almost ran perfectly (locked on 99% framerate, with a stutter every now and then) - I then tried increasing the max hfreq (bit by bit in Arcade OSD, like you suggested), and stopped at 16335.  This made mk2 run perfectly - locked on 100%, no stuttering at all!  Thank you for your advice!

I'm starting to understand the verbose debugging text more and more, and have been looking at some of the games that are double-ressing.  e.g. Pitfighter (attached) - did it really originally sync at 16.891 hfreq, or am I reading it wrong?  If so, is it common for 15Khz monitors to be able to sync at that speed?  If it push my hfreq max up towards that number in Arcade OSD, as long as I do it bit by bit (and stop as soon as it goes out of sync), is damage extremely unlikely?  I'd really like to run as many 15Khz games at their native res if possible (especially as with this chassis, I have to pop open the control panel and change the sync frequency manually every time).

I completely understand you can't guarantee no damage, I'm just after a best guess.  :)

Thank you again!

Calamity:
I didn't notice before, but actually that vertical backporch value seems too high:

monitor_specs_0 = "15450.00-16050.00, 54-65, 3.19, 4.75, 6.45, 0.826, 0.191, 1.462, 0, 0, 288, 448"

1.462 equals 23 lines (too many I think). I'd use a value slightly above 1.000. Again, you can use Arcade_OSD to find the value that's good enough, you'll notice it's too low when top of the screen starts getting distorted.

That's probably why you're getting such high horizontal frequencies for those otherwise usual modes. Using lower vertical porches allows for creating the same resolution+refresh at a lower hfreq.

Tomorrow I'll post some links about how you can potentially damage your monitor by 'overclocking' it. Always take care!

senorchris:
Awesome - thank you!  Taking the back porch down to 1.164 and the vfreq min down to 50Hz has enabled a couple more modelines in VMMaker - it'll do all the way up to 288 lines, now (which has pushed a couple of vertical games down into the 15Khz mode).

Pitfighter is still double-ressing, though - it's asking for a horizontal sync of ~16.8Khz.  The spec sheet on my monitor states a hfreq at 15Khz of 15.75Khz +/- 300Mhz.  Using VMMaker, I've pushed it to 16.3Khz (as previously mentioned), and it seems fine - I'm just a bit nervous about continuing to push it higher, especially considering I'm well outside its specs.  Think I should leave Pitfighter alone, or are there other settings I could play with to get it viewable at a lower hfreq?

As ever - thank you for your help!  You've been invaluable - I've learnt more about CRT technology in the last week than I ever thought I would.  :)

Calamity:
I see now that your vertical front porch is abnormally high, it shouldn't need to be higher than your sync pulse actually:

monitor_specs0            15450.00-16050.00,55-65,3.19,4.75,6.45,0.191,0.191,1.164,0,0,288,448

With that change you'll get pitfight inside your native ranges without forcing it.

Navigation

[0] Message Index

[#] Next page

[*] Previous page