Final Fantasy 4 on real hardware via cart mod/powerpak broke
Moderator: Moderators
Forum rules
- For making cartridges of your Super NES games, see Reproduction.
Final Fantasy 4 on real hardware via cart mod/powerpak broke
Anyone able to get final fantasy 4 to work via repro or the powerpak? Cant get either working correct. On powerpak it just comes up a bunch of garbage on screen
Yeah it works fine with me. Maybe you'd want to re-download the ROM and re-apply the translation patch.
Interestingly enough, I have a french translation, based on a 8x16 font hack, that works fine in SNES9x and ZSNES, and it was a black screen on BSNES. Sursprisingly, it woked just fine with the Powerpak so I guess there was a problem in BSNES (and not with the patch).
Also I noticed that there is a "transparent line" on dialog boxes in ZSNES on some versions of the game (I think this is due to IRQ timing errors or something in the like). This works fine on real HW.
Interestingly enough, I have a french translation, based on a 8x16 font hack, that works fine in SNES9x and ZSNES, and it was a black screen on BSNES. Sursprisingly, it woked just fine with the Powerpak so I guess there was a problem in BSNES (and not with the patch).
Also I noticed that there is a "transparent line" on dialog boxes in ZSNES on some versions of the game (I think this is due to IRQ timing errors or something in the like). This works fine on real HW.
Useless, lumbering half-wits don't scare us.
Are you sure your ROM has or doesn't have the 512 byte copier header when you apply the patch? If you have that backwards it won't work correctly.
Another issue you might have with FF4 translated is they did not alter the embedded ROM header which says the ROM is still 8 megabits when it should read 16mbits since it is 12mbit but that is signified by 16mbit in embedded headers. The GDSF copiers rely on this byte for memory mapping as I recall and not changing it caused all information beyond 8mbits to be inaccessible causing messed up text and possibly could cause crashes later on.
Another issue you might have with FF4 translated is they did not alter the embedded ROM header which says the ROM is still 8 megabits when it should read 16mbits since it is 12mbit but that is signified by 16mbit in embedded headers. The GDSF copiers rely on this byte for memory mapping as I recall and not changing it caused all information beyond 8mbits to be inaccessible causing messed up text and possibly could cause crashes later on.
They were prepatched and worked fine in an emulator so I have no idea. Ill try to remove header then do a patch and see how that goes
MottZilla wrote:Are you sure your ROM has or doesn't have the 512 byte copier header when you apply the patch? If you have that backwards it won't work correctly.
Another issue you might have with FF4 translated is they did not alter the embedded ROM header which says the ROM is still 8 megabits when it should read 16mbits since it is 12mbit but that is signified by 16mbit in embedded headers. The GDSF copiers rely on this byte for memory mapping as I recall and not changing it caused all information beyond 8mbits to be inaccessible causing messed up text and possibly could cause crashes later on.
If they work fine in an emulator then it isn't a patching problem. You might try changing the embedded ROM header to change the ROM Size. PowerPAK depends on this information I believe.
If your ROM has a 512byte header (lots of 00 in the first 512 bytes of the file) then goto $81D7 in the file and change the $0A to $0B and it might fix it. If there is no header than $7FD7 is where you should find a $0A to change to $0B.
If your ROM has a 512byte header (lots of 00 in the first 512 bytes of the file) then goto $81D7 in the file and change the $0A to $0B and it might fix it. If there is no header than $7FD7 is where you should find a $0A to change to $0B.