• This forum is strictly intended to be used by members of the VS Battles wiki. Please only register if you have an autoconfirmed account there, as otherwise your registration will be rejected. If you have already registered once, do not do so again, and contact Antvasima if you encounter any problems.

    For instructions regarding the exact procedure to sign up to this forum, please click here.
  • We need Patreon donations for this forum to have all of its running costs financially secured.

    Community members who help us out will receive badges that give them several different benefits, including the removal of all advertisements in this forum, but donations from non-members are also extremely appreciated.

    Please click here for further information, or here to directly visit our Patreon donations page.
  • Please click here for information about a large petition to help children in need.

MHA: Potential FTL Calc Arrives

Status
Not open for further replies.
Kingofwolves999

Kingofwolves999

Messages
8,734
Reaction score
13,878
vsbattles.fandom.com

All Might Dodges a Radio Wave

vsbattles.fandom.com vsbattles.fandom.com

vsbattles.fandom.com

All Might Dodges Afo's Raidowave

vsbattles.fandom.com vsbattles.fandom.com

Two new calculations have sprung up, with one of them already being accepted, which would result in FTL (1.467c) or FTL+ (28.77c or 45.81c) for Armored All Might. This would naturally then scale to basically every top tier in the verse.

This thread exists to get a larger consensus on the legitimacy of the calculations and to determine which one is best to use. Are the methods for the calcs correct? Or can a better method be used separate from both of them?

EDIT: Alternative Calculation

vsbattles.fandom.com

My Hero Academia: Radio Dodge

vsbattles.fandom.com vsbattles.fandom.com

Calc 1 is Good:

Calc 2 is Good:

Alternative Calc: 2 (TheRustyOne, Damage3245)
 
Last edited:
I do have my own proposal: since we can't use the distance All Might moved, because the radio waves were already past him by the time he finished that movement, what we can do instead is measure the diameter of the beam. Since it looks like a cylinder, we can use its radius to calculate the minimum distance All Might needs to move his head to narrowly miss the beam.

This, of course, assumes AFO was aiming directly at All Might's head before he dodged, which I think is obvious.
 
Therefir said:
I do have my own proposal: since we can't use the distance All Might moved, because the radio waves were already past him by the time he finished that movement, what we can do instead is measure the diameter of the beam. Since it looks like a cylinder, we can use its radius to calculate the minimum distance All Might needs to move his head to narrowly miss the beam.

This, of course, assumes AFO was aiming directly at All Might's head before he dodged, which I think is obvious.
Click to expand...
I mean, that seems like a good compromise and what I think the second calc is trying to do?

AFO is obviously aiming at AM’s head, he hates him and AM is charging at him. He literally could not have aimed it anywhere but dead center.

Also the Radio Waves quirk attack from AFO or Shigaraki is consistently always a cylinder so that is also a good assumption that the second calc did.
 
Kingofwolves999 said:
I mean, that seems like a good compromise and what I think the second calc is trying to do?
Click to expand...
The other problem with this feat is calculating the distance between the beam and All Might's head, the second calc measures it to be only 2.4 centimeters, so it's no surprise they got such a high result.
 
Therefir said:
The other problem with this feat is calculating the distance between the beam and All Might's head, the second calc measures it to be only 2.4 centimeters, so it's no surprise they got such a high result.
Click to expand...
Got ideas on how it should be measured?

And we should probably tag the two who made these calcs to get their perspectives
 
Kingofwolves999 said:
Got ideas on how it should be calculated?

And we should probably tag the two who made these calcs to get their perspectives
Click to expand...
Since the scene is depicted in front of All Might, we can use the field of view as a reference point, measuring All Might's distance to it and subtracting the beam's distance to obtain the true separation (between All Might and the beam).

@JoeDM021

I can't find LumberSpirit here unfortunately.
 
I believe this should fall under the idea of evading punches.

"Refrain from calculating feats based on dodging attacks from other characters at extreme proximity, as this is primarily a trope used to exaggerate a narrow miss rather than a literal representation of overwhelming speed. Taking it at face value is often inconsistent with the battle in which the feat occurs, where the opponents are presented as equals, but the calculation results in them being considered several times faster. This should only be used when the character in question is greatly superior to the one who's attack he is evading and the speed of the attack is concretely stated, such as being able to surpass the speed of sound, or light, or uses a basis in the Real World such as the speed of an athlete's punch. If the two fighters are equal, you should simply scale them to the stated speed of the attack, or off of other feats they perform."

This is a narrow miss. All Might is clearly slower than the attack. No result should have All Might being faster than it.

The calculations are also wrong because they have no idea how angles work. You cannot use All Might and pixel scale the attack coming towards him. That's impossible because they aren't on the same plane of reference. The attack is coming towards All Might from the camera.

Both of them are using All Might as a measuring stick and using pixel scaling to get the distance between All Might and the attack. In order for that to work, the angle would need to show them on the same plane, from the side.
 
Oh, wow, I just noticed this. Looking after the attack is fired, it's clear to me All Might dodged it way earlier than these calcs suggest.

This is how All Might looks after All For One has fired the attack.

This is how All Might looks when the attack comes on screen for us.

He's already dodged out of the way. The point of that attack isn't going towards his head; it's passing behind his shoulder because he moved out of the way.

There's proof on the screen. Look at All Might's right finger. We can see that part of the attack overlaps with his hand.

All Might's fingers are in the foreground, meaning the attack is further away from him than people are suggesting.

Yeah, the current calculations are wrong.

All Might had already moved out of the way by the time they're measuring him, and the attack has passed into the space he used to occupy.

At minimum, we would need the exact distance between All For One and All Might, which would lead to far lower results.

You can see how far All Might is from All For One using these scans, although I don't know if anyone will attempt to calc this. (I'm currently busy preparing something)

The above one is before AFO attacks, while the bottom one is after All Might dodged the attack.
 
Mazdoesstuff said:
“If the two fighters are equal, you should simply scale them to the stated speed of the attack, or off of other feats they perform.”

Since this is an injured All Might in an already damaged Armored suit, couldn’t this be used to argue FTL off of pure upscaling?
Click to expand...
All Might's dodge doesn't require him to be SoL.

His dodge makes sense with his current value. Nothing suggest he was equal to it.

All Might is not equal to the attack. It was a narrow dodge against a faster attack.

I can assure you that whatever results a recalc brings will be less than their current value. Could be a supporting feat, but that's it.

Also, this isn't about scaling, so don't bring that up here. This is about the calculations for this feat. Scaling discussion is saved for a CRT.
 
Kingofwolves999 said:
Also why would Black Clover paladins use light speed attacks on people 400x faster than light speed, it just be like that I suppose.
Click to expand...
Currently black clover has a light speed cap accepted on this site so lmao

I also agree with Rusty here its clearly portrayed to be a narrow miss and all might being dozens of times faster than light just to barely evade it would be kinda absurd
 
So like.

Is the other calc where he’s 1.4c just being ignored or? Cause you can be slightly faster than something and do what he did there where it’s a near miss.

Also, it’s not like AM responded before the attack was fired going by the scene, AM is reacting to the attack coming his way and dodges narrowly because he’s mid-run and isn’t expecting it. Y’all are acting like the speed of the attack is the ONLY factor to why it’s a near miss.

If the calc is just unusable, sure, but AM very clearly is not several times slower than the attack either. He’s reacting to it while in an unfavorable position, while running towards it and not expecting it.
 
Mommyleona said:
Currently black clover has a light speed cap accepted on this site so lmao

I also agree with Rusty here its clearly portrayed to be a narrow miss and all might being dozens of times faster than light just to barely evade it would be kinda absurd
Click to expand...
Ok but the 1.4c calc is the one that was accepted and makes more sense than being dozens of times faster (the ftl + one is funny)
 
Kingofwolves999 said:
Is the other calc where he’s 1.4c just being ignored or?
Click to expand...
I addressed all of the calculations for being wrong based on the pixel scaling.

Here's a quote in case you missed it.
TheRustyOne said:
The calculations are also wrong because they have no idea how angles work. You cannot use All Might and pixel scale the attack coming towards him. That's impossible because they aren't on the same plane of reference. The attack is coming towards All Might from the camera.

Both of them are using All Might as a measuring stick and using pixel scaling to get the distance between All Might and the attack. In order for that to work, the angle would need to show them on the same plane, from the side.
Click to expand...
Also, this revelation I had here.
TheRustyOne said:
Oh, wow, I just noticed this. Looking after the attack is fired, it's clear to me All Might dodged it way earlier than these calcs suggest.

This is how All Might looks after All For One has fired the attack.

This is how All Might looks when the attack comes on screen for us.

He's already dodged out of the way. The point of that attack isn't going towards his head; it's passing behind his shoulder because he moved out of the way.

There's proof on the screen. Look at All Might's right finger. We can see that part of the attack overlaps with his hand.

All Might's fingers are in the foreground, meaning the attack is further away from him than people are suggesting.

Yeah, the current calculations are wrong.

All Might had already moved out of the way by the time they're measuring him, and the attack has passed into the space he used to occupy.

At minimum, we would need the exact distance between All For One and All Might, which would lead to far lower results.

You can see how far All Might is from All For One using these scans, although I don't know if anyone will attempt to calc this. (I'm currently busy preparing something)

The above one is before AFO attacks, while the bottom one is after All Might dodged the attack.
Click to expand...
Both of them are wrong. The one Therefir posted is also wrong for the same reason.
 
TheRustyOne said:
I addressed all of the calculations for being wrong based on the pixel scaling.

Here's a quote in case you missed it.

Also, this revelation I had here.

Both of them are wrong. The one Therefir posted is also wrong for the same reason.
Click to expand...


Here is the full frames of his dodge.

His left arm starts in front of him, crossed over his chest.

He then sees the attack and tilts his body to his left to avoid it.

Does this affect anything or nah? Cause I’ve never seen anyone posting the frame where his left arm starts in front of him.

Edit: You can also see that he is clearly eye tracking the attack the entire way, so any claim that he’s multiple times slower in this instance doesn’t make sense.
 
Last edited:
Wouldn’t be more logical to just use All Might’s own body to determine the distance he moved?

He clearly tilts his entire body 90 degrees to avoid this attack, since his arm starts in front but ends behind him / his chest starts facing the attack then moves to be perpendicular to it. Can’t we just use that?
 
Kingofwolves999 said:
Snip.
Click to expand...
I'm well aware of what the frames are.

Since we don't know when exactly All Might dodge, we should use the entire distance between All Might and AFO as the attack movement.

By the time the attack appears on screen, All Might has already moved out of the way. It's impossible to compare their movements.

Assuming AFO has the same proportions as a twelve year old, who is 147 cm tall.

His shoulder width would be 34.3 cm. Screen Height is 1080 px.

The below frames show All Might before and after dodging All For One's attack.

34.3*1080/[38*2*tan(70deg/2)] = 696.10 cm or 6.961 m

34.3*1080/[59*2*tan(70deg/2)] = 448.341 cm or 4.483 m

Average Between Two = 5.722 m

All For One also held out his arm. We should take that into account.

Arm Length = 60.8 cm or 0.608 m

Distance = 5.722 - 0.608 = 5.114 m

Timeframe = 5.114/299792458 = 1.70584678e-8 seconds

All Might is 220 cm tall. This should give him as shoulder width of 55 cm. (I know All Might's proportions are funky, but I'm trying to make a point here)

Assuming a 90 degree movement, with a 27.5 radius, that gives us an arc length of 43.1969 cm.

Speed = 0.431969/1.70584678e-8 = 25322848.74 m/s or 8.44% SoL (Sub-Relativistic+) This should be our minimum.

I wouldn't be surprised if these numbers aren't fully accurate, but that's irrelevant. All Might doesn't need to move over 5 meters to dodge this attack.

All Might is moving forward at the same time, but we cannot calculate that.

He does move sideways as well, not just turning. He has to avoid the radius of the attack.

Let's assume the attack's diameter is equal to All Might's height. (I'd prefer to pixel scale, but I'm doing this quickly and to make a point)

220/2 = 110 cm or 1.1 m

Speed = 1.1/1.70584678e-8 = 64484103.31 m/s or 21.5% SoL (Relativistic)

Absolute/wanked high-end?

Let's assume All Might had his arm straight forward, which is wrong since it's clearly bended.

All Might Arm = 96.1 cm or 0.961 m (This would be his radius, since the shoulder would be the center point of this movement)

Arc Length = 1.509 m

Speed = 1.509/1.70584678e-8 = 88460465.36 m/s or 29.5% SoL (Relativistic)

Someone should use All Might's actual proportions by measuring him, but they shouldn't be that much different.
 
TheRustyOne said:
I'm well aware of what the frames are.

Since we don't know when exactly All Might dodge, we should use the entire distance between All Might and AFO as the attack movement.

By the time the attack appears on screen, All Might has already moved out of the way. It's impossible to compare their movements.

Assuming AFO has the same proportions as a twelve year old, who is 147 cm tall.

His shoulder width would be 34.3 cm. Screen Height is 1080 px.

The below frames show All Might before and after dodging All For One's attack.

34.3*1080/[38*2*tan(70deg/2)] = 696.10 cm or 6.961 m

34.3*1080/[59*2*tan(70deg/2)] = 448.341 cm or 4.483 m

Average Between Two = 5.722 m

All For One also held out his arm. We should take that into account.

Arm Length = 60.8 cm or 0.608 m

Distance = 5.722 - 0.608 = 5.114 m

Timeframe = 5.114/299792458 = 1.70584678e-8 seconds

All Might is 220 cm tall. This should give him as shoulder width of 55 cm. (I know All Might's proportions are funky, but I'm trying to make a point here)

Assuming a 90 degree movement, with a 27.5 radius, that gives us an arc length of 43.1969 cm.

Speed = 0.431969/1.70584678e-8 = 25322848.74 m/s or 8.44% SoL (Sub-Relativistic+) This should be our minimum.

I wouldn't be surprised if these numbers aren't fully accurate, but that's irrelevant. All Might doesn't need to move over 5 meters to dodge this attack.

All Might is moving forward at the same time, but we cannot calculate that.

He does move sideways as well, not just turning. He has to avoid the radius of the attack.

Let's assume the attack's diameter is equal to All Might's height. (I'd prefer to pixel scale, but I'm doing this quickly and to make a point)

220/2 = 110 cm or 1.1 m

Speed = 1.1/1.70584678e-8 = 64484103.31 m/s or 21.5% SoL (Relativistic)

Absolute/wanked high-end?

Let's assume All Might had his arm straight forward, which is wrong since it's clearly bended.

All Might Arm = 96.1 cm or 0.961 m (This would be his radius, since the shoulder would be the center point of this movement)

Arc Length = 1.509 m

Speed = 1.509/1.70584678e-8 = 88460465.36 m/s or 29.5% SoL (Relativistic)

Someone should use All Might's actual proportions by measuring him, but they shouldn't be that much different.
Click to expand...
So it’s likely a supporting feat, cool, so no throwing it out either
 
TheRustyOne said:
I'm well aware of what the frames are.

Since we don't know when exactly All Might dodge, we should use the entire distance between All Might and AFO as the attack movement.

By the time the attack appears on screen, All Might has already moved out of the way. It's impossible to compare their movements.

Assuming AFO has the same proportions as a twelve year old, who is 147 cm tall.

His shoulder width would be 34.3 cm. Screen Height is 1080 px.

The below frames show All Might before and after dodging All For One's attack.

34.3*1080/[38*2*tan(70deg/2)] = 696.10 cm or 6.961 m

34.3*1080/[59*2*tan(70deg/2)] = 448.341 cm or 4.483 m

Average Between Two = 5.722 m

All For One also held out his arm. We should take that into account.

Arm Length = 60.8 cm or 0.608 m

Distance = 5.722 - 0.608 = 5.114 m

Timeframe = 5.114/299792458 = 1.70584678e-8 seconds

All Might is 220 cm tall. This should give him as shoulder width of 55 cm. (I know All Might's proportions are funky, but I'm trying to make a point here)

Assuming a 90 degree movement, with a 27.5 radius, that gives us an arc length of 43.1969 cm.

Speed = 0.431969/1.70584678e-8 = 25322848.74 m/s or 8.44% SoL (Sub-Relativistic+) This should be our minimum.

I wouldn't be surprised if these numbers aren't fully accurate, but that's irrelevant. All Might doesn't need to move over 5 meters to dodge this attack.

All Might is moving forward at the same time, but we cannot calculate that.

He does move sideways as well, not just turning. He has to avoid the radius of the attack.

Let's assume the attack's diameter is equal to All Might's height. (I'd prefer to pixel scale, but I'm doing this quickly and to make a point)

220/2 = 110 cm or 1.1 m

Speed = 1.1/1.70584678e-8 = 64484103.31 m/s or 21.5% SoL (Relativistic)

Absolute/wanked high-end?

Let's assume All Might had his arm straight forward, which is wrong since it's clearly bended.

All Might Arm = 96.1 cm or 0.961 m (This would be his radius, since the shoulder would be the center point of this movement)

Arc Length = 1.509 m

Speed = 1.509/1.70584678e-8 = 88460465.36 m/s or 29.5% SoL (Relativistic)

Someone should use All Might's actual proportions by measuring him, but they shouldn't be that much different.
Click to expand...
Supporting feat for Rela, we take those.
 
Status
Not open for further replies.

Similar threads

Therefir
  • Locked
My Hero Academia: Deku's Final Smash Calculation
2 3 4
Replies
121
Views
17K
Dalesean027
Dalesean027
DaReaperMan
Endeavor vs All Might (My Hero Academia) (5-5-0)
2
Replies
44
Views
3K
Metalballrun
Metalballrun
TheRustyOne
  • Locked
MHA: Laser Upgrades
2
Replies
64
Views
6K
TheRustyOne
TheRustyOne
CastoriceTheFifth
All Might Vs Tomura Shigaraki (My Hero Academia)
Replies
39
Views
3K
GunshyFever
GunshyFever
Therefir
  • Locked
My Hero Academia: Final Smash Downgrade
Replies
30
Views
5K
Dalesean027
Dalesean027
Back
Top