ACK! - Mr.Do needs fixin!

[TurboC--]

Just found out that Mr.Do! is one of the games not working with my arcade monitor.    Can't have that!!  It "goes all wavely".  I'm currently set for "224 lines as optimal", all 224 and 240 games work and some others, but it doesn't like 192.  How can I best fix this?  My monitor likely has a wide enough range to accomodate it (15 - 17.5 kHz) but last time I tried multi-sync mode, NOTHING worked. 

[TurboC--]

Can anyone assist?

[2600]

I'm assuming your are reading that resolution and refresh rate from MAME.  I do not think that number has been verified.  I believe, It was upped? to that to fix an odd bug, but may not be the real resolution.

Try putting a specific resolution in for that game instead.

[TurboC--]

Try putting a specific resolution in for that game instead.

But how do I do that?  I haven't had much luck with getting advmame to do what I want to do, usually it does the opposite...

[2600]

In MAME, you put a game specific ini in your INI folder. 
ex. pacman.ini in C:\MAME\INI

That INI file supports all the standard options from mame.ini.
Convienently, there are two option resolution and refresh.

ex: pacman.ini
resolution 640x480
refresh 60

That's all.  Read the docs for more info.

DOSMAME may be different and I'm not sure about advmame.

[TurboC--]

Making this stuff work seems endless.

[TurboC--]

No good.  I tried creating a modeline for the 192x240 res.  I based it on the working Pac-man modeline that advmame creates itself (I logged it) which is:

6.03 (or so) 288 320 352 384 224 238 241 262 -hsync -vsync

Mr.Do! is listed to run at a higher frequency (61.166569 Hz), meaning 257 total lines will keep it at exactly 15.72 kHz refresh.  Sounds logical right?  So I did:

6.0364  240 320 352 384 192 236 240 257 -hsync -vsync

My modeline was "excluded."  Actually now that I think about it, maybe what it didn't like was the 4th decimal point.  Why does everything have to be so hard...

[2600]

Now you know why people don't use ADVMAME.  Not sure what your requirement is that you have to use it.

[TurboC--]

Cause I'm running a suckass 350 MHz machine, and using an arcade monitor with my onboard (only option since I have no AGP slot) video card?  I thought AdvMAME was the only one specifically designed to work with arcade monitors in their native resolutions.  Otherwise I will have to stretch games, which not only defeats the entire purpose of owning an arcade monitor, but also would likely overload my poor processor.  Presumably if I spent 2 weeks memorizing all documentation and changing modelines and options, I could get it to work correctly with every game.  I mean if I can just get Mr.Do! working (and with it hopefully other 192-line games) then the only other game issues are with Galaga '88 and Pacmania, which I think are speed issues.

I honestly blame the documentation rather than the program.  Just a few key examples would help immensely.  Anyway, another theory of why 192 line modes go screwy is this - I noticed in the log file that the mode it chooses for Mr.Do! has a PClock of something like 5.06 MHz.  That is extremely close to the low end, maybe my video card is what doesn't like it, rather than the monitor. 

[Thenasty]

do you have that modeline created ? 192x240x61.1hz
fi so, then add in your rc file:

mrdo/display_mode WHATEVER_THE_NAME_YOU_CALLED_IT_WHEN_CREATED

ie:
mrdo/display_mode 192x240x61.1hz

hope thats what your looking for.

[TurboC--]

I added it as a general modeline that can be used for any game.  I ran Mr.Do! with a log file and it read in my modeline but "excluded" it for some reason.  You can't just put "192x240x61.1" as a modeline because you need to specify blanking lines and all kinds of timings, 4 for horizontal and 4 for vertical.  I tried to get close to what works for other games but .. something was wrong anyway. 

Maybe there's a way to use advcfg to create a desired modeline?  I just have to make sure it doesn't screw up everything else in the process.

As for my machine, just got everything all put together and ready to go.    But some loan shark is over, gonna wait till he leaves, bleh...

[eccs19]

Cause I'm running a suckass 350 MHz machine,

 then the only other game issues are with Galaga '88 and Pacmania, which I think are speed issues.

I expect that at least the Galaga '88 is a speed issue.  I just set up a Windows 2000 machine with mame / Mamewah, and it is a 850 Celeron, with SIS (620 I think) on-board, and Galaga '88 played like crap.  I put in a PCI TNT Riva card, and it improved it (It was ALMOST playable, but still ran bad)  Older games where no prob with the PCI card, but the on board still had resolution problems with some of the games. (Ghosts 'n Goblins)

[RayB]

I expect that at least the Galaga '88 is a speed issue.

[eccs19]

I expect that at least the Galaga '88 is a speed issue.

[RayB]

Really?