Closed ghost closed 5 years ago
barbudreadmon
commented
5 years ago Those translations (last version) were applied to clean No-Intro dump and tested with fbalpha. Closing.
Edit : could be that the "megami tensei gaiden" version is outdated, however you can use the updated one, fbalpha doesn't fail on crc
ghost
commented
5 years ago Those translations (last version) were applied to clean No-Intro dump and tested with fbalpha. Closing.
Edit : could be that the "megami tensei gaiden" version is outdated, however you can use the updated one, fbalpha doesn't fail on crc
shining tactics absolute final edition (hack).bin is definitly wrong crc, romhack point to the correct crc32 of the source file and if you would have been checked on that i think you would agree. so the avail translation does not match to the crc in .dat... whatsoever my point was to help not to complain, i fixed it for me ....
barbudreadmon
commented
5 years ago romhack point to the correct crc32 of the source file
@AntiFly Not true, sometimes it points to the crc of the source file, sometimes the result file. When i couldn't figure out where the crc came from (most likely from a old/bad dump), or if the rom with the expected crc wouldn't work (it happened too, i don't remember which ones), i decided to use the latest clean dump known to produce the translated version (if the result worked).
ghost
commented
5 years ago @barbudreadmon aha with your information about the no-intro i didnt get it. (same crc32 as shinfrc2u and relation to romhack) Shining Force II (USA).md and Shining Force II (Europe).md from 2016 no-intro does not worked either to that crc you point to.
hum ok whats the clue here..? where should people know which one was the source to your crc then ?? i mean there is no information which source did you worked with to create that particular rom with (at least none i would know of)
and if the author (related to romhacks) is pointing to a different checksum , dont you think it would be make more sense to use his tested "major" rom crc32 to point to ? (obviosly point to the patched crc32 then, cause romhacks in that particular case points to the source crc32)...
barbudreadmon
commented
5 years ago @AntiFly It appears you were wrong, as specified in the sources of fbalpha, http://www.romhacking.net/hacks/1736/ was used for this hack. And yes :
If i start updating crc every time there is an update, there will be no end to this. If you have a good source for your fba romsets, don't worry the files with the right crc will be in there after .44 is released.
barbudreadmon
commented
5 years ago @AntiFly They are present on a certain forum you know about...
ghost
commented
5 years ago @barbudreadmon most appreciated. i figured that out for every rom but those ones i was not able to "revert". even with the romhack link from you im on the wrong crc, Im going nuts on that because i just want to make it myself ^^ anyway thanks for help
dat: FB Alpha v0.2.97.43 (ClrMame Pro XML, Megadrive only).dat
current:: rom name="shining tactics absolute final edition (hack).bin" size="4194304" crc="49d556e2"/ should be new:: rom name="shining tactics absolute final edition (hack).bin" size="...." crc="44d9b263"/
as for my understanding its related to http://www.romhacking.net/hacks/670/ which is nowadays (since 2016) v.1.0 but the crc32 does not match to yours. if this source is pointing to a (seems so to me) newer patch file as your implemented one ???
same on this core; FB Alpha v0.2.97.43 (ClrMame Pro XML, Game Gear only).dat the used translation is outdated. new date is 26.06.18 with v1.02 (i guess the old crc was from v1.01??) on the vanilla one the crc should be then: current:: rom name="megami tensei gaiden - last bible s (english translation).gg" size="524288" crc="8a44108b"/ new:: rom name="megami tensei gaiden - last bible s (english translation).gg" size="524288" crc="c9125c8a"/
https://www.romhacking.net/translations/3160/
can you check on that ?