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

The problem with angular size formulas

Antvasima said:
We obviously need to strive for accuracy, but I do not know how we are realistically going to first find all of the calculations that use the wrong method, then redo and evaluate them, and finally revise all of the connected profiles.

It would turn into a massive wiki project involving as much of the staff as possible, and I would much prefer to prioritise improving the accuracy of our lower Attack Potency chart borders first.

You should ask for input from the rest of the calc group in any case.
What's wrong with the AP?
 
We have another project of trying to properly determine what our attack potency borders for tiers 9-A to 6-B or so specifically mean. Kavpeny was the one who defined them, and he isn't here anymore, and has forgotten what he based them on.
 
Okay. I just don't know how we are possibly going to first find and recalculate them all, and then update all of the profiles scaled from them, but we should certainly update our instruction pages to start with.
 
Perhaps this is something best done over time then? Check any angsizing calcs and if they're using the right formula, leave a comment on the blog that it's correct (to avoid doubling up on work). If it's not correct, redo the calc and change any profiles accordingly?
 
Shouldn't these two formulas mentioned in the Calculation Guide

Distance: object size*panel height/[object height*2tan(70/2)]

Size: 2tan(70/2)*distance*object height/panel height

They seem way easier than the first one + ang size calculator method.
 
Yes, and they give you exactly the same result as the ang size calculator method.
 
"Angle: 2*atan(tan(70/2 deg)*(object height/panel height)) "


So does this formula give you the direct result in degrees instead of radians? If one uses this there is no need to convert radians to degrees right?
 
I would appreciate if DontTalkDT could update the appropriate parts of the calculation instruction pages.
 
AguilaR101 said:
"Angle: 2*atan(tan(70/2 deg)*(object height/panel height)) "


So does this formula give you the direct result in degrees instead of radians? If one uses this there is no need to convert radians to degrees right?
Yes.
 
Antvasima said:
I would appreciate if DontTalkDT could update the appropriate parts of the calculation instruction pages.
Can somebody ask him to comment here again?
 
I have for now simply updated the page to mention the degree thing, since that was a minor change to the page.

Kinda busy today, so I will see to integrating new formula another time.
 
I guess the thread can be closed. It seems everything has been concluded
 
It is probably best to wait for DontTalkDT to perform all the necessary updates first. Or has that already been done?
 
So, wait, what exact formulas and exact variables should I plug into google when doing a distance calc, because I'm getting conflicting things with another person
 
Should I use...

This: Object Size*Panel Height/[Object Height*2tan(70/2)]

Or This: Object Size*Panel Height/[Object Height*2tan(70/2) deg]

Cause this apparently is a huge change
 
Object Size*Panel Height/[Object Height*2tan(70/2 deg)] actually
 
BlackeJan said:
So would this upgrade or downgrade
For speed feats it can be either.

For the AP this will downgrade feats in which we calculate distance but will also upgrade those that calc size
 
Antvasima said:
It is probably best to wait for DontTalkDT to perform all the necessary updates first. Or has that already been done?
I'm going to create Calculation Guide Additions thread sometimes soon so I guess this one can be closed after I do
 
It just came to me, since the calculation uses horizontal field of view, shouldn't the panel width be the one used in the angsizing formula instead?

ie: imagine a 1280(width)*720(height) image

The formula to detemine angle would be

2*atan(tan(70/2)*(object height/1280)) instead of 720
 
For my third calc on my speed feats for Pretty Cure Splash Star I used 2atan(tan(70/2)*(object size in pixels/screen height in pixels)). I did it in radians and then converted to degrees and got 157.12m. I then tried doing it with degrees from the beggininning and got 3.4905e+5m which I know for a fact is not the case.

I want my calc to be as good as possible, but when I try to do it this way it didn't work. Given that they were fighting above a town, my intial calc seems reasonable, but would like feedback to see what I can do to fix it, if I need to.

Edit: thank you for the help. fixed it now
 
AguilaR101 said:
It just came to me, since the calculation uses horizontal field of view, shouldn't the panel width be the one used in the angsizing formula instead?
ie: imagine a 1280(width)*720(height) image

The formula to detemine angle would be

2*atan(tan(70/2)*(object height/1280)) instead of 720
Wait, can or should you do this? because that would change my calc
 
I would appreciate if somebody could remind DontTalkDT about this thread.
 
If the idea behind angsizing is as explained the formulas that were suggested should be correct.

I have included them into the page now.
 
Okay. Thank you for the help.

Is there anything left to do here, or should we close this thread?
 
The distance formula is correct

The size formula is also correct though it doesn't need parentheses in the end
 
I have an idea. Maybe for panels that are stretched (like this one) it would be better to assume 180 degrees horizontal view angle.

But the problem is that the formulas above olny work if the view angle is below 180 degrees
 
Okay, I came up with the formula for 180 degrees.

Distance = 0.5*object size/object size in px*panel width

Should I explain geometric meaning of it?
 
Back
Top