NCAA Football 13 Title Update #2 Available Now, Post Your Impressions Here

[Polo Bandit]

Quote: Originally Posted by Lil Worm

I would like to know if freezing is still an issue after the update. I can't make myself stop mashing the A button at the end of quarters and beginning of gametracks to keep it from freezing.

I had to start my Dynasty over. It was working fine before the patch, now won't get past the loading screen after I select playbooks and uniforms. I'd never had any freezing issues before yesterday.

[BA2929]

Quote: Originally Posted by PowerofRed25

There is a reason I can run a play in the 4th quarter with 7 seconds on the clock, quickly huddle, call a field goal and kick it was 3 seconds left and win a football game. Now you tell me what is more realistic. Me getting my FG team on the field in 4 seconds or me having to stand at the line of scrimmage while my WR's look like fools?

I can't tell which way you're trying to say is more realistic, but if there were 7 seconds left there's no way a team even tries to run it's FG team out there to kick a FG.... unless it was 4th down and they had no TOs left. Even then, I highly, highly doubt they get them set in time to get a kick off.

So, I'd go with "me having to stand at the line of scrimmage while my WR's look like fools". Because, being a Kansas fan, I've seen that happen before in real life. Not even getting a last play off because guys were confused or couldn't line up fast enough.

[PowerofRed25]

Quote: Originally Posted by niles08

I haven't had a chance to test it yet, but someone back in this thread mentioned that the no huddle "I can't hear you motion" had to do with your players awareness and younger players especially. If this is the case then it makes sense to me, however I haven't messed with it, so if someone wants to try it out and confirm or deny then that'd be wonderful.

It is all players. Senior RB's right next to my QB do it just as much as Sophomore receivers on the far numbers.

Quote: Originally Posted by TheShizNo1

I was somewhat w/ you until I played it. Every single play should not take 7 seconds b/c the HB RIGHT NEXT to the QB can't hear. Especially at home. I should also not have my WR's coming in b/c they can't hear my QB wanting to spike the football. Guys, I understand what you're saying. No huddle shouldn't be 100 mph every snap. But you have to be realistic here and look at what people are saying. No one is saying it should be right as the ball is placed, we're saying it shouldn't take that long every time. Especially at home, when you quiet the crowd. What's the point of HFA at that point then? It annoys me that some of you think that this was intended, ESPECIALLY when the CPU DOES NOT have this issue. Repeat, the CPU DOES NOT have this issue. It is a bug. If you like the bug, so be it, just please stop calling it a fix. Also, let's not forget EA breaking no huddle last year w/ their second patch.

Agree. None of this would be a problem if it was intentionally implemented accurately to keep things realistic. But it is very clearly a bug. Just look what happens when you call a Shotgun Tight after running no huddle, the WR's will do the animation morphing through the offensive line.

This is just stupid and very clearly a bug. I don't know how people can argue that. It is not intentional, it is NOT realistic (not even a LITTLE) and it is incredibly frustrating.

And for people acting like this helps online play, I would RATHER my opponent be in no huddle. They are usually limited in the plays they select, their players fatigue faster and thus are more prone to mistakes. Now it is faster to huddle and call a play. That should NEVER happen. If they wanted to FIX the no huddle to slow it down, they need to install a universal accelerated clock.

Quote: Originally Posted by xcanadaman9x

Here's a question for all of you. If the animations were the ones that show everyone looking to the sidelines instead of the "can't hear you" ones, would it be ok?

Not if it was buggy like it is now. If it was intentional and didn't have the stupid problems like it happening during a spike or taking 6 seconds every play, then yes, it'd be great.

Quote: Originally Posted by Phobia

I am sorry but the guys saying it is realistic to be able to run no huddle over and over with no time coming off the clock are flat out wrong. I can supply multiple videos showing that this is NOT fact in football, whether college or pro. Granted there have been instances where teams really hustled to do that once a year, but the average no huddle gameplan is going to run clock. Calls have to come in, line has to be given call, and so no. Granted I agree with yall I think it is a bug that was implemented, but it does not take away the fact it remains more realistic. The ONLY unrealistic part is the spike ball no huddle

Quote: Originally Posted by Phobia

I want to remove this "gamey" stigma some of you are following. Just because a team is at home does not mean they are NOT affected by the crowd noise, that is asinine to believe just because they are at home they hear everything perfect while the defense is over come with loud noise. Bottom line BOTH teams are affected.

You want to remove this gamey stigma? THIS IS A GAME. When you have 5 minute quarters to do things, I should not have to wait 6 seconds after EVERY no huddle play to get to run the next one. If someone ran no huddle for an entire 20 minute game, it is conceivable that they will have spent 3 or 4 minutes just standing at the line of scrimmage waiting for their WR's to "hear" the play. That is an extreme example that assumes every play was inbounds and the clock was running, but you see the point.

Please do not even attempt to defend this as realism. It is insulting to anyone who has played or watched football. I cannot think of a time where crowd noise impacted what the WR does. Not one. No huddle teams use hand signals or boards to give formation and assignment to WR's, they know the play at roughly the same time the previous one ended. In the VERY RARE event they forget, they yell "CHECK CHECK" at the WR lined up nearest them, who gives them the call OR they simply check the sideline. Every true fast paced no huddle team I've seen, Oregon included, has their coaches and GA's continuing the signals until the snap. For this very reason.

In the event of an audible or hot route, it is always a signal. That isn't even just for no huddle, I have never once seen a team use verbal signals to WR's. Not in 100,000 seat stadiums, not in 15,000 seat stadiums. Always hand signals or automatic check downs (two plays in the huddle, automatic sight adjustments, etc).

If you want to slow down the no huddle in the game, fine, but that requires the clock and the huddle system to be addressed as well. There is no argument to tell me this is realistic as long as I am able to huddle and kick a field goal in 4 seconds while if I go no huddle my WR's stand there glitching out while the game ends.

This is a bug, plain and simple. I'm really curious where all of you people defending this were when it never existed, I didn't see all that many complaints about no huddle before. But now look. All of a sudden this BUG happens and you think it is amazingly realistic.

If you wanted something like this implemented, it needs to be tied to the tempo coaching adjustment:

Conservative Tempo: Team jogs to LOS, sets, all skill players look at sideline for play, re-set and go. Minimal loss of fatigue.

Normal Tempo: Same as conservative but team moves and sets at a much quicker pace. Average loss of fatigue.

Aggressive Tempo: Team runs to LOS, sets and runs the play as soon as it is called. Maximum fatigue loss, which would only allow this to be run 2-3 plays in a row before significant fatigue sets in for some guys. Ideally the fatigue would slow down the pace at which the team gets set as well as cause false starts and other things, but I'd settle for fatigue.

THAT is realistic. Not whatever the heck this random bug is.

[PowerofRed25]

Quote: Originally Posted by BA2929

I can't tell which way you're trying to say is more realistic, but if there were 7 seconds left there's no way a team even tries to run it's FG team out there to kick a FG.... unless it was 4th down and they had no TOs left. Even then, I highly, highly doubt they get them set in time to get a kick off. So, I'd go with "me having to stand at the line of scrimmage while my WR's look like fools". Because, being a Kansas fan, I've seen that happen before in real life. Not even getting a last play off because guys were confused or couldn't line up fast enough.

The answer is neither is realistic. Of course a FG isn't realistic in that situation, yet I've gotten it down to the point where I can huddle, call a FG and have it in the air in 4 seconds. I did it again last night. 0 timeouts before the end of the half and 10 seconds on the clock, I just ran the football, huddled, called a FG and kicked it with time to spare. Not realistic in the slightest, yet it exists and doesn't draw ANY ire from the people that are defending this bug.

Confusion always happens, especially on teams that don't run no huddle often. When they get to it, they suffer. If they want to implement something to slow down the no huddle, great, I am all for it. But it has to be in conjunction with a bunch of other fixes, not as an isolated bug in the code.

[BA2929]

You can pretty much run a "no huddle" faster in this game by actually calling a play in the huddle then sprinting your guys up to the LOS. I rarely, if ever, use No-Huddle unless I want to keep the same defense on the field for the other team.

[superjames1992]

Did they fix the screen sack issue?

[bucknut7]

I actually love the way the no-huddle is now. Before you would call the play, and your players would automatically know what the play is. What, are they telepathic? The quarterback should have to check the play at the line and that takes some time. The idea of a no-huddle offense is to make the defense keep the same players on the field and wear them out, not necessarily to run play, after play, after play as quick as possible.

[Scott]

Quote: Originally Posted by superjames1992

Did they fix the screen sack issue?

the CPU now calls fewer screens.