Jujutsu Kaisen: Sukuna splits a cloud calc

[Rodriiogo]

This is the calculation and this is the video of the feat.

The Issue
The issue currently is the timeframe really. The currently accepted end of the calculation is the low-end which gives the result of 398.37 Kilotons of TNT and Mach 18.67 using 1.5 seconds as the timeframe as that's the time it takes in the video itself for the feat to happen.

However, despite being 3 still frames it's made very obvious that the timeframe is not "1.5 seconds" via the debris. It's shown that across all three frames the debris barely move the distance across the street barely moving at all. This is not simply slow debris falling considering that their speed comes from Sukuna dismantling the surroundings making them get knocked away at high speeds. And they are even seen flying all around at high speeds just the scene before the cloud cut, alongside Sukuna and Mahoraga who were dashing around the city at high speeds were still just getting out of the building after the cloud cut is over. This alongside the fact that the debris of the fight itself were being shown at slow motion 90% of the time as seen on multiple, multiple, multiple, MULTIPLE scenes leads me to believe that the high-end of the calculation is way more logical and should be used instead. (Getting the timeframe based on the movement of the flying debris)

Conclusion
The High-End of the calculation should be used instead of the Low-End as it is more consistent with what's actually shown on-screen.

EDIT: The calculation's end has been re-done according to Dalesean's instructions. This will be the one used:

Sukuna Splits a Cloud (JJK Anime)

vsbattles.fandom.com

Agree:

Disagree:

Neutral:

 

[Anonymous_Learner]

following

 

[Damage3245]

This doesn't even look like a proper cloud split to me. Where is it shown that it was fully overcast before being "split"? The sequence of frames in the supposed feat at 0.54 seconds in the video cuts between multiple different perspectives instead of actually showing any animation of the clouds moving from Point A to Point B.

I don't think this calc should be useable.

 

[Rodriiogo]

This doesn't even look like a proper cloud split to me. Where is it shown that it was fully overcast before being "split"? The sequence of frames in the supposed feat at 0.54 seconds in the video cuts between multiple different perspectives instead of actually showing any animation of the clouds moving from Point A to Point B.

I don't think this calc should be useable.

In the second we frame we see that the cloud is still in the process off being split while in the third it's already fully split even deforming it's shape, so the split did happen in-between those frames it just isn't animated.

Those are in the same street (we could find this out since it's a real life location) as pointed out in the calc itself, it just zoomed out to show the full split.

 

[Damage3245]

I'm very wary about us trying to calculate a feat that isn't even animated.

 

[Rodriiogo]

I'm very wary about us trying to calculate a feat that isn't even animated.

I mean it's essentially like calculating a manga feat (since those also aren't animated) so I don't see the issue specially when we "see" it happen still

 

[Damage3245]

I mean it's essentially like calculating a manga feat (since those also aren't animated) so I don't see the issue specially when we "see" it happen still

I don't think 2 frames are enough to judge a feat like this properly. Especially when we don't have a clear "before" shot of the feat.

As a feat, it also doesn't make a lot of sense. Sukuna sends out a narrow slash which somehow pushes away all of the mass of the air around it for several hundreds of meters horizontally up to a height of nearly 5 kilometers. We don't ever see his slashes act like this usually at any other time.

 

[Rodriiogo]

I don't think 2 frames are enough to judge a feat like this properly. Especially when we don't have a clear "before" shot of the feat.

We kinda do in some shots where the sky is shown before that moment. The sky was fully clouded in all shots before 0:54, you can't see the moon or anything at all until Sukuna opens the skies, we even see in the second frame how thick and dark the clouds truly were before the dismantle, which kinda makes it consistent with how the sky is shown before this.

As a feat, it also doesn't make a lot of sense. Sukuna sends out a narrow slash which somehow pushes away all of the mass of the air around it for several hundreds of meters horizontally up to a height of nearly 5 kilometers. We don't ever see his slashes act like this usually at any other time.

He is actively doing that throughout this fight where his dismantles affect the enviroment even when not targetted at it, it just depends on the output put into it. But we also do see situations like this in the manga as well where attacks like dismantle go way beyond the thing they were targetting and affect the enviroment:

The anime just took this to the extreme and made it have even more range really, it's just a upgrade for range.

 

[Damage3245]

He is actively doing that throughout this fight where his dismantles affect the enviroment even when not targetted at it, it just depends on the output put into it. But we also do see situations like this in the manga as well where attacks like dismantle go way beyond the thing they were targetting and affect the enviroment:

I think the panel with Mahoraga's slash on Gojo actually disproves it affecting the environment that much; yes it cuts into the building itself, but it doesn't affect the rest of the building beyond what is directly slashes. The top half of the building isn't being launched upwards and the bottom half isn't being flattened as the slash passes through it.

 

[Rodriiogo]

I think the panel with Mahoraga's slash on Gojo actually disproves it affecting the environment that much; yes it cuts into the building itself, but it doesn't affect the rest of the building beyond what is directly slashes. The top half of the building isn't being launched upwards and the bottom half isn't being flattened as the slash passes through it.

That's what I meant really, they just upgraded it's range in the anime and it also varies alot with the output, in the two scenes I linked of the dismantle harming the enviroment, one has way more range than the other, despite both being a dismantle that cuts the enviroment in the same way.

 

[Rodriiogo]

Are we sure he actually cuts the clouds here?

Pretty sure, the whole scene is how he is spamming dismantles everywhere all around him,cutting everything. One of them ends up going to the skies and splitting the clouds, we see in the 3 frames that it happens because a line (dismantle) cut through the clouds which caused it to be knocked away

 

[MrTayman616]

Pretty sure, the whole scene is how he is spamming dismantles everywhere all around him,cutting everything. One of them ends up going to the skies and splitting the clouds, we see in the 3 frames that it happens because a line (dismantle) cut through the clouds which caused it to be knocked away

This is not true. If you check each frame, you can see every building in the frame is actually different (at the very least, a different side of it). So these frames are actually showing different locations.

So there is actually nothing that shows the clouds were slashed.

 

[Rodriiogo]

This is not true. If you check each frame, you can see every building in the frame is actually different. So these frames are actually showing different locations.

So there is actually nothing that shows the clouds were slashed.

This was already brought up and used in the calc itself, the real life locations are in the same street just zoomed out to include the entire street in one frame

All 3 frames are of the same street it just zooms out from down there (that parco building up to the modi, you can even see the Parco right there in the real image of the Modi)

 

[MrTayman616]

This was already brought up and used in the calc itself, the real life locations are in the same street just zoomed out to include the entire street in one frame

All 3 frames are of the same street it just zooms out from down there (that parco building up to the modi, you can even see the Parco right there in the real image of the Modi)

Oh, i see. Even then, the clouds look extremely normal(not slashed) in the anime blu ray version while it's apparently slashed in the normal anime version.

 

[Rodriiogo]

Oh, i see. Even then, the clouds look extremely normal(not slashed) in the anime blu ray version while it's apparently slashed in the normal anime version.

The intention was for it to be slashed really, even on the blu-ray we see that in the second frame the clouds weren't fully separated as the hole in the clouds was small. So that "expansion"/movement happened in that very moment otherwise it'd be fully opened already:

For more proof we also see that the sky was COMPLETELY cloudy before this cut.

 

[Arkenis]

Just wanted to say, he definitely did send one to the sky as just minutes later, an airplane with its wing cut off came crashing down.

 

[ElJoaki5]

The clouds "looking not slashed" isnt a valid argument when theres a frame of them literally splitting apart. Can you stop denying this being a valid feat for no reason?

 

[Electronic74947]

Didn't the next scene after the cloud split show an airplane falling out of the sky lol. Even if we don't accept him splitting thecloud there should still be a speed ugrade from it anyways unless i'm getting something wrong

 

[Rodriiogo]

The feat is accepted as valid already so this is kinda derailing a bit, Im purposing that the end that should be used is the high end via what I said in the post, the current accepted end (low end) is just downplaying whats actually being shown

 

[Damage3245]

I'll wait for a CRT to discuss removing it then instead of here.

 

[Rodriiogo]

Idt removing it is necessary as everyone explained why it is valid

Regardless will wait for inputs on the thread itself (on high end being used or not)

 

[Dark_Soul20189]

Just gonna ask when this calc was even accepted, since I can't find it on the verse page?

 

[Damage3245]

Idt removing it is necessary as everyone explained why it is valid

Regardless will wait for inputs on the thread itself (on high end being used or not)

Feats aren't always appropriate to use even if they did take place. Otherwise concepts like outliers would be nonexistent.

 

[Rodriiogo]

Just gonna ask when this calc was even accepted, since I can't find it on the verse page?

It got accepted in the comments and is being implemented alongside the uraume calc soon but people are still doing the sandboxes. Currently the verse page has the older calc because it hasn't been updated it yet, but this should be decided beforehand (high end or low end)

 

[Arkenis]

Just gonna ask when this calc was even accepted, since I can't find it on the verse page?

We move a bit slow but you can look at Drites comments on the blog. This is in a crt as well.

Basically never go off the verse page or even the character pages

 

[Rodriiogo]

Feats aren't always appropriate to use even if they did take place. Otherwise concepts like outliers would be nonexistent.

Yea but I don't see a issue with the feat myself personally?

Arkenis even brought up how sukuna dismantles getting that high is consistent and a big part of the choreography at one point since the plane in the skies gets its wing cut where maho and sukuna fight in blu ray at one point.

Anyways if anything that should have been adressed on the upgrade crt so for now waiting for inputs on if high end purposal is better or not

 

[Damage3245]

Yea but I don't see a issue with the feat myself personally?

Arkenis even brought up how sukuna dismantles getting that high is consistent and a big part of the choreography at one point since the plane in the skies gets its wing cut where maho and sukuna fight in blu ray at one point.

Anyways if anything that should have been adressed on the upgrade crt so for now waiting for inputs on if high end purposal is better or not

I just said I was dropping it on here, so I'm not sure why you're responding to me about it on here if you don't want the thread derailed.

 

[Chariot190]

Basically never go off the verse page or even the character pages

Like I know my slow ass multi tasking ass aint one to talk but I do it basically solo, but ya'll have a whole squad plus isnt that LITERALLY the point of them.

 

[Arkenis]

Like I know my slow ass multi tasking ass aint one to talk but I do it basically solo, but ya'll have a whole squad plus isnt that LITERALLY the point of them.

A lot happens in the vsbw jujutsu society, the higher ups block us at times but our special grades sometimes help us. (there's just a lot of crts and discussions going on)

 

[Rodriiogo]

Bump

 

[ElJoaki5]

@Dalesean027 @Floxy178
May I summon you?

 

[Dalesean027]

 

[Dalesean027]

I was at work until like 8 hours ago but I was feeling to lazy to comment until now (Please read this full thing before commenting)

a few things I wanna comment on at a glance

multiple, multiple,

in these two links (its the same shot so I'm not even sure why its separated in 2 links to begin with) at the shot where it pans to sky from the perspective of the people on the ground, it briefly shows the people also reacting to the falling debris and moving so its actually not that good as support, one guy swings is torso like 90 degrees in while another turns his head about the same distance in that time too so its not ALL happening at the high end speeds, not discounting it btw just pointing that out.

Really I don't like that OP claims about 90% of the fight is in slow motion, I've rewatched the whole thing from the links above and at like every single moment there are shots immediately before or after the ones that are picked here that are actually in real time (aside from the train swing at the beginning), I'd argue most of the fight is in real time, the vast majority isn't slow motion shots just a few instances and some which aren't consistent to themself.

multiple,

OP links this but literally like in the 6 seconds before it is this in real time and briefly slows going into the shot with the people still reacting to the falling debris even if its in slow motion showing its not dilated as much in this specific shot but that's aside from the point that 90% of the fight is presented in slow motion which isn't true

multiple,

this is slow motion but again immediately followed by the shot of people moving in tandem with and reacting to the debris as I've expressed twice now

MULTIPLE

This scene follows this scene where we once again see the debris falling in real time like for the entire last 20 seconds before this shot. Again though the shots OP chose aren't even the only slow motion scenes in the full fight and I'm not claiming that but for the vast majority of the fight its not presented in slow motion outside of a few instances out of the entire runtime of the fight so the whole basis of saying this should be this fast because these fewer instances out of the total runtime are in slow motion ain't gonna sit right with me. If need be I will closely go bit by bit to timestamp every single instance of real time vs slow motion and give the total runtime or timeframe difference between the two, point is don't claim 90% when if anything its the complete opposite where maybe 10~15% is slow motion vs real time (I'd really really rather not do this tho so pls)

Also though my other problem is that cloud split ain't animated like at all, now imo it obviously happens but like 3 still frames that hold for like a second each aren't any good basis to say the split HAD to happen in like 0.16s as the calc presumes in the high end and with that I can get into my problems with the actual calc itself and instead of just the reasonings why I disagree with the OPs reasonings for it being more valid to begin with.



Just right away starting out already, this ain't gonna fly like at all and is legit unacceptable. Sukuna isn't even on the same plane as the debris so scaling its motion to him is just outright inflating the actual distance it travelled in this moment when instead of your calc suggesting the debris moved 1.65m (a full person's height) when instead its moreso maybe about 0.30m at the most in movement.

You're much better off scaling the debris you used in this shot

To Sukuna in this shot when is actually somewhat on the same plane as the debris here


even then thought he debris is not even going directly to the side and not directly at the PoV either so you need to do some ang sizing or Pythagoras to get the actual appropriate distance travelled in real time. So really assuming the same 0.125s timeframe and about 0.3m instead you get a real time speed of 2.4m/s for the debris speed in this specific shot instead of your 13.2m/s speed, a big difference when you're trying to calculate slow motion speed and makes the speed difference much less than what was previous calculated ofc my numbers are general estimate but the point still stands.

Also minor kinda off topic nitpick but please color code your lines in these blogs and put the actual number in the px scaled images like this (saves us time and is just good practice since it helps others learn how to make better quality blogs)

Anyways getting back to the calc this image has the same problem where you once again are measuring things that aren't remotely sitting on the same plane and are at weird angles, it just doesn't work as the debris is 100% completely in front of everything and sits in the foreground in front of the buildings which are already at an angle behind them so you simply can't px scale the distance from this shot without inflating it as the sizes and distance will come out inflated so it should be discarded as whole as its ultimately unneeded anyways since you already have a better way to find these values.

If we're being 100% real here everything thus far in the calc can all be discarded as there is a much simpler and safer way to get the speed of the debris in slow motion and in real time from one shot, that being this one where we can actually see the debris and people in both slow motion and real time all in one go.


Now for this I'll scale off the people since they are actually something scalable in the shot rather than the debris and it'd work as a bare minimum speed for the debris



1.71m* 404/[54.19 * 2 * tan(70deg/2)] = 9.10335642m


1.71m/54.19 * 157.18 = 4.95991511m
1.71m/54.19 * 29.09 = 0.917953497m (Leg Length)
0.917953497m * 404/[44 * 2 * tan(70deg/2)] = 6.01855996m
9.10335642m - 6.01855996m = 3.08479646m
3.08479646m + 4.95991511m = 8.04471157m

Frame 1209 - Frame 1222 = 13 frames, 13/24 = 0.54166666666s
8.04471157m/0.54166666666s = 14.8517752m/s

The distance from the cut building to the other building is 17.8 m, so the final distance is 17.8 - 4.192941176 = 13.60705882 m

High end time: (13.60705882m)/14.8517752m/s = 0.916190734s
((1186.65215006m+1132.09343052m)/2)/0.916190734s = 1265.42733m/s

So ultimately a big difference from the previous speed in the high end and ultimately much more reliable with better px scaling in place. Now ultimately that's still if we do want to take 3 still frames with cuts between as proof of the debris was in slow motion during the split but ultimately I its a difference of 1.5 seconds versus 0.916s so once the corrections are made I'll leave to other CGMs to see how they feel

 

[Rodriiogo]

in these two links (its the same shot so I'm not even sure why its separated in 2 links to begin with) at the shot where it pans to sky from the perspective of the people on the ground, it briefly shows the people also reacting to the falling debris and moving so its actually not that good as support, one guy swings is torso like 90 degrees in while another turns his head about the same distance in that time too so its not ALL happening at the high end speeds, not discounting it btw just pointing that out.

My mistake, I probably put the wrong link.

Really I don't like that OP claims about 90% of the fight is in slow motion, I've rewatched the whole thing from the links above and at like every single moment there are shots immediately before or after the ones that are picked here that are actually in real time (aside from the train swing at the beginning), I'd argue most of the fight is in real time, the vast majority isn't slow motion shots just a few instances and some which aren't consistent to themself.

OP links this but literally like in the 6 seconds before it is this in real time and briefly slows going into the shot with the people still reacting to the falling debris even if its in slow motion showing its not dilated as much in this specific shot but that's aside from the point that 90% of the fight is presented in slow motion which isn't true

this is slow motion but again immediately followed by the shot of people moving in tandem with and reacting to the debris as I've expressed twice now

I do agree with the previous 6 seconds of the first scene being in real time but the people reacting to the falling debris is dubious, in the previous scene we see how even the ppl being thrown by it were moving at slow mo and the rocks were catching up to them. The way the rocks moves of itself in the people reacting scene is in slow mo, it physically cant be in anything other than slow mo there otherwise both those rocks and the people that were being thrown/falling are just defying gravity and flying like they are on the moon since moving at that much of a slow speed would just make them drop instead.

This scene follows this scene where we once again see the debris falling in real time like for the entire last 20 seconds before this shot. Again though the shots OP chose aren't even the only slow motion scenes in the full fight and I'm not claiming that but for the vast majority of the fight its not presented in slow motion outside of a few instances out of the entire runtime of the fight so the whole basis of saying this should be this fast because these fewer instances out of the total runtime are in slow motion ain't gonna sit right with me. If need be I will closely go bit by bit to timestamp every single instance of real time vs slow motion and give the total runtime or timeframe difference between the two, point is don't claim 90% when if anything its the complete opposite where maybe 10~15% is slow motion vs real time (I'd really really rather not do this tho so pls)

I agree it falls in real time here for a moment, UNTIL it cuts to Sukuna. In the shot where sukuna is in the frame you can see the rocks, specificially the ones hes looking at/in front of him are very much in slow motion. I agree I might have exxagerated with the % so theres no need for you to do that dw, but alot of the times when the scene is meant to show the debris they are in slow mo (when sukuna and mahoraga are fighting on screen it isnt most of the time)

Also though my other problem is that cloud split ain't animated like at all, now imo it obviously happens but like 3 still frames that hold for like a second each aren't any good basis to say the split HAD to happen in like 0.16s as the calc presumes in the high end and with that I can get into my problems with the actual calc itself and instead of just the reasonings why I disagree with the OPs reasonings for it being more valid to begin with.

My reason for it being more valid is the fact that, despite not getting animated yes, you can quite see how the debris barely move while in all other scenes (even in the real time fall of them that you showed in the previous point) they are being flung at extremely high speeds so using the 1.5 seconds makes no sense when the rocks barely move throughout the entire cloud cut unless the rocks are moving at like 2m/s which obviously isnt true.

Just right away starting out already, this ain't gonna fly like at all and is legit unacceptable. Sukuna isn't even on the same plane as the debris so scaling its motion to him is just outright inflating the actual distance it travelled in this moment when instead of your calc suggesting the debris moved 1.65m (a full person's height) when instead its moreso maybe about 0.30m at the most in movement.

You're much better off scaling the debris you used in this shot

To Sukuna in this shot when is actually somewhat on the same plane as the debris here


even then thought he debris is not even going directly to the side and not directly at the PoV either so you need to do some ang sizing or Pythagoras to get the actual appropriate distance travelled in real time. So really assuming the same 0.125s timeframe and about 0.3m instead you get a real time speed of 2.4m/s for the debris speed in this specific shot instead of your 13.2m/s speed, a big difference when you're trying to calculate slow motion speed and makes the speed difference much less than what was previous calculated ofc my numbers are general estimate but the point still stands.

Fair enough on the perspective thing I agree a different way should be used to get the debris speed. (I personally suggest the same scene but using the time it takes for the debris to reach mahoraga there, i dont know if you agree with that, I could show this better at a later time when I get home from uni)

Also minor kinda off topic nitpick but please color code your lines in these blogs and put the actual number in the px scaled images like this (saves us time and is just good practice since it helps others learn how to make better quality blogs)

The calc isn't mine but fairs

Anyways getting back to the calc this image has the same problem where you once again are measuring things that aren't remotely sitting on the same plane and are at weird angles, it just doesn't work as the debris is 100% completely in front of everything and sits in the foreground in front of the buildings which are already at an angle behind them so you simply can't px scale the distance from this shot without inflating it as the sizes and distance will come out inflated so it should be discarded as whole as its ultimately unneeded anyways since you already have a better way to find these values.

Fair enough.

If we're being 100% real here everything thus far in the calc can all be discarded as there is a much simpler and safer way to get the speed of the debris in slow motion and in real time from one shot, that being this one where we can actually see the debris and people in both slow motion and real time all in one go.


Now for this I'll scale off the people since they are actually something scalable in the shot rather than the debris and it'd work as a bare minimum speed for the debris



1.71m* 404/[54.19 * 2 * tan(70deg/2)] = 9.10335642m


1.71m/54.19 * 157.18 = 4.95991511m
1.71m/54.19 * 29.09 = 0.917953497m (Leg Length)
0.917953497m * 404/[44 * 2 * tan(70deg/2)] = 6.01855996m
9.10335642m - 6.01855996m = 3.08479646m
3.08479646m + 4.95991511m = 8.04471157m

Frame 1209 - Frame 1222 = 13 frames, 13/24 = 0.54166666666s
8.04471157m/0.54166666666s = 14.8517752m/s

The distance from the cut building to the other building is 17.8 m, so the final distance is 17.8 - 4.192941176 = 13.60705882 m

High end time: (13.60705882m)/14.8517752m/s = 0.916190734s
((1186.65215006m+1132.09343052m)/2)/0.916190734s = 1265.42733m/s

So ultimately a big difference from the previous speed in the high end and ultimately much more reliable with better px scaling in place. Now ultimately that's still if we do want to take 3 still frames with cuts between as proof of the debris was in slow motion during the split but ultimately I its a difference of 1.5 seconds versus 0.916s so once the corrections are made I'll leave to other CGMs to see how they feel

Now this is where Im confused. The speed you got for the debris is even faster than the current speed being used. You just forgot to remove the initial distance between the debris and the building which should be taken into account. The final distance shouldnt be "13.60705882 m" as thats saying the debris started right where the building was which isnt true, it should be "13.60705882 - (Initial Distance between building and debris)" you will prob get a timeframe close to what the calc does with that so theres no much change other than fixing the initial distance as you pointed out the way its gotten is incorrect.

You also forgot to remove a part of the timeframe since only half of the timeframe is the cloud being cut.

 

[Dalesean027]

Now this is where Im confused. The speed you got for the debris is even faster than the current speed being used.

This is true however its not done via faulty means, just because I made corrections or had issues with the other version that doesn't mean its gonna downgrade every aspect.

You just forgot to remove the initial distance between the debris and the building which should be taken into account. The final distance shouldnt be "13.60705882 m" as thats saying the debris started right where the building was which isnt true, it should be "13.60705882 - (Initial Distance between building and debris)"

It shouldn't be, the original calc didn't need to do something contrived like that and even then the intial distance vs final distance shit is needs to be axed because it has no bearing on actual final timeframe. All that matters is that we know the debris made it x distance at x speed which gives us a timeframe for the split. Its also not even viable to scale from the debris since we don't have a size of these random chunks of rock that would paint the entire building's size as being inconsistent since they are at worst 3m in size while a storey in japan in 3.9m tall yet they are tiny in comparison to the building when they exit, there are clear inconsistencies in using those to scale.


3.9m * 404/[153 * 2 * tan(70deg/2)] = 7.35356209m, this would be the distance from the building to the PoV which contradicts a lot of things in the scene itself obviously.

we know the final speed and final distance, those are all that matter for us to get a solid timeframe

You also forgot to remove a part of the timeframe since only half of the timeframe is the cloud being cut.

that's only relevant to the part with sukuna's slashes attack speed not the dispersal itself so no I didn't forget it

 

[Rodriiogo]

It shouldn't be, the original calc didn't need to do something contrived like that and even then the intial distance vs final distance shit is needs to be axed because it has no bearing on actual final timeframe. All that matters is that we know the debris made it x distance at x speed which gives us a timeframe for the split. Its also not even viable to scale from the debris since we don't have a size of these random chunks of rock that would paint the entire building's size as being inconsistent since they are at worst 3m in size while a storey in japan in 3.9m tall yet they are tiny in comparison to the building when they exit, there are clear inconsistencies in using those to scale.


3.9m * 404/[153 * 2 * tan(70deg/2)] = 7.35356209m, this would be the distance from the building to the PoV which contradicts a lot of things in the scene itself obviously.

we know the final speed and final distance, those are all that matter for us to get a solid timeframe

But it does have importance. The rocks didnt move from the building to the other side of the street during the feat, they were already meters away from the building before the feat even starts so the distance ur using for the apparent speed is way bigger than it actually traveled

Your apparent speed acts like the rocks are during the feat traveling:
Building -> Other side of the street

When its actually:
Meters away from the Building -> Other side of the street.

I do agree that the way it calc'd the initial distance from the building is wrong because its an angular frame. However I think you can still use the frame to get the initial distance just without pixel scaling. Im not home right now but I will check once I am but cant we just use the real life measurement between the building and that lamp post right there (or smth around there) as the initial distance away from the building? Its way more consistent than any pixel scaling eitherway and its what we use for the final distance so using it for the initial should be fine right?

Tho midway through this, seeing the image you sent I was not talking about THAT frame so mb if i misworded but I meant https://vsbattles.fandom.com/wiki/File:SukunaCloud3.jpg this (cant hyperlink it for some reason my phone isnt letting me lmao). This pixel scale is wrong yes as you pointed out however that distance is needed for the initial distance between the rocks and the building. Which as I said now, I purpose we use the real distance of that lamp post (or something around that) and building. (Will do that when home if you agree to it)

 

[Dalesean027]

I'm at work now so I can't comment on it all until later but

Which as I said now, I purpose we use the real distance of that lamp post (or something around that) and building. (Will do that when home if you agree to it)

This doesn't work the lamp is still in thr background compared to the debris which is the closest thing to the screen by far, I mean perspective be damned but the debris is the most foremost thing in the image so no nothing in this image is viable to use, the lamp is closer to the tree than it is the debris in this shot and we can see the debris is much closer than the tree. Using any object there will inflate the results hence why I said to begin with that entire shot needs to be axed from being used as a whole

 

[ElJoaki5]

What about that yellow sign as reference? It’s between the debris.
any size for that thing? @Rodriiogo

 

[Dalesean027]

What about that yellow sign as reference? It’s between the debris.

There is a way that could work but I saw nothing of reference for its size to measure from when I looked over things earlier and I'd rather not assume some arbitrary size otherwise unless Rod finds some concrete way to measure it otherwise

 

[Rodriiogo]

I get home from uni in like an hour and a half and I will check it out with the real life measurements (to see if theres a better way I mean)