Official Ask Anyone Frame Things Thread

[Magus420]

Shield Stuff

____________________________________________________________

Variable Shield Input
Digital/Max Analog = 1 (140/140)
Z Shield = 0.35 (49/140)
Min Analog = 0.30714 (43/140)
-- Range of analog 0.00-1.00 is analog increments 0-140. 0-42 (0.00-0.30) are ignored
-- If dip under 0.30 while shield remains up, use last > 0.30 amount

____________________________________________________________

Shield Size
Shield Size = {[(Shield Health * Analog Effect) / 60] * 0.85 + 0.15} * Shield Size Attribute * Model Scale
-- Analog Effect = 1 - {0.5 * [(Analog Shield - 0.3) / 0.7]}

Max Shield Health = 60
Shield Break Health = 30 (does not regen while dazed)
Max Shield Health Scale = 1
Min Shield Health Scale = 0.15
Powershield Reflect Collision Scale = 0.75

Spoiler

____________________________________________________________

Shield Degeneration/Regeneration
Shield Degeneration = (Analog Effect + 0.1) * 0.14
-- Analog Effect = 1.9 * [(Analog Shield - 0.3) / 0.7]

Shield Regeneration = 0.07

Spoiler

____________________________________________________________

Shield Damage
Shield Damage = [(floor(Damage) + Shield Damage Param) * (Analog Effect + 0.7)] * X
-- Analog Effect = 0.2 * {1 - [(Analog Shield - 0.3) / 0.7]}
-- X = 1 for Normal, 0 for Powershield

Spoiler

____________________________________________________________

Shield Stun
Shield Stun = {[floor(Damage) * (Analog Effect + 0.3)] * 1.5} + 2
-- Analog Effect = 0.65 * {1 - [(Analog Shield - 0.3) / 0.7]}
--- Yoshi is unaffected by shield stun
--- NOTE: Due to the way the game calculates the animation speed for the 20 frame stun animation [(Animation Frames + 0.1) / ShieldStun], it causes the actual resulting stun time to be 1 less than calculated shieldstun if:
20.1 / ShieldStun * floor{ShieldStun} >= 20
On full 1.00 shield input that happens with damages of 20,29,40, 49, 58, and 60 for example.

Spoiler

____________________________________________________________

Shield Knockback
Defender Shield KB = {[floor(Damage) * (Defender Analog Effect + 0.09)] + 0.4} * X
-- Defender Analog Effect = 0.195 * {1 - [(Analog Shield - 0.3) / 0.7]}
-- X = 0.6 for Normal, 1 for Powershield
--- Maximum = 2

Defender (Yoshi) Shield KB = (floor(Damage) * Defender Analog Effect) + 0.4
-- Defender Analog Effect = 0.3 * {1 - [(Analog Shield - 0.3) / 0.7]}
--- Maximum = n/a

Attacker Shield KB = (floor(Damage) * Attacker Analog Effect) + 0.02
-- Attacker Analog Effect = (Analog Shield - 0.3) * 0.1]
--- Maximum = n/a

Spoiler

____________________________________________________________

 

[reverie2]

I was just using the numbers you gave me. Truthfully, 2 frames of shieldhitlag and 5 frames of stun is impossible in the game. Shieldhitlag is calculated the same as regular hitlag as floor[dmg/3+3]. It has a minimum of 3. Shieldstun is calculated by the formula you mentioned, floor((dmg + 4.45)/2.235).


I think you're interpreting it correctly. Let's use a real example though. Marth's uair does 7 frames of shieldhitlag and 7 frames of shieldhitstun. Marth hits Peach's shield with uair. They are both frozen for 7 frames of shieldhitlag. Peach can shield SDI if she wants. After those 7 frames, Marth starts moving as he exits shieldhitlag. Peach enters shieldhitstun and cannot do anything for 7 frames.

I think it all makes sense now, but I'm confused as to why in this link http://smashboards.com/threads/captain-falcon-shield-pressure-data-wip.308010/ if you look in the "low short hop knee" category, it displays

24 / 24 Knee hits
25 / hitlag
26 / hitlag
27 / hitlag
28 / hitlag
29 / hitlag
30 / hitlag
31 / hitlag
32 / hitlag
33 / landlag
34 / landlag
35 / landlag
36 / landlag
37 / landlag
38 / landlag
39 / landlag
40 / landlag
41 / landlag
42 / 25
43 / Stun ends

for kneeing on a shield. Knee does 18 damage. The fact that it's electrical has no influence on shield hitlag/shieldstun. (18/3 + 3) = 9 damage of hitlag (from frame 24 to 32). After hitlag, just like in your example, the defender will experience shieldstun. So far everything makes sense.

Shieldstun = floor ((18+4.45)/2.35 ) = 9 frames of shieldstun. In the link I quoted, frames 33 to 43 are shieldstun which is 11 frames. 9 doesn't equal 11 though, so am I missing something?

 

[Sycorax]

Shieldstun = floor ((18+4.45)/2.35 ) = 9 frames of shieldstun.

Your forumula is wrong, it should be floor ((18+4.45)/2.235) which = 10. That's still not equal to 11. I checked in debug mode and they got their frames wrong. Falcon's fair does 10 frames of shieldstun. I think they just accidentally colored "43 / Stun ends" wrong.

Technically, Shield Stun = {[floor(Damage) * (Analog Effect + 0.3)] * 1.5} + 2 where Analog Effect = 0.65 * {1 - [(Analog Shield - 0.3) / 0.7]}

 

[Roukiske]

Anyone know if any of Fox's dair variations (fullhop/shorthop/fastfall or not) can be shield grabbed (whoever has the fastest) if used up close, L-cancelled, and shined right after? I don't care about post shine, just shield grabbed in between the dair and shine.

 

[Vestboy_Myst]

here's an interesting optimization problem:

lets say peach is under the inner corner of one of YS/DL/PS/BF's side plats, and fox is standing on the platform at the outside corner (rolled to that edge). Between the following options, which is the fastest way to cover the vertical (jump up to platform + land) and horizontal (travelling the length of the plat) distance? Lets assume that shes going for a regrab techchase and therefore only needs to get within her grab box range

1) jump straight up onto the inner corner > horizontal waveland toward fox
2) diagonal jump past the midpoint of plat > DJL next to fox

DJL is obviously superior to waveland when its done in-place, but adding in the horizontal vector makes it a bit trickier. i'd imagine its stage dependent, and my gut reaction is that higher platforms (DL/BF) would favor Opt 1 since it is less distance traveled in her slow jump, but I'm not sure if her waveland speed makes up for it. Perhaps Opt 2 is a straight up improvement on some of the stages?

If anyone needs me to clarify or draw a diagram I can

some data on DJL (vertical jump) http://smashboards.com/threads/dj-land-onto-platform-stage-specifics.385827/

edit:
realized there were a few other questions i am unsure about that pertain to this
-are diagonal DJLs easier / harder or the same as vertical jumps (in terms of input window)?
-are diagonal DJLs possible on ALL platform heights?
-is just running to the outer corner then doing a vertical jump to DJL (Opt 3) faster than both for all platform heights?
-ive been assuming all diagonal jumps were still her standard 'neutral jump' for the whole post, but at an angle. What about her other jump animations (like her 'backflip' if she was falcon) ? do they make the DJL input any harder/easier? could they make it possible to DJL sooner than neutral jump?

paging some of the frame jockeys @Vesne @DarkRijin Sycorax schmooblidon

 

[Sycorax]

Anyone know if any of Fox's dair variations (fullhop/shorthop/fastfall or not) can be shield grabbed (whoever has the fastest) if used up close, L-cancelled, and shined right after? I don't care about post shine, just shield grabbed in between the dair and shine.

It really doesn't matter how Fox jumps before he dairs. What matters is how soon he started the dair before he landed. I can describe the details more if you want, but the gist is that, since it is a multi-hit move making it hard to land on the frame after it hits shield, there is a 2/3 chance the the dair will be able to be shield grabbed. Your opponent isn't going to be able to know if a grab is possible or not, so it's a crap shoot if they try to go for it.

Edit: 2/3

here's an interesting optimization problem:

lets say peach is under the inner corner of one of YS/DL/PS/BF's side plats, and fox is standing on the platform at the outside corner (rolled to that edge). Between the following options, which is the fastest way to cover the vertical (jump up to platform + land) and horizontal (travelling the length of the plat) distance? Lets assume that shes going for a regrab techchase and therefore only needs to get within her grab box range

1) jump straight up onto the inner corner > horizontal waveland toward fox
2) diagonal jump past the midpoint of plat > DJL next to fox

DJL is obviously superior to waveland when its done in-place, but adding in the horizontal vector makes it a bit trickier. i'd imagine its stage dependent, and my gut reaction is that higher platforms (DL/BF) would favor Opt 1 since it is less distance traveled in her slow jump, but I'm not sure if her waveland speed makes up for it. Perhaps Opt 2 is a straight up improvement on some of the stages?

If anyone needs me to clarify or draw a diagram I can

some data on DJL (vertical jump) http://smashboards.com/threads/dj-land-onto-platform-stage-specifics.385827/

edit:
realized there were a few other questions i am unsure about that pertain to this
-are diagonal DJLs easier / harder or the same as vertical jumps (in terms of input window)?
-are diagonal DJLs possible on ALL platform heights?
-is just running to the outer corner then doing a vertical jump to DJL (Opt 3) faster than both for all platform heights?
-ive been assuming all diagonal jumps were still her standard 'neutral jump' for the whole post, but at an angle. What about her other jump animations (like her 'backflip' if she was falcon) ? do they make the DJL input any harder/easier? could they make it possible to DJL sooner than neutral jump?

paging some of the frame jockeys @Vesne @DarkRijin Sycorax schmooblidon

You misunderstand Melee physics. It is not the case that jumping at an angle lowers your vertical velocity in order to contribute to horizontal velocity (like it would in the real world). Instead, when you jump, there is an initial vertical velocity, and an initial horizontal velocity. The vertical velocity is always there as essential to the jump lol. The horizontal velocity comes from residual momentum from the grounded state plus the analog jump effect. Therefore, it takes the same amount of time to reach a platform regardless of whether you jump completely vertically or not. Because of this, the waveland method is always slower. The ten frames of lag are simply not made up for by the increased speed of a waveland. Under any platform, Peach can get to a certain desirable spot the quickest by dashing, then jumping, then using analog control to aim where she wants to go. I'm not even sure the dashing is necessary.

-are diagonal DJLs easier / harder or the same as vertical jumps (in terms of input window)?
The same.

-are diagonal DJLs possible on ALL platform heights?
Of the legal stages, yes. Like I said above, vertical height is not diminished by horizontal momentum.

-is just running to the outer corner then doing a vertical jump to DJL (Opt 3) faster than both for all platform heights?
I don't understand the situation you're describing.

-ive been assuming all diagonal jumps were still her standard 'neutral jump' for the whole post, but at an angle. What about her other jump animations (like her 'backflip' if she was falcon) ? do they make the DJL input any harder/easier? could they make it possible to DJL sooner than neutral jump?
The difference in the bottom of the ECB is minuscule. On Battlefield it doesn't make a difference. I doubt any other stage does. There may be tiny sections on Yoshi's where you get an extra frame, but it'd be TAS level precision.

Edit: "Frame Jockey" :3 Lol, can you change my status from "Smash Apprentice" to "Frame Jockey"? Does mod power allow you to do that?

 

[Vestboy_Myst]

It really doesn't matter how Fox jumps before he dairs. What matters is how soon he started the dair before he landed. I can describe the details more if you want, but the gist is that, since it is a multi-hit move making it hard to land on the frame after it hits shield, there is a 1/3 chance the the dair will be able to be shield grabbed. Your opponent isn't going to be able to know if a grab is possible or not, so it's a crap shoot if they try to go for it.


You misunderstand Melee physics. It is not the case that jumping at an angle lowers your vertical velocity in order to contribute to horizontal velocity (like it would in the real world). Instead, when you jump, there is an initial vertical velocity, and an initial horizontal velocity. The vertical velocity is always there as essential to the jump lol. The horizontal velocity comes from residual momentum from the grounded state plus the analog jump effect. Therefore, it takes the same amount of time to reach a platform regardless of whether you jump completely vertically or not. Because of this, the waveland method is always slower. The ten frames of lag are simply not made up for by the increased speed of a waveland. Under any platform, Peach can get to a certain desirable spot the quickest by dashing, then jumping, then using analog control to aim where she wants to go. I'm not even sure the dashing is necessary.

-are diagonal DJLs easier / harder or the same as vertical jumps (in terms of input window)?
The same.

-are diagonal DJLs possible on ALL platform heights?
Of the legal stages, yes. Like I said above, vertical height is not diminished by horizontal momentum.

-is just running to the outer corner then doing a vertical jump to DJL (Opt 3) faster than both for all platform heights?
I don't understand the situation you're describing.

-ive been assuming all diagonal jumps were still her standard 'neutral jump' for the whole post, but at an angle. What about her other jump animations (like her 'backflip' if she was falcon) ? do they make the DJL input any harder/easier? could they make it possible to DJL sooner than neutral jump?
The difference in the bottom of the ECB is minuscule. On Battlefield it doesn't make a difference. I doubt any other stage does. There may be tiny sections on Yoshi's where you get an extra frame, but it'd be TAS level precision.

Edit: "Frame Jockey" :3 Lol, can you change my status from "Smash Apprentice" to "Frame Jockey"? Does mod power allow you to do that?

Sycorax OOPS lol...
I had NO IDEA that it disobeyed real world physics like that! I'm a physics major too, so I didn't even bother thinking otherwise. i always pictured typical vectors when i heard the horizontal/vertical speed stuff... I'm happy that you were able to realize that was what I was going for, and thanks for answering thoroughly. I must get to work on DJLing asap

for Opt 3, i was describing techchasing a fox rolling to the outer edge by running UNDER the platform a bit toward fox, then doing a straight up DJL to regrab (basically Opt 1 in reverse: horizontal THEN vertical movement)

also yeah, you know, a frame jockey! surely someone else has heard this term before. I don't think I can give you the title sadly, but it could make a good banner someday. you guys are basically melee physicists

Frame Jockey [fraym jok-ee] (n) (pl: jockeys)
a) one with a public reputation for their knowledge and manipulation of frame data in a videogame, who then uses this talent to improve current methods of play and to educate the general public
b) a horserider used for scapegoating
"Kadano and Magus are frame jockeys renowned for their work on Smashboards"

 

[Sycorax]

I don't think I can give you the title sadly

Agonyyyy!

Also, upon further thought, there may be situations in which the waveland is preferable to the DJL. If you're trying to cover tech options on reaction, DJL may be too slow (despite taking fewer frames to become actionable on a platform) because it requires reacting at an earlier time. With the waveland method, you can jump first regardless of their tech option and then waveland a certain way on reaction to their tech option. With the DJL method, you need to react at the moment of your analog jump input which is a good 10 frames or more earlier than the waveland reaction.

On further thought though, it is usually rather obvious where they will land. Therefore, you could option select DJL at their landing and be ready to cover tech in place or tech rolls on reaction. Reacting to tech rolls should be rather easy on platforms and often possible with dash grab (which I think is preferable to dash attack).

 

[tauKhan]

What matters is how soon he started the dair before he landed. I can describe the details more if you want, but the gist is that, since it is a multi-hit move making it hard to land on the frame after it hits shield, there is a 1/3 chance the the dair will be able to be shield grabbed. Your opponent isn't going to be able to know if a grab is possible or not, so it's a crap shoot if they try to go for it.

Actually it's shield grabbable 2/3 of the times if we assume each gap between hit and landing is equally likely. Dair does 3 frames of stun and 9 frames of landing lag, so only in the perfect scenario the fox would be able to shine on the frame the grab hitbox comes out and dodge it with the shine intangibility.

In my experience dair is very vulnerable to shield grabs. I won't say it's impossible to learn certain shffl timings that lead to frame perfect landings, but it definitely isn't easy.

 

[Sycorax]

Discovery:

We all know forbidden smash DI prevents the bottom of your ECB from colliding with the floor. However, when you SDI straight down, but the ground is less than 6mm below the bottom of your ECB, instead of the SDI not happening, your TopN bone will be lowered to the floor. Often times, in the air, your ECB is raised above your TopN bone and this quirk is useless. However, if you are in the first 10 frames of going airborne, say, from your jump, when the bottom of your ECB is attached to your TopN bone, you can SDI down towards the ground to become adjacent to the ground, and then ASDI down to collide with the ground. The SDI still won't cause a collision with the ground. It will merely lower you to be level with the ground. Later, you can ASDI to collide with the ground.

 

[schmooblidon]

Anyone have step by step instructions of how to calculate DI angle from control stick X and Y, then how that angle is applied to the trajectory (how the stick angle turns into a degree offset? or something like that), and also how the angle translates into SDI and ASDI X and Y.

I know Trajectory DI has a maximum offset of 18 degrees in either direction, and how the more perpendicular the angle, the higher the offset, but not the precise maths.

 

[Comet7]

..........................

 

[reverie2]

I have kind of a simple question... If I spam fox's dair on a shield, the timing to fast fall and L-cancel should be 100% identical to spamming dair onto a character not shielding right? Because the only thing different between the 2 is shieldstun, which only the defender experiences after hitlag. The hitlag on the attacker (me) should be the exact same right? It seems like dairing on a shield is a bit slower but i dont know if that's just in my head

 

[Kadano]

I have kind of a simple question... If I spam fox's dair on a shield, the timing to fast fall and L-cancel should be 100% identical to spamming dair onto a character not shielding right? Because the only thing different between the 2 is shieldstun, which only the defender experiences after hitlag. The hitlag on the attacker (me) should be the exact same right? It seems like dairing on a shield is a bit slower but i dont know if that's just in my head

The timing is not always 100% the same due to damage staling. For example, a fresh dair will cause 4 frames of hitlag on hit (assuming you connect the sweetspot), but only 3 frames of hitlag for all subsequent hits. A fresh dair on shield will deal 4 frames of hitlag with every hit (again assuming you always connect the sweetspot).

(In Melee, multi-hit moves add to the stale queue with every single part-hit that deals damage.)

 

[reverie2]

So the stale queue only contains hits that connect to an actual character (not their shield) right? And if i'm understanding correctly, if a multi-hit move is 3 parts, if i hit with the first part and the first part stales, but miss the last 2 parts, the next time i hit with the same move, only the first part is staled?

 

[Traivlin]

I know Trajectory DI has a maximum offset of 18 degrees in either direction, and how the more perpendicular the angle, the higher the offset, but not the precise maths.

It's 18*sin²(x), where x is the angle at which you hold the analog stick in relation to the launch trajectory.
18*sin(90)*sin(90) = 18, so that would be perpendicular DI.

 

[Kadano]

So the stale queue only contains hits that connect to an actual character (not their shield) right? And if i'm understanding correctly, if a multi-hit move is 3 parts, if i hit with the first part and the first part stales, but miss the last 2 parts, the next time i hit with the same move, only the first part is staled?

Only hits that deal damage add to the staling queue, yes.
There is no distinction between the individual hits. Dealing damage with a hit adds its attack into the staling queue. However, an attack will be only staled once even if multiple hits of a single execution connect and deal damage.

 

[Vestboy_Myst]

Only hits that deal damage add to the staling queue, yes.
There is no distinction between the individual hits. Dealing damage with a hit adds its attack into the staling queue.

does pummeling during a grab count toward the stale queue?
and i guess that means counter moves don't unless triggered

 

[tauKhan]

schmooblidon
Magus shared the DI formula on reddit: "Trajectory DI effect in degrees is the perpendicular distance, squared, then multiplied by 18."

 

[Traivlin]

schmooblidon
Magus shared the DI formula on reddit: "Trajectory DI effect in degrees is the perpendicular distance, squared, then multiplied by 18."

That's exactly what I meant. Sorry, if I wasn't clear enough.

 

[tauKhan]

That's exactly what I meant. Sorry, if I wasn't clear enough.

The function you posted depends only on the angle, and it doesn't work for weak inputs. It's correct for full inputs though. Expanded function:

18*(sin(x)*L)² where x is the angle and L is the length of the input.

 

[Traivlin]

Ah yes, that's true. Good that you clarified that.

 

[schmooblidon]

How does it determine perpendicular distance?

I tried using trig and came up with

x = x input
y = y input
a = perpendicular angle
p = perpendicular distance

p = cos(a-arctan(x/y))*sqrt(x^2+y^2)

and it was sooo wrong edit: my b, changing it to arctan makes it sooo right

edit: wait is tanh the same as tan-1 ? my trig so rusty. oh **** they are not, arc was the abbreviation i forgot.

 

[tauKhan]

schmooblidon
p = sin(a)*sqrt(x^2+y^2) where a is the angle between launch angle and your control stick input and x,y represent their respective control stick values. (L = sqrt(x^2+y^2) in the function I previously posted)

 

[Sycorax]

The function you posted depends only on the angle, and it doesn't work for weak inputs. It's correct for full inputs though. Expanded function:

18*(sin(x)*L)² where x is the angle and L is the length of the input.

I wonder if the game actually calculates angles or not. It may not be "technically correct" to say that DI is done with angles. Trying to solve for the perpendicular distance between the control stick input and the line of trajectory could be done using angles and trig, or with lines, points, and linear algebra.

I know barely anything about coding, but if they wanted to do trig functions in code they'd probably do some sort of Taylor series polynomial expansion that was truncated at some point to yield enough significant digits. That seems inefficient compared to linear algebra equations. I don't know the exact math for the linear algebra, but it would require like one or two matrices and the distance formula.

 

[schmooblidon]

schmooblidon
p = sin(a)*sqrt(x^2+y^2) where a is the angle between launch angle and your control stick input and x,y represent their respective control stick values. (L = sqrt(x^2+y^2) in the function I previously posted)

Ohhh I think I get it. So that basically means p = sin(90-a-arctan(x/y))*sqrt(x^2+y^2) on mine, but how do I get the angle without having to do 90-a-arctan(x/y), feel like I'm missing something obvious.

 

[reverie2]

Ohhh I think I get it. So that basically means p = sin(90-a-arctan(x/y))*sqrt(x^2+y^2) on mine, but how do I get the angle without having to do 90-a-arctan(x/y), feel like I'm missing something obvious.

why are you're using arctan(x/y) in the first place? Let's say an attack sends you upwards, and you hold stick 50 degrees right. arctan (x/y) is the same as a. 90 - 2a =/= a. The formula you're using and the one magus/tau khan provided are completely different... ???

 

[schmooblidon]

why are you're using arctan(x/y) in the first place? Let's say an attack sends you upwards, and you hold stick 50 degrees right. arctan (x/y) is the same as a. 90 - 2a =/= a. The formula you're using and the one magus/tau khan provided are completely different... ???

This is starting to get confusing, cos we are using a for different things.

I use a-arctan(x/y) (where a = launch angle) to calculate the angle between the control stick input and the launch angle.

 

[reverie2]

Oh yeah we're using the definition of a differently. But if we do assume a is the launch angle, a-arctan(x/y) is not the angle between the control stick input and the launch angle though. a-arctan(y/x) is. I don't really see a reason to use a as a launch angle though, all you need to know is the angle you're DI'ing relative to the launch angle

 

[schmooblidon]

Oh yeah we're using the definition of a differently. But if we do assume a is the launch angle, a-arctan(x/y) is not the angle between the control stick input and the launch angle though. a-arctan(y/x) is. I don't really see a reason to use a as a launch angle though, all you need to know is the angle you're DI'ing relative to the launch angle

Green is the launch angle/perpendicular. Red is the controller input point.

I want to find the blue angle, I know a, and I calculate theta by doing arctan(x/y)

I want to calculate DI'ed trajectory from only x and y input values.

 

[reverie2]

Green is the launch angle/perpendicular. Red is the controller input point.

I want to find the blue angle, I know a, and I calculate theta by doing arctan(x/y)

I want to calculate DI'ed trajectory from only x and y input values.

Oh so according to your diagram, yeah you can use inverse tan to find theta, and then you can find the angle between your DI and your launch trajectory. If you're given nothing but x, y, and launch trajectory with the "a" you mentioned, I don't think there's an easier way to find that angle in between. When you actually encounter a launch trajectory in smash though, wouldn't it make sense to just think of what angle you want to Di relative to the launch trajectory so you don't even have to worry about doing trig and just plug that angle into 18*(sin(x)*L)²?

You called the variable "a" a perpendicular angle in an earlier post which is different than what your diagram is showing, but I'm just assuming it will always be less than 90 degrees no matter what quadrant it's in?

 

[schmooblidon]

Oh so according to your diagram, yeah you can use inverse tan to find theta, and then you can find the angle between your DI and your launch trajectory. If you're given nothing but x, y, and launch trajectory with the "a" you mentioned, I don't think there's an easier way to find that angle in between. When you actually encounter a launch trajectory in smash though, wouldn't it make sense to just think of what angle you want to Di relative to the launch trajectory so you don't even have to worry about doing trig and just plug that angle into 18*(sin(x)*L)²?

You called the variable "a" a perpendicular angle in an earlier post which is different than what your diagram is showing, but I'm just assuming it will always be less than 90 degrees no matter what quadrant it's in?

I'm building a trajectory simulator with gentlefox and I think it'd be more intuitive to calculate with x and y inputs, so I can just give the user a control stick pretty much (could even allow gc controller adapter maybe) to set the angle to see the altered trajectory. There is also the deadzones to consider.

Ah ye that was because I was drawing out an example that I was simultaneously testing on 20XX, and the x and y inputs I choose and attack's angle made sense to use the perpendicular. So yeah it's pretty much just use which ever line is in the same quadrant so you get less than 90.

 

[tauKhan]

Ohhh I think I get it. So that basically means p = sin(90-a-arctan(x/y))*sqrt(x^2+y^2) on mine, but how do I get the angle without having to do 90-a-arctan(x/y), feel like I'm missing something obvious.

I think you have use arctan and use the launch angle, you're not missing anything. For me it would be more natural to solve the angle as the difference of the control stick angle and launch angle compared to a base line, in this case horizontal line. So I'd do sin(arctan(y/x) - a)*sqrt(x^2+y^2), but it's still basically the same as arctan(y/x) = 90 - arctan(x/y).

 

[schmooblidon]

Ok I think I got it working!

There are a bunch of ifs that need to be addressed, here is the code in javascript if anyone is interested

       var angleConversion = Math.PI / 180;
       //used to convert degrees to radians

       var deadzone = false;
        if (x < 0.2875 && x > -0.2875){
          x = 0;
        }
        if (y < 0.2875 && y > -0.2875){
          y = 0;
        }

        if (x == 0 && y < 0){
          diAngle = 270;
        }
        else if (x == 0 && y > 0){
          diAngle = 90;
        }
        else if (x == 0 && y == 0){
          deadzone = true;
        }
        else {
          diAngle = Math.atan(y/x) * (180 / Math.PI);
          if (x < 0){
            diAngle += 180;
          }
          else if (y < 0) {
            diAngle += 360;
          }
        }

        if (!deadzone){
          var rAngle = launchAngle - diAngle;
          if (rAngle > 180){
            rAngle -= 360;
          }

          var pDistance = Math.sin(rAngle * angleConversion) * Math.sqrt(x*x+y*y);

          var angleOffset = pDistance * pDistance * 18;
          if (angleOffset > 18){
            angleOffset = 18;
          }

          if (rAngle < 0 && rAngle > -180){
              angleOffset *= -1;
          }
        }
        else {
          var angleOffset = 0;
        }

        return (launchAngle - angleOffset);

Thanks for all your help guys! If anyone wants to test it out, I'll PM you a link.

 

[reverie2]

Only hits that deal damage add to the staling queue, yes.
There is no distinction between the individual hits. Dealing damage with a hit adds its attack into the staling queue.

Hold on... Just so I'm 100% understanding correctly, if I hit a Fox dair with 3 hits, the 2nd hit will have reduced damage, and the 3rd will have more reduced damage because all hits add to the staling queue right?

 

[tauKhan]

No, when the first hit connects, the attack will be added to the stale queue, so the consecutive hits do a bit less dmg (unless the move was already fully staled ofc). However the attack is only added once to the queue even if it hits multiple times, so the 3rd hit will do exact same dmg as 2nd hit with fox dair.

 

[tauKhan]

Can anyone ( Kadano , schmooblidon ) figure out why I can combo fox dair into turn utilt on DK in practice mode. When I calculate the expected hitstun using drill properties (30 WDSK, 100 KBG, 0 BKB) in the formula, the result is 15,57. The result apparently includes 1 frame of hitlag in the value, so the stun should be 14 frames. Dair should have 9 frames of landing lag and utilt comes out frame 5, so turn utilt shouldn't come out faster than frame 15, and the combo shouldn't work. Where do I go wrong?

 

[schmooblidon]

Can anyone ( Kadano , schmooblidon ) figure out why I can combo fox dair into turn utilt on DK in practice mode. When I calculate the expected hitstun using drill properties (30 WDSK, 100 KBG, 0 BKB) in the formula, the result is 15,57. The result apparently includes 1 frame of hitlag in the value, so the stun should be 14 frames. Dair should have 9 frames of landing lag and utilt comes out frame 5, so turn utilt shouldn't come out faster than frame 15, and the combo shouldn't work. Where do I go wrong?

Magus physics repeats your results, so I don't believe there is an error in your calculations.

I think training mode considers it a combo if hit on the first actionable frame. Tested a bunch of other scenarios like it and it counted it as a combo.

 

[Bones0]

Yeah, Training Mode gives an extra frame of leniency for combos. If you're testing grounded combos you can always just hold shield for the defender to make sure you're not crazy.

 

[reverie2]

Couple questions...
1. Can you tech during hitlag or does it have to be hitstun only
2. What is the earliest you can tech falcon's up-b? I've been doing it as soon as falcon releases me. when I'm like adjacent to a wall I miss it all the time. Does falcon's up-b incur hitlag?
3. For special attacks like fox's up-b and side b here http://smashboards.com/threads/complete-fox-hitboxes-and-frame-data.285177/ there are both land lag and landfallspecial lag. Do I just add both those up to get the total landing lag? I'm looking at the marth frame data thread here http://smashboards.com/threads/complete-marth-hitboxes-and-frame-data.285324/ and it only has landfallspecial lag