Monitor or Groovymame/ Crtemudriver issue? (Solved)

[brad808]

.

[Calamity]

Are you running the screens as separate desktops or cloned?

[brad808]

.

[brad808]

.

[Calamity]

Have you adjusted H-freq pot already on the problematic monitor?

[brad808]

.

[Calamity]

Yes I have. Is it possible with the new drivers the card is outputting a lower sync signal that one monitor is able to handle and the other not?

It could be that, but then it would have failed too with GM 0.168 because presets are the same as the ones in VMMaker 2.0. Can you test GM 0.168? Just launch it, no need to redo video modes (only try progressive games).

[brad808]

.

[Calamity]

Have you checked the sync polarity on the chassis?

[brad808]

.

[Calamity]

They are both using the same sync cable which I've permanently made composite sync. They are both going to the h sync input on the chassis but is there a polarity switch on the chassis that I'm missing?

There's usually a polarity switch. I believe the problem is the new versions are outputting composite possitive sync, and one of your monitors is not dealing fine with it.

[brad808]

.

[Calamity]

Ok thanks I'll look into it. Is there an easy way to quickly switch back to negative polarity via software for testing purposes?

Create the modes again with VMMaker 1.4.

[brad808]

.

[brad808]

.

[philexile]

I upgraded from Beta 2 to Beta 3 and I cannot update my resolutions. They are generated but when I install it says "busy" and the interface is grey. Nothing happens after that and I've had to force reboot twice.

[haynor666]

I upgraded from Beta 2 to Beta 3 and I cannot update my resolutions. They are generated but when I install it says "busy" and the interface is grey. Nothing happens after that and I've had to force reboot twice.

I have the same problem but not always. After restart I don't have picture on TV. After I plug back to LCD my card is disabled in hardware menager and I have to enable it again. After this desktop returns to 640x480@60i. Maybe the problem is that I used during tests also older VMMaker.

[Calamity]

It simply takes a very long time to restart the video driver once you have many modelines, it grows exponentially, you need to let it finish, otherwise the video card is left disabled. I guess I should make automatic restart of display device optional.

[Calamity]

Ok I tried remaking the modes with older vmmaker but it didn't work. Went into vmmaker to edit modelines and they were all in fact negative. When testing screen went crazy. Made them positive and it worked. That's my initial assessment

The polarity settings in Arcade OSD don't work probably. I could never test this because I didn't have an oscilloscope back then. Now I have one but haven't had the time.

My guess is that the existing documentation about polarity settings for ATI using the registry is wrong. If you use VMMaker 1.4/GM pre-169, polarity will always be negative. With 2.0/GM 169, it will always be positive.

Many arcade monitors only accept negative sync, that's the problem. But negative sync breaks interlaced modes in W7 

[brad808]

.

[Calamity]

I was just in the process of testing this again. In arcadeosd when both vsync and hsync are negative the modes won't display. As soon as I change them both to positive the mode displays. Still won't work in groovymame but they will test ok in arcadeosd. I've tried the old vmmaker but it still has issues. I'll keep going trying to figure out why.

So are you trying all this with new vmmaker?
If that's the case, enter the monitor presets settings, and edit your current crt_range with +hsync and +vsync. Then generate and install the modes again.

monitor "ms929", "Nanao MS9-29", "4:3"
        crt_range0 15450-16050, 50-65, 3.910, 4.700, 6.850, 0.190, 0.191, 1.018, 1, 1, 192, 288, 448, 576
        crt_range1 23900-24900, 50-65, 2.910, 3.000, 4.440, 0.451, 0.164, 1.048, 1, 1, 320, 384, 0, 0

[brad808]

.

[Calamity]

Great! It turns out the polarity settings do something after all...