PhantomØ4
Username Only- 2,248
- 1,485
Heyo, so basically I noticed that a lot of the Saki K calcs currently used in the profile are rather...questionable. This has been addressed years back but the thread fell through due to interest. I also borrowed the name from a previous thread by Don'tTalk.
I would honestly suggest nulling the user's calcs verse and from making any more calculations at least regarding this verse (but I would not be surprised if their other calcs are equally as bad) as it is honestly astonishing the (at best) just how unqualified they are or (at worst) just intentional misportrayal in the feats and reliance on CGMS overlooking them.
^ These are about all of his Saiki K calcs over 2 years that are not something ridiculous and irrelevant and about all of them have at least one large major issue. I do believe that it is a combination of being unqualified and purposely misleading to attain the largest end possible and as such I do think he should stay off calculations pertaining the verse.
I did peek at 5 of his other calcs to see if it was the same for those and as far as I could tell those have a similar pattern but I do not care for them working in other verses.
I would honestly suggest nulling the user's calcs verse and from making any more calculations at least regarding this verse (but I would not be surprised if their other calcs are equally as bad) as it is honestly astonishing the (at best) just how unqualified they are or (at worst) just intentional misportrayal in the feats and reliance on CGMS overlooking them.
Saiki flies across the world.
Saiki causes an explosion
Saiki disperses a typhoon
0.0X frames per second... in an anime where animators only draw 24 frames per second usually on doubles, even in games they don't generate a fraction of a frame. This should be self explanatory. The person calcing them use SMPTE to justify 0.13 frames by totally misreading the format which is indicating hours, minutes, seconds and frame. This effectively x100s almost every single speed result reliant on frames and x10,000 the kinetic energy. Honesty find it hard to believe this was not on purpose as you have to look up what the format is to know it references frames at all.
More recently he has began misreading the format as hundredths of a second for no apparent reason at all like here:
Saiki kicks limiter into space and deflects a meteor
My best guess is that it's very much intentional as 0.01 seconds is better than 1/24ths of a second (~0.0416 seconds) or 0.16 seconds being much better than 16/24 (0.666 seconds) and his previous 0.XX frames per second raised red flags far too easily as when pressed about finding a tenth of a frame by damage they attempted to play it off by claiming "I think I expressed myself wrong, using Filmora (Video Editor) the line appeared in 0.01 seconds. Then I used that time and the fps from the anime" when he had repeatedly used the last digits as fractions of frames doing things like:
0.01 frames / 24 fps
But since they could not justify it they fell back on tenths of a second. I am saying this is intentional as he had demonstrated knowledge of what the the last two digits in SMPTE format represnted... it's also very obvious in the editing program he uses as 00 only goes up to 24 before changing the second. You'd have to be incredibly forgetful and unqualified to do calculations or be intentionally doing this to elevate results by a significant margin.
Saiki causes an explosion
Saiki disperses a typhoon
0.0X frames per second... in an anime where animators only draw 24 frames per second usually on doubles, even in games they don't generate a fraction of a frame. This should be self explanatory. The person calcing them use SMPTE to justify 0.13 frames by totally misreading the format which is indicating hours, minutes, seconds and frame. This effectively x100s almost every single speed result reliant on frames and x10,000 the kinetic energy. Honesty find it hard to believe this was not on purpose as you have to look up what the format is to know it references frames at all.
More recently he has began misreading the format as hundredths of a second for no apparent reason at all like here:
Saiki kicks limiter into space and deflects a meteor
My best guess is that it's very much intentional as 0.01 seconds is better than 1/24ths of a second (~0.0416 seconds) or 0.16 seconds being much better than 16/24 (0.666 seconds) and his previous 0.XX frames per second raised red flags far too easily as when pressed about finding a tenth of a frame by damage they attempted to play it off by claiming "I think I expressed myself wrong, using Filmora (Video Editor) the line appeared in 0.01 seconds. Then I used that time and the fps from the anime" when he had repeatedly used the last digits as fractions of frames doing things like:
0.01 frames / 24 fps
But since they could not justify it they fell back on tenths of a second. I am saying this is intentional as he had demonstrated knowledge of what the the last two digits in SMPTE format represnted... it's also very obvious in the editing program he uses as 00 only goes up to 24 before changing the second. You'd have to be incredibly forgetful and unqualified to do calculations or be intentionally doing this to elevate results by a significant margin.
Explosion of volcano
Extrapolated distress signals from Japanese warning systems taking from one to twenty seconds to reach receivers upon being sent and people still evacuating to mean the entire volume of calculated pyroclastic flow (which was calculated by treating it the same as a storm... which is also wrong) was released at once at speeds exceeding 1% the speed of light.
Presumes this is an accurate representation of the lava in a volcano exploding outwards. Completely messes up lining up the thing with the planet and proceeds with the calc anyways... and doesn't even bother in understanding how volcano eruptions work or earth is laid out as he then proceeds to take that all of this lava had to travel from edge to edge in the same timeframe as before.
This apparently is also enough for a magnitude 8 earthquake on the Richter scale.
Saiki vaporizes 7 km with a punch
Straight up doesn't even line up the measurement line with what he claims to be measuring, giving up 3/4ths of the way. Ignores the resulting crater being incredibly shallow compared to the radius he used and proceeds to treat it as a semi-cylinder.
Saiki dodges alternate Saiki
Calc staking to the horizon and back from characters to are relative to each other IN ADDITION to calculating the speed of an attack from relative characters like this: Thrown punch -> Evade -> Shockwave then destroys background -> Shockwave must have traveled that distance in the same amount of time it took dodge. He has re-posted this calc several times over 2 years indicating that he truly does not see any issue in this logic.
Typhoon dispersion
Anime canonicity aside... "Low End: 5.1884561e+15kg/0.0036s= 1.4412378e+18kg" based on effects to the mass being shown to start being visible at 0.0036? Force = m * a not Force = m / time
It also maximum elevation of a typhoon's top as the thickness of the typhoon clouds (unsourced so I had to look into what they used too) which are colombinous clouds with are generally accepted to average about half that thickness on vsbw.
As a plus the calculation completely ignored the fact that it is visually obvious the typhoon divides into several sections that have much lower speeds each as the center of the typhoon never reaches the measured distance and the clouds that do reach the measured distance are only the outer edge of the typhoon, this goes beyond the omnidirectional kinetic energy formula.
Saki does standard cloud dispersion
"Thunderstorm mass= 167,702,794,067.00543 kg 167,702,794,067.00543*1,003kg= 1.682059e+14 kg" You cannot be fr right now. The calculation multiplied the mass of the clouds by the density of water to get the mass of the clouds. In addition to that the feat was added by him unto the profile without any CGM approving it.
Saiki K meteor ending and its original version
Measures the luminosity given off by the meteor from an aesthetic shit as if it was meteor itself... conveniently cherry picking shots to get the highest result as the meteor would basically already be impacting planet earth but then they use ang sizing in the space shot to find that the meteor (with an in verse estimated impact time of 2 hours from that point) is actually moving at 1 million meters per second.
Saiki kicks his limiter into space
The timeframe issue aside the assumptions this calc makes are also weird as they assume that the object traveled the total measured distance in the time it took for the object to be out of sight... in addition to matter that if the object is burning up in the atmosphere the perspective of the calc is likely just skewed and it is within the atmosphere and unfit for angular methods.
Saiki K defelcts a metor
It seems they'll just try their luck at what gets past CGMS because they are doing the long way round to directly measure the meteor which is much closer to the camera than the earth using the earth in a non-straightforward way by using angular size. Then suddenly they pull a km/px ratio out of nowhere for the panel height "Panel Height 720px= 31839.4191449m/px" to apply to distance not explaining they actually used the earth as frame of reference for the distance moved no different from using the earth and getting m/px from there... just hidden behind unnecessary methodology.
Saiki K destroys the moon 1
Here they don't explain the shot is actually a still frame and say "it took a second due to the dynamics of the scene", again hoping a CGM that doesn't care enough will come by and approve the arithmetic. They multiply Saki's traveled distance in that one second... just because basically? The reasoning is that Saki's travel path went beyond the moon which at best refers to his his aura which extends a couple of meters behind saki as it is very clear. Anyways, all these issues only to get Saki's travel speed which he then applies to the mass of the missing chunk of the moon (which is also calculated wrong as a whole left in the moon is not a sphere) to get the kinetic energy as if Saki had launched that whole chunk of the moon at that same speed which is visually untrue in the shown frame and the chunks we do see seem to just be small fragments of the moon close to Saki.
Saiki destroys the moon 2 and 3
Does the same timeframe trick here, though this one might be his tamest calc but still calculates a hole in the moon as a spherical object which is wrong.
Saiki erases a country
Calculates a very self evidently small explosion as country level because Saiki calls them a " "nation" " INCLUDING THE PARENTHESIS. This is currently part of the justification in the profile...
Saiki K splits the earth
F = W/s ? From where exactly?
3DS Explosion feat
0.0X frames issue. Also calculates the yield of an explosion on a curved surface based on a flat reference which results in inflated results as the reference gets elongated as it gets further way from the equator. Google earthing point to point yields about 5,000 km instead (~Manilla to the Russian peninsula). Additionally the thing being measured for the explosion formula is no longer is the explosion itself but rocks being raised from the earth's surface that do not even follow the sphere-like are of an explosion that are used as a reference
Kusuke gets yeeted into a wall
Assumed pulverization of steel for a feat very clearly containing 0 pulverization, specially using the large AoE he measured which at best shows fragmentation values... depth value for the crater is simply an unfounded a reach.
Saiki K calls down a meteor
Uses earth curvature line up that makes Hokkaido be larger than California in addition to using the earth as reference to a meteor that is much closer to the camera, resulting in a meteor that is a meter across as seen in the anime to be the size of a small country. This is despite Don't Talk previously advising him against him measuring foreground elements with background ones (and every feat where he has done this is post this comment)
Saiki K flies to America
Uses blatant cinematic timing instead of visual showing of the feat in addition to having the SMPTE format.
Extrapolated distress signals from Japanese warning systems taking from one to twenty seconds to reach receivers upon being sent and people still evacuating to mean the entire volume of calculated pyroclastic flow (which was calculated by treating it the same as a storm... which is also wrong) was released at once at speeds exceeding 1% the speed of light.
Presumes this is an accurate representation of the lava in a volcano exploding outwards. Completely messes up lining up the thing with the planet and proceeds with the calc anyways... and doesn't even bother in understanding how volcano eruptions work or earth is laid out as he then proceeds to take that all of this lava had to travel from edge to edge in the same timeframe as before.
This apparently is also enough for a magnitude 8 earthquake on the Richter scale.
Saiki vaporizes 7 km with a punch
Straight up doesn't even line up the measurement line with what he claims to be measuring, giving up 3/4ths of the way. Ignores the resulting crater being incredibly shallow compared to the radius he used and proceeds to treat it as a semi-cylinder.
Saiki dodges alternate Saiki
Calc staking to the horizon and back from characters to are relative to each other IN ADDITION to calculating the speed of an attack from relative characters like this: Thrown punch -> Evade -> Shockwave then destroys background -> Shockwave must have traveled that distance in the same amount of time it took dodge. He has re-posted this calc several times over 2 years indicating that he truly does not see any issue in this logic.
Typhoon dispersion
Anime canonicity aside... "Low End: 5.1884561e+15kg/0.0036s= 1.4412378e+18kg" based on effects to the mass being shown to start being visible at 0.0036? Force = m * a not Force = m / time
It also maximum elevation of a typhoon's top as the thickness of the typhoon clouds (unsourced so I had to look into what they used too) which are colombinous clouds with are generally accepted to average about half that thickness on vsbw.
As a plus the calculation completely ignored the fact that it is visually obvious the typhoon divides into several sections that have much lower speeds each as the center of the typhoon never reaches the measured distance and the clouds that do reach the measured distance are only the outer edge of the typhoon, this goes beyond the omnidirectional kinetic energy formula.
Saki does standard cloud dispersion
"Thunderstorm mass= 167,702,794,067.00543 kg 167,702,794,067.00543*1,003kg= 1.682059e+14 kg" You cannot be fr right now. The calculation multiplied the mass of the clouds by the density of water to get the mass of the clouds. In addition to that the feat was added by him unto the profile without any CGM approving it.
Saiki K meteor ending and its original version
Measures the luminosity given off by the meteor from an aesthetic shit as if it was meteor itself... conveniently cherry picking shots to get the highest result as the meteor would basically already be impacting planet earth but then they use ang sizing in the space shot to find that the meteor (with an in verse estimated impact time of 2 hours from that point) is actually moving at 1 million meters per second.
Saiki kicks his limiter into space
The timeframe issue aside the assumptions this calc makes are also weird as they assume that the object traveled the total measured distance in the time it took for the object to be out of sight... in addition to matter that if the object is burning up in the atmosphere the perspective of the calc is likely just skewed and it is within the atmosphere and unfit for angular methods.
Saiki K defelcts a metor
It seems they'll just try their luck at what gets past CGMS because they are doing the long way round to directly measure the meteor which is much closer to the camera than the earth using the earth in a non-straightforward way by using angular size. Then suddenly they pull a km/px ratio out of nowhere for the panel height "Panel Height 720px= 31839.4191449m/px" to apply to distance not explaining they actually used the earth as frame of reference for the distance moved no different from using the earth and getting m/px from there... just hidden behind unnecessary methodology.
Saiki K destroys the moon 1
Here they don't explain the shot is actually a still frame and say "it took a second due to the dynamics of the scene", again hoping a CGM that doesn't care enough will come by and approve the arithmetic. They multiply Saki's traveled distance in that one second... just because basically? The reasoning is that Saki's travel path went beyond the moon which at best refers to his his aura which extends a couple of meters behind saki as it is very clear. Anyways, all these issues only to get Saki's travel speed which he then applies to the mass of the missing chunk of the moon (which is also calculated wrong as a whole left in the moon is not a sphere) to get the kinetic energy as if Saki had launched that whole chunk of the moon at that same speed which is visually untrue in the shown frame and the chunks we do see seem to just be small fragments of the moon close to Saki.
Saiki destroys the moon 2 and 3
Does the same timeframe trick here, though this one might be his tamest calc but still calculates a hole in the moon as a spherical object which is wrong.
Saiki erases a country
Calculates a very self evidently small explosion as country level because Saiki calls them a " "nation" " INCLUDING THE PARENTHESIS. This is currently part of the justification in the profile...
Saiki K splits the earth
F = W/s ? From where exactly?
3DS Explosion feat
0.0X frames issue. Also calculates the yield of an explosion on a curved surface based on a flat reference which results in inflated results as the reference gets elongated as it gets further way from the equator. Google earthing point to point yields about 5,000 km instead (~Manilla to the Russian peninsula). Additionally the thing being measured for the explosion formula is no longer is the explosion itself but rocks being raised from the earth's surface that do not even follow the sphere-like are of an explosion that are used as a reference
Kusuke gets yeeted into a wall
Assumed pulverization of steel for a feat very clearly containing 0 pulverization, specially using the large AoE he measured which at best shows fragmentation values... depth value for the crater is simply an unfounded a reach.
Saiki K calls down a meteor
Uses earth curvature line up that makes Hokkaido be larger than California in addition to using the earth as reference to a meteor that is much closer to the camera, resulting in a meteor that is a meter across as seen in the anime to be the size of a small country. This is despite Don't Talk previously advising him against him measuring foreground elements with background ones (and every feat where he has done this is post this comment)
Saiki K flies to America
Uses blatant cinematic timing instead of visual showing of the feat in addition to having the SMPTE format.
^ These are about all of his Saiki K calcs over 2 years that are not something ridiculous and irrelevant and about all of them have at least one large major issue. I do believe that it is a combination of being unqualified and purposely misleading to attain the largest end possible and as such I do think he should stay off calculations pertaining the verse.
I did peek at 5 of his other calcs to see if it was the same for those and as far as I could tell those have a similar pattern but I do not care for them working in other verses.
Last edited:
