CRT_Emudriver, Win7, and Interlaced Res ?'s

[2600]

I've read some of the issues of why interlaced resolutions don't show up and I'm wondering if something else is going on. 

I've got a D9200 and my 30Hz resolutions are showing up as 60Hz.  I believe these are my interlaced resolutions.

The D9200 has 75 ohm resistors already built in when using the DSUB connector.  I've measured it and they are fine.

So, why do my interlaced resolutions show up as 60Hz?

Could a monitor inf help with this to override the lack of EDID?

[Calamity]

Well the problem is when interlaced modes don't show at all. If they are there, then all is fine. Arcade OSD will show them as 60 Hz. Windows display properties will show them as 30 Hz.

[2600]

My problem seems to be that after I reboot, Windows display properties don't show them as 30Hz.  The 30Hz option is there before I reboot, but after I reboot they are now 60Hz.

[Calamity]

So are the interlaced modes available in Arcade OSD or not?

[2600]

So are the interlaced modes available in Arcade OSD or not?

They are there but they are 60hz not 30 hz.  I've verified that when selecting them, the monitor is running at 60hz not 30 hz like they should be.

[Calamity]

Ok forget about the 30 Hz thing for a minute.

What you need to check is if they are 15 kHz, check it in your monitor's osd. If they're 15 KHz and they look interlaced (flickery) then all is fine.

The 30 Hz thing is just a lame nomenclature introduced with Windows 7. The modes still have a vertical frequency of 60 Hz. The 30 Hz just refers to the logical frequency that a full frame is shown at (a frame consists on 2 fields in interlaced modes). But your monitor has no idea of logical frequencies, it can only count sync pulses.

[2600]

Finally got back to this and did some more testing and here is what I have found.  Let me know if I'm on the wrong track.

If I just install the crt_emudriver everything is fine.  I can reboot a bazillion times and arcade_osd has a few of the resolutions with an i instead of a p under the vertical refresh rate, Windows 7 list a 30Hz, Interlaced option, monitor reports them as 15kHz, etc.

As soon as I run VMMaker as admin and then reboot, all interlaced resolutions are no longer interlaced.  arcade_osd lists everything with a p and the monitor has them at 31kHz.

[Calamity]

As soon as I run VMMaker as admin and then reboot, all interlaced resolutions are no longer interlaced.  arcade_osd lists everything with a p and the monitor has them at 31kHz.

Then check what VMMaker promts on its console to understand what's going on. And see the resulting Modeline.txt file too. etc.

[2600]

Hopefully you can see what the issue is with these files.  Also, I had previously used XP64 with the XP driver on this system and everything worked fine.  I copied my ReslList and VMMaker.ini file over from XP when setting up the Win7 driver.

Thanks for any information on what the issue may be.

[cools]

You lose the interlaced modes because you are configuring a tri sync monitor. Change the preset in vmmaker to generic and they will come back.

[2600]

You lose the interlaced modes because you are configuring a tri sync monitor. Change the preset in vmmaker to generic and they will come back.

Sounds like I made a rookie mistake and maybe I was wrong about XP working.  I guess I'm confused on why I'm losing interlaced modes with a tri sync monitor.  The monitor supports them and it is the resolution that I specified so why purposely change it.  Is there a reason not to run the same resolution the game ran at?  Or am I missing something else simple?

[Calamity]

Sounds like I made a rookie mistake and maybe I was wrong about XP working.  I guess I'm confused on why I'm losing interlaced modes with a tri sync monitor.  The monitor supports them and it is the resolution that I specified so why purposely change it.  Is there a reason not to run the same resolution the game ran at?  Or am I missing something else simple?

First of all, very few arcade games used to run at interlaced modes (console systems are a different story).

You usually create interlaced modes as a workaround to get more resolution than what's available on standard arcade monitors (typically for vertical games).

But interlaced modes are undesirable if you can use progressive modes instead. VMMaker always tries to use the frequency range that provides better quality, so if you specify a tri-sync monitor it will use the 31 kHz for anything above 400p (you can control the boundaries).

If you have a good reason to use interlaced modes, you can just configure VMMaker for a standard 15 kHz monitor (default options). You can still use "monitor d9200" in mame.ini to take advantage of the upper ranges inside GroovyMAME if that's what you want.

[cools]

I can't think of any interlaced games that don't look 100% better in progressive.

[2600]

I can't think of any interlaced games that don't look 100% better in progressive.

I think I'm just getting old and have been doing things differently then they are done now.  Blows my mind even now the percentage of people who used widescreen LCDs and hdmi.

I've always tried to make the image look as close as possible to how the game looked originally, not better.  I've always done it that way.  Not everything was perfect, but you worked with what you had.  Even now, I'm only testing switching a few things and am not using Groovymame yet, just the crt_emudriver.  There are only a couple of games that I'm trying to run interlaced Popeye and the MCR games like Tapper, Discs of Tron, etc.  I'll try them in progressive first to see if that will work for me.