GroovyMAME 0.220
- Thread starter JonnyG
- Start date
tronads said:
Here it is!
Hope you can find something fixable in there:
#
# CORE CONFIGURATION OPTIONS
#
readconfig 1
writeconfig 0
#
# CORE SEARCH PATH OPTIONS
#
homepath .
rompath roms;f:roms
hashpath hash
samplepath samples
artpath artwork
ctrlrpath ctrlr
inipath .;ini;ini/presets
fontpath .
cheatpath cheat
crosshairpath crosshair
pluginspath plugins
languagepath language
swpath software
#
# CORE OUTPUT DIRECTORY OPTIONS
#
cfg_directory cfg
nvram_directory nvram
input_directory inp
state_directory sta
snapshot_directory snap
diff_directory diff
comment_directory comments
#
# CORE STATE/PLAYBACK OPTIONS
#
state
autosave 0
rewind 0
rewind_capacity 100
playback
record
record_timecode 0
exit_after_playback 0
mngwrite
aviwrite
wavwrite
snapname %g/%i
snapsize auto
snapview internal
snapbilinear 1
statename %g
burnin 0
#
# CORE PERFORMANCE OPTIONS
#
autoframeskip 0
frameskip 0
seconds_to_run 0
throttle 1
syncrefresh 0
autosync 1
sleep 1
speed 1.0
refreshspeed 0
#
# CORE RENDER OPTIONS
#
keepaspect 1
unevenstretch 1
unevenstretchx 0
unevenstretchy 0
autostretchxy 0
intoverscan 0
intscalex 0
intscaley 0
#
# CORE ROTATION OPTIONS
#
rotate 1
ror 0
ror 0
autoror 0
autorol 0
flipx 0
flipy 0
#
# CORE ARTWORK OPTIONS
#
artwork_crop 0
use_backdrops 0
use_overlays 0
use_bezels 0
use_cpanels 0
use_marquees 0
fallback_artwork
override_artwork
#
# CORE SCREEN OPTIONS
#
brightness 1.0
contrast 1.0
gamma 1.0
pause_brightness 0.65
effect none
#
# CORE VECTOR OPTIONS
#
beam_width_min 1.0
beam_width_max 1.0
beam_intensity_weight 0
flicker 0
#
# CORE SOUND OPTIONS
#
samplerate 48000
samples 1
volume 0
#
# CORE INPUT OPTIONS
#
coin_lockout 1
ctrlr
mouse 0
joystick 1
lightgun 0
multikeyboard 0
multimouse 0
steadykey 0
ui_active 0
offscreen_reload 0
joystick_map auto
joystick_deadzone 0.3
joystick_saturation 0.85
natural 0
joystick_contradictory 0
coin_impulse 0
#
# CORE INPUT AUTOMATIC ENABLE OPTIONS
#
paddle_device keyboard
adstick_device keyboard
pedal_device keyboard
dial_device keyboard
trackball_device keyboard
lightgun_device keyboard
positional_device keyboard
mouse_device mouse
#
# CORE DEBUGGING OPTIONS
#
verbose 0
log 0
oslog 0
debug 0
update_in_pause 0
debugscript
#
# CORE COMM OPTIONS
#
comm_localhost 0.0.0.0
comm_localport 15112
comm_remotehost 127.0.0.1
comm_remoteport 15112
comm_framesync 0
#
# CORE MISC OPTIONS
#
drc 1
drc_use_c 0
drc_log_uml 0
drc_log_native 0
bios
cheat 0
skip_gameinfo 1
uifont ui.bdf
ui cabinet
ramsize
confirm_quit 0
ui_mouse 1
language English
nvram_save 1
#
# SCRIPTING OPTIONS
#
autoboot_command
autoboot_delay 0
autoboot_script
console 0
plugins 1
plugin
noplugin
#
# HTTP SERVER OPTIONS
#
http 0
http_port 8080
http_root web
#
# CORE SWITCHRES OPTIONS
#
modeline_generation 1
monitor generic_15
orientation horizontal
connector auto
interlace 1
doublescan 1
super_width 2560
changeres 1
powerstrip 0
lock_system_modes 1
lock_unsupported_modes 1
refresh_dont_care 0
dotclock_min 0
sync_refresh_tolerance 2.0
frame_delay 0
vsync_offset 0
black_frame_insertion 0
modeline auto
ps_timing auto
lcd_range auto
crt_range0 auto
crt_range1 auto
crt_range2 auto
crt_range3 auto
crt_range4 auto
crt_range5 auto
crt_range6 auto
crt_range7 auto
crt_range8 auto
crt_range9 auto
#
# OSD KEYBOARD MAPPING OPTIONS
#
uimodekey SCRLOCK
#
# OSD FONT OPTIONS
#
uifontprovider auto
#
# OSD OUTPUT OPTIONS
#
output auto
#
# OSD INPUT OPTIONS
#
keyboardprovider auto
mouseprovider auto
lightgunprovider auto
joystickprovider auto
#
# OSD DEBUGGING OPTIONS
#
debugger auto
debugger_font auto
debugger_font_size 0
watchdog 0
#
# OSD PERFORMANCE OPTIONS
#
numprocessors auto
bench 0
#
# OSD VIDEO OPTIONS
#
video d3d
numscreens 1
window 0
maximize 1
waitvsync 0
monitorprovider auto
#
# OSD PER-WINDOW VIDEO OPTIONS
#
screen auto
aspect auto
resolution auto
view auto
screen0 auto
aspect0 auto
resolution0 auto
view0 auto
screen1 auto
aspect1 auto
resolution1 auto
view1 auto
screen2 auto
aspect2 auto
resolution2 auto
view2 auto
screen3 auto
aspect3 auto
resolution3 auto
view3 auto
#
# OSD FULL SCREEN OPTIONS
#
switchres 1
#
# OSD ACCELERATED VIDEO OPTIONS
#
filter 0
prescale 1
#
# OpenGL-SPECIFIC OPTIONS
#
gl_forcepow2texture 0
gl_notexturerect 0
gl_vbo 1
gl_pbo 1
gl_glsl 0
gl_glsl_filter 1
glsl_shader_mame0 none
glsl_shader_mame1 none
glsl_shader_mame2 none
glsl_shader_mame3 none
glsl_shader_mame4 none
glsl_shader_mame5 none
glsl_shader_mame6 none
glsl_shader_mame7 none
glsl_shader_mame8 none
glsl_shader_mame9 none
glsl_shader_screen0 none
glsl_shader_screen1 none
glsl_shader_screen2 none
glsl_shader_screen3 none
glsl_shader_screen4 none
glsl_shader_screen5 none
glsl_shader_screen6 none
glsl_shader_screen7 none
glsl_shader_screen8 none
glsl_shader_screen9 none
#
# OSD SOUND OPTIONS
#
sound auto
audio_latency 2.0
#
# PORTAUDIO OPTIONS
#
pa_api none
pa_device none
pa_latency 0
#
# BGFX POST-PROCESSING OPTIONS
#
bgfx_path bgfx
bgfx_backend auto
bgfx_debug 0
bgfx_screen_chains default
bgfx_shadow_mask slot-mask.png
bgfx_avi_name auto
#
# WINDOWS PERFORMANCE OPTIONS
#
priority 0
profile 0
#
# WINDOWS VIDEO OPTIONS
#
menu 0
#
# DIRECT3D POST-PROCESSING OPTIONS
#
hlslpath hlsl
hlsl_enable 0
hlsl_oversampling 0
hlsl_write auto
hlsl_snap_width 2048
hlsl_snap_height 1536
shadow_mask_tile_mode 0
shadow_mask_alpha 0.0
shadow_mask_texture shadow-mask.png
shadow_mask_x_count 6
shadow_mask_y_count 4
shadow_mask_usize 0.1875
shadow_mask_vsize 0.25
shadow_mask_uoffset 0.0
shadow_mask_voffset 0.0
distortion 0.0
cubic_distortion 0.0
distort_corner 0.0
round_corner 0.0
smooth_border 0.0
reflection 0.0
vignetting 0.0
scanline_alpha 0.0
scanline_size 1.0
scanline_height 1.0
scanline_variation 1.0
scanline_bright_scale 1.0
scanline_bright_offset 0.0
scanline_jitter 0.0
hum_bar_alpha 0.0
defocus 0.0,0.0
converge_x 0.0,0.0,0.0
converge_y 0.0,0.0,0.0
radial_converge_x 0.0,0.0,0.0
radial_converge_y 0.0,0.0,0.0
red_ratio 1.0,0.0,0.0
grn_ratio 0.0,1.0,0.0
blu_ratio 0.0,0.0,1.0
saturation 1.0
offset 0.0,0.0,0.0
scale 1.0,1.0,1.0
power 1.0,1.0,1.0
floor 0.0,0.0,0.0
phosphor_life 0.0,0.0,0.0
#
# NTSC POST-PROCESSING OPTIONS
#
yiq_enable 0
yiq_jitter 0.0
yiq_cc 3.57954545
yiq_a 0.5
yiq_b 0.5
yiq_o 0.0
yiq_p 1.0
yiq_n 1.0
yiq_y 6.0
yiq_i 1.2
yiq_q 0.6
yiq_scan_time 52.6
yiq_phase_count 2
#
# VECTOR POST-PROCESSING OPTIONS
#
vector_beam_smooth 0.0
vector_length_scale 0.5
vector_length_ratio 0.5
#
# BLOOM POST-PROCESSING OPTIONS
#
bloom_blend_mode 0
bloom_scale 0.0
bloom_overdrive 1.0,1.0,1.0
bloom_lvl0_weight 1.0
bloom_lvl1_weight 0.64
bloom_lvl2_weight 0.32
bloom_lvl3_weight 0.16
bloom_lvl4_weight 0.08
bloom_lvl5_weight 0.06
bloom_lvl6_weight 0.04
bloom_lvl7_weight 0.02
bloom_lvl8_weight 0.01
#
# FULL SCREEN OPTIONS
#
triplebuffer 0
full_screen_brightness 1.0
full_screen_contrast 1.0
full_screen_gamma 1.0
#
# INPUT DEVICE OPTIONS
#
global_inputs 0
dual_lightgun 0
#
# FRONTEND COMMAND OPTIONS
#
dtd 1
Ok, nothing is really jumping out at me, but I do have 1 or 2 differences you could try :
1. in # CORE PERFORMANCE OPTIONS i also have the line:
lowlatency 1
2. These are my OSD Sound Options:
#
# OSD SOUND OPTIONS
#
sound portaudio
audio_latency 0
3. my PORTAUDIO settings are these :
#
# PORTAUDIO OPTIONS
#
pa_api "Windows WDM-KS"
pa_device "Speakers (Realtek HD Audio output)"
pa_latency 0
1. in # CORE PERFORMANCE OPTIONS i also have the line:
lowlatency 1
2. These are my OSD Sound Options:
#
# OSD SOUND OPTIONS
#
sound portaudio
audio_latency 0
3. my PORTAUDIO settings are these :
#
# PORTAUDIO OPTIONS
#
pa_api "Windows WDM-KS"
pa_device "Speakers (Realtek HD Audio output)"
pa_latency 0
Also, I don't think you have correctly configured your resolutions as your core switchres options crt_range0 looks wrong to me. On both my machines this contains the modes that vmmaker has discovered like this :
crt_range0 15625-15750, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576
crt_range0 15625-15750, 49.50-65.00, 2.000, 4.700, 8.000, 0.064, 0.192, 1.024, 0, 0, 192, 288, 448, 576
cools said:
Suppression = No-Nag
RygarR said:
I've not used Chunksin's installer so unsure how much it automates but you want to make sure you've got CRTemu Drivers installed and that VMMaker has been run, otherwise GM isn't really going to be doing much.
Really straightforward guide here for you from GM dev...
http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=433
JonnyG2020-05-13 08:04:36
RygarR said:
Well VMMaker just determines what video modes your monitor is capable of, and it updates the ini file accordingly. You can run it multiple times without issue as far as I know.
It is in Richards guide to run it - check here on his video at 25:30 http://www.youtube.com/watch?v=6ZT1T2W3etg
Think I might have got your hopes up then I'm afraid. I just called it plugin as I remembered having to do something differently with the plugin system when it came out other than just the usual .ini edits. Can't remember exactly what though, was ages ago. These days I just extract the new binary over my current MAME folder and replace the mame64.exe with my GM build.
tronads said:
Morning Chaps,
Just to say, I've applied my meagre talents to this, and ended up having to reinstall everything again, with the same results. Doh!
I wonder if it has something to do with Kungfu Master having a slightly unusual video mode? When I think about it, it's always started way over-stetched vertically on my CRTs compared with all other games. I don't think I've had an install when you could see the score-line without shrinking the vertical size quite a bit. I do seem to recall that it worked OK in the past though.
Double checking video mode maker, I noticed that while it found gazillions of modes, it only installed 120 of them. So, I tried upping the default to 240, but it only installed 134... and KFM stayed the same. Maybe it's a quirk of my graphics card or set-up. Garragh! I've sunk more hours into trying to sort out KFM than I probably would have actually playing it. Lol!
I see Mr Chunksinis doing an update of his Gcoovy Mame / Attract Mode installer. Think I'll wait and give that a go when it's ready...
I was messing around with my build yesterday and copied the GM executable (thanks Jonny!) over the top of the version of MAME which I think is 207 and got a plugin error so I downloaded the full MAME 220 installer, replaced the existing version and copied the new GM exe over the top. Seems to be behaving itself now, did some of the plugin code change then? I'll add the portaudio settings, been meaning to get back to doing that, are these still the best settings to use?
sound portaudio
audio_latency 0
pa_api "Windows WDM-KS"
pa_latency 0.003
New build coming out this week, probably in the next few days if I can fit testing in. Hacking around with themes now trying to get text readable!
sound portaudio
audio_latency 0
pa_api "Windows WDM-KS"
pa_latency 0.003
New build coming out this week, probably in the next few days if I can fit testing in. Hacking around with themes now trying to get text readable!
Chunksin said:
I don't remember the plugin system changing as early as 207 but if its working now I suppose it must have. Best to update the binary along with the exe anyway I reckon. Never used port audio though! Feel free to sell me the virtues...
JonnyG2020-05-18 11:45:17
All about reducing audio latency, I don't profess to know the science behind it! Link here to GroovyMame install guide section: http://geedorah.com/eiusdemmodi/forum/viewtopic.php?pid=1547#p1547
The Kung Fu Master, the saga continues...
I never did get the sound fixed on Kungfu Master on my GroovyMame setup. That's probably because I'm an idiot ;-) But following on from Chunksin's last post, I've made a discovery which might be significant. Unfortuantely, I don't have the technical chops to figure out how!
It goes like this...
I had resigned myself to avoiding KFM until the next big update when I have to re-install everything anyway (don't fancy doing that again any time soon!). However, after playing Moon Patrol for the first time in ages, I found there was a slight problem with the sound on that too. So I came back to this thread with a view to starting again, and working through all the variables from the top.
I reinstalled the appropriate Calamity Drivers for my GPU, and re-ran VMM. So far so good.
Then, following the link posted by Chunksin, I spent about an hour and a half messing about with the MAME.ini file, trying out loads of different combinations of settings - as per the GroovyMame installation instructions.
Now, video-wise - the system doesn't look any different. It was pretty much bang on before.
Audio-wise - Moon Patrol seems to be fine now (fingers crossed!).
KungFu Master seemed OK initially after almost every tweak to the Audio settings, but by the end of level one, the music was distorting all over the place like a warped LP.
Something I hadn't done before was view the frameskip and %speed by pressing F11. With this being Mame, the trimmers on my arcade monitor are set to the best compromise position - and with KFM always producing a far taller image than every other game I play, these get cropped off the display. So, I shrunk the vertical size (genious move, eh?), turned on the speed display and had a play. And the reading... was all over the place - skipping from about 107% - 94% and everywhere in between, with the sound warping accordingly. Frameskip was set to 0. Changing this to auto made zero difference. Thing is, for every other game I tried after this, from Moon Patrol to Deathsmiles, the speed during gameplay was a rock solid 100%.
So what on Earth is going on with KFM?!?!?!
Any ideas?
I noticed some settings on the VMM console, including an extended arcade range - from 15.7 - 16.5 kHz, or something like that. Might selecting one of those and re-running VMM help?
Or could it be my graphics card? I've read posts on other forums suggesting that some ATI cards are less problematic than others. Can anyone confirm what cards they use on systems that are fully working?
Thanks in advance - again!
I never did get the sound fixed on Kungfu Master on my GroovyMame setup. That's probably because I'm an idiot ;-) But following on from Chunksin's last post, I've made a discovery which might be significant. Unfortuantely, I don't have the technical chops to figure out how!
It goes like this...
I had resigned myself to avoiding KFM until the next big update when I have to re-install everything anyway (don't fancy doing that again any time soon!). However, after playing Moon Patrol for the first time in ages, I found there was a slight problem with the sound on that too. So I came back to this thread with a view to starting again, and working through all the variables from the top.
I reinstalled the appropriate Calamity Drivers for my GPU, and re-ran VMM. So far so good.
Then, following the link posted by Chunksin, I spent about an hour and a half messing about with the MAME.ini file, trying out loads of different combinations of settings - as per the GroovyMame installation instructions.
Now, video-wise - the system doesn't look any different. It was pretty much bang on before.
Audio-wise - Moon Patrol seems to be fine now (fingers crossed!).
KungFu Master seemed OK initially after almost every tweak to the Audio settings, but by the end of level one, the music was distorting all over the place like a warped LP.
Something I hadn't done before was view the frameskip and %speed by pressing F11. With this being Mame, the trimmers on my arcade monitor are set to the best compromise position - and with KFM always producing a far taller image than every other game I play, these get cropped off the display. So, I shrunk the vertical size (genious move, eh?), turned on the speed display and had a play. And the reading... was all over the place - skipping from about 107% - 94% and everywhere in between, with the sound warping accordingly. Frameskip was set to 0. Changing this to auto made zero difference. Thing is, for every other game I tried after this, from Moon Patrol to Deathsmiles, the speed during gameplay was a rock solid 100%.
So what on Earth is going on with KFM?!?!?!
Any ideas?
I noticed some settings on the VMM console, including an extended arcade range - from 15.7 - 16.5 kHz, or something like that. Might selecting one of those and re-running VMM help?
Or could it be my graphics card? I've read posts on other forums suggesting that some ATI cards are less problematic than others. Can anyone confirm what cards they use on systems that are fully working?
Thanks in advance - again!