øAslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=15e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index2174.htmlslickproductions.org/forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index2174.html.zx?›h^ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈà•¤zõOKtext/htmlISO-8859-1gzip(¾ÖzõÿÿÿÿÿÿÿÿWed, 11 Mar 2020 08:19:35 GMT0ó°° ®0®P®€§²ð®>›h^ÿÿÿÿÿÿÿÿø*zõ Show Posts - assassin

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 - assassin

16
Final Fantasy IV Research & Development / Re: Filly Fantasy IV
« on: October 06, 2017, 01:43:33 PM »
^ this is identical to your 10/3 post, aside from changing 5 nonessential words.  why not flip a coin and delete one?

17
Game Modification Station / Re: New patch: Color Wheel tweak
« on: October 05, 2017, 02:58:23 PM »
- thanks; i follow better now.
- yeah, some of the SoE status colors aren't too visible on certain terrain backgrounds to begin with, so when things speed up with multiple statuses, it gets harder yet to tell what i'm seeing.  not to mention, some individual status indicators involve multiple colors, iirc.  the 4 status per entity cap limits the madness some, but it's still not fun.

maybe FF6 could get away with half the length of vanilla periods or so, but it's probably not worth the work.  for a status to take any appreciable toll on you, it needs to last awhile.  if it's gone by the time its color is due for showing and you never get to see it, no harm no foul.

18
Game Modification Station / Re: Remaining bugs in FF3us
« on: October 05, 2017, 02:24:48 PM »
dude:
http://masterzed.cavesofnarshe.com/GameDocs/ff3bug.txt
"Prevent manual character targeting with certain attack animations"

this and the Chocobo thing make me think you're ignoring the best single source of bugs on this game (admittedly not complete, as Square programmers are somehow still adding bugs to FF6 -- some of them from beyond the grave -- but it's a superb starting point for any research).

19
Game Modification Station / Re: New patch: Color Wheel tweak
« on: October 05, 2017, 02:15:59 PM »
sounds spiffy.. the SoE makers will be flattered. ;)

trying to follow along, and a few questions:
- what is the wait bit?  i don't see mention of it in your vanilla disassembly.  and why once cleared, is it apparently never set again?
- why do you rotate $2EA9,Y in two different loops?
- sort of a combo of above two: you normally won't clear the wait bit until in the second loop, but will do it after the first loop when reaching "reset_rotation:".  is it assumed that once you've iterated that much, whatever reason there was for the initial wait has subsided?

if the patch users had true mastery of the Almighty Color Wheel, you should have been able to simply mix the applicable colors, and let them interpret the result.  but i guess that one will need to wait until humanity is further evolved. ;)

20
General Discussion / Re: RHDN Currently Down
« on: October 03, 2017, 06:16:51 PM »
as in "Different Final Fantasy XII releases?" ?

that is on archive.org and in the fleeting google cache, if you need to refer to anything in it.

21
Final Fantasy V Research & Development / Re: What emulator to use?
« on: September 15, 2017, 03:24:07 PM »
uh, pretty much all of them, provided filenames without extensions match, e.g. FILENAME.ROM and FILENAME.IPS, and are in the same directory.

22
- maybe if i sandwich his username in between enough profanity, it'll act as a summon, and he'll finally make his first post in 9.5 years.
- thanks.
- yeah, the board was offline for nearly a week.  9 days is a fairly timely reply regardless, so no complaints here.

-----------

Quote from: me
dunno whether it was a manual typo, or if there's some wider malfunction in any program he's using to automate things.

investigating this some, here are match counts for text searches in his entire disassembly:

"ASL A : LSR" = 1
"LSR A : ASL" = 1

"LSR #3 : ASL" = 1
"LSR #4 : ASL" = 1

(no other matches for "ASL/LSR #N : LSR/ASL" (with N 1 thru 5) were found.)

that seems a bit low, but it could just be Nintendo's coding style.  and i can't say anything concrete without knowing the actual number of these pairs used in the game.  which i unfortunately have no idea how to search for 2 bytes at a time without a billion false positives.

so hopefully MoN will see this topic, and shed some light on whether he used any automation to generate these pseudo-instructions.

23
Final Fantasy IV Research & Development / Re: Filly Fantasy IV
« on: September 11, 2017, 10:02:54 PM »
thank you for reformatting
in your latest installment of
what will no doubt be a
feasible and successful hack.
due to unforeseen financial
hardship, i recently lost
Internet access.  thus, i am
resorting to surfing the Net
through a generous but
overly cautious neighbor's
mail slot.  posts with wider
lines are baffling at best,
or horrible taunting of what
i'm missing at worst.  i
expect to emerge from this
downturn stronger than
ever, and seek no material
handouts here.  however,
i do lean on my SNES
hacking brethren for moral
support even more than
usual.  it's the little things
that matter.  from
encouraging words, to
playtesting, to aiding in
deciphering for projects in
my growing backlog, to
formatting posts to have
a width equal to that of
the mail slot.  all of these
kind gestures will help me
stay afloat in my ROM
hacking, and inspire me to
get back on my feet faster;
all of them will be fondly
remembered.
     Warmest
       Regards,
          Assassin

               PITNEY BOWES
             $000.34
003167432    SEP 12 2017
MAILED FROM ZIP CODE 54321


24
Game Modification Station / Re: New patch: Caravaggio Bug fix
« on: September 05, 2017, 06:31:33 PM »
if space is a concern, another way to go about it is to not have "enemy_roulette" mess with $3415, then do something like this:

Code: [Select]
org $C231D3

lda $3a7c
pha

lda $b3
lsr
bcs noBlitzFail
lda #$1e
sta $01,s
bra noForceRandom
noBlitzFail:
lda $3415
bmi noForceRandom
lda #$40
tsb $ba
noForceRandom:

...

pla   ; was "LDA $3A7C"
CMP #$1E       ; did we have either original command of Enemy Roulette, or a set Failed Blitz Input flag?

a bit more intrusive, as it edits a general function instead of just adding a bunch of code to a Roulette-specific one.  but the assumption that a failed Blitz wouldn't want to randomly retarget seems fairly safe, given the other steps it takes.

:edit: scrapped more complicated code that wasn't any smaller.

25
Round 2 of staring at the computer screen for hours and wanting to put my face through it.  but this time, not due to my own retardation.

so i code the discussed space optimizations in mid-February, not touching the file since 2/16.  then yesterday, i pick it up again, and add/tweak a few labels so it'll assemble.  but it runs like a mess.  when a torch extinguishes, it's still illustrated as burning, and random un-lit torches show up in the wall or elsewhere on screen.  occasionally, they'd disappear from their original places.

this is another case of "no way my changes are causing this".  i stared at it so long that it took me from alert to fatigued, with frustration and rage varying but persisting through many levels of consciousness.  a little after waking up today, i finally pin down the issue to MathOnNapkins' disassembly (from which i've copied much of my code on this iteration; why rebuild the wheel?):

Code: [Select]
        LDA $0540, Y : ASL #2 : STA $0540, Y : STA $7EFB40, X
that should be "ASL / LSR".  while the two ASLs did seem a little odd yesterday, it took scanning an original disassembly today to learn the problem.  dunno whether it was a manual typo, or if there's some wider malfunction in any program he's using to automate things.

drove me effing nuts!  i can't really judge, as i've had incorrectly disassembled or typed instructions in my own documentation sometimes.  but these pseudo-instructions (see also: "CLC / ADC $nn" becomes "ADD $nn") annoyed me even before this issue popped up.  this is assembly language; don't obscure stuff from the reader.

anyway, this substitutes for torch-light-and-go-out-new-complex1a2.asm (which itself replaced light-torch-new1.asm and torch-go-out-new1.asm):

http://assassin17.brinkster.net/forum-posts/zelda-torches/torch-light-and-go-out-new-complex2a1.asm

it seems to run alright.  but if you're up for further testing, that'd be appreciated.  i hesitated to ask when i knew this is not a final product candidate (as it still needs $0414 and/or room-specific checks).  but clearly, this cursed project needs to be checked at every remotely major update..  because when it's not me forgetting how to count bytes, there's trouble like this.

---

EDIT: to refresh (in case you didn't spend the last 6.5 months thinking about this patch): you want to apply a palette handler along with the above .asm file.  you preferred palette-putz2d5b.asm , available in the first post's .ZIP file.

26
Game Modification Station / Re: Remaining bugs in FF3us
« on: August 29, 2017, 06:38:40 PM »
random thoughts:

- maybe the BG3 Priority flag is set generally so text shows up on top of everything?  namely boxless text, as textboxes seem to clip (or delete?) sprites.
- on some screens (e.g. Albrook, Cid's house exterior), a portion of the party sprite will be moved between Priority 2 and Priority 3, depending on where you're currently standing.  the beach looks to be Priority 2 all the time (albeit tested without fish, bird, magicite, Cid, or raft present).  that could give some flexibility in using additional priorities for whatever fix is eventually pursued.
- something that poses a challenge before register access or hardware programming: there is low tide and high tide here.  conceptually, the "height" the water is relative to a character should vary.  having a constant portion of the sprite submerged might look better than having it all on top, but it'd still be at odds with the wave movement.

EDIT: come to think of it.. because the tide is fairly gentle and the absolute height of a character is pretty small, depth changes from tide would probably translate to just 1-2 pixels in water height.  so small enough to ignore without looking too off, and not worth the ungodly amount of effort it'd take to represent.

27
Game Modification Station / Re: Remaining bugs in FF3us
« on: August 20, 2017, 11:49:25 PM »
maybe write a specialized event function and command to copy the lead character's palette data into one of Palettes 0 thru 3 when entering that screen (and exiting the main menu)?  which palette numbers aren't claimed by Cid, fish, the bird, the raft, magicite, etc?

:edit: (9/14/17) to elaborate:

if (lead character's palette < 4) then begin
 copy palette data into a palette slot that's >= 4
 assign the higher palette slot to bottom sub-sprite
end
else begin  ; character's palette is >= 4
 copy palette data into a palette slot that's < 4
 assign the lower palette slot to top sub-sprite
end
 
iow, like the Transparency article said: "One way around this is to make palettes 4-7 mirrors of 0-3 so that you can select individually on each sprites".

Quote
Unfortunately, there's a major flaw: the game is set up so that layer 3, which shows the waves, will be displayed on any map either over all sprites or beneath all sprites, regardless of the sprite's priority.

how much of this area is broken should you disable the BG3 Priority flag there?

28
Game Modification Station / Re: New patch: Bird Bars Glitch fix
« on: August 19, 2017, 03:58:58 PM »
*checks* yep, they'll step forward beforehand.  a subtle difference from normal, but probably not worth it to save some space.

29
Game Modification Station / Re: New patch: Caravaggio Bug fix
« on: August 19, 2017, 11:37:52 AM »
the Sketch target is already copied to the backup variable by that command's call to C2/317B.  normally, Sketch zeroing $3415 after that prevents the command invoked by Sketch from overwriting it.  however, Enemy Roulette now does so, due to FFh'ing $3415.  i suspect you do this to try and keep the Roulette targets empty to start?

it's like we want to preserve and restore $3A30 if Enemy Roulette is being run by Sketch:

Code: [Select]
stz sketchFlag

LDA #$FF
TSB $3415
bne noSketch
inc sketchFlag
noSketch:

...

lda $3a31
pha
lda $3a30
pha

JSR $175F

rep #$20
pla
dec sketchFlag
bne noSketch2

sta $3a30
noSketch2:
sep #$20

only 700 added bytes!

moving the $3415 writing to after the $B3 and $B5 ones can shorten (and speed up) that some:
Code: [Select]
...

LDA #$FF
TSB $3415
bne noSketch

lda $3a31
pha
lda $3a30
pha
JSR $175F
rep #$20
pla
sta $3a30
sep #$20
bra continue

noSketch:
JSR $175F
continue:

30
Game Modification Station / Re: New patch: Caravaggio Bug fix
« on: August 18, 2017, 09:18:49 AM »
when Mimicking Sketch, Gogo is supposed to Sketch the original enemy, unless it's been killed or Hidden/etc.

that won't necessarily be the case with Roulette now.  i believe the problem stems at least partially from you assigning FFh to $3415.

abridged description of variable:
Code: [Select]
C21540: STZ $3415  ; force random targeting
full description of variable:
Code: [Select]
C2/1543: 9C 15 34     STZ $3415      (will force randomization and skip backing up of
                                      targets)

:P

now, this issue can be elusive to verify in gameplay, because to see it:
- there must be a mixed formation; i.e. some non- Pipsqueak or Veteran monster for Gogo to possibly Sketch instead.
- the differing enemy must not have been killed (e.g. by Roulette) since initial Sketching of Pipsqueak/Veteran.
- the initially Sketched enemy must not have been killed since said doodle.
- Gogo can't have been slayed by Roulette.

pile on the Safety Bits and Memento Rings, and make liberal use of emulator fast forward.

also, i am curious as to what you're doing with Bit 0 of $B3, as vanilla just uses that with Blitz.