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

Mash Calculation Stacking

It's my fault; I used the wrong number from our Speed page, and then I misread the number on my calculator.
 
I don't care about the distance stuff. idk if there's an issue, so I won't fight it.
 
Bump. Has the recalc been turned into a blog yet?
 
Do you agree with my Distance scaling?
Prolly should need more evaluation on the distance thing before this goes through. If someone can get the distance for one single set travelled, I can do the rest of the math.
 
Prolly should need more evaluation on the distance thing before this goes through. If someone can get the distance for one single set travelled, I can do the rest of the math.
The distance is difficult to determine because there are many panels with different backgrounds such as L.O.K's Scaling but to be more safe and very lowball you can use 1 Panel like I used on my calc.
 
The distance is difficult to determine because there are many panels with different backgrounds such as L.O.K's Scaling but to be more safe and very lowball you can use 1 Panel like I used on my calc.
Anyway, ang-sizing too fucky to use within that scan, prolly get a fresh scan where it isn't at an angle or some shit.
 
You can use this
I think this scan is the best one to use ang-sizing on, I don't think this'll need Pythagoras after all. Just use the farthest afterimage at the back and panel height, the rear surroundings are more or less at 90 degrees so just use the following from the Calculations Page:


Distance from point of view to object = object size * panel height in pixels/[object height in pixels*2*tan(70deg/2)]
 
I think this scan is the best one to use ang-sizing on, I don't think this'll need Pythagoras after all. Just use the farthest afterimage at the back and panel height, the rear surroundings are more or less at 90 degrees so just use the following from the Calculations Page:


Distance from point of view to object = object size * panel height in pixels/[object height in pixels*2*tan(70deg/2)]
I already used that on my calc here


Edit : I can edit my calc method.
 
I already used that on my calc here
Ah. That looks better now.

Now you can just go multiply that distance with the "tens of thousands of times" ends, then proceed straight to this:

(Object's true speed / Object's apparent speed) * Person's Apparent speed = Person's True Speed

Object's true speed being the water jet speed of at least Subsonic (34.3 m/s),

Object's apparent speed being walking speed (1.45288 m/s average speed based on the average of 2.5-4 mph walking speed),

and Person's apparent speed being... well, (37.16 * however many tens of thousands of times he did that move) / Subsonic timeframe of 0.0292 seconds.
 
Last edited:
Ah. That looks better now.

Now you can just go multiply that distance with the "tens of thousands of times" ends, then proceed straight to this:

(Object's true speed / Object's apparent speed) * Person's Apparent speed = Person's True Speed

Object's true speed being the water jet, Object's apparent speed being walking speed, and Person's apparent speed being... well, (37.16 * however many thousand times he did that move) / Subsonic timeframe of 0.0292 seconds.
I thought we agree for using 0.013 seconds?
 
No we didn't. We agreed on baseline Subsonic reactions, which is 0.0292 seconds.
 
Fair Enough, then for the Tens of Thousand things, let's determine the number
The lowball is 20k , The Midball is 45k and The Highballl is 90k.
I need y'all input from now! But i prefered the midball one because it's Consistent with the 65k punches.
 
Meh, it's a different feat, right? Just go with 20k then. It's much more difficult than just punching an opponent in front of you (if that's what 65k punches is referring to), so it makes sense to be lower.
 
Meh, it's a different feat, right? Just go with 20k then. It's much more difficult than just punching an opponent in front of you (if that's what 65k punches is referring to), so it makes sense to be lower.
No problem, i'll update my calc in less than 24 hours.
 
I thought we agree for using 0.013 seconds?
That's not the timeframe LOL, that's snail speed and it's 0.013 m/s. You mixed the units up LOL.

We didn't use snail speeds for apparent speed either, we used walking speed of 1.45288 m/s average.
 
Meters per second. People do not walk 1.45 miles per second.
 
Wait i thought we used Running speed?
No, object true speed would be 34.3 m/s

Apparent speed would be walking speed of 1.45288 m/s (AKA the speed you are seeing the object move at, in Mash's case he is viewing it as slow enough to just walk up to and bucket while also simultaneously creating afterimages to it).

The slower you view the object as, the faster you are than the object overall.
 
No, object true speed would be 34.3 m/s

Apparent speed would be walking speed of 1.45288 m/s (AKA the speed you are seeing the object move at, in Mash's case he is viewing it as slow enough to just walk up to and bucket while also simultaneously creating afterimages to it).

The slower you view the object as, the faster you are than the object overall.
Ok i get it.
 
Back
Top