Software Support > GroovyMAME

Confusion on how to install Groovymame32...

<< < (3/6) > >>

repetto74:
Hi Calamity,

First of all sorry for the double thread I opened and good you merged them into one single discussion ::)
Thank you very much for your time dedicated to my issue here. I will first of all follow your advice and upgrade to GM 0.147 if this can make things more easy to handle.


--- Quote ---- GM can make all your resolutions to almost fit perfectly on the HORIZONTAL, once you find your custom specs.
- No software can control the VERTICAL size of a resolution on a CRT monitor, you need to adjust it physically (potentiometers, service menu, etc.).

If you want pacman to fit in the screen, you either need to adjust your potentiometers or setup GM to create interlaced modes for resolutions above a given value (e.g. 256)
--- End quote ---

In this thread
http://forum.arcadecontrols.com/index.php/topic,128623.0.html
you are helping the user on his monitor set up so that pacman and other 288 lines games will fit the screen at their native resolution. Correct me if I am wrong but maybe this is possible because his monitor can handle also 31khz which is not my case (only 15-25Khz)?

With my actual monitor adjustments I can display most of my horizontal game fine and vertical games with <=256 lines. I can understand then that number of vertical lines (256 here) is the limit and extra lines will not be displayed at native resolution. ( i don't think it is possible to adjust the V-size and fit the game right?)
My question is to know what would be the best set up to have 288 vertical games displayed nicely (limiting the nasty blurry effect of hardware stretch). How the new version of GM can handle this? Is it better to use D3D for those games with filters??
I am just trying to reach more or less an optimum considering my monitor specs.

Thanks again for your interest on this.
Rick

Calamity:
Hi repetto74,


--- Quote ---In this thread
http://forum.arcadecontrols.com/index.php/topic,128623.0.html
you are helping the user on his monitor set up so that pacman and other 288 lines games will fit the screen at their native resolution. Correct me if I am wrong but maybe this is possible because his monitor can handle also 31khz which is not my case (only 15-25Khz)?
--- End quote ---

That user is the lucky owner of a NEC XM, those monitors are truly multisync, and they seem to adjust v-size dynamically. On the other hand, our arcade monitors are "banded" (dual-sync, tri-sync), so they accept 15/25/31 KHz, but not the frequencies in the middle, like 18 kHz, and they have a v-size preset for each of the bands/ranges which can only be adjusted manually.


--- Quote ---With my actual monitor adjustments I can display most of my horizontal game fine and vertical games with <=256 lines. I can understand then that number of vertical lines (256 here) is the limit and extra lines will not be displayed at native resolution. ( i don't think it is possible to adjust the V-size and fit the game right?)
--- End quote ---

It is certainly possible to adjust v-size and get 288 lines fit in the 15 kHz range, that's what GM assumes you're going to do, because we always try give a chance to the user to display the resolution without any sort of stretching artifact, even if that involves messing with potentiometers.

However, it's not possible to get 60 Hz for 288 lines in 15 kHz, so you either have to renounce to v-sync or to live with an important slowdown for these games.

The workaround for both the unconvenience of messing with pots all the time and living with speed slowdowns is to use hardware stretching for resolutions above 256 lines. If you have a 25 Khz monitor you can benefit from the higher resolution available and use the upper range (25) to do the streching. If you combine that with interlace, you can achieve 1024x768i at 25 kHz, even 1024x800i, and trust me when I say it's hard to say these modes are interlaced when in MAME, because GM automatically sets the d3d filtering and you can hardly see any flicker at all.

In order to do that, you need to edit mame.ini, set 'monitor' option to 'custom' and edit these lines:

crt_range0 15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 256, 448, 576
crt_range1 24960-24960, 49.50-65.00, 0.800, 4.000, 3.200, 0.080, 0.200, 1.000, 0, 0, 320, 384, 640, 768

There's a catch however, you need to have a custom 1024x768i resolution available in your system. Unfortunately I'm in the process of updating VMMaker to the new crt_range, so you need to use somewhat different options in vmmaker.ini, combined with the MonitorType = "CUSTOM":

monitor_specs0 15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 256, 448
monitor_specs1 24960-24960, 49.50-65.00, 0.800, 4.000, 3.200, 0.080, 0.200, 1.000, 0, 0, 384, 640

In case you don't obtain a 1024x768i custom resolution with these lines, add an explicit 1024x768@60 resolution in the ReslList.txt file before creating the modes with VMMaker. Once you see this resolution listed in Arcade_OSD, you're ready to go with the settings above for GM.

repetto74:
Million thanks for this clear explanation!!  :applaud: :applaud:

I am following your suggestions with groovy147 but I cannot generate the 1024x768 modeline with VMmaker.
I added this line down the list of the Resllist.txt in the Aux section. I also edited mame.ini and Vmmaker ini as per your instructions.

1024x768@60.000000 aux

I then saved and generated modelines with VMmaker but this modeline is not in the OSD modelist
Any idea??? ??? ???

PS : the closest modeline available is 1024x384

Calamity:
The ReslList.txt file is super-sensitive to white spacing, you need to use the exact same format. Anyway attach here your vmmaker's txt files (modeline.txt, modelist.txt, resllist.txt) so I can have a look.

repetto74:
Hi Calamity,

Here enclosed the VMmaker text files. I have another question concerning mame.ini setting : shall I use d3d or ddraw in my case or is GM automatically switching to d3d for high resolutions??

Thanks again for your help

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version