øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=278;area=showposts;start=435e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index1cdf.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=278e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index1cdf.html.zxÅåg^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ0P.öBOKtext/htmlISO-8859-1gzip0|ÖöBÿÿÿÿÿÿÿÿTue, 10 Mar 2020 19:25:16 GMT0ó°° ®0®P®€§²ð®Ååg^ÿÿÿÿÿÿÿÿ¸0öB 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

436
Congratulations, Pinkpuf!

It was my pleasure to have been of assistance whenever I could.

Out of curiosity, do you have a particular plan for a NES project?

437
Since I know your hack is kinda parody, you might be interested in this, though: I figured out while working on Pinkpuff's one-moon issue that changing just one byte in the orbiting routine makes the planets orbit in a really wacky wobbly fashion. There really wouldn't be any serious use for it, but watching it made me laugh out loud. I don't have the info handy at the moment, but if that's something you'd be interested, I can dig it up again...

438
Eureka!

I can't believe it was actually this easy...
The reason the Earth visuals in my Moon Flies Off visual effect weren't displaying properly is that the graphics for the spinning Earth are drawn from a bank of RAM (7E:8000-7E:B400 or so) that is written during the Mysidian Legend IN SPACE visual effect.
In vanilla FFIV, the Moon Flies Off effect never happens until the IN SPACE happens first, and since the game doesn't use this block of RAM in between the two, it doesn't bother to rewrite it before the Moon Flies Off effect runs.

In fact, it's the routine that writes this huge block of RAM that is what causes the long pause before the IN SPACE effect actually begins to run (that's the long pause you were talking about, Bahamut ZERO, so no - unfortunately that cannot be shortened unless you want your spinning earth to look weird).

So for my purposes, it's an easy fix... Instead of the Moon through the Telescope effect that I was using in my opening events, I'll run the IN SPACE effect... blank out the text, and shorten the amount of time the effect plays (which can be done by only changing one byte).

And voila! It works like a charm!

This has been an issue that's plagued me for quite literally years, and it's finally solved!
 :banonsmash:

439
That's actually a really good idea, BZ.
I observed the routines for the location title window, and while I could understand and manipulate that pretty easily, it's nothing like the dialogue window in the way it works. The item selection window, being the same size and on the bottom half of the screen, might be more helpful.
I'll give it a try when I finally crack the orbiting earth conundrum I'm currently mired in...

440
Final Fantasy IV Research & Development / Re: Modifying orbiting VFX
« on: June 17, 2015, 05:11:18 PM »
Complicated... Yes. I admit I didn't expect it would take all that when I set out, but all-in-all it was a rewarding experience

441
Right, I forgot about the trigger cap.
You must be able to find one that isn't necessary...
I seem to remember some doorway in the tower of bab-il that the player can never reach... Maybe?
Check also locations with two-tile warping points that could be narrowed...

442
In the trigger editor, hit the "Insert" key when you've selected your location.
Also how you add NPCs, and extra Bank 2 messages in their respective editors.

I should mention, I guess, that I've never tried to add triggers to a location that has none, but it works for NPCs, so I don't see why it wouldn't for triggers.

443
Final Fantasy IV Research & Development / Re: Modifying orbiting VFX
« on: June 17, 2015, 11:55:18 AM »
SUCCESS!

So, OK, if you want, you can skip past all the BS that follows and just download the patch linked herein (apply to an un-headered 1.1 US ROM), but for those interested in the process involved in creating the patch, here goes...

So, as previously mentioned, the sprite data are loaded into VRAM from RAM beginning at 00:0300. The data at 300 are loaded from a couple of different banks in the 12- and 130000s (LoROM... exact location I did not record, and is kinda irrelevant here). The values here are constantly refreshed to control the constantly moving planets, moons and sun. In order to decide which sprite data to use, the game references constantly descending two-byte values beginning at 7E:2000 (I guess they figured, no battle is going on at the time, so why not use this RAM?). A separate routine controls the descent of these values, but I didn' use it at all, so again, kinda irrelevant. Each sprite ends up having four values in the RAM 300 bank. I'm pretty sure they represent x-pos, y-pos, then the standard "vhopppcc cccccccc" sprite data. Since I'm not a computer and cannot easily interpret the x,y values with any accuracy, the trick to cracking all of this was looking at the vhopppcc cccccccc bytes in conjunction with the tile spread in Tile Layer (which technically begins at ACE00, though the first two lines of tiles look like gibberish...).
So, freeze frame, compare tile values with the tile map... from there, it's just a couple of tries before you find the tiles that represent the moon you want to delete. When you want "no sprite," the game uses F0F0F0F0. I don't know why not FFFFFFFF, but eh, whatever.

First problem that arose: the "revlolving moons" don't actually make a full revolution. The sprites at any given (moon) location control half of a full revolution, then skip back to the opposite side for a second pass. Most likely, this was an easier thing to program, because one portion of RAM could be devoted to the smaller sprites (that pass behind the earth) and the other to the larger sprites (that pass in front). So, by observing the constantly descending two-byte values at 2000, I noticed that a (complete) half-revolution always begins when the (one-byte) value at 2000 equals FF. So, pick a previously unused byte (in this case, I chose 7E:2400), and make it toggle between 00 and 01 every time 2000 hits FF. Then, if 2400 = 00, blank out one moon; if 2400 = 01, blank out the other moon. Voila! full revolution!

Second problem that arose: one of the two moons (the behind moon, I think) always uses the data at 300-30F, but the other moon uses different data depending on whether the Earth is in front of or behind the Sun. I originally thought this was because of the moons, but now I think it's actually because of the size of the earth. Anyway, doesn't matter really.
So, I had to figure out 1) exactly where in the 300 bank the changing moon's sprites were located in both situations, and 2) what other predictable values in RAM (in the constantly-rotating 2000 area) I could use to tell the game which of those locations to blank out.
Over the course of the full visual effect, the moons make eleven full revolutions (or, more appropriately, 22 half-revolutions) around the earth. So, I had already made my life easier by setting up that alternating byte at 2400. I set a breakpoint to 2400 and recorded the values at 2000 for each (only the first 12 bytes do anything at all, so that's what's shown here):
Code: [Select]
FIRST CHANGE:
FF 00 FF FF FF 00 53 01 F3 02 80 01

SECOND CHANGE:
FF FF FF FE BF 00 13 01 B3 02 80 01

THIRD CHANGE:
FF FE FF FD 7F 00 D3 00 73 02 80 01

FOURTH CHANGE:
FF FD FF FC 3F 00 93 00 33 02 80 01

FIFTH CHANGE: (GOES BAD HERE)
FF FC FF FB FF FF 53 00 F3 01 80 01

SIXTH CHANGE:
FF FB FF FA DF FF 33 00 D3 01 80 01

SEVENTH CHANGE:
FF FA FF F9 BF FF 13 00 B3 01 80 01

EIGHTH CHANGE:
FF F9 FF F8 9F FF F3 FF 93 01 80 01

NINTH CHANGE:
FF F8 FF F7 7F FF D3 FF 73 01 80 01

TENTH CHANGE:
FF F7 FF F6 5F FF B3 FF 53 01 80 01

ELEVENTH CHANGE: (FINISHES PASS BEHIND SUN)
FF F6 FF F5 3F FF 93 FF 33 01 80 01

TWELFTH CHANGE:
FF F5 FF F4 1F FF 73 FF 13 01 80 01

THIRTEENTH CHANGE: (WILL REAPPEAR IN FRONT OF SUN)
FF F4 FF F3 FF FE 52 FF F3 00 80 01

FOURTEENTH CHANGE:
FF F3 FF F2 BF FE 13 FF B3 00 80 01

FIFTEENTH CHANGE:
FF F2 FF F1 7F FE D3 FE 73 00 80 01

SIXTEENTH CHANGE:
FF F1 FF F0 3F FE 93 FE 33 00 80 01

SEVENTEENTH CHANGE: (GOES BAD HERE)
FF F0 FF EF FF FD 53 FE F3 FF 80 01

EIGHTEENTH CHANGE:
FF EF FF EE DF FD 33 FE D3 FF 80 01

NINETEENTH CHANGE:
FF EE FF ED BF FD 13 FE B3 FF 80 01

TWENTIETH CHANGE:
FF ED FF EC 9F FD F3 FD 93 FF 80 01

TWENTY-FIRST CHANGE:
FF EC FF EB 7F FD D3 FD 73 FF 80 01

TWENTY-SECOND CHANGE:
FF EB FF EA 5F FD B3 FD 53 FF 80 01

After analyzing these data, what I noticed was, whenever the earth and moons are behind the sun (or at least, out of view), the lowest bit at 2009 is 1, and whenever the earth and moons are visible in front of the sun, the lowest bit at 2009 is 0.
So then, the path was clear: load 2009; AND 01; if A = 00, do one thing, if A = 01, do the other.

So, here are the routines...

load 301,x (the y-pos byte):
Code: [Select]
$13/DA95 20 E0 F7    JSR $F7E0  [$13:F7E0]   A:005C X:00B4 Y:0004 D:0000 DB:7E S:02D1 P:envMxdIzc HC:0776 VC:019 FC:21 I:00
~~~~~~~~~~~~~~~~~~
$13/F7E0 48          PHA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0026 VC:000 FC:09 I:00
$13/F7E1 20 80 F8    JSR $F880  [$00:F880]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0042 VC:000 FC:09 I:00
$13/F7E4 D0 06       BNE $06    [$F7EC]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0058 VC:000 FC:09 I:00
$13/F7E6 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0074 VC:000 FC:09 I:00
$13/F7E7 20 60 F8    JSR $F860  [$00:F860]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0090 VC:000 FC:09 I:00
$13/F7EA 80 04       BRA $04    [$F7F0]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0106 VC:000 FC:09 I:00
$13/F7EC 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0122 VC:000 FC:09 I:00
$13/F7ED 20 70 F8    JSR $F870  [$00:F870]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0138 VC:000 FC:09 I:00
$13/F7F0 99 01 03    STA $0301,y[$00:0301]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0154 VC:000 FC:09 I:00
$13/F7F3 60          RTS                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0170 VC:000 FC:09 I:00

Load 300,x (The x-pos byte):
Code: [Select]
$13/DAA9 20 00 F8    JSR $F800  [$13:F800]   A:00DC X:00B4 Y:0004 D:0000 DB:7E S:02D1 P:eNvMxdIzc HC:0498 VC:020 FC:21 I:00
~~~~~~~~~~~~~~~~~~
$13/F800 48          PHA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0186 VC:000 FC:09 I:00
$13/F801 AD 00 24    LDA $2400  [$00:2400]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0202 VC:000 FC:09 I:00
$13/F804 D0 06       BNE $06    [$F80C]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0218 VC:000 FC:09 I:00
$13/F806 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0234 VC:000 FC:09 I:00
$13/F807 20 60 F8    JSR $F860  [$00:F860]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0250 VC:000 FC:09 I:00
$13/F80A 80 04       BRA $04    [$F810]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0266 VC:000 FC:09 I:00
$13/F80C 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0282 VC:000 FC:09 I:00
$13/F80D 20 70 F8    JSR $F870  [$00:F870]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0298 VC:000 FC:09 I:00
$13/F810 99 00 03    STA $0300,y[$00:0300]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0314 VC:000 FC:09 I:00
$13/F813 60          RTS                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0330 VC:000 FC:09 I:00

Load 302,x (Sprite Byte 1):
Code: [Select]
$13/DAB0 20 20 F8    JSR $F820  [$13:F820]   A:0036 X:00B4 Y:0004 D:0000 DB:7E S:02D1 P:envMxdIzc HC:1088 VC:020 FC:21 I:00
~~~~~~~~~~~~~~~~~~
$13/F820 48          PHA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0346 VC:000 FC:09 I:00
$13/F821 AD 00 24    LDA $2400  [$00:2400]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0362 VC:000 FC:09 I:00
$13/F824 D0 06       BNE $06    [$F82C]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0378 VC:000 FC:09 I:00
$13/F826 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0394 VC:000 FC:09 I:00
$13/F827 20 60 F8    JSR $F860  [$00:F860]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0410 VC:000 FC:09 I:00
$13/F82A 80 04       BRA $04    [$F830]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0426 VC:000 FC:09 I:00
$13/F82C 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0442 VC:000 FC:09 I:00
$13/F82D 20 70 F8    JSR $F870  [$00:F870]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0458 VC:000 FC:09 I:00
$13/F830 99 02 03    STA $0302,y[$00:0302]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0474 VC:000 FC:09 I:00
$13/F833 60          RTS                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0490 VC:000 FC:09 I:00

Load 303,x (Sprite Byte 2):
Code: [Select]
$13/DAC5 20 40 F8    JSR $F840  [$13:F840]   A:0002 X:00B4 Y:0004 D:0000 DB:7E S:02D1 P:envMxdIzc HC:0434 VC:021 FC:21 I:00
~~~~~~~~~~~~~~~~~~
$13/F840 48          PHA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0506 VC:000 FC:09 I:00
$13/F841 AD 00 24    LDA $2400  [$00:2400]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0522 VC:000 FC:09 I:00
$13/F844 D0 06       BNE $06    [$F84C]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0538 VC:000 FC:09 I:00
$13/F846 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0554 VC:000 FC:09 I:00
$13/F847 20 60 F8    JSR $F860  [$00:F860]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0570 VC:000 FC:09 I:00
$13/F84A 80 04       BRA $04    [$F850]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0586 VC:000 FC:09 I:00
$13/F84C 68          PLA                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0602 VC:000 FC:09 I:00
$13/F84D 20 70 F8    JSR $F870  [$00:F870]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0618 VC:000 FC:09 I:00
$13/F850 99 03 03    STA $0303,y[$00:0303]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0634 VC:000 FC:09 I:00
$13/F853 60          RTS                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0650 VC:000 FC:09 I:00

Toggle the byte at 2400, and change which values are blanked out when 2400 = 01:
Code: [Select]
$13/F880 AD 00 20    LDA $2000  [$00:2000]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0826 VC:000 FC:09 I:00
$13/F883 C9 FF       CMP #$FF                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0842 VC:000 FC:09 I:00
$13/F885 D0 2A       BNE $2A    [$F8B1]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0858 VC:000 FC:09 I:00
$13/F887 C0 00 00    CPY #$0000              A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0874 VC:000 FC:09 I:00
$13/F88A D0 25       BNE $25    [$F8B1]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0890 VC:000 FC:09 I:00
$13/F88C AD 00 24    LDA $2400  [$00:2400]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0906 VC:000 FC:09 I:00
$13/F88F 49 01       EOR #$01                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0922 VC:000 FC:09 I:00
$13/F891 8D 00 24    STA $2400  [$00:2400]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0938 VC:000 FC:09 I:00
$13/F894 AD 09 20    LDA $2009  [$00:2009]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0954 VC:000 FC:09 I:00
$13/F897 29 01       AND #$01                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0970 VC:000 FC:09 I:00
$13/F899 D0 0C       BNE $0C    [$F8A7]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0986 VC:000 FC:09 I:00
$13/F89B A9 8C       LDA #$8C                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1002 VC:000 FC:09 I:00
$13/F89D 8D 01 24    STA $2401  [$00:2401]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1018 VC:000 FC:09 I:00
$13/F8A0 A9 9C       LDA #$9C                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1034 VC:000 FC:09 I:00
$13/F8A2 8D 03 24    STA $2403  [$00:2403]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1050 VC:000 FC:09 I:00
$13/F8A5 80 0A       BRA $0A    [$F8B1]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1066 VC:000 FC:09 I:00
$13/F8A7 A9 20       LDA #$20                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1082 VC:000 FC:09 I:00
$13/F8A9 8D 01 24    STA $2401  [$00:2401]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1098 VC:000 FC:09 I:00
$13/F8AC A9 30       LDA #$30                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1114 VC:000 FC:09 I:00
$13/F8AE 8D 03 24    STA $2403  [$00:2403]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1130 VC:000 FC:09 I:00
$13/F8B1 AD 00 24    LDA $2400  [$00:2400]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1146 VC:000 FC:09 I:00
$13/F8B4 60          RTS                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:1162 VC:000 FC:09 I:00

Blank out 300-30F if 2400 = 00:
Code: [Select]
$13/F860 C0 10 00    CPY #$0010              A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0666 VC:000 FC:09 I:00
$13/F863 B0 02       BCS $02    [$F867]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0682 VC:000 FC:09 I:00
$13/F865 A9 F0       LDA #$F0                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0698 VC:000 FC:09 I:00
$13/F867 60          RTS                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0714 VC:000 FC:09 I:00

Blank out other (alternating) range if 2400 = 01:
Code: [Select]
$13/F870 CC 01 24    CPY $2401  [$00:2401]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0730 VC:000 FC:09 I:00
$13/F873 90 07       BCC $07    [$F87C]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0746 VC:000 FC:09 I:00
$13/F875 CC 03 24    CPY $2403  [$00:2403]   A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0762 VC:000 FC:09 I:00
$13/F878 B0 02       BCS $02    [$F87C]      A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0778 VC:000 FC:09 I:00
$13/F87A A9 F0       LDA #$F0                A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0794 VC:000 FC:09 I:00
$13/F87C 60          RTS                     A:0010 X:000F Y:0000 D:0600 DB:00 S:02F7 P:envMxdiZc HC:0810 VC:000 FC:09 I:00

So there you have it - One Moon in the Mysidian Legend IN SPACE visual effect!

444
Final Fantasy IV Research & Development / Re: Modifying orbiting VFX
« on: June 16, 2015, 04:11:48 PM »
UPDATE 3
Getting there. I didn't get to work on it yesterday at all, but I was able to chart some numbers today before work. I now have everything I need to make this work, it's just a matter of writing the routines. I'll post them all when the patch is up and running (as well as the patch).
It's all pretty straightforward and observable, though the custom routines will certainly not be an exercise in efficiency.
It all boils down to sprites being copied from the 300 section of RAM to VRAM, and the data at 300 are written depending on variables (believe it or not) at 7E:2000.

Like I was just saying, helping other ROM hackers out often leads to learning stuff that will help me out, and this is no exception. I'm sure that by studying this stuff, I'll finally be able to figure out how I screwed up the earth graphics in my own hack.
 :childish:

445
So, if I understand correctly, you want it to use a normal sword swing by default, but if its special whatever triggers, then it uses a bow and arrow animation instead?

446
Final Fantasy IV Research & Development / Re: Modifying orbiting VFX
« on: June 14, 2015, 10:58:28 PM »
UPDATE 2
Okay, so "a snap" was a bit of an exaggeration of the simplicity of this project.
I mean, I'll get it, but it's going to take a smidge longer than I originally thought.
As of now, the second moon is gone right up to the point when the earth finishes its first pass in front of the sun, but then it reappears for parts of the pass behind the sun.
I think I know why this is happening, and fixing it won't be impossible, but it's going to take a bunch of custom routines (because the moon sprites that I'm blanking out are in different places in RAM depending on where the earth is, I think because the larger moon images require more tiles).
Anyway, gonna take a few days, but I'll get there...

447
Final Fantasy IV Research & Development / Re: Modifying orbiting VFX
« on: June 14, 2015, 05:56:12 PM »
UPDATE
This should be a snap, actually.
I've already zeroed in on all of the data and assembly involved in drawing the planets. It will require a custom routine, because the same assembly and some of the same data are used to draw all of the objects in the effect, but no problem.
Shouldn't take too long, but it will take a little trial and error to get it just right.

448
Well, what the heck, I'll put this up.
I'm trying to figure out how to make the dialogue window appear on the bottom half of the screen instead of the top. For most events, it would make sense, since the main character is always in the center (unless you make yourself invisible and use an NPC stand-in), and the tendency is to make the action occur north of the main character (for several reasons).
Unfortunately, it seems the dialogue window is the hardest of all to manipulate.
I've found this post from many years ago
http://slickproductions.org/forum/index.php?topic=1007.msg10152#msg10152
But the "Main Dialogue Window" referenced there must be something else entirely, because those offsets are not called at all when dialogue appears. (The addresses shown are ROM with header, and yes, I did try converting to LoROM - they're definitely not called)
Kinda too bad HHIPDragonFox isn't still around. He spoke in very difficult-to-understand terms, but if you look at his posts, he was into a lot of really cool stuff. Looks like he cracked five-digit damage display ages before I did.
Anyway, the problem is he never posted anything about the dialogue window.

Nor did Dragonsbrethren in this post:
http://slickproductions.org/forum/index.php?topic=88.0
Again, lots of window data, but not the primary dialogue window.

I also found the sprite map for the window frame, at $14/F6D6 (that's LoROM, it's 976D6 in ROM without header), but that information on its own doesn't help me change where on the screen those sprites are drawn.

So... Any graphics gurus out there reading this and have any insight?

449
Final Fantasy IV Research & Development / Re: Modifying orbiting VFX
« on: June 14, 2015, 08:13:28 AM »
Probably... just the IN SPAAACE effect?
That is, you don't need it removed from any of the other space visual effects, right?
I recently looked into trying to fix the earth graphics in the "moon flies away" VFX in the opening of TfW. No luck there, but in messing around with it I was able to change the graphics of just about every other object in the effect, the experience of which may have been enough to help in this situation (assuming the planetary graphics are encoded similarly). I'm off today and could use a break from the toil I've gotten myself into lately. No promises, but I'll look into it.

450
Quote
I want to find out how to shorten the length of time it takes for the visual to start (feels like 8-10 seconds), but for now I'm taking baby steps haha

If you mean the amount of time between when the visual effect begins, and when the scrolling words first appear on the screen, check for a bunch of spaces and/or line breaks before the text begins. It might actually be that simple.