Why wasn't field degradation put into the 2nd patch?

[Radioactiveman]

Quote: Originally Posted by doctorhay53

Who cares? They had too much other stuff to fix. I don't care if the field looks worse over the course of the game that much anyway. I'm usually too busy trying to win.

Ditto...field degradation is the least of my worries....non issue as far as I'm concerned...I'd kill to see a cpu pass miss the mark every once in a while...

[rckabillyRaider]

Quote: Originally Posted by Majoniak

This was posted late last week on pastapadre.com The work on the patch has been completed and is being submitted to MS and Sony on Tuesday. This puts the time frame to expect it to arrive still at least a few weeks out. Continue on to read the full list of issues and workarounds. 1. Kicking play disconnect: If two opponents play a game with two different camera angles, in any situation where a game winning or tying kick was to be made, a disconnect could occur. “ActionCam” forces the game to go into slow-motion to add drama to these late kicks, but unfortunately the Classic camera does not, thus forcing the “disconnect”. This has been fixed…all cameras can still be used as well. Workaround until the patch: If possible, ensure that you and your opponent have the same camera type chosen before starting an online game. 2. Stability issues in the play call / halftime highlights / postgame highlights screens (especially in Franchise mode after training games): This was a hard one to track down as not everyone was seeing it , we did find the issue however with some Instant Replay / cache corruption, and have a fix ready for patch 2. Workaround until the patch: Save and re-boot after any point where you have entered the game. We learned that the likelihood of this issue appearing is magnified after multiple loads into and out of the game engine. From what we’ve seen so far, people that have tried playing only one game at a time (or even one Franchise training session at a time), and saving/rebooting afterwards, have had zero crashes. 3. Stability issues with Madden IQ end of game popup: This has been fixed. Workaround until the patch: Always choose “No” at the Madden IQ end of game popup. 4. “WR direct snap” exploit: Cheesers found an exploit to direct snap to a WR for easy short yardage gain. Not only are we fixing this play (i.e. we aren’t removing it), we are also going to be re-setting records for anyone with a winning record that has been found to be using this play. 5. Franchise Progression / Regression (or lack thereof): The lack of higher numbers was a tuning value that I think everyone agreed was just too low. This has been juiced up so you should see more realistic progression now. 6. Edited players don’t progress: Players were not progressing after their jersey number (or pretty much any other attribute). This has been fixed. 7. Stability issue when exiting Madden ‘93 in CE version: This has been fixed. 8. Deep ball glitch: Some enterprising gamers found a way to throw a deep ball while crossing the LOS and hit a receiver wide open at a decent rate. We addressed this by making sure the DB will no longer break on the ball when the QB crosses the line while throwing. 9. CPU running out of bounds: This bug appears when the CPU tries to switch hands while running to the sidelines. This is fixed for patch 2. 10. Penalty sliders ineffective: A common complaint from the hardcore community was the lack of effect from the penalty sliders. We increased these substantially for patch 2. 11. Field degradation: Another common complaint was the lack of field degradation. Our effect was very subtle, which was also getting overshadowed by our lighting and post effects, so we increased this effect for the patch. 12. Stability issue with the Eagles and a full ring meter: We found and fixed a rare issue where the gamer could run into stability issues while using the Eagles in mini-game with a ring meter that was completely full. 13. Play call screen hitch: We found and fixed a bug that was causing a noticeable hitch when exiting the play call screen 14. Prevent Defense issue: We found and fixed an issue where defenders sharing a deep zone/prevent assignment would loosen their coverage (because they thought the other guy was covering for them), which allowed the receiver to get behind them even though they were in Prevent. 15. Brett Favre stats: With the late addition of Brett Favre, we were not able to get his Career and Season statistics into the game for the roster update. This has now been added for patch 2. 16. Defensive Preplay Mis-cue: We found and fixed an issue where defenders would leave their man wide open in a Cover 3. 17. CPU quick-snap: A very common complaint on the forums was the speed at which the CPU snapped the ball. We added a random length of time (no less than 5 seconds) for the CPU to wait and even make pre-play adjustments. 18. Online playbook switch: We found and fixed an issue where playbooks were re-setting to the defaults after the playbook select popup was closed. Check out Number 11. It was adressed.

thats for Madden homie. And the reason it can be addressed in that patch is because the game already has it built in. It was just being covered up by some lighting junk. Not sure if NCAA even had it built in, in the first place?

[FearTheTurtle]

It seems that in NCAA the fields are untouchable.

No team-specific endzone art for bowl games (that's a huge oh c'mon) and no field degradation

It's the little things that make the game...and these two omissions make me sad in the pants

[Comrade Kirk]

Quote: Originally Posted by Majoniak

11. Field degradation: Another common complaint was the lack of field degradation. Our effect was very subtle, which was also getting overshadowed by our lighting and post effects, so we increased this effect for the patch.

Field Degradation was already in Madden. The 2nd patch for Madden is fine tuning it so that its more noticeable. They probably couldn't add this to NCAA with just a patch. There would be a lot more coding required than what a patch could handle.

[Tig5309]

Adam has checked on this and said that it's in the game but not as dominant as most of us would expect IMO. I did play a game in the rain last night that showed some brown field wear between the hashes.

[crques]

This is a definite feature that I hope gets fixed for next year's game. If I'm playing on natural grass in the pouring run I want to see some wear and tear on the field dammit.

[yankees022]

Quote: Originally Posted by fatheifer

I mean, c'mon.

Stop crying like a baby and play the game. So what if the field doesn't get worse over time, it's a friggin video game. Get over it.

[crques]

Quote: Originally Posted by yankees022

Stop crying like a baby and play the game. So what if the field doesn't get worse over time, it's a friggin video game. Get over it.

It adds another dimension to the game and it should be included, especially since past versions have had it. What's wrong with wanting a more realistic game to play considering the prices we pay for these things?