Software Support > GroovyMAME
Horizontal Glitch Line At Top Of Vertical Games
bumble:
I am running GoovyMame0244 with CRT Emudriver on a 25 inch K7000. My machine is in a horizontal position, so when running vertical games I ran into a problem where the game was going off screen, both top and bottom. Searching for answers I stumbled upon this post:
http://forum.arcadecontrols.com/index.php?topic=155575.0
A suggestion Calamity made was to create a custom veritcal.ini file with the following line:
--- Code: ---crt_range0 15625-16200, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 240, 448, 480
--- End code ---
This does work, however it seems to be producing a side effect where the very top of the screen has a horizontal glitch, on all vertical games. An example picture is attached of Galaga. It happens on all vertical games I tested. This does not happen if I remove vertical.ini and resize the screen to see the top.
In the code line above, if I change "240" back to "288" and resize my screen to be able to see the top, the glitch is not present. It seems specifically related to the reduction of the vertical lines, though I am not sure.
Attached is a log file of the game running with the glitch.
Any help would be greatly appreciated!
Zebidee:
Galaga has 288 vertical lines. If you only have 240 lines, some lines will have to get squished.
You'll have this problem for most vertical games.
Running in horz mode with 288 vertical lines will have the wrong vertical freq (closer to 50hz) for Galaga, but GM can compensate for that.
Otherwise, you would need to run vertical games in an interlaced mode to get enough lines.
Does this help?
makya:
bumble, according to your log (see excerpts below) you are running the game at 480i. When you put back 288 instead of 240, probably GM picks 288p. Can you try setting your desktop resolution to 2560x480 and check whether the glitch also appears out of GM ?
Switchres: get_mode(0) 288 224 60.606061 1.333333
Switchres: Calculating best video mode for 288x224@60.606060 orientation: rotated
Switchres: Modeline "2560x480_30i 15.787879KHz 60.606060Hz" 52.620999 2560 2665 2912 3333 480 482 488 521 interlace -hsync -vsync
Switchres: updated AMD ADL timing "2560x480_30i 15.787879KHz 60.606060Hz" 52.620999 2560 2665 2912 3333 480 482 488 521 interlace -hsync -vsync
lilshawn:
--- Quote from: Zebidee on October 05, 2022, 02:42:21 am ---Galaga has 288 vertical lines. If you only have 240 lines, some lines will have to get squished.
You'll have this problem for most vertical games.
Running in horz mode with 288 vertical lines will have the wrong vertical freq (closer to 50hz) for Galaga, but GM can compensate for that.
Otherwise, you would need to run vertical games in an interlaced mode to get enough lines.
Does this help?
--- End quote ---
just to expand a bit, galaga runs on a horizontal monitor...rotated 90 degrees vertically... so at 240x320
your horizontally oriented monitor has 320x240 worth of pixels to work with. Galaga's "width" of 240 is fine, and fits within your monitor's 320 available horizontal pixels... but the Galaga's game "height" of 320 pixels is a little hard to fit in a screen with only 240 lines of resolution the monitor has available in the vertical dimension.
bumble:
Thank you everyone for your replies!
--- Quote ---bumble, according to your log (see excerpts below) you are running the game at 480i. When you put back 288 instead of 240, probably GM picks 288p. Can you try setting your desktop resolution to 2560x480 and check whether the glitch also appears out of GM ?
--- End quote ---
That worked! I don't have enough time at the moment to go further with this information, but I don't really understand why the game would be running at 480i. Of course the monitor is set to that, but I was under the assumption that the mode list was changing the resolution of the game while running. I'm sure there is something I'm not understanding.
Do I somehow automatically change the desktop resolution when a vertical game is launched to 2560x480, or is there a cleaner solution?
Navigation
[0] Message Index
[#] Next page
Go to full version