Madden NFL 10 FAQ - Part 1

[Disqo]

Quote: Originally Posted by TombSong

You dont really have to be a "glitch hunter" to see a lot of the problems going on in the game. The game has problems as evidenced in vids and acknowledged in Ian's just released blog. I am glad Ian has thick skin and has taken all the bullets shot at him over the past few months. I am also glad he does listen to these same people you like to point out as whiners. Because if he only listened to people like you, we would all be stuck with a game full of obvious flaws that we would have to ignore for another year. Its clear YOU like the game as is based on YOUR post history. No one gonna call you a name for that though. Glad for you. However some of us got issues and have pointed them out. That IS the feedback Ian was looking for. I will agree that the personal attacks on Ian and each other have to stop.

I agree with your post. I don't understand how anyone can insinuate that the flaws in Madden have only been found due to people excessively looking for them. The problems with the game are plain for everyone to see, which is why the dev team is trying to iron them out.

[edgarallanpoe]

Coach mode needs an important feature. Primary reciever orange route pre-snap adjustment is very essential in coaching an I do hope they can patch it.

[Bears_16_and_0]

Aww no answer on what exactly the slide protection 'aggressive' actually does =( Anyone know?

[Guigsdaddy]

what do you think the chances of auto replay frequency being fixed is?

[tyler289]

Someone may have answered this in this thread, but I didn't notice it in Ian's videos: will they be fixing the IR stuff? Right now, if you put a guy on IR it doesn't free up a roster spot.

[bomza]

Really, really outstanding and comprehensive videos.
Thank you Ian.
I haven't seen community response from EA like this EVER.

That being said... (you knew it was coming)

Some of the more important issues I brought up that affect game play were not mentioned. So maybe nothing can be done about them this year? I don't know.

The two most egregious are...
1) Blitzers with a clear shot at the QB inexplicably changing directions and not sacking the QB
(I think some plays are programmed as play action that shouldn't be - I have a saved example)
2) Ball morphing through the receiver to be intercepted by DB standing behind him

These things don't happen all that often, but when they do I want to pull my hair out, throw the controller, etc. Maybe nothing can be done about them this year, but at least I'd like to know if they are being researched or not. Some other things that weren't mentioned that might not be too difficult to add...

1) A way to save a flipped defensive or offensive audible
(Menu says "Toggle side" but it toggles defense and offense audibles instead)
2) Tweak the ref cut scenes so obvious first downs and TD's don't trigger them, or else have an option like "Fight For The Fumble" to just turn them off
3) Legacy/customizable control configuration
(Or at least the ability to switch RT/LT for sprint and RB/LB for last receiver)

Once again, thanks for the very detailed response Ian, and you deserve to have a better view from your office.

[Dianwei32]

Also, what about the CPU calling so much press coverage? and my WRs inability to beat it? The issue of WRs always releasing to the same side is part of it, but if the CPU calls press coverage (which they do, excessively, even with DBs who have low Press ratings), it's a guaranteed 3-4 seconds before my WRs can get open. I have yet to see a WR beat the press at the line, they always struggle and only are able to beat it because they can push the DB past the 5 yard mark and they're forced to stopp pressing them.

In a game where I run 55-60 offensive plays, I can count the number of times the CPU doesn't call press coverage on one hand (usually 3-4 times). Even with WRs with good Strength (50-60) and great Beat Press ratings (90+) against DBs with 40-50 Strength and 70-75 Press, my WRs cannot beat the press at all.

[leereezy]

all i saw was the basic answers. some stuff being addressed is needed but alot of the main issues will have to be in patch 2.

we are working on that.
we are looking into this.
hopefully we can get it in patch 2.
hopefully madden 11 it will show up.
we are trying to tune it now.
it's touchy and we can't fix it right now.
it's really difficult for our talented guys to fix.
we overlooked that.

sounds like standard marketing questions.
it's not like he actually went indepth as to why things happen.

i think if he did we would really see the mess this engine really is.

why can't we have just go back to 5min qt?

why is it that everytime this dev gets an idea it is always implemented poorly?

whenever they have a remedy to fix a problem it's really boneheaded?

these answers were what i was expecting was not wrong.

plus we have already started talking bout next yr.

another thing, the issues patch 1 fix are booty compared to what u have on patch 2.