Originally posted by IdRatherFlyFish
I'm going to call this Working As Intended, due to the post I've quoted and to my interpretation of how this play was simmed.
TE and RG, HB blocks
TE feels that the RG (and/or HB) is in position to block the LO so he does not consider the LO an immediate threat. CB, meanwhile, is taking a looping route to the outside of the WR who is engaged with the SS.
QB sees the LO filling the hole that the TE just went through, so instead of cutting up-field and following the TE, the QB makes the decision to bounce the run further outside. Had the RG and or HB been able to engage the LO, the ball carrier could very well have followed the TE up-field.
RG misses a block (looks like he tried a cut block), HB is too slow to engage the LO, QB continues to the edge, where the CB is waiting for him.
If the RG had been able to get to his spot a tick or three earlier, then the LO would have been blocked by the RG.
I don't see a bug here in my opinion.
Peace,
Fish
No, it's not working as intended. I have that straight from support when I posted the bug. They did nothing then though because the new blocking code and DPC was suppose to solve the issue.
Of course, that's only one replay, so nothing says it wasn't a missed vision check.
I'm going to call this Working As Intended, due to the post I've quoted and to my interpretation of how this play was simmed.
TE and RG, HB blocks
TE feels that the RG (and/or HB) is in position to block the LO so he does not consider the LO an immediate threat. CB, meanwhile, is taking a looping route to the outside of the WR who is engaged with the SS.
QB sees the LO filling the hole that the TE just went through, so instead of cutting up-field and following the TE, the QB makes the decision to bounce the run further outside. Had the RG and or HB been able to engage the LO, the ball carrier could very well have followed the TE up-field.
RG misses a block (looks like he tried a cut block), HB is too slow to engage the LO, QB continues to the edge, where the CB is waiting for him.
If the RG had been able to get to his spot a tick or three earlier, then the LO would have been blocked by the RG.
I don't see a bug here in my opinion.
Peace,
Fish
No, it's not working as intended. I have that straight from support when I posted the bug. They did nothing then though because the new blocking code and DPC was suppose to solve the issue.
Of course, that's only one replay, so nothing says it wasn't a missed vision check.
Edited by IdRatherFlyFish on Jan 24, 2012 10:21:10






























