So I get a safety and force a free kick. I pause the game in the middle of the kick to check out what's on TV ... when I resume the game, the camera's locked on to the kicker. Never mind that I'm the receiving team. I'm lucky the game didn't make me fumble the kick so it could recover and return for a TD.
This kind of bug mystifies me. I cannot understand how a game that has been around for this long can be released with so many glaring errors in it. Somebody at EA needs to be fired for this.
A profile of zlionsfan
- zlionsfan
- Indiana, United States
- I like cats. I play a lot of games. Sometimes I develop web-based applications; this keeps my current employer from firing me too often. My favorite color is blue, or maybe green.
Showing posts with label the last person in ea quality control already shut off the lights. Show all posts
Showing posts with label the last person in ea quality control already shut off the lights. Show all posts
Saturday, January 09, 2010
Friday, October 10, 2008
Bugs that make you go "hmmm"
Kickoff return. We force a fumble at the 24 and recover it. But we're called for a face mask. Opponents get the ball ... at our 39.
Yep, that's EA Sports Quality Control for you.
Update: The very next game I played in our online dynasty, I'm up 7-0 and returning a punt. We fumble and it's returned for a TD (ah, the old EA trick of forcing you to give it the ball) ... but wait, there's a penalty! So I already knew what would happen, and sure enough, we got the ball on their side of the field.
I'm not saying I did this on purpose, but we won 41-12. It was 24-12 and we could have run out the clock, but this was more fun: TD, then we ran back an INT for another one, then we ran an INT to the 11 and kicked a FG as time expired.
Yes, it was for the Bucket. :)
Yep, that's EA Sports Quality Control for you.
Update: The very next game I played in our online dynasty, I'm up 7-0 and returning a punt. We fumble and it's returned for a TD (ah, the old EA trick of forcing you to give it the ball) ... but wait, there's a penalty! So I already knew what would happen, and sure enough, we got the ball on their side of the field.
I'm not saying I did this on purpose, but we won 41-12. It was 24-12 and we could have run out the clock, but this was more fun: TD, then we ran back an INT for another one, then we ran an INT to the 11 and kicked a FG as time expired.
Yes, it was for the Bucket. :)
Thursday, August 21, 2008
Bug o' the day
If you get sacked by someone coming directly toward you, your throwing hand and the ball will magically pass through his body. When the ball comes out the other side, surprise! It's made contact with a player and is knocked free.
I'm sorry. I think that if my QB can stick the ball through an onrushing defender, he gets to keep it.
I'm sorry. I think that if my QB can stick the ball through an onrushing defender, he gets to keep it.
Saturday, August 16, 2008
Bug o' the day
This one is bad.
When an offensive player is near you, he can automatically engage you (in a blocking stance) no matter where he is with respect to you, and you must break free of the block before moving on.
Situation: leading Kansas 6-3, third-and-6 at our 8. Toss play to the right. I cut inside the receiver as I see it's a run and move to cut off the RB. As soon as the RB catches the pitch, I turn away from the RB, who is in front of me and slightly to my left, and move to engage the WR, who is still behind me and to my right! Turning so my back is completely to the play I had just successfully identified. To make matters worse, even though I want to get to the ball carrier who is behind me, I am stuck on the guy in front of me. Naturally, because I'm the CB, no one has a pursuit angle and the RB scores easily.
What is this crap? Offensive players carry mind-control rays that prevent you from moving in the direction you want to move? No wonder it's so hard to play defense in this game.
Congratulations, EA, you've crapped all over yet another successful franchise.
EA Sports. It's not in the game, we put it there because we don't test our games any more.
When an offensive player is near you, he can automatically engage you (in a blocking stance) no matter where he is with respect to you, and you must break free of the block before moving on.
Situation: leading Kansas 6-3, third-and-6 at our 8. Toss play to the right. I cut inside the receiver as I see it's a run and move to cut off the RB. As soon as the RB catches the pitch, I turn away from the RB, who is in front of me and slightly to my left, and move to engage the WR, who is still behind me and to my right! Turning so my back is completely to the play I had just successfully identified. To make matters worse, even though I want to get to the ball carrier who is behind me, I am stuck on the guy in front of me. Naturally, because I'm the CB, no one has a pursuit angle and the RB scores easily.
What is this crap? Offensive players carry mind-control rays that prevent you from moving in the direction you want to move? No wonder it's so hard to play defense in this game.
Congratulations, EA, you've crapped all over yet another successful franchise.
EA Sports. It's not in the game, we put it there because we don't test our games any more.
Sunday, August 10, 2008
Strategy flaws o' the day
Legend mode, we're Missouri, 4-1 playing at 5-0, top-ranked Texas. Trailing 16-7 at halftime, we close to 16-14 in the third quarter, then force a fumble on a screen pass and return it to the 5. Three plays later, we score ... but then the stupid computer goes for 2. With a spread offense. Why? Because it's EA. When you're leading, especially on the road, you get the sure points. Make the opponents chase. Of course we miss, and it's 20-16. (Earlier in the quarter, we decide to punt on fourth-and-1 from the 31 instead of going for it or trying a 48-yard field goal with the best kicker in the country. Yet more stupidity.)
So on the ensuing drive, we have a great goal-line stand (thanks in part to a great play by me, crashing through the line and chasing down the RB for a one-yard loss on third-and-1), so we take over at the 5. 3:31 to play.
What do we do? Three straight plays out of the shotgun. Freaking morons. And on top of that, the punter kicks it straight out of bounds. So the three-and-out we force doesn't do much good, as they hit the FG to make it 20-19.
2:10 to play. What formation? Spread, of course, and of course we're running the ball. QB gets hurt on the first play, dislocated ankle, out for 10 weeks. Did I mention he's the backup? The third-string QB comes in, hands off once and throws a terrible screen pass, we punt. They convert on the short drive, field goal, 22-20.
However, the game's not over. The bug where the clock doesn't run on kickoff returns comes into play again, and we get one more play. Oddly enough, the third-string QB fails to throw a touchdown pass and we lose.
EA's playcalling is absolutely terrible. Don't run out of the spread. Run out of a running formation.
So on the ensuing drive, we have a great goal-line stand (thanks in part to a great play by me, crashing through the line and chasing down the RB for a one-yard loss on third-and-1), so we take over at the 5. 3:31 to play.
What do we do? Three straight plays out of the shotgun. Freaking morons. And on top of that, the punter kicks it straight out of bounds. So the three-and-out we force doesn't do much good, as they hit the FG to make it 20-19.
2:10 to play. What formation? Spread, of course, and of course we're running the ball. QB gets hurt on the first play, dislocated ankle, out for 10 weeks. Did I mention he's the backup? The third-string QB comes in, hands off once and throws a terrible screen pass, we punt. They convert on the short drive, field goal, 22-20.
However, the game's not over. The bug where the clock doesn't run on kickoff returns comes into play again, and we get one more play. Oddly enough, the third-string QB fails to throw a touchdown pass and we lose.
EA's playcalling is absolutely terrible. Don't run out of the spread. Run out of a running formation.
Sunday, August 03, 2008
What he said
Genius.
He explains many of the things I dislike about NCAA 09 much better than I could, and his key point is right on the money: EA made such a mess of the AI defense over that unless you're great at NCAA 09, you're screwed, because you will get no help at all.
In fact, I agree so much I'm registering on those boards just to say so.
He explains many of the things I dislike about NCAA 09 much better than I could, and his key point is right on the money: EA made such a mess of the AI defense over that unless you're great at NCAA 09, you're screwed, because you will get no help at all.
In fact, I agree so much I'm registering on those boards just to say so.
Bug o' the day
This is a fun one. Legend mode, Alamo Bowl against Michigan, we force a punt. Coach finally has me on the punt return team (but not returning, yet). I cover my guy, but realize the guy on the right side is coming in untouched. I miss him and he forces a fumble, but I'm right there. I scoop it up and run it for 13 yards. (Of course, the camera doesn't switch. The camera angles are one of the worst things about this game, compounded by the fact that you can't choose them. at all. EA, this is the 21st century; 21st century, this is EA. But that's not the bug.)
The Super Sim pbp shows the returner, the guy who fumbled it, as having a 13-yard return.
Um, no.
On top of that, the stats do seem to show his return correctly (should be 1 return for 0 yards), but don't show me recovering the fumble or returning it for 13 yards (which is how my yards should be shown).
At this point, I believe no one at EA even bothers to verify stats in these games. Sure, some of these situations are unusual, but a company EA's size should have a large enough testing team to see some of these events, and there's no excuse for recording or announcing stats improperly, not when the NCAA's entire set of rulebooks (for all sports) are available on line for free.
The Super Sim pbp shows the returner, the guy who fumbled it, as having a 13-yard return.
Um, no.
On top of that, the stats do seem to show his return correctly (should be 1 return for 0 yards), but don't show me recovering the fumble or returning it for 13 yards (which is how my yards should be shown).
At this point, I believe no one at EA even bothers to verify stats in these games. Sure, some of these situations are unusual, but a company EA's size should have a large enough testing team to see some of these events, and there's no excuse for recording or announcing stats improperly, not when the NCAA's entire set of rulebooks (for all sports) are available on line for free.
Monday, July 28, 2008
Bug o' the day
This time, it's in online play. (Buggy as hell, not too laggy, well, except for today.) It's a conference game. I'm Purdue, he's Ohio State, and you can't really throw slants or drags if there's a defender anywhere in the vicinity, and my receivers are all slow guys, so I'm screwed, but we're pretty close early on.
Then I force a third-and-long, and he has to chuck the ball deep to a receiver who's a good three feet out of bounds when he catches the ball. Incomplete pass, fourth down, so he lines up to punt ... but wait! The booth is reviewing the call. (At least I think it was the booth. It could have been my opponent, I didn't check to see if he had any challenges left.)
They reverse the call. I didn't pause the game to check it myself, thinking it would show up in the highlights at the end.
Ha. Not quite. The play is missing. Completely.
If that isn't a steaming pile of <earmuffs>bullshit</earmuffs>, I don't know what is.
It didn't cost me the game, of course, but it was one hell of a swing, considering that he drove down and scored a TD to take a seven-point lead, and the next time I scored was a field goal as time expired.
<earmuffs>Fuck</earmuffs> EA.
Then I force a third-and-long, and he has to chuck the ball deep to a receiver who's a good three feet out of bounds when he catches the ball. Incomplete pass, fourth down, so he lines up to punt ... but wait! The booth is reviewing the call. (At least I think it was the booth. It could have been my opponent, I didn't check to see if he had any challenges left.)
They reverse the call. I didn't pause the game to check it myself, thinking it would show up in the highlights at the end.
Ha. Not quite. The play is missing. Completely.
If that isn't a steaming pile of <earmuffs>bullshit</earmuffs>, I don't know what is.
It didn't cost me the game, of course, but it was one hell of a swing, considering that he drove down and scored a TD to take a seven-point lead, and the next time I scored was a field goal as time expired.
<earmuffs>Fuck</earmuffs> EA.
Sunday, July 27, 2008
Sideline, shmideline
Today's NCAA 09 bug of the day: a receiver can go out of bounds, run out of bounds for as long as he likes, and then come back in bounds and catch the pass. No problems with that at all.
Of course, we know differently. On page 80 of the 2007 official rules, available here, we see Rule 4-1-2-1-a:
Most decent college football fans know this. EA, apparently, does not. No surprise.
Of course, we know differently. On page 80 of the 2007 official rules, available here, we see Rule 4-1-2-1-a:
A player or an airborne player is out of bounds when anyAnd on page 102, we see Rule 7-3-4:
part of his person touches anything, other than another player or game
official, on or outside a boundary line (A.R. 4-2-1-I and II).
ARTICLE 4. No eligible offensive receiver who goes out of bounds during(Note that it's okay if you're forced out and try to come right back in. Running out on your own = ineligible to touch the ball first.)
a down shall touch a legal forward pass in the field of play or end zones or
while airborne until it has been touched by an opponent or official (A.R.
7-3-4-I-III).
Most decent college football fans know this. EA, apparently, does not. No surprise.
Saturday, July 26, 2008
Dumbest thing I have ever seen
Halftime of the BCS National Championship game. We come out for the second half ... and the ball is spotted at the 30 for a play. We line up. The ball is "snapped", but instead of a play being run, the screen says "KICKOFF", which doesn't seem to matter for the players. They are running around endlessly, which is a big fucking joke, because now I'm going to have to restart the game.
I don't know that I've seen bugs in NCAA games bigger than this one. Well, except for the one a few years ago where if you tried to run a hurry-up offense late in the game, it would crash and you'd have to restart the game.
I know, I'll check on the status of our online dynasty. Oops, the servers are down again, please try later.
EA = teh suck.
I don't know that I've seen bugs in NCAA games bigger than this one. Well, except for the one a few years ago where if you tried to run a hurry-up offense late in the game, it would crash and you'd have to restart the game.
I know, I'll check on the status of our online dynasty. Oops, the servers are down again, please try later.
EA = teh suck.
Canada time?
Apparently EA thinks that Canada uses a different calendar than the US, which is kind of odd considering that EA actually has a studio in Canada ... but anyway, today's NCAA 09 bug is a fun one. I'm simming through the bowls in Legend mode prior to the BCS title game, and I noticed that while the scores were flashing by (because they don't display slowly as you'd think they would, you know, so you can actually watch them), I saw what I thought was Western Michigan-Notre Dame. (Yes, in video games, Notre Dame doesn't get favorable treatment ... it's more like the way things should be.)
See, the thing is that they're playing in the International Bowl in Toronto, and as we all know, that's not played until the 5th. It's still December in the game. So I check the results, and sure enough, it simmed already. (Western won, 34-20. Ha ha ha ha ha. Guess video-Weis couldn't tape Western's signals.)
That's a little worse than the typo about the Big 12 title game. (It kept telling me we were invited to play in the Big 12 title game on 12/6, even though it was telling me on the 8th and the game is actually the 13th.) But it's all right, I'm sure EA knows about it and will fix it in the patch they'll be issuing before the season begins.
Yeah, I didn't think so. I didn't believe it either.
Update: I think it's an anti-MAC bias. The GMAC Bowl sims a week early as well. Now, I don't think those bowl should be played when they are, but the fact is, they are played after January 1, and they should sim then. After all, isn't that EA's rationale for excluding playoffs from NCAA football games the last 10 years or so?
See, the thing is that they're playing in the International Bowl in Toronto, and as we all know, that's not played until the 5th. It's still December in the game. So I check the results, and sure enough, it simmed already. (Western won, 34-20. Ha ha ha ha ha. Guess video-Weis couldn't tape Western's signals.)
That's a little worse than the typo about the Big 12 title game. (It kept telling me we were invited to play in the Big 12 title game on 12/6, even though it was telling me on the 8th and the game is actually the 13th.) But it's all right, I'm sure EA knows about it and will fix it in the patch they'll be issuing before the season begins.
Yeah, I didn't think so. I didn't believe it either.
Update: I think it's an anti-MAC bias. The GMAC Bowl sims a week early as well. Now, I don't think those bowl should be played when they are, but the fact is, they are played after January 1, and they should sim then. After all, isn't that EA's rationale for excluding playoffs from NCAA football games the last 10 years or so?
Wednesday, July 23, 2008
EA r dum
I guess I'll bring myself to post a full review of NCAA 09 at some point, as much as I dislike the thought, but I can't deal with it right now. There are, however, some things that are so bad (minor though they might seem) that I can't help but share them.
Take coin tosses, for example. What's supposed to happen is that the team that wins the toss picks first in the first half, and the team that loses the toss picks first in the second half. Most games don't do it that way, which isn't that big of a deal unless the weather really sucks: they just make you switch sides every quarter, so one team chooses kick/receive and the other effectively chooses the wind for all four quarters.
I lost the toss, and the AI took the ball, so I wanted the wind in my face, figuring I'd get the wind at my back in the second and fourth quarters. It worked great in the first half: I kicked a 46-yard field goal as time expired to take the lead.
In the second half, I have a three-and-out, and so I get ready to punt ...
... with the wind.
Um, no. Either we switch sides, or I get to pick first and the AI picks second, and because you didn't let me pick, then we switch sides, and I'm heading into the wind.
EA = teh sux0r.
Take coin tosses, for example. What's supposed to happen is that the team that wins the toss picks first in the first half, and the team that loses the toss picks first in the second half. Most games don't do it that way, which isn't that big of a deal unless the weather really sucks: they just make you switch sides every quarter, so one team chooses kick/receive and the other effectively chooses the wind for all four quarters.
I lost the toss, and the AI took the ball, so I wanted the wind in my face, figuring I'd get the wind at my back in the second and fourth quarters. It worked great in the first half: I kicked a 46-yard field goal as time expired to take the lead.
In the second half, I have a three-and-out, and so I get ready to punt ...
... with the wind.
Um, no. Either we switch sides, or I get to pick first and the AI picks second, and because you didn't let me pick, then we switch sides, and I'm heading into the wind.
EA = teh sux0r.
Subscribe to:
Posts (Atom)