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

Jujutsu Kaisen: Mechamaru’s year charge calc [Staff Votes Needed]

Status
Not open for further replies.
I've posted earlier the issue about height, and have calced the height of mechamarus mech earlier last month. I've also done the math for KE as well,

Only difference is speed, as Mechanaru travels and moves WAY way faster than a regular human walking speed
Your height is inconsistent too, since every single time the robot is actually shown side by side with something, its way smaller than that. The robots height is not drawn consistently so its not like theres an actual good or bad size for it, lowballing it makes sense. In addition to this, your results are helluva inconsistent with the already stablished verse scaling and already got rejected, just let it go.
You havent calculated the speed correctly either: it’s 1.3*64.7161673018/1.7 = 49.488833819 m/s
 
Is it possible to use the structures in the fight to scale the robot's height instead? Character heights can be inconsistent in scenes like this
 
Your height is inconsistent too, since every single time the robot is actually shown side by side with something, its way smaller than that. The robots height is not drawn consistently so its not like theres an actual good or bad size for it, lowballing it makes sense. In addition to this, your results are helluva inconsistent with the already stablished verse scaling and already got rejected, just let it go.
You havent calculated the speed correctly either: it’s 1.3*64.7161673018/1.7 = 49.488833819 m/s
I’m not using external characters like Mahito for size comparison precisely because he’s inconsistent, he alters his size and proportions throughout the fight. That makes him an unreliable reference point. The calculation I’m using is based on consistent, internal components of Mechamaru’s robot itself, like the size of the cockpit/orb room, which we directly see Mechamaru inside of. This avoids any external inconsistency and focuses only on fixed, verifiable parts of the mecha’s own structure. The robot’s height in certain wide shots may fluctuate because of manga frames/angle inconsistencies, which happens in practically every manga, but that doesn't mean arbitrarily lowballing is more valid. The calc uses proportional measurements within the mecha’s own anatomy, not external scaling with characters or environment, making it internally consistent and more reliable than picking and choosing random lowball frames.

Also the speed is X normal speed times Y times larger, as on the large size calculation page.
 
Also the speed is X normal speed times Y times larger, as on the large size calculation page.
Yes, thats what I said and what you havent done
I’m not using external characters like Mahito for size comparison precisely because he’s inconsistent,
you can compare him to Kenjaku too and the height is also way lower
 
Yes, thats what I said and what you havent done
but I have, its there??

you can compare him to Kenjaku too and the height is also way lower
Not really, because you’re not seeing them from a direct, head-on view with both positioned side by side. Instead, the perspective is from a right-side angle, with the two not aligned evenly. One of them is positioned slightly closer to the foreground, which affects how their sizes appear relative to each other. It’s kind of like claiming a person is as tall as the Leaning Tower of Pisa just because they’re standing closer to the camera, obviously not to that extreme, but it’s the first comparison that came to mind.
 
but I have, its there??
No. You multiply human walking speed by robot height, not difference in height. Difference in height is robot height divided by human height.
1.3*64.7161673018/1.7 = 49.488833819 m/s

but I have, its there??


Not really, because you’re not seeing them from a direct, head-on view with both positioned side by side. Instead, the perspective is from a right-side angle, with the two not aligned evenly. One of them is positioned slightly closer to the foreground, which affects how their sizes appear relative to each other. It’s kind of like claiming a person is as tall as the Leaning Tower of Pisa just because they’re standing closer to the camera, obviously not to that extreme, but it’s the first comparison that came to mind.
Its the opposite way around, if anything Kenjaku is further from the camera and yet pixelscaling the robot is just 24.3 m.
 
No. You multiply human walking speed by robot height, not difference in height. Difference in height is robot height divided by human height.
1.3*64.7161673018/1.7 = 49.488833819 m/s
Its the difference in size, An x-times larger character should also be x-times faster.
I mean, that’s my point. The problem lies with the perspective and positioning in the frame. Because Kenjaku is further back, it isn’t an accurate measurement to compare their sizes. The two aren’t aligned side by side, and when characters aren’t on the same plane in a shot. You just showcased that it isn't accurate.
 
Its the difference in size, An x-times larger character should also be x-times faster.
Thats literally what im saying and your calculation doesnt do that.
I mean, that’s my point. The problem lies with the perspective and positioning in the frame. Because Kenjaku is further back, it isn’t an accurate measurement to compare their sizes. The two aren’t aligned side by side, and when characters aren’t on the same plane in a shot. You just showcased that it isn't accurate.
If Kenjaku is farther back that makes the robot appear larger in comparison.
 
Thats literally what im saying and your calculation doesnt do that.
It does do that??
If Kenjaku is farther back that makes the robot appear larger in comparison.
If Kenjaku being farther back makes the robot appear larger, then the perspective is already skewing the apparent size difference. That’s my entire point: the depth and positioning in the frame distort both characters differently, and you’re assuming that distortion affects them equally, which it doesn’t. Because they’re not on the same plane or aligned side by side, any pixel scaling from that frame becomes unreliable. The issue isn’t just that the sizes are skewed, it’s that none of these shots are from the same distance, angle, or plane. You’re comparing two different perspectives with different depth placements and expecting consistent results. You can’t treat these as 1:1 scaling references when the framing isn’t consistent.
 
~10 meters seems to be the most consistent height

The height in the calc got to slightly over 10 meters

My calc got to slightly under 10 meters:

He generally was portrayed as not insanely larger than Mahito but still much bigger than the trees
 
Last edited:
idk why it won't let me quote it but @ElJoaki5

You don't do a /1.7 at the end. The speed for large size is if x is 10 times bigger, it would be 10 times regular speed. The height isn't dividing with the speed. It's just x times bigger is x times faster
 
idk why it won't let me quote it but @ElJoaki5

You don't do a /1.7 at the end. The speed for large size is if x is 10 times bigger, it would be 10 times regular speed. The height isn't dividing with the speed. It's just x times bigger is x times faster
The 1.7 isn't speed that's 1.7 m which is around regular human height which is also what you're describing, dividing the height by regular human height to find it as x times bigger. What you did was straight up multiply human speed by the calc'd height you got for Mechamaru and skipped the step where you get the "x times bigger" value.

64.7161673018 m is the height you used for GPE so you still have to divide it by human height still which is what ElJoaki is saying you didn't do and what he actually did in his calc.
 
The 1.7 isn't speed that's 1.7 m which is around regular human height which is also what you're describing, dividing the height by regular human height to find it as x times bigger. What you did was straight up multiply human speed by the calc'd height you got for Mechamaru and skipped the step where you get the "x times bigger" value.


64.7161673018 m is the height you used for GPE so you still have to divide it by human height still which is what ElJoaki is saying you didn't do and what he actually did in his calc.
insert tropic thunder quote here

damn yeah my bad, I was too focused on the speed itself. fixed it up now
 
Status
Not open for further replies.
Back
Top