Forum Discussion
3 Replies
- EA_Blueberry4 years ago
Community Manager
@zberman21
Thank you! Will try testing the RPO issue out later myself, I don't see any other reports on it so far so it may have just popped up from a recent update. - zberman214 years agoSeasoned Novice
Sounds good, as you saw it happens every so often not ever time, but it is usually when it’s a late pass instead of run. Bottom of the screen shows throw out of sack but clearly the defense is no where near tackling baker.
I'm not sure whether I correctly interpret/know the NFL rules, but in the case of the "incomplete catch" my guess would be that the catch was assessed complete because it came out only after felling to the ground while the WR was touched (in the air). My impression is that the program code always blows the play dead as soon as a WR touches the ground and was touched during the catch. in your case, I guess it is not possible for the human eye to exactly see whether when exactly the ball came out while the program code decides by milliseconds. maybe the program code should be changed allowing him to wait a few milliseconds after ground contact to decide whether the ball was really caught or dropped during ground contact. but as I said, I'm not exactly sure whether a contested catch (i.e. when the WR is touched in the air) is incomplete or not if the ball comes out slightly after the ground contact (according to the NFL rules) .
by the way: I often see animations, where the QB is sacked but drops the ball before touching the ground. from my point of view the result should be a fumble while it is just called a sack.