Author Topic: hiscore diff (with no nag/white box removal) (Read 620826 times)

TelcoLou · « **Reply #240 on:** December 01, 2008, 12:02:24 pm »

Quote from: headkaze on November 30, 2008, 08:20:37 pm

Quote from: TelcoLou on November 30, 2008, 04:13:01 pm
Hmmm ...

I was able to compile mame .128 using the posted 128 - 128u3 patch, easy as pie thanks to the mame64 compiler.
The nag screens are gone, but the hi score isn't working ... I created a hi folder, and placed the hiscore.dat file in my mame folder, but it never saves my score (using Radiant Silvergun to test it). Any ideas?

Thanks in advance.

That's an easy one to answer, hiscore.dat doesn't support that game. How do I know that? If you open up hiscore.dat in a text editor and search for rsgun it doesn't find anything.

Also the game does not have save state support so there is really no way to keep hiscores for this game. You could of course read the tutorial on creating a hiscore.dat entry for the game.

Ah! Thanks for the explanation

(<=== hahahaa! was looking for an "embarassed" smiley, but this is just TOO funny!)

9innail · « **Reply #241 on:** December 22, 2008, 10:46:13 pm »

Is a new diff needed for 128u7? This is the first time I have been unable to get it to work. Thanks.

MKChamp · « **Reply #242 on:** December 23, 2008, 05:01:06 pm »

Quote from: 9innail on December 22, 2008, 10:46:13 pm

Is a new diff needed for 128u7? This is the first time I have been unable to get it to work. Thanks.

Oops...I got lazy...
Yes, there is a new diff needed for u7...it's uploaded and ready to go.

9innail · « **Reply #243 on:** December 24, 2008, 12:33:55 pm »

Thank you. This diff makes all the difference with my Arcade Machine.

Gatsu · « **Reply #244 on:** January 04, 2009, 07:50:30 pm »

just recompiled mame 127. Worked like a charm. no more annoying nag screens!!

FrizzleFried · « **Reply #245 on:** January 05, 2009, 01:48:25 am »

Is .128u7 working with .129?

headkaze · « **Reply #246 on:** January 05, 2009, 03:54:03 am »

Quote from: FrizzleFried on January 05, 2009, 01:48:25 am

Is .128u7 working with .129?

I'm not sure but you could always give it a try. I'm sure MKChamp will make a new one soon if needed.

FrizzleFried · « **Reply #247 on:** January 05, 2009, 10:22:47 am »

Quote from: headkaze on January 05, 2009, 03:54:03 am

Quote from: FrizzleFried on January 05, 2009, 01:48:25 am
Is .128u7 working with .129?

I'm not sure but you could always give it a try. I'm sure MKChamp will make a new one soon if needed.

I usually check first because I have to compile a 64 bit version and I can only do it on the cab itself and it's ...well ...a pain in the ass frankly so I usually hold off until I hear confirmation the DIFF works.

headkaze · « **Reply #248 on:** January 05, 2009, 01:06:39 pm »

Quote from: FrizzleFried on January 05, 2009, 10:22:47 am

I usually check first because I have to compile a 64 bit version and I can only do it on the cab itself and it's ...well ...a pain in the ass frankly so I usually hold off until I hear confirmation the DIFF works.

Okay I just checked and no it doesn't work. src\emu\profiler.c has changed too much for the patch to apply. We will have to wait for MKChamp to make a new diff.

Code: [Select]

Applying Diff Patch...
patching file src/emu/crsshair.c
patching file src/emu/emu.mak
Hunk #2 succeeded at 52 (offset -1 lines).
patching file src/emu/emuopts.c
patching file src/emu/emuopts.h
patching file src/emu/fileio.h
patching file src/emu/hiscore.c
patching file src/emu/hiscore.h
patching file src/emu/mame.c
patching file src/emu/profiler.c
Hunk #1 FAILED at 125.
1 out of 1 hunk FAILED -- saving rejects to file src/emu/profiler.c.rej
patching file src/emu/profiler.h
Hunk #1 succeeded at 48 with fuzz 2 (offset 9 lines).
patching file src/emu/romload.c
Hunk #1 succeeded at 556 with fuzz 2 (offset 52 lines).
patching file src/emu/ui.c
patching file src/emu/video.c
patching file src/emu/video.h
patching file src/mame/machine/cps2crpt.c
patching file src/osd/osdepend.h
patching file src/osd/windows/video.c
patching file src/osd/windows/window.c
patching file src/osd/windows/window.h
Finished!
0 Hours 0 Minutes and 0 Seconds Elapsed.

Paul Olson · « **Reply #249 on:** January 05, 2009, 02:53:21 pm »

I tried it at 2am and it didn't work, looking forward to the update.

Friz - Use remote desktop and configure everything on your cab from another computer. I have the same problem with 64bit, and it is much nicer to work on the cab using remote. I worked on this watching a movie in the living room last night.

Edit: Make sure MALA is closed first (if you use it), it doesn't handle the resolution change very well.

MKChamp · « **Reply #250 on:** January 06, 2009, 06:43:25 pm »

hiscore 129 ready to roll...

TheManuel · « **Reply #251 on:** January 06, 2009, 08:21:38 pm »

Thanks, Champ!

TheManuel · « **Reply #252 on:** January 06, 2009, 08:24:48 pm »

Not a popular option here but, does the diff work with MAMEUI?

TheManuel · « **Reply #253 on:** January 06, 2009, 08:27:32 pm »

Never mind.
I was reading Headkaze's compiler instructions and apparently you can.

FrizzleFried · « **Reply #254 on:** January 06, 2009, 08:33:01 pm »

Thank you MKChamp....

....Soul Caliber here I come!

TheManuel · « **Reply #255 on:** January 06, 2009, 08:42:00 pm »

Quote

....Soul Caliber here I come!

Did it not work before?
Remember you can play the Dreamcast version with NullDC...

nuka1195 · « **Reply #256 on:** January 06, 2009, 11:06:47 pm »

Thank You

SirPeale · « **Reply #257 on:** January 16, 2009, 08:02:41 pm »

I just compiled .108. Having some severe problems. I'm trying to configure some things, but it seems that I can not use the enter key. Anywhere.

csa3d · « **Reply #258 on:** January 18, 2009, 10:56:28 pm »

Do i need to disable any save state settings in mame.ini to get hiscores to save in v129? Something is making my scores not save since updating...

Thanks
-csa

MKChamp · « **Reply #259 on:** January 19, 2009, 01:03:05 pm »

Quote from: Peale on January 16, 2009, 08:02:41 pm

I just compiled .108. Having some severe problems. I'm trying to configure some things, but it seems that I can not use the enter key. Anywhere.

It used to make the "enter" key "1". ( to make it work better for dedicated cabs...this was taken out starting with 124)
What you can do is use your "1" key as enter and you can change it back to the "enter" key in the configuration menu.

csa3d · « **Reply #260 on:** January 19, 2009, 02:08:08 pm »

Quote from: csa3d on January 18, 2009, 10:56:28 pm

Do i need to disable any save state settings in mame.ini to get hiscores to save in v129? Something is making my scores not save since updating...

Thanks
-csa

Is this just a millipede issue? Seems to be saving for frogger...

MKChamp · « **Reply #261 on:** January 19, 2009, 02:34:54 pm »

Quote from: csa3d on January 19, 2009, 02:08:08 pm

Quote from: csa3d on January 18, 2009, 10:56:28 pm
Do i need to disable any save state settings in mame.ini to get hiscores to save in v129? Something is making my scores not save since updating...

Thanks
-csa

Is this just a millipede issue? Seems to be saving for frogger...

I think this might be due to a mistype in the hiscore.dat. Due a search for "silliped" and change the "s" to "m" so it reads "milliped"...then see if it saves.

csa3d · « **Reply #262 on:** January 19, 2009, 02:56:22 pm »

Quote from: MKChamp on January 19, 2009, 02:34:54 pm

Quote from: csa3d on January 19, 2009, 02:08:08 pm
Quote from: csa3d on January 18, 2009, 10:56:28 pm
Do i need to disable any save state settings in mame.ini to get hiscores to save in v129? Something is making my scores not save since updating...

Thanks
-csa

Is this just a millipede issue? Seems to be saving for frogger...

I think this might be due to a mistype in the hiscore.dat. Due a search for "silliped" and change the "s" to "m" so it reads "milliped"...then see if it saves.

Naming issue was the trick! ON a side note, if we compile with HighScore enabled, autosave should be set to 0 and all .nv files in the nvram should be disabled, or not? If you enable autosave, is the default behaviour to check the .nv ram file first, then default to the .hi files? Also, is there a way to disable the State Loading box if autosave is set to 1?

Thanks!
-csa

MKChamp · « **Reply #263 on:** January 19, 2009, 04:46:32 pm »

Quote from: csa3d on January 19, 2009, 02:56:22 pm

Quote from: MKChamp on January 19, 2009, 02:34:54 pm
Quote from: csa3d on January 19, 2009, 02:08:08 pm
Quote from: csa3d on January 18, 2009, 10:56:28 pm
Do i need to disable any save state settings in mame.ini to get hiscores to save in v129? Something is making my scores not save since updating...

Thanks
-csa

Is this just a millipede issue? Seems to be saving for frogger...

I think this might be due to a mistype in the hiscore.dat. Due a search for "silliped" and change the "s" to "m" so it reads "milliped"...then see if it saves.

Naming issue was the trick! ON a side note, if we compile with HighScore enabled, autosave should be set to 0 and all .nv files in the nvram should be disabled, or not? If you enable autosave, is the default behaviour to check the .nv ram file first, then default to the .hi files? Also, is there a way to disable the State Loading box if autosave is set to 1?

Thanks!
-csa

.nv files are not a part of the save state system. NV files are generated by games that saved data when they were turned off. The save state files are stored in the sta folder. To be honest, if you have hiscore support, then isn't any reason to enable save states...unless you just want to be able to start a game where you left off. If you upgrade often, you'll find that save states are not that reliable anyways.

iano · « **Reply #264 on:** January 22, 2009, 07:25:40 am »

I'm trying to compile MAME0.129 with MKChamps diff file but i keep getting the same error. I've no doubt that i'm doing something wrong because other people have compiled MAME0.129 without a hitch. Any help would be appreciated.

src/emu/sound/ay8910.c: 751: internal compiler error: in assign_386_stack_local, at config/i386/i386.c: 13482

Please submit a full bug report, with preprocessed source if appropriate.
see<URL: http://www.mingw.org/bugs.shtml> for instructions
mingw32-make: ***[obj/windows/mame/emu/sound/ay8910.o] error 1

Thanks,
ian.

MKChamp · « **Reply #265 on:** January 22, 2009, 10:22:59 am »

Quote from: iano on January 22, 2009, 07:25:40 am

I'm trying to compile MAME0.129 with MKChamps diff file but i keep getting the same error. I've no doubt that i'm doing something wrong because other people have compiled MAME0.129 without a hitch. Any help would be appreciated.

src/emu/sound/ay8910.c: 751: internal compiler error: in assign_386_stack_local, at config/i386/i386.c: 13482

Please submit a full bug report, with preprocessed source if appropriate.
see<URL: http://www.mingw.org/bugs.shtml> for instructions
mingw32-make: ***[obj/windows/mame/emu/sound/ay8910.o] error 1

Thanks,
ian.

I think this might be related to Headkaze's MAME compiler...you are using that, right? If so, are you using Pentium 4 (+SSE3) optimize option? If you are, try compiling with Pentium 4 (-SSE3) option instead. If that doesn't work (and you ARE using this program to compile MAME) you may want to post in his thread for assistance....
http://forum.arcadecontrols.com/index.php?topic=71845.0

iano · « **Reply #266 on:** January 22, 2009, 12:10:27 pm »

Yes MKChamp, i am using HK's MAME Compiler with that option and i will post in the link you provided. Thanks for your help.

gatordad · « **Reply #267 on:** January 27, 2009, 11:03:55 pm »

Will the diff attached in the first post Remove loading messages (decoding/decrypting/Updating Artwork, etc.) and the 'white box' when loading for mame 114?
Thanks

MKChamp · « **Reply #268 on:** January 28, 2009, 01:58:12 am »

Quote from: gatordad on January 27, 2009, 11:03:55 pm

Will the diff attached in the first post Remove loading messages (decoding/decrypting/Updating Artwork, etc.) and the 'white box' when loading for mame 114?
Thanks

No, that was added starting with MAME v120. It will get rid of the 'nag' screens such as 'type ok' or incomplete driver screens, etc.

Dazz · « **Reply #269 on:** January 28, 2009, 10:10:45 am »

MKChamp,

Have you and Fyrecrypts talked about these diffs? I know that he has made several additions/corrections to these .diffs when working on his HiToText project. Are you including his updates?

headkaze · « **Reply #270 on:** January 28, 2009, 10:24:21 am »

Quote from: Dazz on January 28, 2009, 10:10:45 am

MKChamp,

Have you and Fyrecrypts talked about these diffs? I know that he has made several additions/corrections to these .diffs when working on his HiToText project. Are you including his updates?

He hasn't touched the diff's only the hiscore.dat file because the memory locations needed to be changed. So it's leezer who distributes the hiscore.dat that should update to use Fyrecypts mods.

Dazz · « **Reply #271 on:** January 28, 2009, 10:53:54 am »

Quote from: headkaze on January 28, 2009, 10:24:21 am

Quote from: Dazz on January 28, 2009, 10:10:45 am
MKChamp,

Have you and Fyrecrypts talked about these diffs? I know that he has made several additions/corrections to these .diffs when working on his HiToText project. Are you including his updates?

He hasn't touched the diff's only the hiscore.dat file because the memory locations needed to be changed. So it's leezer who distributes the hiscore.dat that should update to use Fyrecypts mods.

Oh snap, my bad. You are correct. It is the dat file that I am questioning not the diffs. Thanks HK!

Fyrecrypts · « **Reply #272 on:** February 01, 2009, 01:02:42 pm »

Quote from: headkaze on January 28, 2009, 10:24:21 am

Quote from: Dazz on January 28, 2009, 10:10:45 am
MKChamp,

Have you and Fyrecrypts talked about these diffs? I know that he has made several additions/corrections to these .diffs when working on his HiToText project. Are you including his updates?

He hasn't touched the diff's only the hiscore.dat file because the memory locations needed to be changed. So it's leezer who distributes the hiscore.dat that should update to use Fyrecypts mods.

I've talked with Leezer, and have been giving him the updates, I'd bet his releases will contain the fixes added in the HiToText hiscore.dat file.

Tinydane · « **Reply #273 on:** February 05, 2009, 12:56:25 pm »

Just wanted to toss out a big thanks to the guys that put this together. I just did my first recompile on .128 and it went real smooth. I followed MrDo's step by step info on the actual recompile and all went well..

thanks again.

csa3d · « **Reply #274 on:** February 07, 2009, 03:51:09 pm »

I want to pose this question:

Given that I've seen at few people attempting to hook up the mouse Z-Axis to the spinner, do we think it might be beneficial to roll the option to use the Z-Axis when applying this patch as well? I typically apply this patch and then the TT2 Z-Axis patch described here when I compile my own.

Just a thought
-csa

MKChamp · « **Reply #275 on:** February 08, 2009, 01:23:45 pm »

Quote from: csa3d on February 07, 2009, 03:51:09 pm

I want to pose this question:

Given that I've seen at few people attempting to hook up the mouse Z-Axis to the spinner, do we think it might be beneficial to roll the option to use the Z-Axis when applying this patch as well? I typically apply this patch and then the TT2 Z-Axis patch described here when I compile my own.

Just a thought
-csa

Then we'd have to add a hundred other patches used by a 'few' people :-)

csa3d · « **Reply #276 on:** February 08, 2009, 02:32:50 pm »

Quote from: MKChamp on February 08, 2009, 01:23:45 pm

Then we'd have to add a hundred other patches used by a 'few' people :-)

Ha! True..

-csa

Todd H · « **Reply #277 on:** March 06, 2009, 08:57:27 am »

Probably a stupid question but in order to compile a 64-bit version you need to do it in a 64-bit OS correct? I assume I couldn't compile a 64-bit version under a 32-bit version of Vista.

FrizzleFried · « **Reply #278 on:** March 06, 2009, 09:58:06 am »

Quote from: Todd H on March 06, 2009, 08:57:27 am

Probably a stupid question but in order to compile a 64-bit version you need to do it in a 64-bit OS correct? I assume I couldn't compile a 64-bit version under a 32-bit version of Vista.

Correct.

kaptainsteve · « **Reply #279 on:** March 10, 2009, 06:42:41 pm »

Hello,

Wondering if anyone can help?

Where does one go about finding the mame "patch.exe" used when compiling?

thanks.

Steve

Found it Here at http://gnuwin32.sourceforge.net/packages/patch.htm for those who bump into the same problem.


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