Umpiring simulator

[JHSump]

Pilots have flight simulators where they can practice flying, without flying a real airplane.  In umpiring, we only get to "practice" calling balls and strikes during actual games.  Does anyone know of an "umpiring simulator" that you can run on your own computer, for practice calling balls and strikes?

 

Looking around online, I couldn't find one.  I know a bit about writing 3D simulations in the computer language Python.  So, I tried writing an umpiring simulator.  I'm not completely satisfied with it.  It's missing a catcher, which actually makes it much harder to call balls and strikes (no surprise).  But it's not too bad, I think.  If anything, it might be useful in convincing someone that a catcher plays a large role in calling balls and strikes.

 

I'm looking for a way to share this simulator, here on U-E.  Normally, to run a Python program you first need to install the Python programming language on your computer.  But, to avoid that first step, I tried making a separate executable program for the simulator, but couldn't figure it out. So, if anyone wants to try this simulator, the first step is to install the Python programming language on your computer. Luckily, Python is not very difficult to install, and run.

 

The simulator gives you a 3D view from the slot, with a RHB.  The plate, batter's boxes, dirt circle, and pitcher's mound are present.  You hit any key and an 80 mph fastball is thrown.   The ball follows the laws of physics, and looks similar to those pitches you see on the mlb.com Gameday display. The exact initial direction of the pitch is randomly selected to produce a strike or ball somewhat near the strike zone (no wild pitches).  The ball's flight stops at approximately where the catcher would catch the ball. You decide on your call, then hit any key, and a strike zone box (like the pitch f/x box) appears.  Hit any key and the pitch is repeated with the strike zone displayed; when the ball passes the front edge of the plate, a stationary image of the ball is displayed, again like in the pitch f/x display during a televised game, so you can check your call. Hit the key again, the strike zone is erased, and your're ready to start a new pitch.

 

Attached are two screen shots.  The first shows the scene before the pitch.  In either screen shot, there are two images so that by crossing your eyes, you can see a 3D view of the scene (alternatively, the simulator can be run so that two colored images are made, and with colored "3D" glasses, you can see a 3D scene)..  The second screen shot shows the scene after the repeat of a pitch, showing the strike zone and ball image at the front edge of the plate.

 

If anyone is interested I can post the simulator source code in another post, and tell how to install Python and run the simulator.

 

[BigUmp56]

It looks like fun, but I'm suspiciuos about how using it would really translate to calling real pitches.

Also, not to be overly critical because I applaud your efforts, but it looks like the view for the umpire is too low.

Tim.

[JHSump]

Yeah, I'm not sure how useful it is in the end.  But the idea was to make it 3D so it might be somewhat realistic.

 

And, BTW, you can change the view point, lowering it, raising it, zooming in more, zooming out, etc., just using the mouse!  Once you have the "positioning" you like, you just don't play with the mouse anymore.  The view stays the same, and you hit a key to throw a pitch.  So, that is one of the beauties of Python --- you get to play with the view in a very simple way!

[Replacematt]

[carolinablue]

 Might be helpful for practice tracking pitches, especially if you could make some kind of wireless sensor ( like WII has ) to attach to a mask which could detect any head movement and show it on the screen.

 

 

The batter needs to eat, and I'm not sure that bat is legal.

[JaxRolo]

Low and not really slot but good idea

[JHSump]

"Too much time on my hands."  --- yeah, I'm in a "no games" drought between local all-stars and start of the fall season.

 

Here is another view slightly shifted.  All I did was hold down the right mouse button, and slide my mouse around to change my viewpoint.  I held down both the left and right mouse buttons, and moved the mouse to move my view up closer to the plate.  All these actions are built into Python.

 

Batter needs to eat, that's for sure --- and maybe some HGH.

[mjr_2013]

There is this cool thing in my town called Virtual Baseball... Basically, you pay $30 for thirty minutes with the machine (which turned into an hour because the owner was cool and we were the only people there)... There is a batting cage with a real 60' distance... There is a cage behind the batter and a small room there with a computer... On the computer, you choose...

 

- Level (Anything from 10U to MLB)

- Set or windup

- Pitcher handedness

- Pitch type (pretty much every option but knuckle)

- Pitch speed (40mph-100mph)

- Pitch location (to an extent, it's not perfect)

- Number of pitches in the series

 

When you set it, a video projection of the pitcher you chose comes on the screen in front of you, where you would normally see the cage... The pitcher's projection goes through the windup (or stretch), and when the delivery would come, the ball comes out of the shoot exactly how you wanted it.

 

It's pretty wicked... I got to stand behind the plate with an umpires view (on a cinderblock behind the cage) for about twenty 100mph fastballs plus some splitters, cutters, sliders, and curves, while my friend tried to hit them (he sent one back up the middle, tipped another, and missed the rest)... It was cool from an umpires perspective!

[JHSump]

Ok, I got one PM for the code,  So, just in case someone is shy about asking, here is the code.  In the next post, I will describe how to install Python and run the simulator.

 

************* Once you have Python installed, you will just copy and paste the following into your VIDLE window (leave off this line) **********

# Simulates a pitch as seen by the plate umpire

# JHS 2013

#

# Coordinates are in feet

# Speed of pitch is in mph

# Angles of pitch are in degrees

# Point of Plate is at origin, x is direction from pitcher's rubber to plate, y is up, z is toward RHB box

# Pitch is released at x=-56 feet, y=6 feet, z=0 feet

#

# RHB (a stick figure)

# Randomized initial pitch direction, within bounds

# Pitch is repeated: first view without strike zone box, second with strike zone box

# white batter box lines.

#

# Hit Enter key to throw a pitch

 

from __future__ import division

from visual import *

from math import *

 

# The following pauses until a keyboard event occurs.

def pauseforkey():

    while True:

        rate(50)

        if scene.kb.keys:

            k = scene.kb.getkey()

            return

 

scene = display(title='View of a Baseball Pitch',

                width=1000, height=800, center=(0,0,0),

                background=color.black)

 

scene.autoscale=False

 

scene.center = (-10,0,10/12)  # Umpire looks at x=-10 feet, y=0, z=10/12 feet

scene.forward = (-20,-3,0)    # Umpire's eyes point along a vector parallel to x=16 feet, y=3 feet, z=0 feet

scene.fov = math.pi/2.5

# scene.stereo = 'redcyan'    # will work if you have red-cyan 3D glasses!

# scene.stereo = 'redblue' 

# scene.stereo = 'yellowblue' 

scene.stereo = 'crosseyed'    # works with crossing eyes

 

# Dirt circle around plate

dirtCircle = cylinder(pos=(0,-0.01,0), axis=(0,0.01,0), radius=13,

                      color=(1.0,0.7,0.2))

 

# Pitcher's mound

pitcherMound01 = cylinder(pos=(-60.5,0.0,0),axis=(0,0.05,0),radius=9.0,color=(1.0,0.7,0.2))

pitcherMound01 = cylinder(pos=(-60.5,0.05,0),axis=(0,0.05,0),radius=8.75,color=(1.0,0.7,0.2))

pitcherMound01 = cylinder(pos=(-60.5,0.1,0),axis=(0,0.05,0),radius=8.5,color=(1.0,0.7,0.2))

pitcherMound02 = cylinder(pos=(-60.5,0.15,0),axis=(0,0.05,0),radius=8.25,color=(1.0,0.7,0.2))

pitcherMound03 = cylinder(pos=(-60.5,0.2,0),axis=(0,0.05,0),radius=8.0,color=(1.0,0.7,0.2))

pitcherMound04 = cylinder(pos=(-60.5,0.25,0),axis=(0,0.05,0),radius=7.75,color=(1.0,0.7,0.2))

pitcherMound04 = cylinder(pos=(-60.5,0.3,0),axis=(0,0.05,0),radius=7.5,color=(1.0,0.7,0.2))

pitcherMound05 = cylinder(pos=(-60.5,0.35,0),axis=(0,0.05,0),radius=7.25,color=(1.0,0.7,0.2))

pitcherMound05 = cylinder(pos=(-60.5,0.4,0),axis=(0,0.05,0),radius=7.0,color=(1.0,0.7,0.2))

pitcherMound05 = cylinder(pos=(-60.5,0.45,0),axis=(0,0.05,0),radius=6.75,color=(1.0,0.7,0.2))

pitcherMound06 = cylinder(pos=(-60.5,0.5,0),axis=(0,0.05,0),radius=6.5,color=(1.0,0.7,0.2))

pitcherMound07 = cylinder(pos=(-60.5,0.55,0),axis=(0,0.05,0),radius=6.25,color=(1.0,0.7,0.2))

pitcherMound07 = cylinder(pos=(-60.5,0.6,0),axis=(0,0.05,0),radius=6.0,color=(1.0,0.7,0.2))

pitcherMound07 = cylinder(pos=(-60.5,0.65,0),axis=(0,0.05,0),radius=5.75,color=(1.0,0.7,0.2))

pitcherMound08 = cylinder(pos=(-60.5,0.7,0),axis=(0,0.05,0),radius=5.5,color=(1.0,0.7,0.2))

pitcherMound09 = cylinder(pos=(-60.5,0.75,0),axis=(0,0.05,0),radius=5.25,color=(1.0,0.7,0.2))

pitcherMound09 = cylinder(pos=(-60.5,0.8,0),axis=(0,0.05,0),radius=5.0,color=(1.0,0.7,0.2))

 

# RHB Box

rightBox1 = box(length=6, height=0.03, width=4, pos=(-1/sqrt(2.),-0.01,3.2083), color=color.white)

rightBox2 = box(length=5.67, height=0.05, width=3.67, pos=(-1/sqrt(2.),-0.01,3.2083), color=(1.0,0.7,0.2))

 

# LHB Box

rightBox1 = box(length=6, height=0.03, width=4, pos=(-1/sqrt(2.),-0.01,-3.2083), color=color.white)

rightBox2 = box(length=5.67, height=0.05, width=3.67, pos=(-1/sqrt(2.),-0.01,-3.2083), color=(1.0,0.7,0.2))

 

plate1 = box(length=8.5/12.0, height=0.05, width=17.0/12.0, pos=(-4.25/12.0-1/sqrt(2.),0,0), color=color.white)

plate2 = box(length=1, height=0.05, width=1, pos=(-1/sqrt(2.),0,0), axis=(1,0,1), color=color.white)

 

baseballradius = 9.125/(12.0*2*math.pi)   # circumference of a baseball is 0.125 inches

 

platelength = 8.5/12 + 1/sqrt(2.0)

platewidth = 17./12.

front = -platelength

left = platewidth/2.

right = -left

bottom = 1.25   # lower strike zone (in feet)

top = 3.65      # upper strike zone (in feet)

 

strikeZone = curve(pos=[(front,top,left),

                    (front,top,right),

                    (front,bottom,right),

                    (front,bottom,left),

                    (front,top,left)],

                     color=color.yellow)

strikeZone.visible = True

 

# Right Hand Batter (RHB), coordinates are specified in feet

lowerRightLeg = curve(pos=[(1.81,0,2.74),(1.32,1.32,2.48)],

                      color=color.white,radius=0.1)

rightFoot = curve(pos=[(1.81,0,2.74),(1.81,0,2.04)],

                      color=color.white,radius=0.1)

upperRightLeg = curve(pos=[(1.32,1.32,2.48),(0.94,2.58,2.78)],

                      color=color.white,radius=0.1)

lowerLeftLeg = curve(pos=[(-0.94,0,2.74),(-0.40,1.21,2.48)],

                      color=color.white,radius=0.1)

leftFoot = curve(pos=[(-0.94,0,2.74),(-0.94,0,2.04)],

                      color=color.white,radius=0.1)

upperLeftLeg = curve(pos=[(-0.40,1.21,2.48),(0.18,2.64,2.78)],

                      color=color.white,radius=0.1)

hips = curve(pos=[(0.18,2.64,2.78),(0.94,2.58,2.78)],

                      color=color.white,radius=0.1)

shoulders = curve(pos=[(0.27,4.30,2.22),(1.43,4.39,2.41)],

                      color=color.white,radius=0.1)

torso = curve(pos=[(0.56,2.61,2.78),(0.85,4.35,2.32)],

                      color=color.white,radius=0.1)

upperRightArm = curve(pos=[(1.43,4.39,2.41),(1.97,3.88,2.87)],

                      color=color.white,radius=0.1)

lowerRightArm = curve(pos=[(1.97,3.88,2.87),(1.70,4.23,1.97)],

                      color=color.white,radius=0.1)

upperLeftArm = curve(pos=[(0.27,4.30,2.22),(0.83,3.56,1.52)],

                      color=color.white,radius=0.1)

lowerLeftArm = curve(pos=[(0.83,3.56,1.52),(1.79,3.98,1.77)],

                      color=color.white,radius=0.1)

neck = curve(pos=[(0.85,4.35,2.32),(0.87,5.02,1.80)],

                      color=color.white,radius=0.1)

head = sphere(pos=(0.87,5.02,1.80), radius=0.45)

bat = curve(pos=[(1.79,3.98,1.77),(1.84,6.00,3.51)],

                      color=color.yellow,radius=0.1)

 

pitchspeed = 80.0        # in mph

 

# verticalangle = 2.0     # test; degrees, should range from about -1.2 to 2.0

# horizontalangle = 1.2   # test; degrees, positive is toward RH batter side of plate; range from -1.2 to 1.2

 

showZone = False   # display starts without a strike zone

 

while True:    # continue until program is closed

 

    if showZone == False:

        strikeZone.visible = False

        # this is a new pitch: randomly choose vertical and horiztonal direction of pitch

        # values for angles are in degrees

        verticalangle = random.uniform(-1.2, 2.0)

        horizontalangle = random.uniform(-1.2,1.2)

    else:

        strikeZone.visible = True

 

    ball = sphere(pos=(-60,6,0), radius=baseballradius, color=color.white)

    ps = pitchspeed*5280.0/3600.0      # 5280 feet in one mile, 3600 seconds in one hour

    vangle = verticalangle * math.pi/180.0

    hangle = horizontalangle * math.pi/180.0

    ball.velocity = vector(ps*cos(vangle)*cos(hangle),ps*sin(vangle),ps*cos(vangle)*sin(hangle))

 

    pauseforkey()   # once any keyboard key is hit, pitch is thrown

 

    onepitch = True

    flag=0

    dt = 0.001

    while onepitch:

        rate(1000)

        ball.pos = ball.pos + ball.velocity*dt

        ball.velocity.y = ball.velocity.y - 32.17*dt

        if ball.y < baseballradius:

            ball.velocity.y = -ball.velocity.y

        if (ball.x > -platelength) and (flag==0):

            spot = sphere(pos=(ball.x, ball.y, ball.z), radius=baseballradius, color=color.yellow, visible=False)

            if showZone == True:

                spot.visible = True

            flag = 1

        if ball.x > 2.5:

            onepitch = False

            pauseforkey()

            spot.visible = False

            ball.visible = False

 

    if showZone == False:

        showZone = True

    else:

        showZone = False

[JHSump]

To install Python, and the necessary VPython component, go to

http://www.vpython.org/

 

In the upper left, under Download, click on the appropriate choice for your machine (Windows, Macintosh, or Linux).

 

On the page that opens, follow the directions to download and install Python, then download and install VPython.  The page gives you all the necessary links.  I am familiar with the Windows instructions only.

 

Once Python and VPython are installed, an icon labeled "VIDLE for VPython" will appear on your Windows desktop.  Double-click it to open it.  Copy and paste the source code from the above post into this window.  Save the program anywhere you want on your file system (Desktop is fine).  Give the file a name like pitch.py (the .py  is necessary).  Then hit the F5 key to run it!

 

You can adjust the view by holding down the right mouse key and moving the mouse.  You can zoom in or out by holding down both the right and left mouse keys, and moving the mouse.

 

Cross your eyes so the two different views converge in the middle --- and you should see a 3D view of the scene!

 

Hit any key on the keyboard and a pitch will be thrown.  After the pitch is thrown, hit a key and a strike zone appears.  Hit another key and the same pitch is repeated with the strike zone in place.  Repeat for additional pitches.

 

Let me know how it works!

[th3]

let me guess - it also activates your webcam and records you crossing your eyes right?

[JHSump]

let me guess - it also activates your webcam and records you crossing your eyes right?

Haha, ...and looking confused.

[Texas Manny]

The intention is good, but one of the keys to a good strike zone is following the ball with your eyes through the strike zone and into the catcher's glove. Then you call the pitch. Tracking the ball with your eyes is paramount to being successful behind the plate. It is very hard not to be consistent, if you have proper head height, are in the slot correctly, body is square and you are tracking pitches with your eyes successfully.

 

In order to use a simulator, you'd have to be able to set the parameters so that the umpire's viewpoint is correctly in the slot, the right height, and that you are able to track the ball with your eyes into the catchers glove. I don't see how the present configuration allows that and can be detrimental when the umpire goes into a real game because he's conditioning himself to looking at a computer screen. I don't think at the level of software presently, (no disrespect intended), that you are able to get the ball to break like a curve, drop like a slider, float like a knuckler, or sink like a sinker.

 

I know this is in development stages. Just trying to share some observations.

 

Manny

[JHSump]

The intention is good, but one of the keys to a good strike zone is following the ball with your eyes through the strike zone and into the catcher's glove. Then you call the pitch. Tracking the ball with your eyes is paramount to being successful behind the plate. It is very hard not to be consistent, if you have proper head height, are in the slot correctly, body is square and you are tracking pitches with your eyes successfully.

 

In order to use a simulator, you'd have to be able to set the parameters so that the umpire's viewpoint is correctly in the slot, the right height, and that you are able to track the ball with your eyes into the catchers glove. I don't see how the present configuration allows that and can be detrimental when the umpire goes into a real game because he's conditioning himself to looking at a computer screen. I don't think at the level of software presently, (no disrespect intended), that you are able to get the ball to break like a curve, drop like a slider, float like a knuckler, or sink like a sinker.

 

I know this is in development stages. Just trying to share some observations.

 

Manny

Good comments.

 

Truthfully, I also don't think the present configuration of the program is totally realistic.

 

Here are somethings that are, in my opinion, ok:

1) It's 3-D, not a 2-D view.

2) The ball's trajectory is pretty realistic.  The trajectory is calculated according to the laws of physics.  It's not a guess as to how the ball should move.  I could add a realistic curve, sinker, etc.  Actually, this is probably a sinker now, since spin is ignored in this version (so no lifting force at all).

3) You can change your view point at will, using the mouse.  So, you can set yourself up wherever you wish.

 

Here are some things that could be done better:

1) There is no catcher!!!!!!  As you point out, the catcher is an important piece of the process of calling pitches.  Unfortunately, adding a realistic catcher would be very hard to program well.

2) Yes, you can move your perspective, but you can't quite get up close to the catcher/plate where you would have to look down to see the catcher's head and forward to see the pitcher.  In other words, the computer screen is just a "window" through which you look at the 3-D scene.

 

Really great would be a simulator built literally around the user --- like for pilots.  This could be done in a "cave" environment (it's a room-like setting on the walls of which are displayed the 3-D, all-around, scene.  But, you need to have a cave room (there are only a few in the US, as far as I know).

 

It is much more difficult to call pitches WITHOUT the catcher!  From this program you can dramatically see that a catcher helps quite a bit.  It helps to see how the catcher moves, catches the pitch, turns over or does not turn over this mitt, extends his arm, reaches, does not reach, etc., etc., etc.  That was, for me, the really interesting thing I very dramatically saw from writing this program.  The trajectory of the ball is only "half" the story.  The other half is tracking it into the mitt and watching how it is received by the catcher.

 

Now, if I could program that into the simulator, it would improve tremendously.

[semper_fi_72]

So do you collect a simulated game fee also

[johnnyg08]

Bringing this thread back to the forefront. Mr. @JHSumpwas WAY ahead of his time. 

[BLWizzRanger]

Well, if the batter had a glove sticking out his backside and maybe an elbow guard, make it more realistic.

All joking aside, I applaud his attempt.  Sometimes bringing your profession and your hobby together makes both skill sets rise.

[ousafe]

Win Reality could probably create an "umpire mode" but it's targeted exclusively at batters for now.  I sent them an email a while ago. winreality.com

[834k3r]

On 11/3/2023 at 8:59 PM, ousafe said:

Win Reality could probably create an "umpire mode" but it's targeted exclusively at batters for now.  I sent them an email a while ago. winreality.com

I meant to try it out in the strike zone recognition mode, but never got around to it. Now you've given me additional motivation to actually try it out.

I emailed them a year ago or so and suggested they develop an umpire mode as well, and they seemed receptive to it.

[jms1425]

I have been using WinReality to practice calling pitches for about 2 months now, using the Pitch Recognition training mode. It is outstanding. You can select pitchers based on LHP/RHP, velocity, pitch types, pitch locations, arm slots, and windup or set. I had seen about 1000 pitches before my first actual cagework, and rather than feeling any need for "adjustment" or "settling back in" behind the plate, I felt immediately comfortable, as though it was not the first time I was seeing pitches since last season.

Now, all that being said, it's a little expensive. You have to subscribe to their monthly program, which is $29 / month. I got a holiday season deal where I bought a full year, and it was reduced to $19 / month, so that's $120 cheaper for the year, but it was still nearly $250. Yes, I occasionally take BP or mess around with the other drills and modules for hitters, but 95% of my use is only in the Pitch Recognition module for ball/strike training as an umpire. 

Also, there is no catcher nor batter, so you cannot use info from how the pitch is received to help, and judging up/down won't perfectly transfer to the real world. But, all in all, I have found it to be a very useful tool.

If they came out with an "umpires" version at a much reduced price, I would rather have that and live without my occasional frolic into the hitting exercises. But if you don't mind dropping $250 for the Oculus and another $250 (or more) for the subscription, I highly recommend this.

[834k3r]

3 minutes ago, jms1425 said:

I have been using WinReality to practice calling pitches for about 2 months now, using the Pitch Recognition training mode. It is outstanding. You can select pitchers based on LHP/RHP, velocity, pitch types, pitch locations, arm slots, and windup or set. I had seen about 1000 pitches before my first actual cagework, and rather than feeling any need for "adjustment" or "settling back in" behind the plate, I felt immediately comfortable, as though it was not the first time I was seeing pitches since last season.

Now, all that being said, it's a little expensive. You have to subscribe to their monthly program, which is $29 / month. I got a holiday season deal where I bought a full year, and it was reduced to $19 / month, so that's $120 cheaper for the year, but it was still nearly $250. Yes, I occasionally take BP or mess around with the other drills and modules for hitters, but 95% of my use is only in the Pitch Recognition module for ball/strike training as an umpire. 

Also, there is no catcher nor batter, so you cannot use info from how the pitch is received to help, and judging up/down won't perfectly transfer to the real world. But, all in all, I have found it to be a very useful tool.

If they came out with an "umpires" version at a much reduced price, I would rather have that and live without my occasional frolic into the hitting exercises. But if you don't mind dropping $250 for the Oculus and another $250 (or more) for the subscription, I highly recommend this.

I had been wondering about that myself (as mentioned above), but never got around to trying it out. I'll now have to definitely try it. How do you set up behind the VR plate?

[jms1425]

1 minute ago, 834k3r said:

I had been wondering about that myself (as mentioned above), but never got around to trying it out. I'll now have to definitely try it. How do you set up behind the VR plate?

Just like IRL. When you put on the headset, you are in a virtual stadium, standing in the circle around homeplate, with batter's box lines, a catcher's box, foul lines... it's literally like standing on a real field.

There is a "radio interface" that hovers in space at the back of the catcher's box that could get in your way if you wanted to be deep, but I find I can "set up" with my head just in front of that and it feels pretty normal. In fact, when I did the cagework IRL, I felt closer to the plate that I had been getting in VR. 

When I go home today I'll try to get some video or stills that I can upload here. (You can "cast" what you see in the headset to a laptop or other device.)

[834k3r]

Just now, jms1425 said:

Just like IRL. When you put on the headset, you are in a virtual stadium, standing in the circle around homeplate, with batter's box lines, a catcher's box, foul lines... it's literally like standing on a real field.

There is a "radio interface" that hovers in space at the back of the catcher's box that could get in your way if you wanted to be deep, but I find I can "set up" with my head just in front of that and it feels pretty normal. In fact, when I did the cagework IRL, I felt closer to the plate that I had been getting in VR. 

When I go home today I'll try to get some video or stills that I can upload here. (You can "cast" what you see in the headset to a laptop or other device.)

I'm pretty familiar with the GUI (my son uses the Oculus/WinReality combo for our winters), but I'm sure others will find the video helpful.

I think I'll need to get an account on WinReality for just me (don't want to mess up my son's stats).

[johnnyg08]

I'd like to try it before investing $500...I feel like I'd want a batter & a receiver there...but maybe after trying it...find that I don't need a batter/catcher. But not having an F2 there...I feel is missing....our view of the plate is not unobstructed. I LOVE the idea...I just haven't seen one that's quite there yet. 

[834k3r]

On 3/1/2024 at 8:28 PM, johnnyg08 said:

I'd like to try it before investing $500...I feel like I'd want a batter & a receiver there...but maybe after trying it...find that I don't need a batter/catcher. But not having an F2 there...I feel is missing....our view of the plate is not unobstructed. I LOVE the idea...I just haven't seen one that's quite there yet. 

It is pricey, but in my case the money was already spent. My son's the primary user of the WinReality for his off-season batting training; I'm just using it when he's not.

No affordable simulation will be perfect for sure.