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

VS Battles Wiki Forum

Chariot190
Chariot190
I've seen it, it's inflated and wrong, put simply, I've just refrained because I didn't wanna come off as mean.
Literally just do what I said in the thread when I originally brought it up, it's the safest way. But.

Using multiple shots to calc it is kinda bad because we have no idea when and where each individual sun is in, in relation to each other, between said scenes.

The shot used to angsize on landing isn't usable, as we do not know which sun that is, that could be the sun furthest away, which in turn wanks the next panel because you could be taking the distance from the furthest sun, applying it to the closest sun, and then getting hyperinflated results, which is why I said how to do it. unless multiple suns in shot, you simply can't do it that way.

Additionally, the angsize distance to PoV in the next shot, doesn't work.
That very panel shows how wrong it is, we know, for a fact, that one such sun must be parallel with Namek, ie, directly next to or in front of it, for the day/night cycles to work. Yet, by taking the 19m km distance, well put simply the gap between Namek and said sun, or ****, any sun, should be 20 suns long visually, that, is evidently not how it's drawn, and most definitely not with the sun that's used for scaling, at best it'd a few sun gap.
But then you could say "well maybe the sun is smaller/bigger", yeah, sure, but then that'd also affect the angsize distance in turn, ultimately, no matter the case, the gap should be 20 of however big that sun is in length, it isn't, in any shot we have.

Then there's just art accuracy, assuming Akira drew the sun in the sky perfectly as per distance, when we know he's kinda bad with stuff like that (just look at moon shots from earth, they never align with the actual stated moon distance and sizes) not exactly reliable, doubly when you're taking it onto a panel drawn months later irl that physically can not corroborate the angsized distance based on how it's drawn.

I could go on, there's a lot of stuff here that nuh uh.

Literally just pick a panel, draw two lines and be done with it, it's the safest, and put simply, only way, to calc it without having like a 3D dioramic shot of the thing or jst guessing. And unless some game has that, it be what it be.
Chariot190
Chariot190
which btw, gets namek to be like, 5-7m km in diameter, **** do a high end with the spirit bomb shot if ya want, probably get like 25m km, as long as ya have the low ends too, but this way ain't it chief
TheGodOfICE777
TheGodOfICE777
Hey, thanks for letting me know what was wrong with the calc. I wouldn’t have taken any offense to it since I wanted it to be accurate as well. I think I’ve done as you’ve said now, could you tell me if there are any other errors?

Btw, I did the high end and the low end as you suggested too.
Back
Top