Author Topic: Save states are borked when MAME is upgraded. (Read 2430 times)

Shoegazer · « **on:** February 14, 2007, 02:31:24 pm »

I completely understand the rationale behind removing hiscore.dat, being that it was hacky to the point of intrusiveness. I also understand how infinitely cooler it is to have an entire state saved for any given system, as the far better alternative.

What I don't understand is why I get the "Failed to load state" message for every game that supports save states, every time I upgrade MAME. Is there something I'm doing wrong that causes this, or is the save state feature just not ready for prime time yet? It's frustrating to get some pretty nice scores going on certain games like Galaga, only to have them completely zeroized with each new upgrade.

Not trying to whine here, honest - but at the risk of offending Aaron or anyone else who may be developing this feature - I just hope this is either user error or something to be addressed soon. If the latter is true, I'll just increase my daily dose of patience and STFU.

Shoegazer

FrizzleFried · « **Reply #1 on:** February 14, 2007, 02:34:36 pm »

You hit the reason why I stopped using savestates right on the head. They are not compatible (for whatever reason) from version to version. Screw that. I just compile HISCORE.DAT support back in to Mame when I upgrade....

Havok · « **Reply #2 on:** February 14, 2007, 02:40:27 pm »

Quote from: FrizzleFried on February 14, 2007, 02:34:36 pm

You hit the reason why I stopped using savestates right on the head. They are not compatible (for whatever reason) from version to version. Screw that. I just compile HISCORE.DAT support back in to Mame when I upgrade....

Amen!

Savestate is the sux0r!

sewerrat · « **Reply #3 on:** February 14, 2007, 07:11:58 pm »

Quote from: FrizzleFried on February 14, 2007, 02:34:36 pm

You hit the reason why I stopped using savestates right on the head. They are not compatible (for whatever reason) from version to version. Screw that. I just compile HISCORE.DAT support back in to Mame when I upgrade....

Is there a "how-to" guide to be able to do this?
I cant seem to find one.

FrizzleFried · « **Reply #4 on:** February 14, 2007, 07:26:29 pm »

Download hiscore.txt here: http://forum.arcadecontrols.com/index.php?topic=63130.0

Change the name to hiscore.diff.

Then go here and read how to compile. It took me all of 20 minutes to figure out the first time and then another 30 minutes or so to compile....

http://www.mameworld.net/mrdo/compile.html

sewerrat · « **Reply #5 on:** February 14, 2007, 07:30:26 pm »

Thanks

SodaPopinksi · « **Reply #6 on:** February 14, 2007, 10:52:28 pm »

Awesome, I didn't know about this or how to do it, now I do. It should satisfy the George Costanza in all of us

Now to finish my cab and finally get to playing, almost, almost!!

DarkDraco · « **Reply #7 on:** February 15, 2007, 03:06:13 am »

i followed that guide the other day and for some reason my compiled version of mame wont play any roms. it just says files are missing

FrizzleFried · « **Reply #8 on:** February 15, 2007, 10:15:44 am »

Did you compile the correct HISCORE.DIFF? I assume you did as it would have likely errored out when you attempted to compile.

I don't know what to say? I haven't had any problems thus far. Are you having problems with ALL roms or just a select few?

What version were you updating from?

DarkDraco · « **Reply #9 on:** February 15, 2007, 11:47:31 am »

im using the 112u1 diff with 112u1 source. tried compiling twice and when i try to run galaga or pacman i get the error:

54xx.bin not found

FrizzleFried · « **Reply #10 on:** February 15, 2007, 11:49:38 am »

I dunno about Pac Man, but I DO know that Galaga has a new ROM set as of v112u1. You need a new ROM set for that. Also, try to run PUCK MAN instead of PAC MAN and see if it runs (PAC MAN is a clone actually).

DarkDraco · « **Reply #11 on:** February 15, 2007, 12:01:16 pm »

all the galagas new in 112u1? i tried all the versions and clones too, theres like 10 of them. can u tell me a game that works with 112 romset so i can test when i get home?

FrizzleFried · « **Reply #12 on:** February 15, 2007, 12:09:23 pm »

All clones use files from the parent set and the parent set has been changed. Try running a few other games or go get the new rom sets (there are like 15-20 new rom sets for 112u1 I believe).

FrizzleFried · « **Reply #13 on:** February 15, 2007, 12:13:30 pm »

Also, what was your last version you were running? If you are updating from an old version, MANY MANY MANY roms have changed between then and now, if you are updating from 112 itself (not u1), then only like 15 or so have changed.

This is from the latest WHATSNEW.TXT:

Quote

Replaced implementation of Namco 54xx sound chip with new MB8844 CPU
core running the original embedded ROM code. Removed old sound core.
Pole Position and Bosconian no longer require samples as a result.

So I am assuming that any game that errors out with 54xx error needs a new ROM set.

DarkDraco · « **Reply #14 on:** February 15, 2007, 12:16:05 pm »

i updated my romsets every mame update. so ive been up to date.i dont update romsets by updates, only the big releases .110, .111, .112 etc

Havok · « **Reply #15 on:** February 15, 2007, 02:45:08 pm »

There is a 112u1 ROM update - it came out yesterday. Somewhere...

DarkDraco · « **Reply #16 on:** February 15, 2007, 03:56:25 pm »

guess ill try updating my set to 112u1 to see what happens. but i did just run puckman and it worked but the highscore was blank and when i got a score on there and exited it didnt save. so meh T_T

DarkDraco · « **Reply #17 on:** February 15, 2007, 06:02:07 pm »

ok for anyone that cares and has same problem as me, you need to run mame -createconfig, then edit the ini file and set hiscore_directory to where u want hiscores saved. thanks for everyone that helped

PS: whats the latest hiscore.dat version? im using 105 cuz thats the only one i could find. if theres a new one can i get a link? i didnt see any newer

Shoegazer · « **Reply #18 on:** February 15, 2007, 09:04:25 pm »

Well, I can appreciate the fact that some folks have taken the renegade approach by reanimating hiscore.dat, but since this solution will become increasingly difficult to manage over time, I still see the future as being linked purely to save state support.

So, I'm still curious to know if anyone is aware of any development efforts underway to fix this issue so we can keep the old save states with each new mame release? On the surface it *seems* to be a minor bug, and since it obviously has major impact it would be great to know if someone was at least looking into it. I looked in MAMEtesters and didn't see this as a reported issue, though I could be missing it.. am I right, or blind?

Shoegazer

Shoegazer · « **Reply #19 on:** February 23, 2007, 08:09:04 am »

Quick update: I keep looking around for some sign of hope but am coming up zeroes. Anyone here have any real evidence that someone is looking at making save states compatible across releases? This is the biggest "ouch" in MAME right now.. though I'm sure it is a well known problem since it must be very high visibility.

Buddabing · « **Reply #20 on:** February 23, 2007, 10:20:12 am »

I dimly recall reading a post from Aaron on mame.net regarding this topic. So try searching there. But I could be wrong and there was no such post.


Main	Restorations	Software	Audio/Jukebox/MP3	Everything Else	Buy/Sell/Trade
Project Announcements	Monitor/Video	GroovyMAME	Merit/JVL Touchscreen	Meet Up	Retail Vendors
Driving & Racing	Woodworking	Software Support Forums	Consoles	Project Arcade	Reviews
Automated Projects	Artwork	Frontend Support Forums	Pinball	Forum Discussion	Old Boards
Raspberry Pi & Dev Board	controls.dat	Linux	Miscellaneous Arcade	Wiki Discussion	Old Archives
Lightguns	Arcade1Up	Try the site in https mode		Site News


Unread posts \| New Replies \| Recent posts \| Rules \| Chatroom \| Wiki \| File Repository \| RSS \| Submit news