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

Possible issues with Asta's Doom's gate calculation

Status
Not open for further replies.
Messages
7,056
Reaction score
5,561
The current Doom's gate calculation has some flaws which I think should be addressed

Issue 1​

In Floxy's Thread we determined ang sizing shots of things in space is inconsistent and gives inaccurate results, especially applying for this case as both BC and Bleach were done by the same studio. These shots are usually made for dramatic effects and style rather than to showcase the actual size of an object. We can notice a trend from these calculations is that in ang sizing, using diameter to gauge distance from pov results in a value orders of magnitude less than what the true size would be (deflation basically), so if we flipt the script like in the BC calc which does the opposite (using distance from POV to find diameter) the reverse ends up happening and instead of deflation we are met with an inflated value far beyond what it should logically be.

As such I believe using ang sizing to find the size of an object is generally too inconsistent to be used.

Issue 2​

The calculated diameter is around 160 km but up close the value is completely contradicted, we can tell just by looking that this is nowhere near 100 km due to how comparable and visible asta is to the meteor (this link will take you to the actual 2 minute scene of him cutting the large rock). When pixel scaled the result actually comes out as little as a little over 100 meters. Now this might be dismissed to be a case where a character is only visible for the watcher so we know where the character is, rather than to show the size of an object but I don't believe this is the case here. Unlike situations like those where the argument would actually be invalid, here Asta (or rather his swords and wings) is VERY large, nowhere near the small speck that he should be if they just wanted to show his location. One might also defend it saying it is a perspective shot but that is not the case because with perspective shots things of the same size extending away from the POV shrink in pixel count. And we see Astas sword remains essentially identical throughout so we can safely say the visible size isn't messed up by perspective.

This leads me to believe this scene should very much work as a good representation of the meteors size, making it over 1000x smaller than what the angsizing end suggests. It's more direct and uses a more reliable method for measurement than what the current calc does.

Conclusion​

We already consider pixel scaling as preferable and more accurate than angsizing. Given that the angsizing method in question is an extraordinarily inconsistent one which has recently been rejected, and the fact that straight forward pixel scaling HEAVILY contradicts it, I believe the calculation should be deemed unusable.

For replacement we can just use this calculation for the destruction of the clover kingdom, as the meteor was said to be capable of doing so. That is unless the supporters find a better alternative for replacement
 
I mean we already accept that ang sizing from things in space is already inconsistent but if that's weaponized to inflate the sizes on top of being contradictory to pixelscaling then yeah it should go

Most animators don't really draw these things with accurate perspective scaling anyway, they just put out what seems cool without being overly contradictory at a first glance so I honestly agree
 
My stance is the same as in the previous thread about this type of pixel scaling. In that the size of celestial bodies are often portrayed in an inconsistent way by animators and manga artists. This method of scaling is also notorious for its inflated values, supporting higher end assumptions and frankly seems to be weaponized as a means of justifying higher end metas that would otherwise fall short.

Lastly, I find that David has done a wonderful job outlining why this cal is wrong via the assertion of using celestial bodies to calculate the size of other objects, but also using inconsistent sizes shown throughout the series to justify this notion.

I agree with this thread
 
Last edited:
Deku bout to slay Asta with this one
Asta would be still 200 exatons more of less if we use all the multipliers in the verse page and the verse is still waiting for the manga to end

For the rest of the thread, do as you please, we can pile this up with the "lightspeed cap" and after the ending, solved everything
 
Asta would be still 200 exatons more of less if we use all the multipliers in the verse page and the verse is still waiting for the manga to end
That’ll be with zetten though, so he’ll be at 20x physically weaker or thereabout which makes him a gearshift victim

All in all, to avoid derailing any further, the thread seems quite reasonable and well grounded.
 
Um yeah, hard disagree. That current calc at minumim should remain in tact. That "close up" shot of that 2 minute scene is most certainly meant to make the character visible to the audience given how its large inconsistent with the narrative and other meteor shots.

The image and calc that's currently used scaling is more aligned and consistent with the narrative and intent considering in the text from novelization, explicitly stated that the meteor was so large that it could be seen from anywhere in the country, which is damn near impossible if that meteor was "a little 100 meters"
 
Last edited:
Um yeah, hard disagree. That current calc at minumim should remain in tact. That "close up" shot of that 2 minute scene is most certainly meant to make the character visible to the audience given how its large inconsistent with the narrative and other meteor shots.

The image and calc that's currently used scaling is more aligned and consistent with the narrative and intent considering in the text from novelization, explicitly stated that the meteor was so large that it could be seen from anywhere in the country, which is damn impossible if that meteor was "a little 100 meters"
I forgot about the novel not gonna lie



Good point that with the novel is not only about spectacle shenanigans
 
Um yeah, hard disagree. That current calc at minumim should remain in tact. That "close up" shot of that 2 minute scene is most certainly meant to make the character visible to the audience given how its large inconsistent with the narrative and other meteor shots.
Can you actually address the arguments I listed for why that's not the case? Because simply going "nuh uh" really isn't helping neither of us.
The image and calc that's currently used scaling is more aligned and consistent with the narrative and intent considering in the text from novelization, explicitly stated that the meteor was so large that it could be seen from anywhere in the country,
Being visible anywhere from the country doesn't mean it has to be over hundred kilometers.
which is damn near impossible if that meteor was "a little 100 meters"
Is it? Is there any calculation that dictates this? Especially given it's literally shining due to being on fire.
Also that aside, all this would mean is both methods are vaguely inaccurate. But the pixel calc method would still remain vastly more accurate due to everything mentioned in the thread.

So at best you're proving this is unquantifiable which is fine given I wasn't planning to quantify the feat anyway, and at worst you're not really doing anything
 
I made a translation on the raws provided here and no where did it say anything about “been seen from anywhere in the country”. Assuming that is, infact, the full japanese text we can probably ask the TL team for further clarification.
…W-what!?”





Blinded by the overwhelming brilliance of the scene, Asta lost his words. As the fierce winds raged, the breath was knocked out of him, and he fell into the midst of it.





Even so—unyielding as ever—Asta refused to give up, struggling desperately against the storm.





“I won’t give up… I’ll never give up… Asta…!”





Uttering the same words he had said before, Conrad rose toward the gate as he spoke.





At that moment, a massive slab of rock appeared from within the gate.


Then, as the slab ascended higher and higher, a pitch-black hole opened at its center


and from within, a face began to emerge
Not like it really changes much considering the original context didn’t really affect the OP’s premise
 
I made a translation on the raws provided here and no where did it say anything about “been seen from anywhere in the country”. Assuming that is, infact, the full japanese text we can probably ask the TL team for further clarification.

Not like it really changes much considering the original context didn’t really affect the OP’s premise
I picked the wrong link, that was from the page before. This is the correct text. I also updated by original post with the correct link.

So here is:

Part 1 of the scenes novelization

Part 2 of the scenes novelization

 
Last edited:
it doesnt really say the size of the meteor here, unless i missed it
Yeah it doesn't but given the meteor that wiped out the dinosaurs was only around 10-15km in diameter I highly doubt a randomass meteor reached anywhere near 160 km.

Tho I never really explored the visibility of an object like that so if anyone has any evidence stating how big a meteor has to be to be seen across such distance I'm open to anything.
 
Why are we using the novel when the source material is the movie?

For animanga movies, novelisations aren’t the primary canon, they’re made after the movie by people that aren’t even the author, if it’s contradicted by the primary canon showing it to be way smaller obviously it cannot be used

And no one attempted to defend the blatant size inflation that ang sizing does (independent of the pixelscaling) so I really don’t see why people are claiming it should stay
 
Angsizing consistently gets the most jarring results. The directors don't care for a consistent size across an entire movie or anime. Better yet story boards actively do the opposite. In order to convey the series in new and refreshing ways. No director worth their salt gives you the exact same aerial shot twice.

Throw the calc out even guessing how big it is based on how you feel is better.
 
With this logic we can just remove 89% of our wiki calcs lol
Tbh not really, if gaining distance from size gives values that are less than what they should be, they can be used as long as it's acknowledged that they're lowballed and the true power/speed of characters is prolly higher, it kinda works so it's allowed in cases where there aren't much contradictions.
 
I agree with point n1 only if we are talking about things that are so incredibly distant, such as celestial bodies. Honestly, it is ambiguous that a thread had to be created to demonstrate that this generated nonsensical calculations.

For this kind of thing, I believe there should be a strict and clear standard because no sequence of scenes is consistent in terms of dimensions and distances. Finding contradictions is quite simple, as it is often something that is not designed to have a certain type of consistency.
 
I agree with point n1 only if we are talking about things that are so incredibly distant, such as celestial bodies. Honestly, it is ambiguous that a thread had to be created to demonstrate that this generated nonsensical calculations.

For this kind of thing, I believe there should be a strict and clear standard because no sequence of scenes is consistent in terms of dimensions and distances. Finding contradictions is quite simple, as it is often something that is not designed to have a certain type of consistency.
Shouldn't even need to have a thread to be reinforced if we're being honest like unless you have some sort of stated distance its just that you shouldn't be picking some random arbitrary distance to just throw in a calc to use anyways especially for something like this when the perspective used isn't one that shouldn't be taken for use in calcs due to the obvious inconsistencies
 
The current Doom's gate calculation has some flaws which I think should be addressed

Issue 1​

In Floxy's Thread we determined ang sizing shots of things in space is inconsistent and gives inaccurate results, especially applying for this case as both BC and Bleach were done by the same studio. These shots are usually made for dramatic effects and style rather than to showcase the actual size of an object. We can notice a trend from these calculations is that in ang sizing, using diameter to gauge distance from pov results in a value orders of magnitude less than what the true size would be (deflation basically), so if we flipt the script like in the BC calc which does the opposite (using distance from POV to find diameter) the reverse ends up happening and instead of deflation we are met with an inflated value far beyond what it should logically be.

As such I believe using ang sizing to find the size of an object is generally too inconsistent to be used.

There is a glaring issue I have with this approach of yours. The Bleach example doesn’t even seem comparable to Black Clover's scenario The issue is you’re treating Doom's Gate like the moon, rather than a giant object that’s muchhhhhh closer and smaller and affecting the narrative, like the meteor that was going to destroy the Seireitei.

The moon is roughly 384,400 km from the earth with a diameter of roughly 3,474 km, while the Dooms Gate meteorite is roughly 100-160 km, that’s a 3,844x difference in distance and over a 20x difference in size. Obviously trying to ang size an object like the moon, or another celestial object like planet or sun that has relatively fixed distances and sizes would lead to far more inflated results because of how far away they are. Those celestial objects already have fixed sizes and distance so whatever calc you use will be inflated regardless. This is why it’s better to choose the distance or size that aligns most with the narrative. The moon and the Dooms Gate have vastly differences distances and sizes and serve completely different purposes. The Bleach scenes you used in your example simply uses the moon and sun as a celestial objects that are large enough to be viewed in background, not some object that’s actually going to crash into the planet and affect the narrative.

Issue 2​

The calculated diameter is around 160 km but up close the value is completely contradicted, we can tell just by looking that this is nowhere near 100 km due to how comparable and visible asta is to the meteor (this link will take you to the actual 2 minute scene of him cutting the large rock). When pixel scaled the result actually comes out as little as a little over 100 meters. Now this might be dismissed to be a case where a character is only visible for the watcher so we know where the character is, rather than to show the size of an object but I don't believe this is the case here.
You used possibly the worst, and most inconsistent scene for sizing. What you're suggesting above is narratively inconsistent. Conrad was essentially on his last crumbs of life and at his wits end. Furthermore his intention was to use Dooms Gate to destroy to not just the country, but the world itself before his life ended since he sacrificed the rest of his life span to activate it, which he says himself:この命尽きる前に、この国を、この世界を、救わねばならない…
"Before this life ends, I must save this country, this world..."

At the minimum that’s roughly in the ballpark of the current Dooms Gate calculation that's accepted (594.1 petatons) and similar to the accepted commons feats for surficial destruction that's accepted referenced on this site (646.57 petatons) so narratively it’s consistent. A meteorite with the diameter of 140 meters has the impact energy of approximately 100 megatons, which can be found here. I highly doubt Conrad's intention was to summon something so tiny with such little impact given how his intention was to cleans the planet. Even in early BC it was stated Yami and Jack allegedly shaved down a mountain in a casual scuffle, so what you’re suggesting is narratively inconsistent.

Unlike situations like those where the argument would actually be invalid, here Asta (or rather his swords and wings) is VERY large, nowhere near the small speck that he should be if they just wanted to show his location. One might also defend it saying it is a perspective shot but that is not the case because with perspective shots things of the same size extending away from the POV shrink in pixel count. And we see Astas sword remains essentially identical throughout so we can safely say the visible size isn't messed up by perspective.

This leads me to believe this scene should very much work as a good representation of the meteors size, making it over 1000x smaller than what the angsizing end suggests. It's more direct and uses a more reliable method for measurement than what the current calc does.

Conrad and Asta were fighting ontop of the demon-skull, so Doom' Gate was summoned right above that location in the exosphere (which the light novel AND movie supports), and at the edge of the country. The demon bones is the very first relevant depiction we see of its scale and it literally turns the whole sky red in the country red and, and the scene of the meteor ablating above said bones is the most consistent shot, since it was shown multiple times at different points in the story. Edward froze the entire Yultim volcanic belt, which is in the strong magic region, and even THAT space was illuminated red. The scene is using a landmark aka the demon bones-skull to convey it’s size and essentially tell us that this object that was summoned at the edge of the country, high in the exosphere, is so large that it's extremely visible everywhere in the country and is substantially affecting atmosphere.

That “2 minute” scene you picked out as I said earlier is the most inconsistent shot in the entire movie. It's simply meant to capture the action in one scene and show us where Asta actually is and what he's doing. It’s literally too difficult and impossible to portray Asta and the entire meteorite in the same frame with detail at their true sizes. I don’t think we’re going to sit here and pretend that damn near every anime doesn’t have some inconsistencies here and there when it comes to some scenes with ginormous objects, so I find it odd that we're piggy backing off of one inconsistent scene to completely ignore the narrative.

In addition, why are we skipping the ONLY scene we have of Asta and meteorite being truly parallel together/ within the same plane of geometry? That scene doesn't utilize any weird angles like the one you put forth and it depicts his body, and the two giant swords stabbed in the meteor as a stream of anti-magic and a cluster of light, with no distinguishable distance or features, whatsoever. The giant swords of magic and anti-magic that he generated are too small to be depicted. Even if they were 1 km long, it would still be too small to distinguish.

Doom-Gate-Cluster.jpg


I overlaid the image with the size of Asta from that "2 minute scene” you supplied with the image of Asta and the meteor parallel to one another in relation to the meteor and the size difference is vast. You can’t even Asta's body yet alone any distinguishable features like his giant swords so why you specifically chose that ONE scene is beyond me.

With that being said, the VERY first scene that revealed the size of Dooms Gate's door, is relative to the other scenes that was used for the accepted calc.

When the meteorite first emerges, we see it's size relative to the demon-bones as it begins to ablate. Later, that exact same scale, and scene is used to depict Asta interacting with the meteorite as he plunges giant Demon-Slayer and giant Elsdocia into. In that scene Asta and his weapons are displayed as a giant cluster of light and anti-magic in the exosphere and this is consistent with the same scene that depicted them as clusters of light and darkness when they were parallel to the meteorite. That same scene of the demon bones is repeated multiple times, unlike the others. You chose the most inconsistent scene and used it as a way to tremendously deflate the calc and ignored every other instance that essentially that views Asta as indistinguishable. We're only ever shown Asta's distinguishable features when it's literally just him and the meteor. The scene with the demon-skull has the most consistency and isn't used just "once" it's actually a pretty pivotal frame of reference. Lastly, the debris from meteor’s destruction in exosphere can visibly be seen from the planet’s surface below. That same destruction is vast enough to illuminate a large portion of the night sky despite the fact it’s in the exosphere.

dgate-0.jpg


dgate-1.jpg

dgate-2-5.jpg

dgate-4.jpg




Conclusion​

We already consider pixel scaling as preferable and more accurate than angsizing. Given that the angsizing method in question is an extraordinarily inconsistent one which has recently been rejected, and the fact that straight forward pixel scaling HEAVILY contradicts it, I believe the calculation should be deemed unusable.

For replacement we can just use this calculation for the destruction of the clover kingdom, as the meteor was said to be capable of doing so. That is unless the supporters find a better alternative for replacement

I think the calc should certainly stay since:

1.) It’s value is consistent with Conrad wanting to destroy the world and aligned with the accepted common feat on this site for doing so.

2.) All portrayals of the meteor in comparison to the verses landmarks is consistent, and shows no distinguishable features of the human sized characters that interacts with it.

3.) The most repeated AND consistent scene that uses relevant landmarks (demon-bones) all share the same consistency. Again this scene from space is relatively consistent with this scene from the ground which serves a consistent frame of reference is also supported by the narrative.

DG-Comparison.jpg
 
Last edited:
Tbh not really, if gaining distance from size gives values that are less than what they should be, they can be used as long as it's acknowledged that they're lowballed and the true power/speed of characters is prolly higher, it kinda works so it's allowed in cases where there aren't much contradictions.
I was talking about the part where Snakes said that the best option is to remove the calc completly since it's inconsistent lol
 
There is a glaring issue I have with this approach of yours. The Bleach example doesn’t even seem comparable to Black Clover's scenario The issue is you’re treating Doom's Gate like the moon, rather than a giant object that’s muchhhhhh closer and smaller and affecting the narrative, like the meteor that was going to destroy the Seireitei.

The moon is roughly 384,400 km from the earth with a diameter of roughly 3,474 km, while the Dooms Gate meteorite is roughly 100-160 km, that’s a 3,844x difference in distance and over a 20x difference in size. Obviously trying to ang size an object like the moon, or another celestial object like planet or sun that has relatively fixed distances and sizes would lead to far more inflated results because of how far away they are. Those celestial objects already have fixed sizes and distance so whatever calc you use will be inflated regardless. This is why it’s better to choose the distance or size that aligns most with the narrative. The moon and the Dooms Gate have vastly differences distances and sizes and serve completely different purposes. The Bleach scenes you used in your example simply uses the moon and sun as a celestial objects that are large enough to be viewed in background, not some object that’s actually going to crash into the planet and affect the narrative.
The values don't have to be the same for the issue to be the same.

The core problem is that animators and artists usually don't take these distances, whether it's the height of the atmosphere or the distance from the moon, instead inflating sizes for dramatic and stylistic effects. And THAT then creates inconsistencies such as this.

So saying "it's much smaller than the moon" doesn't save it from suffering from the exact same problem.
You used possibly the worst, and most inconsistent scene for sizing.
I used the scene that gives us THE most direct size comparison for the meteor and even explained why that is the case.
What you're suggesting above is narratively inconsistent. Conrad was essentially on his last crumbs of life and at his wits end. Furthermore his intention was to use Dooms Gate to destroy to not just the country, but the world itself before his life ended since he sacrificed the rest of his life span to activate it, which he says himself:この命尽きる前に、この国を、この世界を、救わねばならない…
"Before this life ends, I must save this country, this world..."
First of all, your constant use of untranslated novel over the source material is heavily questionable both due to the uncertain canonicity and a lack of a proper translation. So please first clear that up.

Second of all, the word "world" famously has a lot of definitions most of which don't really help here. World can straight up just refer to a specific region, society, or just inhabitants of earth. Which is pretty detrimental as even a kilometer around 1 kilometer in diameter can cause an extinction event.

So the statement itself could have a lot of different meanings all of which would be comparably valid, leaving us no reason to assume it's straight up surface wiping.
That's assuming he's surface wiping which we can't prove. I mean the simple fact we don't use thy 646 petatons value inherently tells us that we don't consider the meteor to be a surface wiper.

Furthermore, even if we did assume that, the 646 petaton value is made strictly using our real world's values while BCs earth has a vastly different geography. So even if we were to take the most generous route it still wouldn't mean we can use that value for reference.
A meteorite with the diameter of 140 meters has the impact energy of approximately 100 megatons, which can be found here. I highly doubt Conrad's intention was to summon something so tiny with such little impact given how his intention was to cleans the planet. Even in early BC it was stated Yami and Jack allegedly shaved down a mountain in a casual scuffle, so what you’re suggesting is narratively inconsistent.
3 problems with this.

1. I already addressed this. I'm not suggesting the meteor caps at 100 megatons, but that the size is inconsistent and the angsized value can't be used as a result. So at best you're not actually addressing any arguments here while at worst you're further supporting my claim by pointing out how the calculated values are completely off.


2. That aside this line of thinking just outright doesn't work because it assumes our values are perfect when many of them are just standard assumptions and measurements. The meteor could be far denser than just basic average meteors and it could be flying far faster than the calculated 17474.31 m/s which would all make up for the difference in values. Hell we don't even know what speed the 100 megaton value from your link used.
I mean generally speaking 90% of meteors completely vaporize before even hitting earth while this one doesn't even seem to be getting smaller which on its own implies it's more durable and likely denser than a standard meteor.

3. It could just not be applicable for calculations. For example, we wouldn't say a human moving at relativistic+ speed only having 7-A kinetic energy makes the calc from because they're stated to have star level AP. We would just say that rel+ speed isn't usable to scale their AP. Meaning the results of a calculation can be VASTLY below the "narratively intended" destruction. However that does NOT mean we should use inaccurate measurements to force a calculation into meeting our expectations.
Conrad and Asta were fighting ontop of the demon-skull, so Doom' Gate was summoned right above that location in the exosphere (which the light novel AND movie supports), and at the edge of the country. The demon bones is the very first relevant depiction we see of its scale and it literally turns the whole sky red in the country red and, and the scene of the meteor ablating above said bones is the most consistent shot, since it was shown multiple times at different points in the story.
It lighting up the sky fits exactly the idea of it being drawn bigger for dramatic purposes. This line just repeats what's already been addressed.
That “2 minute” scene you picked out as I said earlier is the most inconsistent shot in the entire movie. It's simply meant to capture the action in one scene and show us where Asta actually is and what he's doing. It’s literally too difficult and impossible to portray Asta and the entire meteorite in the same frame with detail at their true sizes.
Like I said before it's the only actual scene that gives us a direct size comparison. You saying this scene is inconsistent is no different from me saying the angsizing is inconsistent. The only difference is that pixel scaling is way more reliable than angsizing.

And it's not "impossible" to portray Asta and the meteor in the same frame while staying true to their sizes.
In addition, why are we skipping the ONLY scene we have of Asta and meteorite being truly parallel together/ within the same plane of geometry? That scene doesn't utilize any weird angles like the one you put forth and it depicts his body, and the two giant swords stabbed in the meteor as a stream of anti-magic and a cluster of light, with no distinguishable distance or features, whatsoever. The giant swords of magic and anti-magic that he generated are too small to be depicted
Because there's a giant glare of light completely covering Asta and his giant swords are stuck inside of the meteor.

The only thing we can truly distinguish there to use for reference is the width of the anti magic trail. Which is actually detrimental because unless the trail coming off of Astas body is for absolutely unknown reasons several hundred times wider than Asta himself and his anti magic sword, the shot would still make meteor would still be nowhere near even 1 kilometer.
I overlaid the image with the size of Asta from that "2 minute scene” you supplied with the image of Asta and the meteor parallel to one another in relation to the meteor and the size difference is vast. You can’t even Asta's body yet alone any distinguishable features like his giant swords so why you specifically chose that ONE scene is beyond me.
Actually this shows the trap behind Asta which shouldn't be much wider than his body and swords is comparable in width to the swords. Hell I'd say it's almost identical in width.

So under the assumption the width of the trail behind asta is comparable to the width of Astas body, this actually completely supports the 100 meter size…

Meanwhile Asta himself but being visible is against, completely fine because he's covered in a giant glare of light from the top and in the anti magic train from the bottom. So this argument actually just solidifies the OP.
I think the calc should certainly stay since:

It’s value is consistent with Conrad wanting to destroy the world and aligned with the accepted common feat on this site for doing so.
Even if I were to steelman this and say Conrad wants to surface wipe, that wouldn't justify the use of calculation with an invalid measurement method. Like I pointed out already, we can't justify using incorrect calculations by them fitting our expectations.
3.) The most repeated and consistent scene that uses relevant landmark all share the same consistency. whatsoever. Again this scene from space is relatively consistent with this scene from the ground which serves a consistent frame of reference, which is also supported by the narrative.
Both of these scenes show Asta completely covered by light and therefore invisible. However even if that wasn't the case, that would only mean the meteor size is inconsistent and wouldn't justify using the angsized size.
 
The current Doom's gate calculation has some flaws which I think should be addressed

Issue 1​

In Floxy's Thread we determined ang sizing shots of things in space is inconsistent and gives inaccurate results, especially applying for this case as both BC and Bleach were done by the same studio. These shots are usually made for dramatic effects and style rather than to showcase the actual size of an object. We can notice a trend from these calculations is that in ang sizing, using diameter to gauge distance from pov results in a value orders of magnitude less than what the true size would be (deflation basically), so if we flipt the script like in the BC calc which does the opposite (using distance from POV to find diameter) the reverse ends up happening and instead of deflation we are met with an inflated value far beyond what it should logically be.

As such I believe using ang sizing to find the size of an object is generally too inconsistent to be used.

Issue 2​

The calculated diameter is around 160 km but up close the value is completely contradicted, we can tell just by looking that this is nowhere near 100 km due to how comparable and visible asta is to the meteor (this link will take you to the actual 2 minute scene of him cutting the large rock). When pixel scaled the result actually comes out as little as a little over 100 meters. Now this might be dismissed to be a case where a character is only visible for the watcher so we know where the character is, rather than to show the size of an object but I don't believe this is the case here. Unlike situations like those where the argument would actually be invalid, here Asta (or rather his swords and wings) is VERY large, nowhere near the small speck that he should be if they just wanted to show his location. One might also defend it saying it is a perspective shot but that is not the case because with perspective shots things of the same size extending away from the POV shrink in pixel count. And we see Astas sword remains essentially identical throughout so we can safely say the visible size isn't messed up by perspective.

This leads me to believe this scene should very much work as a good representation of the meteors size, making it over 1000x smaller than what the angsizing end suggests. It's more direct and uses a more reliable method for measurement than what the current calc does.

Conclusion​

We already consider pixel scaling as preferable and more accurate than angsizing. Given that the angsizing method in question is an extraordinarily inconsistent one which has recently been rejected, and the fact that straight forward pixel scaling HEAVILY contradicts it, I believe the calculation should be deemed unusable.

For replacement we can just use this calculation for the destruction of the clover kingdom, as the meteor was said to be capable of doing so. That is unless the supporters find a better alternative for replacement
That doesn't make sense; your suggestion is to ignore the consistency of the other scenes in favor of one with a better pixel scale.
 
Status
Not open for further replies.
Back
Top