øA slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;u=25;area=showposts;start=225 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index1dba-2.html slickproductions.org /forum/index.php?PHPSESSID=5f0fck550j2m4m2fpbtkj2vkm1&action=profile;area=showposts;u=25 e:/My Web Sites/Slick Productions - FFIV Message Board/slickproductions.org/forum/index1dba-2.html.z x E›h^ ÿÿÿÿ ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÈ 0Pd ô OK text/html ISO-8859-1 gzip 8:Ö ô ÿÿÿÿÿÿÿÿ Wed, 11 Mar 2020 08:19:41 GMT 0ó° °® 0® P® €§² ð® D›h^ ÿÿÿÿÿÿÿÿ4 ô
We have EVEN MORE themes now, but some old ones are gone...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.
If your spidey senses are tingling, I'll definitely keep this in mind. However, from what I can understand, C2/1211 always gets called every (other) frame as long as $3EE2 is set, and if only C2/0AA8 clears it, Revert is forced to happen at the soonest possible moment as long as the Morph timer is zero. The function to update Morph-related stuff (C2/0AA8) is called every turn and both clears $3EE2 and calls C2/0B36. C2/0B36 updates the Morph supply from the Morph timer ($3F30-$3F31) and that variable never changes outside of C2/1211 (except for being initialized by Morph and cleared by Revert). I can't see how waiting for C2/0AA8 to update the Morph supply would be an issue, unless you think there's another way Revert could get thwarted. Sorry if I seem hard-headed about this, I just want to make sure I didn't miss anything. :)
Now that I think of it, I suppose the battle ending would thwart Revert. Not updating the supply immediately when the timer runs out actually kind of silently fixes the problem with the timer running out during end-of-battle messages, but certain special battle endings don't update the Morph supply, such as Gau Leaping or Returning, or Shadow leaving, and in those cases the supply wouldn't get updated even if the timer ran out just as the battle ended. That's a pretty good tradeoff though, in my opinion (but it's easy to fix).
On another note, someone made a menu Swdtech patch? I'd like to see that.
;To remedy this hypothetical sitation, lower the cap on the
;Morph decrementor at C2/0B27. For a 128 Haste multiplier
;(double speed) set it to 511 to prevent overflow.
;I'm not sure why that's set to 2048, since it should never
;get that high.
LSR #6 ;(Divide by 64 [the "Normal" ATB multiplier])PHX
LDX #$3F
CPX $EA (if top byte of product is >= 64, it'll have a nonzero value
after routine C2/0DD1, meaning the decrementor exceeded
65535.)
BCC reduce_it
LDA #$0005
JSR $0DD1 (Divide 32-bit product by 64. the product doesn't occupy
more than 3 bytes going into this call, but the function
operates on 32-bits.)
reduce_it:
TDC
DEC
PLX
Quoteno, you'd still be queuing up Revert from the same place. yes on clearing the bit when Revert is executed. what it'd be doing is adopting periodic damage/healing's just-one-queued-at-a-time system (as achieved by bit 4 of $3AA1,index , but we'd use our own flag), which is more robust.
I don't think I follow. Where is the bit set, and where is it checked?
Quotethe check you're currently using will prevent multiple sequential queued Reverts, which is probably the prime offender in terms of that pause, but it'll be fooled if anything gets queued or run in between them. obvious culprits are high-priority stuff, like statuses auto-expiring or equipment magic activations on low HP. also, i believe a Revert that gets queued during a string of an enemy's counters (which are equal-priority, but the first actor gets precedence), as it'll wait until the monster is done to execute. another equal-priority way: attack whacks ally with Retort, Interceptor, or Black Belt on; Revert gets queued during attack animation; counter executes and overwrites $3A7A. really, lots of things can overwrite $3A7A (like a party of Cure Ring wearers queuing their Regen healing), so this approach has its holes. Square's way is more thorough. but if our only concern is aesthetics of a visible lag, and the prime offender IS being taken care of, then maybe it's not worth claiming the extra RAM bit to be more thorough.
I think it's fine that counterattacks get priority over Revert, it would look weird to have Terra Revert in between attacks. As for Revert getting delayed by Relic activation, periodical damage, or status expiration, that could get a little weird. The delay might be noticeable if a lot of automatic actions happen in succession and one may wonder why Terra is waiting for things that are happening to others before she transforms. Of course, it's an artifact of the battle system that things can't happen simultaneously, but there should be the illusion of things happening independently of each other, and that requires fair queueing. It's not a big issue, but I, too, appreciate when things are done right.
Could you elaborate on this? You mean periodically queuing up Revert via another function that doesn't depend on $3EE2 being set, like C2/5A83, conditional on bit 3 of $3AA1,index being set instead? Would you then be setting that bit in C2/1211 to allow Revert to be queued up, and then clear it when Revert is executed? Essentially offloading the responsibility for Revert onto an unused bit instead of $3EE2?
Yes, I just tested it by simply hitting Terra with Stop, and letting her Morph gauge run out during the casting animation for Stop, and her Revert does indeed slip through the time freeze. The case was the same with Quick.

If I'm right, then all you need to do before queueing Revert is to make sure it's not already queued. There's a bit of code in my "Dead in the Air" Fix A that can help you out.
What do these [$3AA0,index] bits do, anyway?
Since all of that is now fixed, I have only one small reservation: do you think it would still be possible to trigger the bug with frame-perfect timing, by hitting Terra with Stop or having someone else enter Quick just as the Morph timer ran out, but before Revert could be executed? I can't make it happen during testing, but I don't have the patience for testing with frame-perfect input. This is the difference between "fixed" and "well hidden" that will gnaw at my conscience late at night.
However, it seems to me that the function to update Morph supply doesn't need to be called every frame.
It seemed like a good way to make sure that Terra Reverts no matter what, but it causes that pause, and I'm not sure why it only happens when the timer runs out during an attack animation.
Revert doesn't clear $3EE2, it just sets Morph status to be removed, by the way.
Anyway, I would prefer to find a way to make sure she Reverts immediately after Sleep and Freeze wear off instead of during, but I tried your suggestion:
[...]
I think there's a more efficient way to structure those branches and jumps, but it works, both for Sleep and Freeze. Even if it looks funny. Perhaps it might be more aesthetically pleasing to hook into however Sleep and Freeze are removed when their timers run out, and queue Revert from there, instead.
Clearing $3EE2 at the end of battle fixes the issue with the Morph gauge ticking down, by the way.very nice and direct. i hadn't written any code, but the crap i was mulling was more complicated (e.g. trying to detect it was post-battle somehow
).