| Main > Software Forum |
| resolution assistance |
| (1/3) > >> |
| dax:
I'm hoping someone can help me with this issue. I keep working on settings and just do not know what's wrong. First, I have a P3-550 running two versions of mame: .69 dos and 102. I think the computer is too slow to run 102, but .69 runs well. The problem is there are differences in how these two versions work and read config/rom info and I can't seem to get straight answers on the details. I have a ArcadeVGA card and can't seem to figure out how to force the proper video modes for the games. When I run 0.69 from ArcadeOS the video modes generally look really nice. When I run 102 from MameWAH, the modes are horrible if they display at all (I have to hit ALT-ESC after the screen blanks to get the "ok" screen, and the resolution looks to be something like 640x480). 1. Does 0.69 read the .ini files in /mame/ini ? Or does it use that older .cfg style? I am playing around with running .69 and .102 in Mamewah to figure out if the different versions read the same config files - I cannot figure this out yet. 102 seems to not work properly except the mame32 version. 0.69 runs much better, so I'm assuming it has better code to select monitor mode or isn't confused by some other ini file? And does anybody know what mame.dat does? What files and things to do I need to get working to get the game resolutions proper? EDIT: removed some questions I got answers for |
| dax:
Update... I figured out the Mamewah resolution generation tool and got it working. The problem is the sequence of events you need to do are not clearly outlined (if you update the game list, alter the resolution, auto-generate native resolutions and generate ini files out of sequence, it un-does previous settings). Now that I've gotten the ini files generated, I can't seem to get the windows command line version of mame102 to read them when called from Mamewah and I still don't know why. |
| subcriminal:
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. |
| dax:
Thanks for the reply! I still have this problem. MameWah just shows every game in the same, high resoluion... My directory setup is this: c:\mame (standard with all the roms, artowrk, ini, etc) c:\mame\mamewah (contains the Mamewah files, mamewah's ini dir, etc.) I have two versions of mame in the c:\mame directory, mamep102.exe and dmame.exe (0.69 that I use with ArcadeOS) Now IF these two versions create files of the same name somewhere that conflict with other versions, this might have something to do with the problem, but I can run 0.69 through AOS with no trouble, and then command line mamep102 from DOS or Mame32, but just not Mamewah - it does not work. (mamep102 is the windows command line version of mame) I notice that since I renamed the program to mamep102.exe, it expects to see mamep102.ini - so I have that file set up, and I've made copies of it everywhere trying to figure out where MameWah expects it to be, because it sure as hell isn't looking for it in \mame for some reason... when I run from Mamewah here's what I get: (running RType II for example) loading roms.. parsing mamep102.ini ... N/A parsing drivers/m72.ini ... N/A parsing rtype2.ini ... OK ... It finds the .ini file for rtype2, but it doesn't find the mamep102.ini??? This doesn't make sense since the rtype2.ini file would be in the standard mame path, just like where mamep102.ini is. Here are my config file contents: /mame/mamewah/mamewah.ini: ### mamewah.ini (mamewah v1.61) ### ### (Global) Screen-Saver Options ### delay 300 slide_duration 3 ### Audio Options ### enable_sounds 1 sound_volume 100 music_path enable_music 1 music_volume 100 ### Movie Options ### intro_movie_file exit_movie_file keep_movie_preview_aspect game_aspect delay_before_movie_preview 2 music_movie_mix mute_movies movie_volume 100 ### Misc Options ### layout Classic 640x480 ctrlr wrap_list 0 remember_current_game 1 keep_image_aspect 1 refresh_images 0 correct_orientations horizontal safe_mode 0 show_cursor 0 keyboard_led_states -,-,- winipac_file mamewah_ipc_file lcd_com_port 1 lcd_settings exit_action windows /mame/mamewah/ini/mame.ini: ### mame.ini (mamewah v1.61) ### emulator_title M.A.M.E. ### List Generation Settings ### rom_path c:\mame\roms rom_extension zip dat_file c:\mame\arcadeos\mame.dat nms_file catver_ini_file list_generation_method rom_folder_vs_listinfo ### Execution Settings ### emulator_executable c:\mame\mamep102.exe commandline_format [name] -readconfig alt_commandline_format_1 [name]{autodosbox}{nosafelaunch} alt_commandline_format_2 [name]{autodosbox}{nosafelaunch} game_specific_config_path ### Artwork Locations ### artwork_1_image_path c:\mame\snap artwork_2_image_path c:\mame\marquees artwork_3_image_path c:\mame\cabinets artwork_4_image_path c:\mame\cpanels artwork_5_image_path artwork_6_image_path artwork_7_image_path artwork_8_image_path artwork_9_image_path artwork_10_image_path movie_preview_path movie_artwork_no 1 ### Screen-Saver Settings ### enable_music_in_screensaver 1 saver_type slideshow \mame\mamep102.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 |
| dax:
Here's what the mamewah log shows: 1/4/06 12:37:25 PM MAMEWAH launched 1/4/06 12:37:25 PM Desktop colour: 0 1/4/06 12:37:25 PM Wallpaper filename: 1/4/06 12:37:25 PM Display mode: 800x600 @ 0Hz, 32 bit colour 1/4/06 12:37:25 PM Decimal symbol: '.' 1/4/06 12:37:25 PM Games list read: mame-0.lst 1/4/06 12:37:28 PM Layout selected: C:\MAME\MAMEWAH\layouts\Classic 640x480\layout.lay 1/4/06 12:37:29 PM Ctrlr file selected: C:\MAME\MAMEWAH\ctrlr\default.ini 1/4/06 12:37:34 PM Commandline run: c:\MAME\MAMEP102.EXE RTYPE2 -readconfig {flags=18} It still can't find the mamep102.ini. I put the file in both mamewah's directory and in \mame and Mamewah still doesn't find it... Where is it coming up with this 800x600 display mode???? If I put mamep102.ini in \mame\ini then when MameWah spawns mame, it reads the ini file, HOWEVER, it still shows every game in 800x600... arg! |
| Navigation |
| Message Index |
| Next page |