+  RHDN Forum Archive
|-+  Romhacking
| |-+  ROM Hacking Discussion
| | |-+  Cannot find string in Nekketsu Kakutou Densetsu
Pages: [1]
Author Topic: Cannot find string in Nekketsu Kakutou Densetsu  (Read 2 times)
Nosuch
Guest
« on: March 18, 2009, 02:52:00 am »

I've got a small dilemma here.  I've been working on a hack of sorts of Nekketsu Kakutou Densetsu, and I'm basically finished with what I plan to do with it, but there's one thing that still eludes me.  In particular, after a fight ends due to a chosen rule, the game shows a text string that I can't seem to find.



I've tried searching for it, I've tried looking around areas where I found other text, and I've even tried scrolling through the entire ROM in a hex editor.  If I could get FCEUXD to run at a decent clip on this old computer, I'd try using that on it, but as it is I'm stuck.  It's just a small thing but it bugs me.  Can anybody possibly help?
Tauwasser
Guest
« Reply #1 on: March 18, 2009, 05:17:54 am »

So how are you searching for that string?
Are you using your roman table? If so, did you search for "h-hK XBgc" or did you figure the "," on top of the K into your search? It looks like you edited a (han-)dakuten to be a comma and it is used in this particular string, so maybe that's why you don't find it.

Also, it might be easier to search for the Japanese string with your Japanese table if you haven't already done so. Maybe that way, you'll make less mistakes on the search entry part.

Also remember that it may be a string that inserts special words or something. Like "[HERO] lost [NUMBER] hit points." where usually strings are replaced while it is being copied to ram/drawn onto the screen. So maybe figuring out what the text is actually saying might help a lot.

cYa,

Tauwasser
Gideon Zhi
Guest
« Reply #2 on: March 18, 2009, 09:55:59 am »

Out of sheer curiosity, is there a reason this thread is pinned?
Tauwasser
Guest
« Reply #3 on: March 18, 2009, 10:19:13 am »

Yes. I moved it out of a topic that was stickied. I wouldn't have thought it'd become a sticky itself tho...

cYa,

Tauwasser
Deathlike2
Guest
« Reply #4 on: March 18, 2009, 10:21:14 am »

I'm assuming the post itself inherits the property of the host topic... which is generally not what you want when splitting topics.
Nosuch
Guest
« Reply #5 on: March 18, 2009, 02:49:32 pm »

Quote from: Tauwasser on March 18, 2009, 05:17:54 am
So how are you searching for that string?
Are you using your roman table? If so, did you search for "h-hK XBgc" or did you figure the "," on top of the K into your search? It looks like you edited a (han-)dakuten to be a comma and it is used in this particular string, so maybe that's why you don't find it.

I searched for it in segments using a roman table.  I tried "XB," "Bg," "gc," etc, just in case there were other bits of code within this particular string.  It would make sense if that was the case since the game does the same thing in other parts as well.  Unfortunately, that didn't work.

Quote from: Tauwasser on March 18, 2009, 05:17:54 am
Also, it might be easier to search for the Japanese string with your Japanese table if you haven't already done so. Maybe that way, you'll make less mistakes on the search entry part.

Er... I'm not actually using a Japanese table.  My "translation," such as it is, is just making up something that looks like it makes sense in context rather than translating what's really being said.

That said, for whatever use it may be, below is the string as seen in the unaltered (J) version.



Quote from: Tauwasser on March 18, 2009, 05:17:54 am
Also remember that it may be a string that inserts special words or something. Like "[HERO] lost [NUMBER] hit points." where usually strings are replaced while it is being copied to ram/drawn onto the screen. So maybe figuring out what the text is actually saying might help a lot.

I tried repeating the same victory method with different characters and different rules, just in case.  The text is identical every time, so I know there aren't any special words further hindering the search.

Thanks for the suggestions, though. Smiley Like I said, it's stumping me why this one single string is eluding me even though everything else has been found.
Ryusui
Guest
« Reply #6 on: March 18, 2009, 03:37:45 pm »

1. Load the ROM in FCEUXD.

2. Find the place in the PPU where the problem string is displayed.

3. Set breakpoints and see if you can catch the write in the act.

4. Trace the code and find out where the bytes are coming from.

5. Huh

6. PROFIT!!!
Nosuch
Guest
« Reply #7 on: March 19, 2009, 12:58:52 am »

Huh, that's odd.  The last time I tried to run FCEUXD on this ancient relic of a computer, it was immensely sluggish.  Now it's running like a charm.  Go figure.

Okay, I'll see if I can get that to work.  Thanks.

EDIT: Alright, I apparently don't know what I'm doing.  I've got a save state set up right before the string is prompted, but I still can't find it in the PPU or anything whenever it runs.
« Last Edit: March 19, 2009, 02:09:09 pm by Nosuch »
tummai
Guest
« Reply #8 on: March 19, 2009, 04:22:51 pm »

Can you post up the savestate?
Ryusui
Guest
« Reply #9 on: March 19, 2009, 04:43:40 pm »

Quote from: Nosuch on March 19, 2009, 12:58:52 am
Huh, that's odd.  The last time I tried to run FCEUXD on this ancient relic of a computer, it was immensely sluggish.  Now it's running like a charm.  Go figure.

Okay, I'll see if I can get that to work.  Thanks.

EDIT: Alright, I apparently don't know what I'm doing.  I've got a save state set up right before the string is prompted, but I still can't find it in the PPU or anything whenever it runs.

It'll only show up in the PPU when it's on screen. Get the start address and set a write breakpoint.
UglyJoe
Guest
« Reply #10 on: March 19, 2009, 09:04:21 pm »

You need a new table file.  Start up a fight and then go to your PPU viewer.  Set the scanline option to any value greater than 187.  You'll see a full English font, a partial kana font, and a few kanji.  Use those values to make a table and you should see the string you want at 0x76C1 (I'm looking a the (J) rom, not the (J) [p1] rom).
Kitsune Sniper
Guest
« Reply #11 on: March 19, 2009, 10:06:09 pm »

I remember Dunk Heroes gave me a hard time with certain... things. It would basically switch the values of each letter around for no reason at all. So the string is probably being referenced with other values. Check the CHR RAM in memory and compare the values of each tile to your table, then search for that in your hex editor.

(I can't explain it any better, it's one of those things I figured out on my own a while back. :p)
Nosuch
Guest
« Reply #12 on: March 19, 2009, 11:48:29 pm »

Quote from: tummai on March 19, 2009, 04:22:51 pm
Can you post up the savestate?

As requested.

Quote from: UglyJoe on March 19, 2009, 09:04:21 pm
You need a new table file.  Start up a fight and then go to your PPU viewer.  Set the scanline option to any value greater than 187.  You'll see a full English font, a partial kana font, and a few kanji.  Use those values to make a table and you should see the string you want at 0x76C1 (I'm looking a the (J) rom, not the (J) [p1] rom).

Okay... I started with the (J) ROM, too, and I do see the string in question at that location, but it isn't showing any difference whatsoever if I try changing it (which is a first for this series).  That's the only place I'm seeing it, too.  I even tried the "search in segments" approach again and still nothing.

Talk about resistant. Tongue

EDIT: Alright, posted too soon.  It turns out that that is the right place, and the lack of difference was because I was using the above savestate.  I was expecting it to not be in the state's RAM already, but it for some reason was.  Go figure.

But yeah!  It turns out I've got the fix I was after now.  Thanks, everybody. :thumbsup:
« Last Edit: March 19, 2009, 11:59:03 pm by Nosuch »
Pages: [1]  


Powered by SMF 1.1.4 | SMF © 2006-2007, Simple Machines LLC