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

Chapter 156 Content Revision and Speed Upgrade

The diameter of the hole was measured with a horizontal line, so there is no problem there.
I'm talking about the oblique lines of the light design. I definitely have no desire to go all the way to 1300 lines and re-enter the calculator. I don't find this to be my fault as I used the data photoshop gave me, but I can multiply the result by 1.3 if necessary, though I don't think the 30% difference will make a difference when we already have FTL
 
I've been using Photoshop for years. Will the result really be better?
Well at least paint.net gives out the full pixel length values properly even for diagonal lines. I personally haven't had issues using it.

Fair warning tho, if you wanna make curves, 4 points is the limit, can't make more points to make more intricate curves.
 
The diameter of the hole was measured with a horizontal line, so there is no problem there.
I'm talking about the oblique lines of the light design. I definitely have no desire to go all the way to 1300 lines and re-enter the calculator. I don't find this to be my fault as I used the data photoshop gave me, but I can multiply the result by 1.3 if necessary, though I don't think the 30% difference will make a difference when we already have FTL
It’ll make quite the difference for vsbw debaters…
 
In fact, counting the power of fictional characters by pixels, trying to use physics, when often the author did not even think about it, is my strangest hobby.
I feel like Murata is the exception, and he is at least somewhat aware of the scale of his characters.

Makes Saitama reflect a surface-wiping attack

It's actually MC

Makes Garou blitz FF

Actually FTL
Just imagine how your brother/girlfriend/mother sees you at this process and asks, "Hey, buddy, what are you doing for more than an hour?". And you answer, "I count how many ******* meters Garou overcame to find out how many speeds of light he has, so that ultimately in the battles on this wiki, users equate speed."
Hey, hey-... Some people use this data to do unequalized matches that often go "X character speedblitzes and kills"
 
Because there's an entire other dimension of space missing.

If the structure was seen at the edge of the circumference of Earth, then it would be acceptable, but we're seeing it from a 3D angle. Using a 2D scaling, without the presence of any angle at all and applying to this is completely wrong and will inflate the size of the structure by a significant amount.
 
Because there's an entire other dimension of space missing.

If the structure was seen at the edge of the circumference of Earth, then it would be acceptable, but we're seen it from a 3D angle. Using a 2D scaling, without the presence of any angle at all and applying to this is completely wrong and will inflate the size of the structure by a significant amount.
Prove it inflates it? I don't get what that means
 
The shot ain't coming from outer space at all

It would probrably need to be something like a shot where we can see the planet fully or a significant portion of it
 
As you could tell, Im not very good at it
Imagine a cube.
You put it sideways and look slightly from above. You can see the cube's outlines. Lets say one side is 10cm. But then you take a photo of the cube in that exact position from your POV and you print the photo. Now if you measure the same line on the photo it would be smaller as we only see it in 2 dimensions rather than three and thus we can't aporoach it from the side and measure it's actual length, we can only see the length that we get on the image.
 
Imagine a cube.
You put it sideways and look slightly from above. You can see the cube's outlines. Lets say one side is 10cm. But then you take a photo of the cube in that exact position from your POV and you print the photo. Now if you measure the same line on the photo it would be smaller as we only see it in 2 dimensions rather than three and thus we can't aporoach it from the side and measure it's actual length, we can only see the length that we get on the image.
Oh my god, I was typing this EXACT example yesterday (which I gave up on because I was too sleepy for that shit)
 
He wouldn't scale. They both sped up significantly after getting rid of Flashy.
Yeah but the feat only account for 2D distance, and that’s not even the full 2D distance in the calc. So unless the lowballed feat is cubed or something to still get a low balled number then FF should scale to something this lowballed.
 
Actually, now all the lines on the page that only exist are taken into account
Yeah I peeped the re calc, nice job.
Is there any way that the offscreen lines can be accounted for? I know you added the 1.2x multiplier to account for the unadded lines, but some of the longest lines go off panel, especially that top right corner.
 
Imagine a cube.
You put it sideways and look slightly from above. You can see the cube's outlines. Lets say one side is 10cm. But then you take a photo of the cube in that exact position from your POV and you print the photo. Now if you measure the same line on the photo it would be smaller as we only see it in 2 dimensions rather than three and thus we can't aporoach it from the side and measure it's actual length, we can only see the length that we get on the image.
That's very different from the scan. it simply compares it to the curvature of the Earth.
 
Scaling by the curvature of the horizon does not work, because in this case we have a crater with a diameter of 1000 km and a high-rise building 10 km.
 
Yeah my favorite part about upgrading a verse's speed is that everyone will just equalize it anyways.
But we're an indexing wiki first battling is just extra Ant says
 
Back
Top