Aslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=278;area=showpostse:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/indexae5a-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/indexae5a-2.html.zxg^0P.NOKtext/htmlISO-8859-1gzip8:NTue, 10 Mar 2020 19:25:04 GMT0 0Pg^/N 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

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 »
1
Final Fantasy IV Research & Development / Re: [Introduction] + FF4 MGE - ver0.40 + [Hack Help] Imp Caller Orb crashes game?
« on: March 22, 2018, 07:22:43 PM »
yeah, it almost definitely has to do with the edits you made to the dialogue bank right before the bytes in question. Every time you save with FF4kster it does the same thing, wherein it accidentally bleeds that dialogue bank into that little bit of code that deals with caller's orbs.

Best thing to do: Start with a version of your ROM that works (with all the edits you've made thus far, plus the fix I helped you with); make a copy of the file; open the ROM in FF4kster; don't make any changes with FF4kster but save changes in FF4kster; use Lunar IPS to create a patch, using the saved-with-FF4kster version as the "base" and the original working ROM as the "edited." Then, every time you make edits with FF4kster, apply this patch afterwards.
A bit more work up front, but easier to deal with than hex editing every time thereafter.

2
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: February 23, 2018, 06:01:13 PM »
My plan is more to make it "does it make sense that the character would leave his/her equipment?" So, the people in the shipwreck won't leave their equipment, because why would they stop to take all their armor off before falling off the boat? Every time Kain leaves it is sudden and "unexpected," too, so he won't leave his equipment. Cid, however, is like, "I'm gonna stay here in the dwarf castle for a while, see ya later!" So it makes sense that the party would be like, "OK, but can we have all those weapons and armor back that we spent all that money on?"
Tellah dies right in front of you. It's kinda weird, but the party could choose to take his equipment off before they move on to save Rosa.
So I'll be looking at each departure and deciding if it makes sense story-wise that they might leave their equipment benind.

3
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: February 23, 2018, 09:38:32 AM »
No that's all part of the game. The only thing I'm showing off here is that I was able to make the "choose what to take" screen appear when a character departs, if and only if a) the character has items equipped, and b) The character has a particular flag set to indicate that their equipment is "keep-able."

4
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: February 23, 2018, 08:07:33 AM »
Update time!

Progress has been slower than I had hoped it'd be, but I have a LOT of RL stuff going on these days.

Anyway, I perfected the part of the mod that enables the player to keep a character's equipment when they depart.

If the character is set to "discard," then equipment is lost, but if they are set to a shadow slot the player will have the option of keeping their equipment. In the full mod, this will be a choice depending on whether it makes sense in the story - you won't get to keep any of the equipment from characters lost in the shipwreck, but you'll get to keep Cid's stuff.

https://youtu.be/T7gjur_2-v4

5
General Discussion / Re: Slick was down
« on: February 20, 2018, 10:25:08 PM »
Yeah, I was actually surprised that I was able to get it to load today. It's been about five weeks since the last time I could connect reliably.

6
Final Fantasy IV Research & Development / Re: [Introduction] + FF4 MGE - ver0.40 + [Hack Help] Imp Caller Orb crashes game?
« on: January 14, 2018, 10:23:54 PM »
Happy to help!
 :happy:

7
Final Fantasy IV Research & Development / Re: [Introduction] + FF4 MGE - ver0.40 + [Hack Help] Imp Caller Orb crashes game?
« on: January 14, 2018, 05:48:22 PM »
Hey, Mike.

So, I can't say how this happened to your ROM, but the crash is happening because part of the routine got Zeroed out. Specifically, it's the subroutine at FC600 (in LoROM), which is 7C600 if you open your ROM in a hex editor. Looking at what data are where, I can only assume you edited the Abnormal Status text a lot, and FF4kster accidentally bled the empty space at the end into that routine. But that's just a guess.

Anyway, what you need to do is open your ROM and a clean ROM side-by-side in a hex editor, and copy the three lines beginning at 7C600 from the clean ROM into your ROM. That should fix it.

8
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: January 12, 2018, 02:27:27 PM »
Well, thanks! I sure hope it all turns out as well as I envision it. So far I haven't hit any major roadblocks!

9
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: January 12, 2018, 08:39:55 AM »
In terms of FuSoYa's availability for the final battle, I plan to have him available.

Because the PHS system is replacing the Namingway screen, it will be relatively simple to insert a set-your-party prompt into an event.

As for making FuSoYa available through PHS when he wasn't before, that's been accounted for. When a character is removed from the party, they will be set automatically to a "Not Available in PHS" status (which PHS will recognize by the MSB being set in the character's level byte) When an event script calls for "Add Character to Party," the routine will check that level byte. If the MSB is set, then the "Add Character to Party" command will simply clear the bit. If the bit is not set, then the character will be added to the party. It's a relatively simple way to work PHS availability into event scripts without disrupting much else. Of course, it will require me to edit every already-existing event to add an extra "Add Character" command every time a character is actually supposed to be added, but I consider that a small price to pay in the long run.

As far as not-in-party characters participating in autobattles (I guess FuSoYa is the only one, but I may face a similar type of situation with the Cecil vs. Cecil battle and Adult Rydia's return), I'm not fully sure how this will work yet, but I'm confident that I can figure it out when necessary.

10
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: January 09, 2018, 09:14:25 AM »
Thanks!
I spent the better part of yesterday just preparing a ROM to reinvestigate the add character/remove character/re-add character routines, which was an unflinching reminder of what a massive undertaking this project is going to be. With a lot of hard work, I'm still probably a month away from a final product. But at least it has a visible end. You know, unlike TfW which will probably be a WIP until just before I die =p

I've got a routine worked out that will add the equipment of a removed character into the player's inventory, or bring up the "choose what to keep" screen if the player's inventory is full. I'm pretty sure it will work, but I'm nowhere near the point where I can actually write it into ROM and run it, so there's not really anything to show ATM.

The other thing I did is create a ROM with FF4kster that gives me easy access to all of the different party-change situations. Essentially, I turned the town of Baron into a sort-of debug room. The four buildings across the front of the town are now Rydia House, Kain House, Tellah House and Edward House.
In Rydia House, there are two Kid Rydias and Two Adult Rydias, which will add and remove the respective character when spoken to.
In Kain House, there are three Kain's - one which adds Kain from ROM, one which adds Kain from RAM, and one which removes either Kain from the party.
In Tellah House, there are four Tellahs. One adds Tellah (from ROM), one removes Tellah, one "transforms" Tellah into his ultimate version (like what happens on Ordeals) and one removes ultimate a version Tellah.
Edward House just has two Edwards - one to add Edward and one to remove him.

If I'm not mistaken, this should be an example of every kind of party change dynamic in the game, which will allow me to breakpoint the add character and remove character functions in order to see all of their routines in action.

All of that was just prepwork to begin investigating what normally happens so I can formulate a plan for how I'm going to hack it.

Good times...

11
Final Fantasy IV Research & Development / Re: FF4kster's mystery flags/bytes
« on: January 07, 2018, 08:06:07 AM »
Hey, Pinkpuff, long time.

I don't have a running list of them,  it I'm sure I would know at least some by context. Do you perchance have a list of everywhere the program labels something a mystery flag or byte?

12
Final Fantasy IV Research & Development / Re: FF2US -- Mimic Glitch + Kick = Softlock
« on: January 05, 2018, 08:08:47 PM »
Sorry, but as much as I've studied and messed around with the inner workings of FFIV, I'm not very familiar with what may be well known glitches, so... How do you trigger the mimic glitch?

13
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: January 03, 2018, 10:31:06 AM »
*whew*

writing these routines took quite a bit longer than I expected, but it works!

Some screenshots, which show off the ability to load different palettes depending on who's in the party, and also the ability to determine if a slot is empty, and leave the space blank:







Ignore the image of Namingway in the top corner. He won't be there anymore once I swap out the routine that loads him for the one that will load the character portraits.

For those interested in seeing the ASM:

Main Routine
Code: [Select]
$01/9DF5 A9 00       LDA #$00   
$01/9DF7 85 F0       STA $F0   
$01/9DF9 A2 00 00    LDX #$0000
$01/9DFC DA          PHX        ;Preparing registers
$01/9DFD 22 60 FD 0B JSL $0BFD60 ;Routine that assigns palettes 1-5 (04,08,0c,10,14) to each character graphic
$01/9E01 A0 00 00    LDY #$0000
$01/9E04 FA          PLX       
$01/9E05 22 85 FD 0B JSL $0BFD85 ;Routine that determines if a character is present in each slot, and if so loads the appropriate tiles
$01/9E09 22 AC FD 0B JSL $0BFDAC ;Routine that loads the appropriate palette for each character
$01/9E0D C2 20       REP #$20   
$01/9E0F 8A          TXA       
$01/9E10 18          CLC       
$01/9E11 69 40 00    ADC #$0040
$01/9E14 AA          TAX       
$01/9E15 98          TYA       
$01/9E16 18          CLC       
$01/9E17 69 06 00    ADC #$0006
$01/9E1A A8          TAY       
$01/9E1B E2 20       SEP #$20   
$01/9E1D E6 F2       INC $F2   
$01/9E1F C6 F0       DEC $F0   
$01/9E21 D0 E2       BNE $E2    ;Loops back to 19E05 to run four more times, for each character slot
$01/9E23 64 F2       STZ $F2   
$01/9E25 20 B2 80    JSR $80B2  ;DMA transfer of all palette data into CGRAM
$01/9E28 20 36 94    JSR $9436  ;DMA transfer of tilemap into VRAM
$01/9E2B 60          RTS       
Palette Assignment Routine:
Code: [Select]
$0B/FD60 A9 02       LDA #$02   
$0B/FD62 85 F2       STA $F2   
$0B/FD64 A5 F0       LDA $F0   
$0B/FD66 1A          INC A     
$0B/FD67 0A          ASL A     
$0B/FD68 0A          ASL A     
$0B/FD69 9D 63 B7    STA $B763,x
$0B/FD6C 9D A3 B7    STA $B7A3,x
$0B/FD6F 9D E3 B7    STA $B7E3,x
$0B/FD72 E8          INX       
$0B/FD73 E8          INX       
$0B/FD74 C6 F2       DEC $F2   
$0B/FD76 D0 F1       BNE $F1   
$0B/FD78 E8          INX       
$0B/FD79 E8          INX       
$0B/FD7A E6 F0       INC $F0   
$0B/FD7C A5 F0       LDA $F0   
$0B/FD7E C9 05       CMP #$05   
$0B/FD80 D0 DE       BNE $DE   
$0B/FD82 7B          TDC       
$0B/FD83 EB          XBA       
$0B/FD84 6B          RTL       
Character Tile Assignment Routine:
Code: [Select]
$0B/FD85 BD 00 10    LDA $1000,x
$0B/FD88 F0 21       BEQ $21   
$0B/FD8A BD 01 10    LDA $1001,x
$0B/FD8D 48          PHA       
$0B/FD8E 0A          ASL A     
$0B/FD8F 0A          ASL A     
$0B/FD90 0A          ASL A     
$0B/FD91 0A          ASL A     
$0B/FD92 1A          INC A     
$0B/FD93 99 62 B7    STA $B762,y
$0B/FD96 1A          INC A     
$0B/FD97 99 64 B7    STA $B764,y
$0B/FD9A 1A          INC A     
$0B/FD9B 99 A2 B7    STA $B7A2,y
$0B/FD9E 1A          INC A     
$0B/FD9F 99 A4 B7    STA $B7A4,y
$0B/FDA2 1A          INC A     
$0B/FDA3 99 E2 B7    STA $B7E2,y
$0B/FDA6 1A          INC A     
$0B/FDA7 99 E4 B7    STA $B7E4,y
$0B/FDAA 68          PLA       
$0B/FDAB 6B          RTL       
Character Palette Loading Routine:
Code: [Select]
$0B/FDAC DA          PHX       
$0B/FDAD 5A          PHY       
$0B/FDAE C2 20       REP #$20   
$0B/FDB0 0A          ASL A     
$0B/FDB1 0A          ASL A     
$0B/FDB2 0A          ASL A     
$0B/FDB3 0A          ASL A     
$0B/FDB4 0A          ASL A     
$0B/FDB5 AA          TAX       
$0B/FDB6 A5 F2       LDA $F2   
$0B/FDB8 0A          ASL A     
$0B/FDB9 0A          ASL A     
$0B/FDBA 0A          ASL A     
$0B/FDBB 0A          ASL A     
$0B/FDBC 0A          ASL A     
$0B/FDBD A8          TAY       
$0B/FDBE E2 20       SEP #$20   
$0B/FDC0 A9 20       LDA #$20   
$0B/FDC2 85 F4       STA $F4   
$0B/FDC4 BF 00 FD 1C LDA $1CFD00,x
$0B/FDC8 99 20 A0    STA $A020,y
$0B/FDCB E8          INX       
$0B/FDCC C8          INY       
$0B/FDCD C6 F4       DEC $F4   
$0B/FDCF D0 F3       BNE $F3   
$0B/FDD1 7A          PLY       
$0B/FDD2 FA          PLX       
$0B/FDD3 6B          RTL       

The next step in this process will be writing in the system that stores and retrieves characters to and from the "shadow." This will probably also take a considerable amount of time, and there won't really be any screenshots to show for my work when it's all done, but I will post the ASM as relevant routines are completed.

 :cycle:

14
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: December 29, 2017, 04:46:36 AM »
Quote
Would you like to share the code in ASM?

Sure:

Code: [Select]
$01/BA78 A9 0D       LDA #$0D                A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0396 VC:000 FC:24 I:00
$01/BA7A 85 F0       STA $F0    [$00:01F0]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0412 VC:000 FC:24 I:00
$01/BA7C A9 10       LDA #$10                A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0428 VC:000 FC:24 I:00
$01/BA7E 85 F2       STA $F2    [$00:01F2]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0444 VC:000 FC:24 I:00
$01/BA80 A9 50       LDA #$50                A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0460 VC:000 FC:24 I:00
$01/BA82 85 F3       STA $F3    [$00:01F3]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0476 VC:000 FC:24 I:00
$01/BA84 A2 00 00    LDX #$0000              A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0492 VC:000 FC:24 I:00
$01/BA87 A0 60 00    LDY #$0060              A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0508 VC:000 FC:24 I:00
$01/BA8A 20 D0 BA    JSR $BAD0  [$01:BAD0]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0524 VC:000 FC:24 I:00
$01/BA8D C2 20       REP #$20                A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0548 VC:000 FC:24 I:00
$01/BA8F 8A          TXA                     A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0564 VC:000 FC:24 I:00
$01/BA90 18          CLC                     A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0580 VC:000 FC:24 I:00
$01/BA91 69 40 07    ADC #$0740              A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0596 VC:000 FC:24 I:00
$01/BA94 AA          TAX                     A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0612 VC:000 FC:24 I:00
$01/BA95 A5 F2       LDA $F2    [$00:01F2]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0628 VC:000 FC:24 I:00
$01/BA97 69 00 01    ADC #$0100              A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0644 VC:000 FC:24 I:00
$01/BA9A 85 F2       STA $F2    [$00:01F2]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0660 VC:000 FC:24 I:00
$01/BA9C E2 20       SEP #$20                A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIzc HC:0684 VC:000 FC:24 I:00
$01/BA9E C6 F0       DEC $F0    [$00:01F0]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0700 VC:000 FC:24 I:00
$01/BAA0 D0 E6       BNE $E6    [$BA88]      A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0716 VC:000 FC:24 I:00
$01/BAA2 64 F2       STZ $F2    [$00:01F2]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0732 VC:000 FC:24 I:00
$01/BAA4 64 F3       STZ $F3    [$00:01F3]   A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc HC:0748 VC:000 FC:24 I:00
$01/BAA6 60          RTS                     A:0C02 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIzc
This part of the routine essentially sets all of the variables that will be used 13 times over to copy the tiles for each character. The 0D written to 01F0 is used to count the number of times the routine loops. The 5010 written to 1F2 sets the address in VRAM where the data will be written (multiplied by 2, so it actually starts at $A020). The 0060 stored in Y counts the bytes of graphic data copied to VRAM - I'm only using the first $C0 bytes of each character, and since two bytes are written at a time we're counting down from half of C0. Register X functions as an index for the source of copied graphical data.

Code: [Select]
$01/BAD0 8B          PHB                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0020 VC:000 FC:28 I:00
$01/BAD1 A9 00       LDA #$00                A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0036 VC:000 FC:28 I:00
$01/BAD3 48          PHA                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0052 VC:000 FC:28 I:00
$01/BAD4 AB          PLB                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0068 VC:000 FC:28 I:00
$01/BAD5 8D 15 21    STA $2115  [$7E:2115]   A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0084 VC:000 FC:28 I:00
$01/BAD8 C2 20       REP #$20                A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0108 VC:000 FC:28 I:00
$01/BADA A5 F2       LDA $F2    [$00:01F2]   A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIZc HC:0124 VC:000 FC:28 I:00
$01/BADC 8D 16 21    STA $2116  [$7E:2116]   A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIZc HC:0140 VC:000 FC:28 I:00
$01/BADF E2 20       SEP #$20                A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envmxdIZc HC:0164 VC:000 FC:28 I:00
$01/BAE1 BF 00 80 1A LDA $1A8000,x[$1A:3D0C] A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0180 VC:000 FC:28 I:00
$01/BAE5 EB          XBA                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0196 VC:000 FC:28 I:00
$01/BAE6 E8          INX                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0212 VC:000 FC:28 I:00
$01/BAE7 BF 00 80 1A LDA $1A8000,x[$1A:3D0C] A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0228 VC:000 FC:28 I:00
$01/BAEB 8D 19 21    STA $2119  [$7E:2119]   A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0244 VC:000 FC:28 I:00
$01/BAEE EB          XBA                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0260 VC:000 FC:28 I:00
$01/BAEF 8D 18 21    STA $2118  [$7E:2118]   A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0276 VC:000 FC:28 I:00
$01/BAF2 E8          INX                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0292 VC:000 FC:28 I:00
$01/BAF3 88          DEY                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0308 VC:000 FC:28 I:00
$01/BAF4 D0 EB       BNE $EB    [$BAE1]      A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0324 VC:000 FC:28 I:00
$01/BAF6 7B          TDC                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0340 VC:000 FC:28 I:00
$01/BAF7 EB          XBA                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0356 VC:000 FC:28 I:00
$01/BAF8 AB          PLB                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0372 VC:000 FC:28 I:00
$01/BAF9 60          RTS                     A:0C00 X:BD0C Y:0300 D:0100 DB:7E S:02DD P:envMxdIZc HC:0388 VC:000 FC:28 I:00
And this is the part of the routine that actually copies the data into VRAM. You may notice that the routine writes the data one byte at a time by writing to $2119 and then $2118. I was originally under the impression that I could write a two-byte value to $2118, but it turns out that doing so copies the two bytes to bytes $00 and $02 in VRAM, which is weird and unhelpful. But I figured out this workaround, so no problem.


The end result of all this has the tile data written as characters 01, 02, 03, 04, 05, 06, 11, 12, 13... D6. This leaves a lot of unused space in VRAM, but is much easier to index.

Quote
Since the tutorial was more of introduction rather detail coding, would you like to do some practical coding? I'm going to give standalone tasks, that doesn't require zillions of line of code, you must make the ASM code. We will test the result in emulators. I found a small library that produce all the initialization you need, so you can focus mainly on the task that I'm going to give. It doesn't require specific library (so you can implement whatever is on your mind, not limiting yourself to specific) but has defined all PPU registers for easy use (by name rather numbers). So far it produces small 32k ROM files that you can load in any emulator.

Yeah, that sounds like a good exercise. Not sure when I'd be able to get to it, but let's see what you've got.

15
Final Fantasy IV Research & Development / Re: Chillyfeez's Shadow Party Hack V 2.0
« on: December 28, 2017, 11:41:01 AM »
So, slow going, but yesterday I finally got the routine written that loads the battle character "sprites" into VRAM (they're not really sprites in this instance, as they are part of BG1). By tomorrow, I plan to finish the routine that actually displays the images of the characters currently in the party. At that point, I'll finally have some new screenshots to show off!

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 »