Software Support > GroovyMAME
Fuzzy image on many games with CRT EmuDriver and 15kHz monitor
Calamity:
Hi tiobolinha,
In order to find out what's happening, please try the following:
1) Download the latest VMMaker/Arcade_OSD versions, from Krick's mirror site: http://mame.3feetunder.com/windows-ati-crt-emudriver/
2) Edit vmmaker.ini, set MonitorType = "CUSTOM" and the following line: monitor_specs_0 15625-15800, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.160, 1.056, 0, 0, 200, 448
3) Still in vmmaker.ini, set your GroovyMAME's path
4) Run VMMaker, restart (make sure your desktop is set to 640x480@60 before restarting)
5) Once in Windows, adjust your monitor if necessary to get a proper picture at 640x480. Notice it will be interlaced (flicker), that's fine.
6) Launch Arcade_OSD. Now, start testing resolutions, from the lower to the higher ones. ONLY test the ones marked as CUSTOM!! Notice which ones work, which ones don't. Try to find a logic. Probably the lower ones don't work, but the higher ones do. That would be a problem with low dotclocks. Report back.
7) If you can't find any logic, post your Modeline.txt file (inside your VMMaker folder) and mark a few of them that work, a few that don't (don't need to test them all).
krick:
I just wanted to note that when testing resolutions with Arcade_OSD, you may find that some resolutions cause the screen to "roll". This is normal and may require you to fiddle with the vertical hold or other monitor setting to get a stable non-rolling image. I have a 15KHz Hantarex Polo 25 monitor and it took me a while to find the "sweet spot" on my montor adjustments so that certain resolutions didn't roll. Also, some monitors are more harder to stabilize than others. It may have something to do with the age of the capacitors.
tiobolinha:
I called the guy who sold me the cabinet and he said the monitor is a "Barawood, MC220 / PV 2020". Does this ring any bells?
I googled it and found absolutely nothing.
I'll make the tests tonight and report back right away. Thank you guys!
tiobolinha:
--- Quote from: Calamity on July 30, 2012, 02:36:13 pm ---Hi tiobolinha,
In order to find out what's happening, please try the following:
1) Download the latest VMMaker/Arcade_OSD versions, from Krick's mirror site: http://mame.3feetunder.com/windows-ati-crt-emudriver/
2) Edit vmmaker.ini, set MonitorType = "CUSTOM" and the following line: monitor_specs_0 15625-15800, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.160, 1.056, 0, 0, 200, 448
3) Still in vmmaker.ini, set your GroovyMAME's path
4) Run VMMaker, restart (make sure your desktop is set to 640x480@60 before restarting)
5) Once in Windows, adjust your monitor if necessary to get a proper picture at 640x480. Notice it will be interlaced (flicker), that's fine.
6) Launch Arcade_OSD. Now, start testing resolutions, from the lower to the higher ones. ONLY test the ones marked as CUSTOM!! Notice which ones work, which ones don't. Try to find a logic. Probably the lower ones don't work, but the higher ones do. That would be a problem with low dotclocks. Report back.
7) If you can't find any logic, post your Modeline.txt file (inside your VMMaker folder) and mark a few of them that work, a few that don't (don't need to test them all).
--- End quote ---
Hi,
I did the testing as advised and found out that:
With the specs you gave me Vmaker created only 32 resolutions from 574 found in total.
The monitor supports vertical resolutions from 432 until 704 pixels and flickering starts to show as i go up.
It likes Frequency arround 60Hz. Slightly lower frequencies do show image but starts to go out of vertical sync and it gets worse as I go far from 60Hz. For instance in 51 Hz I can't stabilize even messing with the monitor potentiometers.
That's. I'm excited to know what the next step is! lol
Thank you!
Calamity:
Hi tiobolinha,
32 resolutions seems too few to me, did you point to the GroovyMAME's patch in vmmaker.ini?
Make sure the ModeTableMethod_XML value is set to 1.
Could you attach here your modeline.txt file?
It sounds odd that only resolutions above 432 lines work. Those are interlaced resolutions, it could be just a coincidence. No progressive resolution works ??!!
Navigation
[0] Message Index
[*] Previous page
Go to full version