+  RHDN Forum Archive
|-+  Romhacking
| |-+  ROM Hacking Discussion
| | |-+  Quick FF6 Question
Pages: 1 [2]
Author Topic: Quick FF6 Question  (Read 2 times)
Lenophis
Guest
« Reply #15 on: December 17, 2008, 04:20:06 am »

Quote from: Zeemis on December 17, 2008, 01:30:38 am
What about the title screen issue, I can't seem to fix the issue where it darkens and then freezes.
My custom title screen (or rather intro) loads up fine, but after you press A, it freezes.
Sounds like a header issue (you either assembled with the header parameter to a non-headered rom, or assembled without the header parameter to a headered rom). The only two options are to replace the broken code/data, or start over.
Zeemis
Guest
« Reply #16 on: December 17, 2008, 10:30:33 am »

Hmm.

You told me to put in header below Hirom Lenophis in which I did, and the default rom comes with a header.
I thought it had to do with this, which I wasn't quite sure how to modify:
Code:
;old code from beginning of unchanged rom
CLC
XCE
SEI
REP #$10
JMP.l $008005 ;jump to fifth instruction
Lenophis
Guest
« Reply #17 on: December 17, 2008, 02:38:39 pm »

Quote from: Zeemis on December 17, 2008, 10:30:33 am
Hmm.

You told me to put in header below Hirom Lenophis in which I did, and the default rom comes with a header.
I thought it had to do with this, which I wasn't quite sure how to modify:
Code:
;old code from beginning of unchanged rom
CLC
XCE
SEI
REP #$10
JMP.l $008005 ;jump to fifth instruction
That file I gave you was made specifically for FF6, and was not to be touched. It worked fine the way I gave it to you, with the exception of the header parameter. If your rom has a header, add the header parameter. If not, remove or comment out the header parameter. Run, assemble, boom. Screwing this part up will create problems.

Now, since you've already assembled on it, what you do to that specific rom no longer matters. You will either have to find and replace the broken code, or start over. The tutorial mentions the tracer, which is extremely helpful for this task. I'd suggest running WindHex32, compare your rom to a clean rom, and find out where things went wonky in the first bank (first 0xFFFF bytes).

There is also one other thing I did not realize when you said it. You said you used FF3usME to expand the rom to 4 megs, which is ok. But, if you moved the AI data or anything else after that, then I believe that will clash with this code, causing crashes.
Zeemis
Guest
« Reply #18 on: December 17, 2008, 08:05:50 pm »

I've tried using a fresh rum, although I believe I altered the code because the first time it didn't work was with my hacked rom.

I also make backups first before making any patchs/hacks to it.
If possible, could you copy and paste the ASM file you sent me once more and I'll try it again with the fresh rom?


Sorry for my incompetence. ;(
Pages: 1 [2]  


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