Jump to content

Oedit coordinates vs. "real-life" distance


joshdixon1980

Recommended Posts

I'm just wanting verification of some things.

From what I can tell, all stadiums use 0,0 (x, z) as the back corner of homeplate. Since, according to the rules of baseball, home plate is supposed to be entirely inside the base paths, we can assume that 0,0 is the start of the base paths. There is 90 ft. between home and first ANd home and third (where both first and third are also completely inside the base path "square").

Since every stadium I have checked has the outside corners of first and third being (1081.23, 0) and (0, 1081.226) respectively in Oedit, we can assume that roughly 1081.228 is equal to 90 ft. Thus, based on my calculations, each foot is roughly 12.014 points in Oedit.

Has anyone else verified this?

So, a wall that is 330 ft. away at the left field foul line should have the coordinates (at the foul pole) of (0, 3964.503).

Of course, there are a lot of mathematical formulas to find various points along the wall if you're wanting to know distances or coordinates. Mainly, a lot of trigonometry :).

Link to comment
Share on other sites

12" = 12 oedit units = 1 foot.

Trust me, anything more in depth than 12=1 will drive you up the wall. Oediting is bad enough without having a calculator at the ready. Trust me, from somebody who knows.

I do trig for wall distances in the alleys and center field, but that's about it. As a hint, andrewclem.com's site is your friend. It's a great last-ditch way to get distances correctly.

Link to comment
Share on other sites

Haha, I know.

I'm a Physics, Algebra, and Trigonometry teacher. I'm okay with the 3 decimals. Usually they don't bother me, let alone the amount of formulas I type into the CSV rhino files to do all the trigonometry for me. Half the time, moving a wall from one loctaion to another is just a matter of knowing one coordinate and the length of the wall and letting Excel do all the rest of the work for me.

But, 12 pts is about right? good. Because I read some post about some weird estimating which appeared ot be way off to me.

Link to comment
Share on other sites

Yeah, the main thing is, as well organized as you may be, it'll still get really confusing when you're changing around line after line after line of code in wall.dat.

It's not too bad when you're dealing with a minor league park, but when you try to make something like the Pennant Porch for KC Municipal, watch out. Not to mention spreading out 4 vertices to cover what should be done with 6 at a place like Cleveland Municipal.

Link to comment
Share on other sites

Okay, what about the Y-axis distance?

I'm completely lost with this one, because in the stadium I'm editting, the walls are 208 high. This would be 17 ft. high. I'm pretty confident they're not 17 ft. high.

I don't have a normal wall height to make comparisons to, sorry.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...