- 17,883
- 27,987
Anyway, to go about why speeds fucky.
Cloud thickness from around that line is 3000m apparently, idk I'm just copying the current pixel scaling.
86px = 3000m~
48px = 1674.4186046511627595457m~
Overlapped first and final frame of that scene, ****** with opacity.
This happened over 2 seconds and 29 frame. And thus a speed of about 564.41mps.
This would mean it'd take 1.48 hours for the feat to occur. Which, is hilariously unrealistic based on the info we have, Wario did not stick around that long, it did not take him that long to go back.
But wait,
Panel height 810px.
Object size = 37.632380952380952596.
3000*810/(86*2*tan(70deg/2)) = 20176.7422m.
Is the general distance, give or take, kinda half assed that but close enough, so about 20km between there and that island. This would mean, being generous here, it'd actually be longer, it'd have taken about 35 seconds to reach the island at the speed it was going, but that is demonstrably not the case nor what happened. 35 seconds might not seem like much, but like, it not seeming like much doesn't change the fact it didn't happen.
funny epilepsy warning, the clouds spontaneously cover that distance in a literal frame. In real time mind you.
That's, 1/30th of a second, 20km in that instance, or about 605302.266mps. That'd give us a timeframe of 4.97 seconds for the whole feat, that is evidently not the case, but that doesn't change the fact it still covered said disance in that time and thus had that speed for however long.
Which as an fyi, I'm not arguing the 2633.584 speed here. It doesn't actually work to begin with. The actual scene shows the clouds moving at the 500mps after the beam, then it cuts to the captain and clouds already behind her and parting further. Which is to say it didn't cover those 20km~ in that alleged 9 seconds. We see it start at about 16kms, slow down drastically to about 500mps, and then is suddenly where they are. Ignoring this means the clouds sped up regardless (They were parting at about 500mps), rendering the suggested proposal faulty and physics yap, but, it means there doesn't actually exist a 9 second timeframe for them to cover that 20km, it happens instantly almost, even if one argues it was a jump cut in time, that still invalidates 9 seconds. At best you'd argue the speed shown as it passes overhead.
Ok but for arguments sake, let's ignore the funny big number, I'm sure you'd call it a cinematic cut anyhow, but regardless 2633mps doesn't actually exist.
We see the clouds part behind the lil ***** and the captain, notice how the speed at which they disperse is still completely different from the initial parting or the following part at 500mps? In fact being quite a bit quicker than 500mps, isn't that odd. Why are they, on screen, visibly, moving at a quicker speed than they were seconds ago?
For reference instance 1 is 1.76 seconds, instance 2 is 1.73 seconds. The clouds covered a relevant distance, in less than 2 seconds, at a blatantly different rate compared to initial, slowdown and even subsequent instance.
Ok but, ignore even THAT
From the tip of the clouds in the frame (look in the corner, you can like barely see it still but it there), to the wideview, is 1.23 seconds.
We KNOW there isn't a timeskip in here, as the merfs cheering drags on between both uninterrupted.
Here's some very rough scaling, just moreso for proof of concept, it's a certified close enough.
Mind you this is an extreme lowend, the beach is exponentially larger than this too.
Anyway, yap aside, this gives us a horizon distance in the final shot of 80km. Given we know, at MINIMUM, it cleared out between the merf cheering and the, well, the view itself, which is only 1.23 seconds (lowballing, could have easily cut a few frames off),
That would give us a Horizon distance of 80.22km, which given it cleared in 1.23 seconds at worst, would be about 65.21kms, or 65219mps.
Which, would be a timeframe of 46.13 seconds. Literally lower than the minute presumed, exponentially lower than your numerous claims of 20m+ based on the, unfortunately, non-existent 2000mps, and not far off from the evident intent of the scene which is only 27 seconds and 18 frames.
It's also, despite the multiple claims of the fluctuating being minimal, extremely drastic.
The speed starts off
16283.296 m/s (Initial parting)
Drops to 564.41m/s (Clouds moving in the distance)
Jumps to 605302.266m/s (Jumps to right above them from 20km away).
Slows back down to, idk, just gonna eyeball it, ive done looked over enough shit but say like 3000mps? Like evidently it's covering a distance thicker than itself in that timeframe, good enough. Also important to note, due to the upward facing angle, the clouds at the end of this, are over the island still, not past it. Which is pretty important when factoring in the final horizon speed.
Then jumps back up to 65219mps as it goes from over the island, to a high horizon shot being completely clear in less than 2 seconds (This, would be the speed we'd use fyi if we ignore the inconstent visuals, as it happened last, and thus the speed the majority would be presumed pushed at).
To put that into numbers.
Between 16283.296 and 564.41: It got 28.85× slower.
Between 564.41 and 605302.266: It got 1072.45× quicker.
Between 605302.266 and 3000~: 201.77× slower.
Between 3000 and 65219: 21.74× quicker.
Or if we ignore the 600k one for the **** of it.
Between 16283.296 and 564.41: 28.85× slower.
Between 564.41 and 3000~: 5.32× quicker.
Between 3000 and 65219: 21.74× quicker.
With the largest gap being 115.55× (between 65219 and 564.41).
With it somehow consistently picking UP in speed after the initial burst.
You've already conceeded it fluctuates. But handwaved it off being minor, that shit is NOT minor my dude. Obviously I'm kind of half assing it here, but the numbers ain't that far off.
It's drastic. You can't even argue the funny physics thing because it gets quicker over time, not slower, unless you want that random spike I'm going to presume you'll argue as cinematic timing (And if not, well, my bad then), in which it literally ups and down and the highest point is insane.
Regardless, your argument, the very premise doesn't work.
Worse case scenario, we use the final speed which is ironically the quickest (Meaning all the arguments about slow down, physics, timeskips, etc, were kind of meaningless).
So, tldr.
1. Active admittance of fluctuating speeds.
2. Active admittance that the Wario scene likely isn't a time skip.
3. To use the horizon clear view speed (Would literally be sub-minute anyway?).
4. Aserting weird time cuts, handwaving of character placements, or taking a statement not at face value with no reason beyond the faulty point 1.
5. Given the admittance of speeding up clouds, and other such facets rendering several points invalid, it discredits the other points as well as they now lack corroboration.
I don't see why this should be continued any longer, But I suppose others can judge. Kinda why I even replied to begin with, less to change your stance, and more for others to weigh in.
Honestly feels like instigating to get me to start being rude but what do I know.
Besides everything. I'm never wrong ong. Give a warning when it's warranted, framing a non-justified warning as "an informal warning", is still a warning and uncalled for.
Now, to propose what I think should be done, ignoring I have but to state it again.
The only legitimate methods I can see to get around the inconsistent fluctations, is to use the final speed of about 60kms (would need to be calced better though, don't use the yap in this post it's super rough), personally I'm unsure because the statement still exists, or to just go with the obvious 27 second time frame for the whole scene as we know by the end of it it's gone because they actively make it a point to show it's gone, say it's gone, and the globe not even 10 seconds later is cleared up too.
20 minutes still isn't an averge when this is the numbers for how the speed jumps as per the above post
So I'm still not seeing where that comes from, can you show your math for that here please
