03:12 PM - June 7, 2012 by illwill10NCAA Football 13 News Post
03:12 PM - June 7, 2012 by illwill10NCAA Football 13 Videos
Member Comments
# 2
daytarious5 @ 06/07/12 03:20 PM
gt did better than they would have last year! im a coach mode guy but this looks like it can be tuned with sliders
RB skill should be set at 60 as default. There is just no threat for the cpu to bust a long run on the default 50 setting. Also, I have not seen a CPU pitch on an option go for positive yards yet while playing the demo or during the gameplay videos. 
GTech drive started on its own 32 and stalled on Clemson's 42.
Not a bad drive but the bulk of those yards came on a QB scramble, not a designed option play.
Still, the option plays looked a lot better than last year.
Not a bad drive but the bulk of those yards came on a QB scramble, not a designed option play.
Still, the option plays looked a lot better than last year.
I think it has been discussed here before in other threads ... but to me it seems like the D's pursuit it fast as hell, making it tough to run the option. I'm no triple-option expert, but it didn't seem like there were many decisions by the QB.
I'm not an EXPERT, but I know my CPJ stuff.
It's definitely better than last year.
Still watching.
I don't know where they get the idea that the tail motion is run 3 yards behind the B-Back. I always told my A-back to aim at the B-Back; running it any deeper really slows things down in real life. Makes it look wonky in the game.
It's definitely better than last year.
Still watching.
I don't know where they get the idea that the tail motion is run 3 yards behind the B-Back. I always told my A-back to aim at the B-Back; running it any deeper really slows things down in real life. Makes it look wonky in the game.
# 8
Jakeboutte @ 06/07/12 03:48 PM
|
|||||||||||||
|
Im right there with you. It seems like the defense knows what is coming. Yes it is GT and they are know for the triple option, but dont you think they could break at least one off. Maybe Clemson just had a superb gameplan and knew what to expect, which isnt hard to do! lol I know we saw only one drive so Im not jumping to conclusions, I would just love to see GT break one off though!
GT plays:
1. speed option right (-4 yards) - correct read, receivers don't block anyone and half of clemson's defenders crash left at the snap much too quickly.
2. triple option left (9 yards) - de crashes, qb keeps, db covers rb. Correct read. Sound and realistic play offensive and defensively.
3. PA pass scramble (15 yards) - Nice decisive scramble by CPU. Unable to tell if anyone is open or may become so.
4. FB dive - ( No gain) - FB looked to have 2-3 yards up the middle but tries to bounce it outside.
Defensive pursuit again seems too fast.
5. Triple option left (-2 yards) - Here's where it gets really frustrating... The play is run/read correctly. The end crashes forcing the qb to keep, the DT
and linebacker chase the qb down forcing him to pitch. The rb has AT LEAST 8 yards if he continues towards the side line, but for some reason tries to spin inside two defenders and loses two yards.
The CPU definitely does a better job running the option than in 12. However, the defensive pursuit to the outside basically negates all possible positive gains on the speed option for the CPU. Hopefully sliders can help tweak the outcome of the final play because it was run perfectly until the back decides to try and spin past two defenders rather than just continuing his momentum and taking the play to the outside. That being said, the running back AI as a whole needs to be tuned.
1. speed option right (-4 yards) - correct read, receivers don't block anyone and half of clemson's defenders crash left at the snap much too quickly.
2. triple option left (9 yards) - de crashes, qb keeps, db covers rb. Correct read. Sound and realistic play offensive and defensively.
3. PA pass scramble (15 yards) - Nice decisive scramble by CPU. Unable to tell if anyone is open or may become so.
4. FB dive - ( No gain) - FB looked to have 2-3 yards up the middle but tries to bounce it outside.
Defensive pursuit again seems too fast.5. Triple option left (-2 yards) - Here's where it gets really frustrating... The play is run/read correctly. The end crashes forcing the qb to keep, the DT
and linebacker chase the qb down forcing him to pitch. The rb has AT LEAST 8 yards if he continues towards the side line, but for some reason tries to spin inside two defenders and loses two yards.The CPU definitely does a better job running the option than in 12. However, the defensive pursuit to the outside basically negates all possible positive gains on the speed option for the CPU. Hopefully sliders can help tweak the outcome of the final play because it was run perfectly until the back decides to try and spin past two defenders rather than just continuing his momentum and taking the play to the outside. That being said, the running back AI as a whole needs to be tuned.
|
|||||||||||||
|
5:05 - a defensive tackle pursues flat down the line to tackle an A-back behind the line of scrimmage on an option pitch.
How many times has that happened in history?
(Hint: zero)
How many times has that happened in history?
(Hint: zero)
That "speed option" play - GT's first in this video - needs to go.
Excellent breakdown at the end of Page 1.
The last play is frustrating for the stated number of reasons, but also fascinating for one big reason - there's no pitch read.
The End is the dive read. The next man outside of him is the Corner. The QB pitched off a missed block of a MLB/slid-over-OLB... that guy is NOT a pitch read.
That's a DREAM situation for a spread option/flexbone team. I'd tell my QB to pull & pitch all day on that when I was coaching. Defensive pursuit is too quick for that in this game, however, and the pitch relationship is still off.
Excellent breakdown at the end of Page 1.
The last play is frustrating for the stated number of reasons, but also fascinating for one big reason - there's no pitch read.
The End is the dive read. The next man outside of him is the Corner. The QB pitched off a missed block of a MLB/slid-over-OLB... that guy is NOT a pitch read.
That's a DREAM situation for a spread option/flexbone team. I'd tell my QB to pull & pitch all day on that when I was coaching. Defensive pursuit is too quick for that in this game, however, and the pitch relationship is still off.
Seeing Clemson's offense in this vid and WV in another, the hurry-up offense is still ran too fast. Players line up too quick and hardly anytime at all is ran off.
|
|||||||||||||
|
Man it is depressing seeing the line play sometimes lol. I watched the GT offense and the play at 4:10 (QB scramble) I saw something that just looked wierd. The entire D line stays there trying to collapse a pocket in which there is no QB. They just keep on pushing up field even after the QB takes off with the ball. At least that is what the end keeps doing in the replay can't really see the others but it just looks silly lol.
# 16
Gotmadskillzson @ 06/07/12 04:15 PM
4 option attempts by GT, 3 of them ended up as a lost in the backfield. So how people say that is better then it was in NCAA 12 is beyond me. It is the same result you get in NCAA 12, most option runs by the CPU ending up as a lost.
Might be a combination of defenders acceleration ratings too high and defenders shedding their block too easy on outside runs.
Not a fan of QB that has speed, SLIDING when they should just cut to the outside where there was OPEN FIELD.
When that Clemson QB got sacked, it would have been better if he spun away from the pressure and rolled out. This is something Madden CPU QBs has been doing since Madden 10. Why that logic hasn't made it yet into NCAA series is beyond me.
The option needs some tuning and the defenders well, their acceleration is too high because they cover ground too quick. I can see one or two people on defense with the ability to do it, but not the entire defense.
Might be a combination of defenders acceleration ratings too high and defenders shedding their block too easy on outside runs.
Not a fan of QB that has speed, SLIDING when they should just cut to the outside where there was OPEN FIELD.
When that Clemson QB got sacked, it would have been better if he spun away from the pressure and rolled out. This is something Madden CPU QBs has been doing since Madden 10. Why that logic hasn't made it yet into NCAA series is beyond me.
The option needs some tuning and the defenders well, their acceleration is too high because they cover ground too quick. I can see one or two people on defense with the ability to do it, but not the entire defense.
The first triple option play - where the QB keeps for the nice gain - actually looked okay. Better than what we had last year.
But the strange defensive overspeed and still-broken pitch relationships make option ball pretty dumb looking overall.
I'm sure we can still get yardage as users - I had 400 yards as a QB in one game last year, on Varsity, against the #1 team in the country... - but it'll feel cheap. And A-Backs will be mostly ineffective in the option because of the lack of relationship.
I hope I'm wrong. I really do.
But the strange defensive overspeed and still-broken pitch relationships make option ball pretty dumb looking overall.
I'm sure we can still get yardage as users - I had 400 yards as a QB in one game last year, on Varsity, against the #1 team in the country... - but it'll feel cheap. And A-Backs will be mostly ineffective in the option because of the lack of relationship.
I hope I'm wrong. I really do.
|
|||||||||||||
|
Hopefully roster makers can balance out the rosters/
I'll give EA credit for this: People on here wanted a CPU vs CPU game to see the CPU option and they gave us CPU vs CPU play with Georgia Tech.
# 20
daytarious5 @ 06/07/12 04:37 PM
|
|||||||||||||
|
Post A Comment
Working...