Main > Main Forum

Mame ui_key_start

Pages: << < (2/2)

Dazz:


--- Quote from: VanillaGorilla on December 27, 2010, 10:40:10 am ---One big thing with Hyperspin, as I have found:

Don't waste your time configuring MAME's ini settings via the MAME UI while launching it with Hyperspin. MAME does not appear to be able to save its config changes when launched from Hyperspin. Run MAME standalone [mame.exe] instead if you are setting up mame via the embedded interface, or changing your mame.ini file. This also goes if , for example you use any of the video mode tweaks on a per-game basis; Bezel artwork, custom pixel dimensions, color overlays etc. They wont save cfg or ini changes when launched with Hyperspin. This may be more closely tied to whether or not you are using an AHK to launch MAME, or Hyperspin by way of a command line string.

--- End quote ---
This is actually incorrect...  Simply do not select HyperLaunch on your MAME settings within HyperHQ.  The HyperLaunch script causes emulators to force quit which does not allow the emu to go through the close processes.  In this case MAME saves the settings upon exit and if it is force quit then it's not going to save settings.  MAME is a command line application and doesn't need HyperLaunch anyway.

newmanfamilyvlogs:

Well problem fixed, mystery unsolved.

I decided to just rebuild my whole mame folder from scratch. Moved the roms, sta, and hi folders, copied the bare .EXE and went from there.

Still no clue what actually happened. I went so far as to even use Proccess Monitor to look at the files that it was accessing to see if anything was odd, but nothing looked unusual.

Weird.

VanillaGorilla:

alls well that ends well.  :cheers:

Pages: << < (2/2)

Go to full version