• 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.

Replacement for Kakashi's calculation

Messages
409
Reaction score
254

I more or less stated about issues in the blog, but want to clarify one more thing.

In calculations where we subtract distances, sometimes using something constant can be unhelpful. When we calculate distance via angsizing, there apeears an error, but if we apply angsizing for 2 distances and before subtracting use something constant to add one of them, sometimes we can get very low or negative results. That mostly happen because that 2 distances contain errors while constant distance that we added doesn't.

To escape this we can add that distance(Kakashi's arm) to angsizing as that'd contain same level of error as distance between Kakashi and Choji/Shikamaru and so we can escape catastrophic cancellation or negative result.

As an example let's assume our angsizing gives us 70% of real result. If we apply angsizing to everything, our final result will also be 70% of what it should've been.

0.7*Choji~Lightning - (0.7*KakashiBody~Choji + 0.7*KakashiArm) = 0.7 * real result

But if we will calculate like:

0.7*Choji~Lightning - (0.7*KakashiBody~Choji + KakashiArm) = ???

Result can be like 1000 times less than real one or even can be negative.

That's why I'm suggesting to apply angsizing directly from arm to Choji for accuracy.
 
@Damage3245 @Dalesean027 @CloverDragon03 @Vzearr

Look, guys, I'm very, very sorry for the tag. I know, Naruto thread, ewwww.
I get it. But this is just a simple calc evaluation thread. OP just wants his calc looked at and evaluated. That's all.
I guess it might also be prudent to see which calc is best between the OP's version and the currently accepted calc.

Thank you all so much in advance and happy new year! 😘
 
Why are you using Kakashi's blur as his width for pixel scaling? I get that it still represents him, but if accuracy is your concern, relying on the blur—whether you assume it's half his height or his width—will always be less precise than simply using Shikamaru. While Shikamaru is closer to the POV, the distance between him and Kakashi is relatively insignificant compared to the margin of error introduced by pixel scaling a blur where no distinct body parts are visible.
 
Why are you using Kakashi's blur as his width for pixel scaling? I get that it still represents him, but if accuracy is your concern, relying on the blur—whether you assume it's half his height or his width—will always be less precise than simply using Shikamaru. While Shikamaru is closer to the POV, the distance between him and Kakashi is relatively insignificant compared to the margin of error introduced by pixel scaling a blur where no distinct body parts are visible.
Accuracy of this part doesn't affect the other, the one that is the main reason of re-calculation.

Yeah, body parts are not visible but blur can't be smaller than Kakashi if he was fully visible(and if it's bigger, it makes feat a low-ball).

Largest width starting from below should be his bi-trochanteric width, which then continues nearly parallel. In the calc I used shoulder width, so it should be changed to his bi-trochanteric width but I'll at first wait for Vzearr to comment if he finds it reasonable.
 
I'm against using the blur at all. It's cut off from the top so there is no way to tell what the "largest width starting from below" is. Once again, using Shikamaru eliminates all of these assumptions.
After it reachest largest part, it continues parallelly so we can know that it's his bi-trochanteric width.
I'm in agreement with Kachon so far.
Fine, I will add another end using distance from Shikamaru.
 
Sorry y'all, I've been busy.

I don't think this feat can be calced. I don't necessarily know if Kakashi landed with the lightning not already touching him, I also think the pixel scaling is eh because of the weird angle.
 
I don't necessarily know if Kakashi landed with the lightning not already touching him
You mean touching his body? There's nothing indicating that Kakashi has taken any damage to his body.

Btw anime version also supports that Kakashi's arms were leaned forward before attack reaches him, they were even leaned back at the beginning when he landed but since manga version doesn't show anything like that I didn't include it.
I also think the pixel scaling is eh because of the weird angle.
I'm not sure what panel you're talking about. You mean Kakashi-ground part?
 
Okay, before I accept an end, can you label the text to the images, like.

Image 1:
....
....
....
Image 2:
...
......
...

So I can make sure I read everything correctly.
 
Okay, before I accept an end, can you label the text to the images, like.

Image 1:
....
....
....
Image 2:
...
......
...

So I can make sure I read everything correctly.
Sure, but I believe it's because you're viewing from PC. If so you can view from phone if you want, it's more clear.
 
Back
Top