Wonder if that would involve hacking a V rom or the actual M rom? We have some true wizards in these forums but I wonder if someone would be interested in takin on this challenge :/I've only ever heard rumor of a none "crackle" version of NiTD. I've owned the JPN cart and currently own the US releases of the game.
You have to remember that these games were meant to be played in loud arcades, I dont think sound quality was a focus for a lot of third party developers. Even games from Noise Factory had crackling ( see the Win quote screen from RoTD for example. ).
Honestly, someone should just make a rom hack where they replace / fix the sound and we just call it a day.
I do find it strange that the pirates would spend time fixing the audio as opposed to them just stumbling on a legit cart with the fix already in place.
EDIT: so I started searching for more info on this, and I forgot @twistedsymphony had shared this in the past:
https://mametesters.org/view.php?id=1850
Why can it sound fine on a xx-in-1 multicart then?
Wonder if that would involve hacking a V rom or the actual M rom? We have some true wizards in these forums but I wonder if someone would be interested in takin on this challenge :/
I for one would chip in some cash if we were to have a bounty or something![]()
Is this confirmed? My 161-in-1 has the same scratch sound as my real Nightmare in the Dark cart.Why can it sound fine on a xx-in-1 multicart then?
Is this confirmed? My 161-in-1 has the same scratch sound as my real Nightmare in the Dark cart.
So strange. That would seem to confirm that the problem isn't the sample itself, but something else.So I had some free time today and decided to dig into NiTD.
I was able to identify the sound sample in the V rom and completely remove it, however the crackling was still there. I was starting to think the issue was with the sound driver itself, but it looks like the sound driver "Ver 3.0 by MAKOTO.04/03/10 to SK" is used in a bunch of other games including first party titles.
260-v1.v1:
0x50820: 6E -> 08
it's the same address since it only affects v1. You either split the patched vroma0 or hex edit v1.Hello
Thanks for the hard work
Any chance to have the changelog address for "272-v1.v1" and "272-v2.v2" to patch samsh5sp binaries with winhex ?
(i don't have mister)
Thanks a lot !
Nicolas
just to note which are the correct values:
in order to make the value at 0x60bc0 be 0x08, the encrypted value present at 0x00000 should be 0x43 (it is 0xE0)
in order to make the value at 0x160bc0 be 0x82, the encrypted value present at 0x00001 should be 0xC9 (it is 0x25)