interlaced 640x480 on D9400 monitor

[ahofle]

I had to throttle back the number of video modes generated by the crt emu driver to 90 so that Hyperspin wouldn't crash.  Now it seems that playing a game at 640x480 results in an interlaced video mode.  Is there any way to manually remove 640x480i?

[Calamity]

640x480 should be automatically recalculated as 31 KHz progressive if you're using the right monitor settings. Something else is going on, it's not a matter of removing modelines, doesn't work like that.

Please attach a log of the game involved using the -v -md 4 params and so I can see your settings and system setup.

Consider using GroovyMAME's "magic resolution" feature if your frontend is HS, it's the current workaround, works much better than reducing the mode list (there's some info on how to do this in the main thread).

[ahofle]

Thanks I'll check that out and get a log to you ASAP.  I'm using D9400 for the monitor type.

[ahofle]

Sorry for the delay on the log (see below).  I mostly notice this on other emulators (non-groovymame) but I did manage to see the same issue in a 640x480 MAME game too (sfexp).  Also, I haven't been able to find the 'magic resolution' feature you mentioned.  Can you point me to that message?  Thanks.

[caskad]

Hello, just take this:

http://mame.groovy.org/WindowsATIDrivers/VMMaker%201.3b%20+%20Arcade_OSD_1.3.rar

then unrar to crt folder, overwrite current files.

edit Vmmaker.ini to adjust:

 MonitorType = "D9400" and Monitor orientation if rotating one.

 save and launch Vmmaker.exe -> reboot

magic resolution


Ps: Mame.ini set d3d instead of Ddraw!

[lettuce]

i thought groovymame should be left on ddraw not d3d?

[caskad]

as i know, Ddraw and magic resolution are not so good.
just o cas ou... juste in case!

make 5 s to test.

[Calamity]

Hi ahofle,

There two issue at least:

- VMMaker is not doing the right job as it's storing 640x480@60i instead of its progressive counterpart even if your monitor if capable of that. I'm aware of this problem as just since this weekend I'm the owner of a brand new Hantarex Polostar and I've seen the same thing. A possible workaround is to edit ReslList.txt, change 640x480@30 for 640x480@60, and recalculate resolutions.

- You're using an old version of GroovyMAME (013b), make sure to pick a newer one. In case you want to use the magic resolution thing make sure to visit this thread (until I write a better guide for it): http://forum.arcadecontrols.com/index.php?topic=110905.msg1209299#msg1209299

All versions since 0143.013c support magic resolutions. And yes, better use d3d in case you decide for the magic resolutions method or there's any scaling involved.

[ahofle]

Well no luck changing the 640x480@30 to 640x480@60.  I regenerated resolutions with vmmaker and rebooted and it seems any VGA and higher are disabled in the ArcadeOSD tool.  The weird thing is my desktop is at 800x600p and that one works fine.  Very strange.  Is d9400 a valid monitor type?  Should I try d9200?  Not sure if there are any differences.

Do you think using a newer groovymame would matter?  I'm not even seeing the resolutions getting generated in Windows  Any ideas would be appreciated.

[nexusmtz]

I had the problem of 640x480 being interlaced on my monitor (D9800) after running VMMaker.

I opened ArcadeOSD, selected the 640x480 interlaced res, hit 2 to edit, selected Edit modeline, set Lock vfreq to no and interlaced to no.

After setting normal VGA frequencies (25.18MHz, 31.475kHz, 59.952Hz), positioning it properly, and saving the changes, it has been fine.

Although I can only guess at what's going on, it seems that if vmmaker thinks it should make the 60p, it uses the built in mode (which would be uneditable in ArcadeOSD) but if you let it make the interlaced mode, ArcadeOSD can 'override' that back to progressive.

Keep in mind that in order to try what I did, you'll first need to remove the 60p line from resllist.txt and recalculate to get the editable interlaced mode back.

--Nexusmtz

[Calamity]

Well no luck changing the 640x480@30 to 640x480@60.  I regenerated resolutions with vmmaker and rebooted and it seems any VGA and higher are disabled in the ArcadeOSD tool.  The weird thing is my desktop is at 800x600p and that one works fine.  Very strange.  Is d9400 a valid monitor type?  Should I try d9200?  Not sure if there are any differences.

Check if all the modelines created, contained in the Modeline.txt file, are actually available through Arcade_OSD.
I'll see if I can get this issue fixed this weekend, I'm suffering the same issue with my new monitor.
By now the fix suggested by nexusmtz is perfectly valid.

Probably that 800x600p resolution is a native one.

Do you think using a newer groovymame would matter?  I'm not even seeing the resolutions getting generated in Windows  Any ideas would be appreciated.

New versions have a modified algorithm that usually picks the right resolution. From the log you passed it seems it was picking some odd resolutions. Anyway the algorithm is far from perfect and needs some work yet.

Although I can only guess at what's going on, it seems that if vmmaker thinks it should make the 60p, it uses the built in mode (which would be uneditable in ArcadeOSD) but if you let it make the interlaced mode, ArcadeOSD can 'override' that back to progressive.

Well it's not exactly like that but there's definitely a bug there I need to fix. Thanks for pointing that.

[ahofle]

Thanks for the help.  I'll see if I can get upgraded this weekend and look forward to your fix.