AVGA 3000 + Makvision?

[wxman13]

Ok so it must be something else.

So better try setting a higher minimal dotclock. Don't be afraid to use 8.0 or even higher. Most lower resolutions will disappear and be scaled by 2. Hopefully that should fix it.

I must have something similar going on with 1941 with groovymame32, when I try it on my LCD monitor and ArcadeVGA3000 PCI E it works, but when I use my Makvision monitor and ArcadeVGA3000 PCI E and try to start 1941, I get a garbled screen? I am also using the drivers from Ultimarc for the ArcadeVGA3000?

[Calamity]

I think yours is a completely different issue. Just get a log like this so we can have a look:

groovymame 1941 -v -md 4 >1941.txt

[wxman13]

I think yours is a completely different issue. Just get a log like this so we can have a look:

groovymame 1941 -v -md 4 >1941.txt

Okay here you go:

[Calamity]

I see what's happening, GroovyMAME is picking a 25 KHz mode and your monitor only admits 31 KHz. On a normal ATI card, GroovyMAME would add extra lines to that modeline to convert it to 31 KHz, but it can't do that with the AVGA 3000 (yet).

So, first download this version of GroovyMAME (groovymame32_0143.013c_test):
http://mario.groovy.org/GroovyMame/WindowsATIDrivers/

Then, edit monitor_specs0 option in mame.ini with this values:

monitor_specs0 31499.99-31500.00,50.00-70.00,0.636,3.813,1.906,0.318,0.064,1.048,0,1,576.0,800

That should skip 384 lines modes (25 KHz) and used a 31 KHz mode instead, however I'm not sure how it will work with that mode table, so anyway please post back your logs after that.

[wxman13]

That works great, I've attached the text document using the test version of groovymame32 with 1941.

I am assuming the monitor specs you had me type in tells mame the limitations of the monitor?
Guess I need to learn some more about the mame.ini file