øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=278;area=showposts;start=540e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index855f-2.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=278e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index855f-2.html.zxÉåg^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ0P.ÍOKtext/htmlISO-8859-1gzip@øÕÍÿÿÿÿÿÿÿÿTue, 10 Mar 2020 19:25:20 GMT0ó°° ®0®P®€§²ð®Èåg^ÿÿÿÿÿÿÿÿ\(Í Show Posts - chillyfeez

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - chillyfeez

541
Final Fantasy IV Research & Development / Re: Japanese Title Screen
« on: April 04, 2015, 11:27:44 AM »
I wonder why didn't NOA just change the IV to a II instead of completely changing out the title screen. Sure they needed to fit Nintendo of America, but still.

The spacing wasn't/isn't there.  To properly have a pixel perfect Final Fantasy IV using the US style larger letters requires more real estate.  The mods out there that change one of the I's in to a V visualize what I'm talking about. While they don't look bad it wouldn't of worked originally due to that lack if space and a redesign would of been needed.  Plus having said all of that the US style letters were only created because Square didn't want to use Final Fantasy IV's numbering.

I think what Rodimus was wondering was why they didn't do the opposite... That is, use the original FFIVJ title screen, but just change the "V" in "IV" to a "I."
If anything, it would require less real estate, and the change would have been super easy. I mean, I could do that using only Tile Layer.

Truth is, though, I do prefer the look of the FFIIUS title screen.

542
Final Fantasy IV Research & Development / Re: Japanese Title Screen
« on: April 03, 2015, 11:59:30 PM »
Whew, so this is another thing that's turning out to be way more complicated than I originally expected.
 :bah:
So whereas tile layout data for the us version is pretty straightforward - all tiles arranged in order (except only 28 rows are used - the last 0x100 bytes are seemingly worthless) - the Japanese layout is... Not so simple.

The layout data begins (as far as I can tell) at 46800. There's 0x180 bytes representing the top layer of "FINAL FANTASY IV" followed by 0x180 bytes for the bottom layer. Each of these layouts fills only the vertical space occupied by the FINAL FANTASY letters. Somehow the game knows not to put anything in the top 8 or so rows.
After the layout data for FINAL FANTASY IV, there's a few bytes that are doing... Something... Then there's layout data for one layer of the crystal. It's the layer that shows up second (not the image of the crystal that appears before anything else). I don't know if it's the top or bottom layer because they're not off-set like the letters are. the crystal layout data only arranges tiles within the vertical and horizontal space occupied by the crystal. Again, somehow the game simply knows not to put anything in the empty (black) space.  I don't know where to find the layout data for the other layer of the crystal, but I've kinda run out of steam for the day, so I stopped looking.

I also documented just about every routine FFIVJ runs up through the title screen. Unfortunately, there's a lot more going on there than in FF2US, but creating something that is similar enough seems within reach.

The biggest roadblock I'm facing here is that I have no idea how the SNES handles graphics in layers.
Using the information I've gathered thus far, I could probably put together a fairly reasonable facsimile of the Japanese title screen in the US version, including (probably, but I'd have to write my own routine, I think) the flashing effect... But I don't think I know enough about SNES graphics processing to recreate multiple layers.

Not that I'm not willing to learn, but I don't really know where to begin.
Anyone have any insight into this?

543
Final Fantasy IV Research & Development / Re: Japanese Title Screen
« on: April 01, 2015, 11:55:00 AM »
Oh, sure, that's what will have to be done, unless it turns out that the stuff in FFIIUS is the easier stuff to move.

544
Final Fantasy IV Research & Development / Re: Japanese Title Screen
« on: March 31, 2015, 10:19:10 PM »
I didn't have a lot of time to look into it this morning, so I don't know for sure, but there's definitely code (or data?) in the US version that does not run during the title screen, which occupies the space that in the Japanese version controls the flash effect. I set a breakpoint and ran ffiius and there was no break at the title screen.
So, yeah...

545
Final Fantasy IV Research & Development / Re: Japanese Title Screen
« on: March 31, 2015, 05:25:38 PM »
You'd think so, right?
No, unfortunately not so.
I took a look under the hood of the Japanese title screen today. Didn't have the chance to get deep into it, but I was able to zero in pretty easily on the active palettes, as well as the routine that causes the flashing effect.

To put it as simply as possible (I'm not home right now anyway, so simple is the best I can do anyway), the game uses four palettes for the title screen: one for the black background, two for the "final fantasy" and one for the crystal. The active palettes (as is the case for most palettes in the game) are stored in RAM at 0CFB. These are constantly reloaded from a static location in RAM in the 0A00s (0A7C or something like that). Then, there's a constantly rotating byte in the 0600s (0675 or something). When the value there/2 is under 16, the game runs through a special set of instructions (otherwise skipped by way of a BCS) that causes a single color in the palette to turn white for a cycle. As X counts up, which color is white increases, 11 cycles until 1/2 that value at 0600-whatever is no longer less than 16.
It's a relatively simple process, however the problem with porting it over to FFIIUS is that none of this happens in that version... And the place in ROM where this routine is (beginning at 8002, I think, in LoROM, so right near 0000 in ROM) is occupied by other stuff in FFIIUS. So this will require finding a new place to put all of the instructions.
I mean, definitely possible, but it'll take a while to work out.

I'll keep ya posted as I make progress.

546
We'd have to run some tests to be sure, but I think "triggered event data" refers to the data that tells the game (hypothetically, as I am at work and nowhere near the real data right now): "event call 05 = run event B2 if flag 61 is set and flag 65 is clear"

547
OK, I remembered you talking about the "enemy ran away" routine, but didn't really remember what it actually did. So party running away is still out there somewhere, then. Guess I'll put it on the list of stuff to find at some point.

So all of those blank spaces seem safe according to ff4.txt with the possible exception of  977F0, which includes the data yousei has listed as "triggered event data," which I assume is the details of trigger event IDs, something that is definitely editable and expandable using FF4kster, which makes it dangerous to use...

548
Yeah, what I'm theorizing here is that the "enemy ran away" routine might actually be the party running away routine.
The way I see it (and maybe I'm wrong, wouldn't be the first time) the party running away routine must be mixed in among the commands somewhere.

Surely you've seen yousei's document. I think we've discussed it before. If you download his FF4ed utility, it's packaged in with that. It'll be in its own subfolder called "documents" when you unzip the utility. I'm pretty sure the ROM map assumes v 1.0 (everything else yousei did specified 1.0) but the addresses are all close enough to give a broad overview of where most things are in ROM.

549
Wait - hang on. All this time when you were talking about "retreat," I assumed it was the thing that the soldier captain does after the three soldiers are defeated. Are you telling me that that's the same routine as when the party runs away?

No, you know the document. Yousei's document. Maybe it's called ff2.txt? Sorry if I made that more confusing. I haven't even had my computer on for the last week or so.

550
Wow, so this is a grand scale type thingy you've got going on!

The expanded spell routine space is what excites me the most personally, for sure, but something like this would really open up the platform for experienced hackers with good ideas to really play around...

Couple things come to mind immediately:

1) I was actually talking about whatever it is that makes the party run away, as in when you hold L and R... But is it possible that that is the actual use of what we've thus far referred to as the "Enemy Runs Away" routine? I'm not gonna get into actually doing stuff this evening, but tomorrow I might try setting a breakpoint to that routine and hold L and R to test that theory out...

2) be careful of those big empty spaces. Compare their locations with the ROM map in ffiv.txt. I had a brush with disaster recently by carelessly using some space in the 90000 block (I think). I was using some supposedly empty space after dialogue bank 3, and I was unaware of it. A long time later, I edited bank 3 in FF4kster and it almost destroyed my game. Took a long time to figure out what went wrong. Had do DL this utility called IPS Peek that analyzes a patch to tell you exactly which parts of ROM it affects, then compared each of those places between a ROM that was and was not patched with the recent changes. Took several hours to figure it all out, and that was only after I figured out that I'd be able to do this at all. Anyway, point is that I'm wary of big empty spaces now... Heh, I developed ROM agoraphobia. But as long as you know what is surrounding the free space you're using, you should be fine.

551
Heh... Yeah. Setting aside the fact that I've been using a year-old version of FF4kster because later iterations are no longer compatible with my hack, this has been a thing I have been dealing with for quite some time now. Programming AI takes me a long time because every time I want to make a monster use a monster spell, I have to open the spell editor and scroll through studying the spell routines until I find the Garbled mess of spell names that is actually the spell I want.
I'm not complaining, mind you. I know that I've made more edits to my ROM than are advisable if one wishes to use FF4kster most effectively and I am happy to suffer the consequences. I'm just relating exemplary experiences.

552
This is a really cool Idea. I'm a little hazy (maybe you went into more detail somewhere else?) On the details of exactly which limits you've overcome to the original set of commands.
As I see it, the limits are:
1) bank 03 space (not too difficult to overcome)
2) command name space (pretty sure command names are wedged into a bank of other text data, like character default names &c. This could probably be moved pretty easily, as long as you find all of the pointers into command name data and adjust them appropriately)
3) command ID numbers - probably the toughest to overcome because of how the game regularly adds C0 to the ID for various functions, meaning there can only be a maximum of 3F commands, ever, and we want to make sure to not overwrite things like Change, Parry, Show (well, except in hacks that get rid of Hide), Off, Land (the second half off Jump), the ending portion of Spirit Wave, Running away (I don't think we've ever explored this, but it must be a command), whatever else I might be forgetting...

553
Yeah, that was something I stumbled upon and eventually had to work with and around for the Shadow Party hack.

I see you two have been busy little bees while I was away. I have a lot to catch up on. :)

554
If I'm understanding correctly, you could actually make the max stat increase 8.
0,1,2,3,4,5,6,7 would raise the stat 1,2,3,4,5,6,7,8 respectively. You wouldn't use the instruction to raise a stat by zero, after all.
Also, would this be able to raise multiple stats with one instruction? For instance, if I made my parameter "CX" would it raise both Wis and Will by X?
Also, I don't really understand what you're saying about Z...
I'm going to disappear for about a week - got some real world stuff I need to do - so this will be my last message for a while.
Some cool stuff happening here, though. I look forward to seeing what develops!

555
A small amount of custom ASM could also be written that tells the default "change character graphic to xx" instruction that, if the parameter indicates DK Cecil, P Cecil is an acceptable alternative.
I actually did something like that for my hack, though not exactly that.