Main > Software Forum
hiscore diff (with no nag/white box removal)
ozfalcon:
--- Quote from: cugel on July 05, 2016, 12:19:44 pm ---
--- Quote from: cugel on July 05, 2016, 09:51:52 am ---
--- Quote ---
These changes do not affect the hiscore code, So it's likely something your doing differently.
You need to be sure you start Mame in the same directory as the hiscore.dat
You also need to use the MKChamp hiscore.dat (Not the one supplied with Mame.zip)
http://highscore.mameworld.info/download.htm
Also ensure you have the Lua script version of hiscore disabled.
--- End quote ---
Yes right, now I remember that http://forum.arcadecontrols.com/index.php/topic,64298.msg1440381.html#msg1440381
I will make a try thanks
--- End quote ---
Ok it's good I added a path in source code
I guess hiscore.dat in hi directory, by default, should be a more logical/practical way ...
--- End quote ---
Yes, It is more convenient to have hiscore.dat coupled with the hi score directory.
However, The HiScore component of this patch is MKChamps expertise - So I don't modify it at all.
I do use the same method, But rather than modifying the source - I just patch the HiScore patch.
ie. Apply the HiScore patch then apply the HiDatDirectory patch (Attached) and your hiscore.dat will be looked for in the "hi" directory.
<Also added current hi_175c.txt for convenience>
cugel:
Yes I did the same thing, hope I will not forget the next time ;)
fleskebacon:
--- Quote from: ozfalcon on July 04, 2016, 09:01:05 pm ---
--- Quote from: kaptainsteve on July 04, 2016, 08:52:17 pm ---Hiscore saving and no nag is included in the plugin option in all Mames now after 174....
--- End quote ---
What is the no nag option to disable the "There are known problems with this machine", White borders and loading messages.....?
The hiscore plugin appears to be fine, But the plugins function still requires bug fixes and the like - Though it is still perfectly usable.
--- End quote ---
I've been using the hiscore plugin for some time now, and as you say - it seems to be working fine, at least in all games I've played.
Worth to mention that the MKChamp hiscore patch and the Mame plugin use different formats of the hiscore.dat file... I sure spent some frustrating time before discovering this.
I also found some old code for supressing the white box and all loading messages, it seems to work fine with the recent Mame versions as well. Could very well be the same code used in this diff for all I know, but at first glance it seems to do it in a different way. My programming skills are absolutely rubbish, so I barely have a clue of what I'm doing... However, I managed to manually patch render.cpp and ui.cpp using the code I found, so now I have a nag-free Mame without added hiscore support, and using the Mame hiscore plugin.
Could very well turn out to be problems with this approach, but so far so good. Will check back later with an update on this. :)
ozfalcon:
--- Quote from: fleskebacon on July 07, 2016, 07:45:07 am ---
--- Quote from: ozfalcon on July 04, 2016, 09:01:05 pm ---
--- Quote from: kaptainsteve on July 04, 2016, 08:52:17 pm ---Hiscore saving and no nag is included in the plugin option in all Mames now after 174....
--- End quote ---
What is the no nag option to disable the "There are known problems with this machine", White borders and loading messages.....?
The hiscore plugin appears to be fine, But the plugins function still requires bug fixes and the like - Though it is still perfectly usable.
--- End quote ---
I've been using the hiscore plugin for some time now, and as you say - it seems to be working fine, at least in all games I've played.
Worth to mention that the MKChamp hiscore patch and the Mame plugin use different formats of the hiscore.dat file... I sure spent some frustrating time before discovering this.
I also found some old code for supressing the white box and all loading messages, it seems to work fine with the recent Mame versions as well. Could very well be the same code used in this diff for all I know, but at first glance it seems to do it in a different way. My programming skills are absolutely rubbish, so I barely have a clue of what I'm doing... However, I managed to manually patch render.cpp and ui.cpp using the code I found, so now I have a nag-free Mame without added hiscore support, and using the Mame hiscore plugin.
Could very well turn out to be problems with this approach, but so far so good. Will check back later with an update on this. :)
--- End quote ---
The suppression code is right at the end of the hiscore patch - The entire lot can be easily removed to be standalone.
Sorn:
--- Quote from: headkaze on June 30, 2016, 01:25:45 pm ---
--- Quote from: Ginsonic on June 30, 2016, 06:34:26 am ---The patch did not work using MAME compiler. When I patched it manually using the buildtools command line, it worked flawlessly ![/b]
--- End quote ---
I changed the default -p option to work with the new feature to create patches. If MKChamp used MAME Compiler to create the patch then there wouldn't be a problem as the -p options would match.
I think I'm going to have to add a manual -p setting to MAME Compiler as there doesn't seem to be a setting that will work with all patches.
--- End quote ---
I would like to get 0175 compiled with the hi score patch, is there currently any work around (such as a diff patching util) or do we need to wait for your update headkaze?
Thank you!
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version