yes chad, but which would I know that I need without comparing to someone that doesn't have the playback issue?!?
You mentioned it played back ok for you above..even with the no clear rom dump warnings.
The question would be is if you have the same rom set version of gtmr that I have.
I guess from a certain "source" I can see what it's supposed to be..and run an audit of it within macmame.
However, even if they report that issue, if that's the same rom set PC players are using that does not have the playback issue, then that still makes it a macmame-only issue...thus an issue not just related to a bad rom dump.
Great 1000 Miles Rally
Moderator: Chad
yes rick, but in order to compare if we have the same rom one of us has to show the crcs of the unknown dumps (and i don't have roms where i am now :) Even an audit would be useless if the rom is still unknown in the current version. Audit with different no good dump roms would report the same NO GOOD DUMP KNOWN message for different people. need the crcs, or existance data to know the differences. I know I HAVE my the bad dump rom files since my message didn't say NO GOOD DUMP KNOWN (NOT FOUND) do you have your file(s)? if so what's the crcs? i'll report/compare mine when i can see my roms.
-skito
k, here ya go...
Code: Select all
Romset format: Zipfile
Driver: gtmr "Great 1000 Miles Rally"
Parent of: gtmre "Great 1000 Miles Rally (Evolution Model)"
gtmrusa "Great 1000 Miles Rally (USA)"
Romset Analysis:
gmmu23.bin (b9cbfbee) is required by this driver and clone(s): gtmre, gtmrusa
gmmu24.bin (380cdc7c) is required by this driver and clone(s): gtmre, gtmrusa
gmmu27.bin (c0ab3efc) is required by this driver and clone(s): gtmre, gtmrusa
gmmu28.bin (cf6b23dc) is required by this driver and clone(s): gtmre, gtmrusa
gmmu29.bin (8f27f5d3) is required by this driver and clone(s): gtmre, gtmrusa
gmmu30.bin (e9747c8c) is required by this driver and clone(s): gtmre, gtmrusa
gmmu52.bin (b15f6b7f) is required by this driver and clone(s): gtmre, gtmrusa
mcu_code.u12 (963dba66) is required by this driver and clone(s): gtmre
sprites (5e0e3316)
u1.bin (6238790a)
u2.bin (031799f7)
I have not tested inp playback with any of the "clones" of that game yet...just the parent. However I see the gtmre clone uses that same mcu_code.u12 rom.
My mcu_code.u12 file is also 131,072 bytes in size. However, it seems your crc isn't the same.
So it seems your rom set is different than mine?!?!
Is that what you are saying?
I guess I'll have to try the inp playback of Ray's inp in VPC using my rom set to see if it plays back ok. If it doesn't then my rom set might be the issue here...not a macmame issue.
However, if VPC plays it back(and others) just fine then that would suggest it's not the fault of the rom set or that particular rom file but something else causing it.
Even in a couple of the scores for this I see the confirmed score changed and different a little bit versus what was "advertised"/submitted.
That to me right there is an indication that perhaps there are playback issues if you don't get exactly all the same race times as the person listed.
My mcu_code.u12 file is also 131,072 bytes in size. However, it seems your crc isn't the same.
So it seems your rom set is different than mine?!?!
Is that what you are saying?
I guess I'll have to try the inp playback of Ray's inp in VPC using my rom set to see if it plays back ok. If it doesn't then my rom set might be the issue here...not a macmame issue.
However, if VPC plays it back(and others) just fine then that would suggest it's not the fault of the rom set or that particular rom file but something else causing it.
Even in a couple of the scores for this I see the confirmed score changed and different a little bit versus what was "advertised"/submitted.
That to me right there is an indication that perhaps there are playback issues if you don't get exactly all the same race times as the person listed.
yeah it doesn't rule out the rand() issue for sure, since they aren't all converted to mame_rand() in the mame source, but i would certainly get a mac hex editor and entre the same 8 bytes repeatedly in the file (or just get the roms from mame.dk which is where i got them) 'DE' 'AD' 'BE' 'EF' and try to play it back...
-skito
aaaah! You actually said it! heheChad wrote:(or just get the roms from mame.dk which is where i got them) 'DE' 'AD' 'BE' 'EF' and try to play it back...
Anyway, I didn't think that was possible from that site anymore as noted here a couple months ago and noted on the main page.
I have always gotten mine elsewhere.

It does seem the content of that rom file is bogus.
Mine actually has 2 repeating hex patterns per line.
In text mode each line actually is
"mame.dk mame.dk"
hehe
I think that means even though I got this from elsewhere it's the same as the one at mame.dk. hehe
I see your above hex just shows as dots/periods.
Ok, I got it from that location and the mcu_code.u12 is exactly like the one I have...same content...same size...same checksum as what I already had.
It seems you and/or others have a different mcu_code.u12 file.
I'll test pc-mame inps for this game in VPC later this evening to see if they playback ok.
It seems you and/or others have a different mcu_code.u12 file.

I'll test pc-mame inps for this game in VPC later this evening to see if they playback ok.