Page 1 of 2
Darkstalkers: The Night Warriors (Euro 940705)
Posted: Mon Oct 20, 2003 3:31 pm
by mahlemiut
Posted: Mon Oct 20, 2003 4:04 pm
by evil_angela
Pardon me while I smack myself upside the head for getting lazy about testing recordings before submitting them.
Shouldn't be a nvram issue though - I use the batch files made available somewhere here to do recording and playback, and it copies out any nvram beforehand.
Posted: Mon Oct 20, 2003 4:07 pm
by Mr. Kelly R. Flewin
evil_angela wrote:Pardon me while I smack myself upside the head for getting lazy about testing recordings before submitting them.
Shouldn't be a nvram issue though - I use the batch files made available somewhere here to do recording and playback, and it copies out any nvram beforehand.
There is an easier way to do it though. Simply delete the NVRAM directory in your mame folder, and then make a new txt document.... or wordpad doc.... and simply save it.. so it's an empty file. Rename that as NVRAM and VOILA!
No more NVRAM as Mame can't write NVRAM to the NVRAM directory, due to this fix. It works quite wonderfully, so ya never gotta worry
Kelly
Posted: Mon Oct 20, 2003 5:59 pm
by evil_angela
Aah, but if I do that, I lose the capability to have an nvram directory for any games. There are plenty of games that I still enjoy playing, but have nowhere near the ability to get scores that I feel are worthy of posting here. I don't see a reason to kill the nvram for them in the process. I haven't had any problems with the current method (that I'm aware of).
Besides, I've tweaked the scripts to automatically add options that I want to use, automatically copy the inp file to a new filename with the score (that I enter afterwards), etc. Since I'll keep using them anyways, I don't see the need to stop as long as they're working.
Posted: Mon Oct 20, 2003 10:01 pm
by mahlemiut
Better way, then, is to use -nvram_directory NUL when recording or playing back.
This will stop any NVRAM use, but leave any you already have intact.
(Linux users need to use -nvram_directory /dev/null which does the same thing.
Posted: Tue Oct 21, 2003 12:05 am
by evil_angela
I played it back just now, and got 555,000. I didn't even leave it at frameskip 0 - I sped it up to 11.
What sorts of things could cause desync issues? I recorded on Win2K, Sound On, manually switched from auto frameskip to frameskip 0.
Posted: Tue Oct 21, 2003 1:12 am
by Chad
i still can't get it going, could be a freaky sound setting,i've tried 22050 and 44100, or the 63 bug, try 75 or later? btw, if three people can't play it back and there are no two people who can, then it gets zereoed by bad playbackability.
Posted: Tue Oct 21, 2003 11:29 am
by evil_angela
I'll have to do another recording, and try it again, see if another one works. I'll double check all the settings, also - though I didn't do anything different from any of my other recordings, so I'm pretty much clueless why this specific one would give everyone else problems but not me, and my others seem to work just fine for me and everyone else.
I'll use .76 on the next recording too.
Question for those attempting to play it back - is Bishamon the opponent in the first round? That's what it should be.
Posted: Tue Oct 21, 2003 1:55 pm
by Chad
yes but he chops you up like suey.
Posted: Tue Oct 21, 2003 2:45 pm
by Weehawk
Chad wrote:yes but he chops you up like suey.
And at one point some sort of ghost-like thing holds her while he whacks her!
Hardly seems fair...
Anyway, it plays back to 3750 iirc, no matter what options I tried.
Posted: Wed Oct 22, 2003 1:27 am
by evil_angela
I think I have figured it out. And I see what you mean, guys.
I forgot that I had upgraded from wolfmame .73 to wolfmame .75. I grabbed .73 again, and ran the inp against it, and it was definitely out of sync and looked bad, with a final score of 3700 for me.
Ran in .75 or .76, though, and it goes to 555,000 for me just fine.
I've edited the mame version in the entry. Could some people try it for me again, this time with the version I actually recorded it in?
Posted: Wed Oct 22, 2003 1:49 am
by Weehawk
Wolfmame says it was recorded with .73, but I tried running it with .75 and got the same results.
If you are using a different mame.ini file with .75 than with .73, check to see if there is anything set differently.
Posted: Wed Oct 22, 2003 11:45 am
by evil_angela
Yes, it appears that it was a setting in the .ini file. I turned off the M86K Core at some point in the past, probably when trying to solve some odd framerate issues (I turned on rdtsc and solved that one).
Try again with the M68K core off, see if THAT does it for you.
I'm deleting the individual game .ini files to make sure I don't run in to this one again.
Posted: Wed Oct 22, 2003 12:18 pm
by Zwaxy
THAT does it for me. It plays back in WolfMAME 0.75 and 0.76 so long as I uncheck the 'MC68000 C Core' option in the GUI version or use "m68k_c_core 0" in my mame.ini for the command-line version.
Posted: Wed Oct 22, 2003 3:47 pm
by mahlemiut
I can't believe that I never thought to look for that - it says that quite clearly in the console output:
Code: Select all
Recorded in WolfMAME 0.73
Recorded system's speed = ~799MHz
This recording was made with the ASM 68k core enabled
Ho well, it works anyway.
