The reticle
-
So, I've been really focusing on the movement (non-movement) of the reticle. I just went through tallying what I saw on 50 different pitches/swings on HOF mode against AI. 13 of the pitches I intentionally didn't move the reticle on middle pitches. Sometimes I was fooled sometimes I made contact and got hits. Really nothing too unusual in middle of the zone on static reticle.
When I started moving around in the strike zone, though, I noticed the obvious. Specifically, when I would move the reticle in the path of where I thought the pitch was coming. When I guessed slightly wrong, which was 9 times, the reticle ALWAYS moved into that missed area and was typically a swinging strike.
When I guessed right and surely "attempted" to move my reticle in the path, 14 times the reticle didn't move and I missed/fouled/rolled-over-grounded/rolled-under-flew-out the pitch. 4 times my move was either exaggerated or a definite different direction than I was gearing the controller. Only 10 times did the reticle move sorta where I shifted the controller. Never once, though, did the reticle move "wrong" into a position that avored my AB.
Hard to follow that probably but, the point is, if this failure for the animation to accurately plot the reticle/controller is due to network lag....that lag BIG TIME favors the AI pitcher. Nearly always "misfires" in favor of the AI pitcher. Is it a misfire or AI simply staging a condition/result and disregarding controller input?
Watch for yourself. Reticle movement may need some tweaking prior to the next update.
