Gorf in MAME?

[cityside75]

OK everyone, fire up your MAME machines and check on something for me...

Does anyone else find Gorf to be almost unplayable in MAME? I have a pretty powerful system for MAME: 2800+ Athlon, a Gig of RAM, Radeon X800xt, etc. and everything else runs almost flawlessly in my Mame32 .102 setup.

The game plays extremely choppy, even though the framerate displayed by MAME never waivers. I remember the original game was a little glitchy, but I don't remember it being nearly as bad as it is in MAME, it's almost unplayable.

The weird thing, is that I remember it being almost perfect years ago on like MAME 0.35 or so. But it has been messed up like this since at least .96, maybe longer.

Also, the explosion sound or sample for your ship exploding sounds all wrong to me. Is it just me???

It bothers me, because all of my other old favorites are basically perfect, but Gorf is seriously messed up.

[Kid Ice]

I keep multiple versions of MAME on my machine because of problems like this. There's always something that doesn't work right.

[NE146]

I thought Gorf was never right in Mame.. but it's been a while since I've checked and to be quite honest, unlike a lot of arcade games my memory of the original Gorf isn't crystal clear and there's no machine near me to check :(

But then again it's Mame.. look at Phoenix. It's all messed up as well :P

[Peale]

Just tried it on my AMD Athlon 1GHz. Full frame. I think you have a config issue. This is with the latest version.

Post your mame.ini here, and I'll take a look.

[cityside75]

Thanks everyone for your feedback so far.

OK, Peale here is my MAME32.ini file. Keep in mind like I said above, everything else is working great. I have toggled many of these settings to try and fix it as well. Let me know what you think:

### global-only options ###

rompath D:\MAME\roms
samplepath D:\MAME\samples
inipath D:\MAME\mame32\Mame32\ini
cfg_directory D:\MAME\cfg
nvram_directory nvram
memcard_directory memcard
input_directory inp
hiscore_directory D:\MAME\hi
state_directory sta
artwork_directory D:\MAME\artwork
snapshot_directory D:\MAME\snap
diff_directory diff
cheat_file cheat.dat
ctrlr_directory ctrlr

### default game options ###

autoframeskip 1
frameskip 0
waitvsync 0
triplebuffer 1
window 0
ddraw 1
hwstretch 1
resolution 1024x768x0
refresh 0
scanlines 0
switchres 1
switchbpp 1
maximize 1
keepaspect 1
matchrefresh 0
syncrefresh 0
throttle 1
full_screen_brightness 1.
frames_to_run 0
effect none
screen_aspect 4:3
cleanstretch none
zoom 2
d3d 1
d3dtexmanage 1
d3dfilter 1
d3deffect auto
d3dprescale auto
d3deffectrotate 1
d3dscan 100
d3dfeedback 100
mouse 1
joystick 0
a2d 0.3
steadykey 0
lightgun 0
dual_lightgun 0
offscreen_reload 0
ctrlr HotRodSE
brightness 1.
pause_brightness 0.65
norotate 0
ror 0
rol 0
autoror 0
autorol 0
flipx 0
flipy 0
gamma 1.
antialias 1
translucency 1
beam 1.
flicker 0.
intensity 1.5
samplerate 44100
samples 1
sound 1
volume 0
audio_latency 1
artwork 1
backdrop 1
overlay 1
bezel 0
artwork_crop 0
artres 0
cheat 0
debug 0
log 0
sleep 0
rdtsc 0
leds 0
led_mode ps/2
high_priority 1
skip_gameinfo 1
bios 0
autosave 0

[Kid Ice]

Heh. I never noticed problems w/ Gorf or Phoenix. I didn't know the cabs initimately though.

[Peale]

Make these changes:

### default game options ###

autoframeskip 0
hwstretch 1
resolution 640x480
artwork 0


Or just make a new gorf.ini file and put this in there.

I would change autoframeskip to zero no matter what, anyway.

[cityside75]

Thanks for the feedback, I'll try this and see if there is any improvement. I did just find a post in the forums of mameworld.net saying that Gorf is broken in .102, although I've been having the problem since before this version.