Need TESTER for PacMan Resolution

[terabit]

I am using a Betson 27inch Multisync monitor and a ArcadeVGA card. I am using Mamewah with the command line Mame. I noticed that when I changed the PACMAN.INI file that AradeVGA Mame Resolution tool created from 352x288 to 288x224, it seem to work perfectly. With resolution at 352x288, I was loosing the top and bottom part of the screen. I also turned off hwstretch in MAME.INI file. (hwstretch 0) Cleanstretch and resolution are set to auto in MAME.INI. Can anyone try that has a similar set up and see if it works for them.
Thanks
Glenn

[Minwah]

Firstly you don't need to start a new thread when everything you are asking is related...

I just tried it, and for me 352x288 works fine (except refresh rate*), and 288x224 makes the game appear on a fraction (~1/4) of the screen (centered).  I just have a 15khz screen but I can tell the game is not truly running at 288x224, looks like 640x480 to me (I can tell from the interlace flicker).  Since you have a multisync, perhaps yours is running at 640x480 too - you wouldn't get the flicker I do.

* 352x288 runs at ~50hz, whereas PacMan runs at ~61hz, so I lose frames.  Note that I have the old version of the ArcadeVGA, I think the new one may address this issue (and run @ 60hz).

[Minwah]

I just have a 15khz screen but I can tell the game is not truly running at 288x224, looks like 640x480 to me (I can tell from the interlace flicker).

[terabit]

Sorry for the re-post.
I have the new ArcadeVGA card and also ran refreshforce to set all resolutions at 60hz. I am running Mamewah at 800x600. The text is much sharper at that resolution. I tried just taking the PACMAN.INI file out and force MAME to set resolution but I still get the top and bottom cut off. Hell, I am not complaning about anything, I am just tyring to figure out why this is working for me. If someone else has a multisync monitor with a new ArcadeVGA card let me know if it works for you. Thanks Minwah for your input. I am new to this venture and am learning more everyday.

I just tried to set the INI file to 640x480 and it takes up a fraction (1/4) of the screen like you said. That does not seem to make sense that when I tell it to 288x224 it works great.
Thanks
Glenn

[Minwah]

Sorry for the re-post.
I have the new ArcadeVGA card and also ran refreshforce to set all resolutions at 60hz. I am running Mamewah at 800x600. The text is much sharper at that resolution.

It would be, almost like running a PC monitor as opposed to an arcade one (high vs low res.)

I just tried to set the INI file to 640x480 and it takes up a fraction (1/4) of the screen like you said. That does not seem to make sense that when I tell it to 288x224 it works great.

As I say try setting log 1 and then you will know exactly what res. it is running at.  It will not be 288x224, it is probably 800x600 since that is what you run MW at.

[terabit]

That seems to be it. This is the error log

using performance counter for timing ... cycles/second = 3579545
width 288, height 224 depth 16
set visible area 223-223 0-0
Namco: freq fractional bits = 16: internal freq = 192000, output freq = 48000
set visible area 0-223 0-287
Physical width 800, height 600
Machine reset

So I guess I am seeing it sharper than the original game? I still don't know why when I set it at 352x288 I get the top and bottom cut off.
Thanks again minwah for your input. It is confusing at times but still a hell of a lot of fun.
Thanks
Glenn

[Minwah]

So I guess I am seeing it sharper than the original game?

Basically yes.  This somewhat defeats the point of having a monitor capable of low resolutions 

I still don't know why when I set it at 352x288 I get the top and bottom cut off.

As I said, horizontal monitors are 'supposed' to display ~240 lines.  Squash the vertical size down and the top / bottom *will not* be cut off!

[terabit]

I guess I have set up something wrong along the way.  When I try to use the setting that the ArcadeVGA tool suggests it cuts off much of the game. I think I just got lucky with Pacman. I tried to do the same thing with centipede but no luck. If I set the hwstretch 1 in the MAME.INI it helps a little but still have some top and bottom missing. Right when I thought I had figured it out, I realize I am far from it.
Glenn

[Minwah]

I guess I have set up something wrong along the way.

[terabit]

I did not know that. Thanks. I did try to adjust the monitor, but could not get the very bottom to show up. Its off by about 2 inches or so. You loose the player when you in the game if you go all the way to the bottom of the screen. The vertical postion will not let me move it up enough.
Glenn

[terabit]

Here is what my error log said:

using performance counter for timing ... cycles/second = 3579545
Reading PNG chunk IHDR
PNG IHDR information:
Width: 686, Height: 667
Bit depth 8, color type: 2
Compression method: 0, filter: 0, interlace: 0
Reading PNG chunk gAMA
Source gamma: 0.227270
Reading PNG chunk cHRM
Ignoring ancillary chunk cHRM
Reading PNG chunk IDAT
Reading PNG chunk IEND
width 333, height 345 depth 32

What is up with the 686 x 667 and 333 x 345? Where did those numbers come from? My INI says 352x256.
Thanks
Glenn

[Minwah]

I did not know that. Thanks. I did try to adjust the monitor, but could not get the very bottom to show up. Its off by about 2 inches or so. You loose the player when you in the game if you go all the way to the bottom of the screen. The vertical postion will not let me move it up enough.

Damn, not sure why that is then.  Not knowing the monitor I don't know what else to suggest - have a good search through the Monitor forum, and the forums at MameWorld to see if anyone else has had similar problems, I know I have seen a few threads regarding your monitor.

Not sure about the width/height thing either, I have only ever taken notice of the 'Physical width/height' part, which your log doesn't seem to contain.  I would have thought neither of those dimensions given are the resolution the game is really running at.

[Silver]

Here is what my error log said:

using performance counter for timing ... cycles/second = 3579545
Reading PNG chunk IHDR
PNG IHDR information:
Width: 686, Height: 667
Bit depth 8, color type: 2
Compression method: 0, filter: 0, interlace: 0
Reading PNG chunk gAMA
Source gamma: 0.227270
Reading PNG chunk cHRM
Ignoring ancillary chunk cHRM
Reading PNG chunk IDAT
Reading PNG chunk IEND
width 333, height 345 depth 32

All this info seems to be referring to a PNG picture (like a GIF or BMP or JPG or whatever) I think the 666 etc is referring to the size of an image - are you running a game with artwork? is Artwork switched on in mame.ini?

[Minwah]

All this info seems to be referring to a PNG picture (like a GIF or BMP or JPG or whatever) I think the 666 etc is referring to the size of an image - are you running a game with artwork? is Artwork switched on in mame.ini?

I'm sure you're right Silver...turn artwork off.

[terabit]

Last night I decided to run Mame32 and it seems to work fine with all the games. I just decided not to use Mamewah as my front end. Not a big deal really.

I just saw the latest post of Minwah and Silver and my art work was turned on. When I turned it off it worked. There still is a little adjusting to do, but that can be done with the monitor adjustment. I have noticed that the new Mame32 has more of the games perfectly on the screen without any monitor adjustment than the Mame command line, but both are great. I am going to have a track ball so using Mame32 does not seem to bad. I kind of like the layout. What are the negatives of the Mame32?
 
I just want to thank Minwah and Silver for your suggestions. I have really learned a lot the last couple of days.

Now the next phase is mounting that 27 inch monitor into an old "Knuckle Heads" arcade cabinet. Wish me luck.
Glenn

[Minwah]

What are the negatives of the Mame32?

Basically just that is looks pretty bad on a cabinet IMO.  It is exactly the same as MAME, but with a GUI lobbed on, so you should be able to get MAME to work the same as MAME32 - if not there is a config issue somewhere.  I suspect MAME32 is using high resolution(s) (640x480 etc.), which defeats the point a little.  Remember once you have adjusted your screen for each mode once you shouldn't have to do it again...

Good luck with the rest of your project