NCAA Football 13 Title Update Arrives July 31, Title Update #2 in Late August

[87Birdman]

Quote: Originally Posted by shttymcgee

The responsiveness of those animations deal with whether or not the player is looking at the ball. The user should not be able to swat, imo, if he is not looking at the ball. They seemed smoother to me when the db had his head turned, but when in a trail position is when you see the delay.

That isn't true to me. The times I see the most unresponsiveness from the system is when I am standing there looking at the ball and go to pick it my guy doesn't jump, and then they get a huge gain because of it. I actually have better luck running up under the ball then waiting for the ball to get there. I don't know if it is when your strafing the player just looks at the ground or what but that usually is where it is the worst for me, and that is when it should be an easy pick.

[nortobc]

Quote: Originally Posted by jsou4646

FIX THE FG LOGIC ON THE HEISMAN LEVEL!

This needs to be fixed and there is absolutely no reason this has not been fixed yet. Ridiculous. 2 or 3 50+ yard FG attempts per game can turn a game around. I've always said that this defect is responsible for lots of CPU losses.

[Skulletor]

Quote: Originally Posted by der juicen

Is it impossible for us to be glad they are patching the game. I am very surprised at the thinly veiled outrage over them patching. It really is never enough. It takes time to patch and, well, they are probably going down a set list of problems by importance. Freezing issues first, etc., etc.

You don't get a gold star for screwing up and fixing your mistakes. Get it right the first time, invest in QA

[Hitokiri Jinchu]

I understand improving zone coverage but at the same time ive seen to many dbs covering their man on the other side of the field not looking back and as soon as i throw it to the other side of the field (while still in throwing motion) theyre already converging on the that reciever. Im not trying to complain cause I enjoy this year alot more than last year but i dont want this becoming like last year when u could hardly throw the ball due to db knowing routes better than wr,. I would also hope in a future update they fix the blocking logic as well i can call in all out blitz and it seems like they get picked up by the cpu but when the cpu blitzes only 2 my line goes ******** and they come thru untouched same as run blocking. Overall tho ive had more fun with this years game in only a couple of weeks then in an entire year of last years.

[Major9]

Quote: Originally Posted by shttymcgee

The responsiveness of those animations deal with whether or not the player is looking at the ball. The user should not be able to swat, imo, if he is not looking at the ball. They seemed smoother to me when the db had his head turned, but when in a trail position is when you see the delay.

Not the case...95% of the time that i have perfect position and my DB is looking at the ball he still will not swat at the ball.

[thelasthurtknee]

Quote: Originally Posted by Skulletor

You don't get a gold star for screwing up and fixing your mistakes. Get it right the first time, invest in QA

dont forge that qa removes anywhere from 200,000 to 300,000 issues a year for ncaa. they are in Baton Rouge doing it at huge new facility. So it could be much worse. but for our sake it could of been better also.

[Buckeye Country]

Are they going to fix the CPU screen that gets blown up everytime? Anyword on that?

[JayD]

Quote: Originally Posted by der juicen

Thanks for you important information. I will really, really miss you. I'm torn up inside, really.

I love people who think they have to come back with a snarky line if they don't agree with the statement.