Main > Software Forum
resolution assistance
dax:
I'm going to dump whatever files I can in hopes of figuring out WTF is wrong..
\mame\error.log:
using performance counter for timing ... cycles/second = 1193180
width 384, height 256 depth 16
set visible area 0-0 0-0
set visible area 64-447 128-383
Physical width 640, height 480
Machine reset
Warning: sound latch 0 written before being read. Previous: 00, new: 20
cpu #0 (PC=00010413): unmapped I/O byte write to 0000008C = 10
cpu #0 (PC=00010413): unmapped I/O byte write to 0000008D = 00
cpu #1 (PC=000001EF): unmapped I/O byte write to 00000087 = 00
cpu #1 (PC=000001FC): unmapped I/O byte write to 00000087 = 01
cpu #1 (PC=000001EF): unmapped I/O byte write to 00000087 = 00
cpu #1 (PC=000001FC): unmapped I/O byte write to 00000087 = 01
(some of this data may be old, I don't know)
\mame\mamewah\mamewah.log (Note this indicates the 800x600 resolution - which is where things are wrong -- further evidence Mamewah has something to do with this?):
1/9/06 1:59:02 PM MAMEWAH launched
1/9/06 1:59:02 PM Desktop colour: 0
1/9/06 1:59:02 PM Wallpaper filename:
1/9/06 1:59:02 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 1:59:02 PM Decimal symbol: '.'
1/9/06 1:59:03 PM Games list read: mame-0.lst
1/9/06 1:59:05 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 1:59:06 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 1:59:10 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 {flags=17}
1/9/06 1:59:28 PM MAMEWAH quit
1/9/06 2:01:12 PM MAMEWAH launched
1/9/06 2:01:12 PM Desktop colour: 0
1/9/06 2:01:12 PM Wallpaper filename:
1/9/06 2:01:12 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 2:01:12 PM Decimal symbol: '.'
1/9/06 2:01:12 PM Games list read: -0.lst
1/9/06 2:01:13 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 2:01:13 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 2:01:19 PM MAMEWAH quit
1/9/06 2:02:10 PM MAMEWAH launched
1/9/06 2:02:10 PM Desktop colour: 0
1/9/06 2:02:10 PM Wallpaper filename:
1/9/06 2:02:10 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 2:02:10 PM Decimal symbol: '.'
1/9/06 2:02:10 PM Games list read: mame-0.lst
1/9/06 2:02:11 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 2:02:11 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 2:02:14 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 {flags=9}
1/9/06 2:02:35 PM MAMEWAH quit
1/9/06 2:02:55 PM MAMEWAH launched
1/9/06 2:02:56 PM Desktop colour: 0
1/9/06 2:02:56 PM Wallpaper filename:
1/9/06 2:02:56 PM Display mode: 800x600 @ 0Hz, 32 bit colour
1/9/06 2:02:56 PM Decimal symbol: '.'
1/9/06 2:02:56 PM Games list read: mame-0.lst
1/9/06 2:02:57 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay
1/9/06 2:02:57 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini
1/9/06 2:02:59 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 {flags=10}
1/9/06 2:03:13 PM MAMEWAH quit
Again, let me REITERATE that I can do this from DOS:
cd \mame
mamep102.exe rtype2
and the game runs perfectly in 392x240 resolution as indicated in \mame\ini\rtype2.ini
as you can see from the logs above, MameWah is also running the same version of mame, but it throws it into 800x600. Note that this is the command line version of Mame and not Mame32.
So what is wrong here?
dax:
Renaming mamep102.exe to mame.exe and changing the reference in the mamewah\ini\mame.ini file didn't make a difference.
Here's the version of mame.ini that's in \mame and \mame\ini
### MAMEP102.ini ###
### Frontend Related ###
### Windows path and directory options ###
rompath roms
samplepath samples
inipath ini
cfg_directory cfg
nvram_directory nvram
memcard_directory memcard
input_directory inp
hiscore_directory hi
state_directory sta
artwork_directory artwork
snapshot_directory snap
diff_directory diff
ctrlr_directory ctrlr
cheat_file cheat.dat
### Windows video options ###
autoframeskip 1
frameskip 0
waitvsync 0
triplebuffer 0
window 0
ddraw 1
direct3d 0
hwstretch 1
# screen <NULL> (not set)
cleanstretch auto
resolution auto
refresh 0
scanlines 0
switchres 1
switchbpp 1
maximize 1
keepaspect 1
matchrefresh 0
syncrefresh 0
throttle 1
full_screen_brightness 0.000000
frames_to_run 0
effect none
screen_aspect 4:3
### Windows Direct3D 2D video options ###
zoom 2
d3dtexmanage 1
d3dfilter 1
d3dfeedback 0
d3dscan 100
d3deffectrotate 1
d3dprescale auto
d3deffect none
# d3dcustom <NULL> (not set)
# d3dexpert <NULL> (not set)
### Windows misc options ###
sleep 1
rdtsc 0
high_priority 0
### Windows sound options ###
audio_latency 1
# wavwrite <NULL> (not set)
### Input device options ###
mouse 0
joystick 0
lightgun 0
dual_lightgun 0
offscreen_reload 0
steadykey 0
keyboard_leds 1
led_mode ps/2
a2d_deadzone 0.300000
# ctrlr <NULL> (not set)
paddle_device keyboard
adstick_device keyboard
pedal_device keyboard
dial_device keyboard
trackball_device keyboard
lightgun_device keyboard
digital none
### Mame CORE video options ###
norotate 0
ror 0
rol 0
autoror 0
autorol 0
flipx 0
flipy 0
gamma 1.000000
brightness 1.000000
pause_brightness 0.650000
### Mame CORE vector game options ###
antialias 1
translucency 1
beam 1.000000
flicker 0.000000
intensity 1.500000
### Mame CORE sound options ###
samplerate 44100
samples 1
sound 1
volume 0
### Mame CORE misc options ###
artwork 0
use_backdrops 1
use_overlays 1
use_bezels 1
artwork_crop 0
artwork_resolution 0
cheat 0
debug 1
# debugscript <NULL> (not set)
# playback <NULL> (not set)
# record <NULL> (not set)
log 1
oslog 1
skip_gameinfo 0
bios default
# state <NULL> (not set)
autosave 0
### Configuration options ###
readconfig 1
verbose 1
Minwah:
--- Quote from: dax on January 09, 2006, 03:10:12 pm ---\mame\mamewah\mamewah.log (Note this indicates the 800x600 resolution - which is where things are wrong -- further evidence Mamewah has something to do with this?):
--- End quote ---
All this part in Mamewah does is read your current (desktop) display settings...so that it can switch back to them after you quit Mamewah (if you are using a layout with a different mode to your desktop). Launch a few games and check the log and you'll see that line is only displayed once, after launching Mamewah.
Earlier on you said this was displayed:
'loading roms..
parsing mamep102.ini ... N/A
parsing drivers/m72.ini ... N/A
parsing rtype2.ini ... OK'
...does that still happen if you run Mame from a command prompt? If so we need to figure out why mamep102.ini isn't being parsed. What I suggest is the following:
Move any non-Windows commandline versions of Mame (dos mame inc. mame.cfg, mame32 etc. and associated files into another directory out of the way,
Make sure your (Windows commandline) Mame executable is called mame.exe,
Delete any ini files you have in the \mame folder (leave the ones in the \mame\ini folder tho),
Go to a command prompt and do a 'mame -cc' to create a fresh mame.ini,
Leave mame.ini as default and run a game - see if mame.ini is parsed.
Next you could change a few obvious settings (not the inipath one tho) to make sure the settings are taking effect - set the resolution to 1024x768 or something (assuming you're not using an arcade monitor).
If the above works you should be almost there...
dax:
Minwah,
Thanks very much for your assistance here. I'm still having problems. I did everything you suggested. I wiped all the ini and cfg files and created them from scratch. No luck. I did notice that if mame.ini is in \mame it shows <null> for inipath, but if you move mame.ini to \mame\ini it will show properly when mame -sc is run.
To clean things up, I've installed Mame 0.69 and am running the i686 version (which is not the "dos" version so I assume this is the "windows command line" version you mention).
I am still having problems and I just don't know what is going on.
Many games, when run from MameWah, show in the wrong resolution. But I can open a DOS window from Win98 and type "mame (gamename)" and they display perfectly. It seems like when invoked from MameWah, the .ini files are being ignored.
I am at my wits end. I just can't figure out why from MameWah, things don't work right. I've removed all extraneous config files, all other Mame versions and it's still messed up.
Could this possibly have anything to do with my directory structure?
Mame's root is c:\mame, but MameWah is in c:\mame\mamewah
When MameWah invokes mame, does it change the directory to c:\mame? If not, this could possibly be the problem, and I'm wondering if I moved MameWah's files into c:\mame, would this help? I'd prefer not to do that and mix that stuff together. Plus, MameWah expects a mame.ini in it's ini folder that is different from what Mame expects in a similar path. But I tried the -inipath parm in the config and that didn't work.
Any help? Anybody? I'm so close to having all of this working beautifully and I really like MameWah, but I cannot for the life of me figure out why the games are displaying in the wrong resolution... any help from anybody would be much appreciated!!
dax:
--- Quote from: subcriminal on January 03, 2006, 12:11:20 pm ---If the inipath is set correctly in mame.cfg. It should read the resolution ok. Have you opened a cmd prompt and typed 'mame gamename -verbose'? When you exit the game there'll be some info in the cmd prompt to tell you if the ini file was read or not. I had a problem with the mamewah res tool generating ini files that mame didn't recognise, I cleared the folder and regenerated them and it worked. Strange.
--- End quote ---
I've done all that. The problem is, when I run Mame from the command line manually, everything works perfect. It's only when it's run from MameWah that things are messed up.
Navigation
[0] Message Index
[*] Previous page
Go to full version