Build Your Own Arcade Controls Forum
Main => Main Forum => Topic started by: leapinlew on July 06, 2006, 09:59:15 pm
-
I just can't seem to get Gorf to run at any decent speed. It speeds up and slows down. Here is what I have:
Pentiun 4 3 ghz
512mb ram
Mame .106
Here is what I've done so far:
Run Gorf with just command line and through FE - both were slow
(when I quit from command line, it says Average FPS: 59.999828)
Pressed F10, the result is it would play way too fast
I downloaded a .69 version of mame and it played Gorf just fine. Same number of frames.
Anyone have any ideas? I want to use the .106 version because I'm playing some newer games, but I want to also play gorf. The .69 version of mame didn't have a mame.ini but the .106 version does. Could any of these settings be causing my problems?
### mame.ini ###
### Frontend Related ###
### Windows path and directory options ###
rompath roms
samplepath samples
# inipath <NULL> (not set)
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
comment_directory comments
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_gamma 1.000000
frames_to_run 0
effect none
screen_aspect 4:3
# mngwrite <NULL> (not set)
### 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
priority 0
### Windows sound options ###
audio_latency 1
# wavwrite <NULL> (not set)
### Input device options ###
mouse 1
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 ###
validate 0
artwork 1
use_backdrops 1
use_overlays 1
use_bezels 1
artwork_crop 0
artwork_resolution 0
cheat 0
debug 0
# debugscript <NULL> (not set)
# playback <NULL> (not set)
# record <NULL> (not set)
log 0
oslog 0
skip_gameinfo 0
bios default
# state <NULL> (not set)
autosave 0
### Configuration options ###
readconfig 1
verbose 0
skip_warnings 1
skip_disclaimer 1
skip_gameinfo 1
-
Hmmm, I get this slowdown - only on the Galaxians level - on 106u10.
Everything reports 100% 60/60 fps, and there is lots of power to spare (removing throttle runs it at 300%).
It looks like emulated slowdown (a la double dragon) except this appears to be far too slow to be accurate - although I am not familar enough with the orginal gorf.
-
It's a known MAME bug -- I submitted it to mametesters back in v101 or v102 (I forget). I can't remember the exact version where they broke it, but I think something before v100 will work better. The bug is gorf0102u5yel on mametesters.org if you're interested.
EDIT: oops I think the version is in the bug name, so it looks like it broke in v102u5.
-
Ok thanks - I searched on mametesters before I posted the reply, so I must have missed it....
EDIT: No I found it, but its just listed as:
"On the Galaxian level especially, the sounds and sprites completely lock up at times."
There is no locking up, just excessive slowdown.
-
I believe it was worse when it first broke. Everything ran really slow and it would periodically lock up for a couple seconds (even sound). It's not quite as bad now, but the timing is still way off. This is, in my opinion, the most significant bug in MAME right now, or at least the bug I am most eager to see fixed. :hissy: