re: TD 360 Dynasty 2010 - Year 3 Week 3 - Advance 1/26 @ 7 PM

I don't mind an ocassional scramble but scrambling on every other play is bs. There are certain routes that CANNOT be stopped on scrambles. If the def is bringing th house on a blitz then get out the pocket and move...but don't just take the snap and directly go to scramble.

And legit, i didnt mention it the other night bc i was so pissed i got my arse kicked so bad, but the league voted to disallow run commit except in the red zone. on that fumble i had out of wildcat on the first play you used run commit and i think you used it a few more times. I didnt mind really because i voted we should be able to use it but just fyi when u play the other people.

how are we looking for next advance?

How fricking annoying is this game. Why can't ea fix shite like this. I can understand last year with it being the first but frick no reason for shite like this in year two.

No. Don't save it. I know last year it caused problems. Not sure if that is what caused it but last years dynasty would be really affected if it was saved to anybodys hard drive. Just load it everytime and it seems to work

if you have it saved, simply go in and delete the OD file.

i wont save it but just out of curiousity....wt does saving it have to do with giving people losses?

im not trying to be a arse either, honest question

Why did I get a lose because lsu fan cried because I beat him. I dominated him on offense and only scrambled because he blitzes the house every play. I ran hurry up a play or two just to catch him in his terrible d. I won the game by three stop crying. Looks like you got some cheesing of your own winning the gm somehow and disconnecting last year on me!

Ok, I don't know WTF is wrong with this game, but obviously many people that won last week had the CPU ignore the win, simmed the game instead, and gave you a loss. This happened twice in a row last season for puma with OU, but it seemed to only affect him, and disappeared after those two instances.

All I can find online is this:

LINK

and this:

LINK

quote:

---

From what I have been told, this happens with no set pattern when the user does NOT go into the Dynasty Headquarters and manually set ready to advance. This doesn't happen to everyone, it doesn't happen often but it should be eliminated by choosing Set Ready to Advance.

Hell some users don't know that it even does it to them because the result doesn't change. The easiest way to see that it happens in the dynasty is to go into the scoring summary for each user and look at when the points were scored. We play 7 minute quarters and were seeing TD's at 11:39 in the first. This was the tell tell sign.

We have since all (9 members) been setting Manual ready to advance and have not had a problem since.

---

and

quote:

---

For us this was huge. We had problems in the first 2 weeks of advancing but have since started doing what I mentioned and the problem has not repeated itself.

Also make sure to do this for the offseason recruiting as well. If not you could lose that weeks recruiting. Happened in a different OD that I was in. Guy forgot to set it, and boom the next week he had 0hrs left in his recruiting.

We all played it off as a recruiting violation just to add some fun with it though. We keep track of everything in our 9 man dynasty so it is fun to follow and keeps everyone entertained. We all write articles (or most), clip highlights, and post like a message board main page for each team. That was the big headline, UW gets slapped with a recruiting violation. Everyone loved it.

---

Moral of the story here:

1.) NO ONE save the dynasty file to your HD. It apparently can eff things up for everyone.

2.) ALWAYS set "Ready to Advance" from now on in every facet of the dynasty: Regular Season, Offseason, etc.

Nelly, I suggest we do the same in the 3* to be preventive.

To reiterate new rules:

1.) No run commit outside the red zones.
2.) Pass commit is always allowed.
3.) No "nano-blitzes."

These will be added to the front page.

Sorry to those that received losses. I would fix it if I could.