Originally posted by bhall43
I'd rather have clock manager than OTR but that's me.Our QB fired OTR 13 times out of 81 pass attempts in our Santa Clara game, against a team that certainly doesn't blitz (mostly 3 and 4 rusher man base stuff). Cleveland was 8/13, with the 5 misses as 1 KL, 2 Drops, and 2 Nearby Defensed. There were two "incomplete" passes, one of which miiiight have been an OTR potential play.
In our recent win over Salty, we fired OTR 20 times out of 93 attempts. 12 catches, 3 nearby defensed, 2 drops, 2 KL, 1 deflected. Salty blitzes more often, and with heavier blitzes than does Santa Clara. There were 3 "incomplete" passes, 2 of which were good OTR candidates had it fired.
In both games, not a single OTR pass was uncatchable. There were a few plays in either game for sure in which I wish it'd fired such as:
http://glb2.warriorgeneral.com/game/replay/79308/2471551?player_id=35272http://glb2.warriorgeneral.com/game/replay/79308/2471981?player_id=35272http://glb2.warriorgeneral.com/game/replay/79314/2670492?player_id=35272It's entirely possible there were a bunch of others that got defended or dropped that might not have been had OTR helped put the ball more on target too. Or even some catches that might have gotten a little more YAC had the receiver not had to adjust the route to catch as much.
Here's one of the gems in which it probably did save an overthrow:
http://glb2.warriorgeneral.com/game/replay/79308/2471809?player_id=35272And it doesn't take much "moving" to be eligible for it to fire at all:
http://glb2.warriorgeneral.com/game/replay/79314/2670331http://glb2.warriorgeneral.com/game/replay/79314/2670435 you can argue the QB fell off balance or something on this throw to cause him to move enough to fire it. Certainly doesn't seem like it was the the pass rush that made him hitch right before the throw.
I love On The Run, and we haven't even golded it yet
