The NEW Build Your Own Arcade Controls
Main => Software Forum => Topic started by: nut854 on April 25, 2006, 08:48:45 pm
-
I'm using MameWah 1.61 and it's going pretty well. I'm rockin out to PacMan, SmashTv, and the Simpsons.
Problem: A small portion of the left side of the screen is cut off. It's probably 30-40 pixels, but it's very noticable in some games. When I use Mame without MameWah, I don't have this problem, so I figure it must be MameWah and not my Mame configs or my hardware. Nosafelaunch and all that jaz doesn't help. Any suggestions? I've looked everywhere.
thnx all
-
Assuming you're using a pc monitor...adjust it!
I expect you are using MAME's 'resolution auto' and it is picking a different mode from Mamewah to when Mame is launched on it's own (this is common...not sure why it happens). You could also use game-specific ini files to explicitly specify what resolution to use for each game...
-
hmmm thanks. I've had a new development.. Yes, I'm using a PC monitor. It's an LCD screen. When I play certain games, like Altered Beast for example, my monitor gives me a warning:
"Out of Range
Warning
Pixel Rate is Over limit.
Horizontal: something
Vertical: something"
I can't get rid of it. Might this have something to do with the problem?
Also, this problem is especially weird since it didn't happen a week ago. Well kinda... it would happen when I would use binary Mame with MameWah, but it wouldnt happen when I would use MAME32 with MameWah. The games were perfectly centered in the screen with MAME32. Now no matter what I use as the emulator, the screen is always off.
I doubt you can help much more, but I figured I'd give as much detail to help out in future development.
Thanks!
-
Yep, this is a MAME configuration issue as I said. Best bet if your using a LCD screen is to edit \mame\mame.ini, and specify the resolution your screen is designed for...eg:
resolution 1024x768
...this will set this mode for all games, which is best for your screen since LCD's only (generally) work well at one resolution.
FYI, this is not a Mamewah or Mame bug/problem...just a config issue.