swat and tackle

[DarthLeon4]

It has been known for years now that a db can swat the pass, and then still tackle the receiver. While it is not a huge deal most of the time, it gets annoying when you realize that it pretty much eliminates the possiblity of the receiver catching the pass after the swat. I have never, ever, ever, ever seen a receiver catch a ball on a bobble, but I have seen a db make a pick on it dozens of times.

I can understand why you want to do it from a programming standpoint, but is it really neccesary?

[adembroski]

Quote: Originally Posted by DarthLeon4

It has been known for years now that a db can swat the pass, and then still tackle the receiver. While it is not a huge deal most of the time, it gets annoying when you realize that it pretty much eliminates the possiblity of the receiver catching the pass after the swat. I have never, ever, ever, ever seen a receiver catch a ball on a bobble, but I have seen a db make a pick on it dozens of times. I can understand why you want to do it from a programming standpoint, but is it really neccesary?

Agreed. A defensive back should have three choices with the ball in the air... tip, tackle, or interception. Generally choosing to tip or intercept will net you the tackle.

I can understand occasionally being in a spot that allows you to become an obstacle for the receiver despite missing the tip, and there ARE circumstances that allow you to do both (such as running in stride with a fly pattern, where the tip is done in the direction you're running and you can simply wrap the receiver up as a part of one continuous motion), but the whole leaping in the air, knocking the ball down, and suddenly morphing into a form-perfect 2-leg takedown of the receiver has got to go.

The question I think more sports game developers should ask themselves when attempting to correct a problem; why doesn't this work in real life?

That way there wont be so many band-aid fixes.

Why can't the quarterback drop back 20 yards and throw passes? Several reasons... the dropback motion isn't a fully controlled move... the body can't move in that unnatural manor indefinitely, eventually he'll fall down. Second, the blocking scheme is such that if a QB drops back beyond his designated hitch-step, the tackles will be escorting the defensive ends right into his lap. Third, he wont be able to see... the passing lanes are 20 yards away from him, they're not basically pinholes between his 300 linemen and the 280 linemen trying to get too him.

So how does one address this? Well, you could drop down to field level with the camera once you drop back beyond a certain point. Perhaps just go to "scramble cam", limiting the players field of vision. Next, institute realistic blocking and allow defensive players to more easily break off a tackle away from the pocket. Finally, have offensive players pass defensive linemen toward the outside and guide them back behind the pocket the way they do in real life.

Now QBs get sacked when they drop back beyond the pocket.

Same principle applies to your issue. Why do corners go for more tips if, in the game, they seem to get burned if they don't have this auto-tackle thing going on? Simple... most tipped passes aren't made on a 46 inch leap 3-5 yards away from the receiver. Most of them are made within inches of the receiver's hands. They're last minute reach-ins that never happen in football games, and they don't take the corner out of position to make a tackle. Back-pocket coverage and reach-in tips need to be a big focus of the animation sessions this year.

[trazzy88]

Agreed hope this is being worked on

[Matt Diesel]

scramble cam is a freaking great idea.