NDL Forum

Shiftdnb wrote:My game froze at loading screen. Had issue where loading play book exited to team choose screen and had to load again and then it froze. Have video if there is anyone who has an issue with restart.

That won't reflect as a restart. It only counts as a restart if you actually advance into the game past the choose team/playbook portion.

I won't lie, this was the first time I ever thought about intentionally restarting an OD game....it was only for a second, but the thought crossed my mind.

Huge blow for Tulsa today, as star HB Trey Watts, the powerful part of the two-headed monster at tailback, went down on his 12th carry. Having already rushed for 154 yds and a score on the day, fans were waiting for him to return....but he never did, and he won't again this season, as he suffered a torn rotator cuff and will not play again in his junior year. There was worry that he might go pro after the season but those worries may now be gone. He will end the season well short of the Heisman trophy that he had a shot at--in just five games he rushed for 833 yds and 9 touchdowns on just 91 carries. Only 8 of those 91 carries went for more than 20 yds, and he didn't fumble the ball a single time.

Meanwhile his backup, just-as-good but not as powerful, Ja'Terian Douglas came in, and he rushed 10 times for 102 yds.....and then HE went down, only for the game however. His two TDs included a 73 yd scamper to start the second half.

So third string HB Alex Singleton came in. Built like a linebacker at 6'1" and 260, he proceeded to rush for 94 yds on 11 carries and destroyed every defender who tried to tackle him alone. Despite being tied 14-14 at one point, Tulsa rolled 59-21. But the loss of Watts will be felt for a while.

We have advanced, no user games this week and several byes. Will advance again by Sunday night.

Playing Marshall was like playing a fucking lobby game, holy shit.....

Nonstop no-huddle, a QB who would run out of shotgun 5 wide, he took off on 9 of the 44 times he dropped back to pass, would scramble on a bunch of others; just pure cheesy bullshit by the computer.

Too bad Tulsa got the ball with 4 minutes to go, ran it down their throats, 12 play drive leading to a 19 yd FG with one second left.

Big plays of the game:

45 yd run by Tulsa's HB Ja'terian Douglass to tie it at 7-7
Tulsa gets a 92 yd kickoff return for touchdown by Douglass after he breaks a tackle and then outruns the kicker, just seconds after Marshall tied the game at 35-35

jsence2 wrote:Playing Marshall was like playing a fucking lobby game, holy shit.....

Nonstop no-huddle, a QB who would run out of shotgun 5 wide, he took off on 9 of the 44 times he dropped back to pass, would scramble on a bunch of others; just pure cheesy bullshit by the computer.

Too bad Tulsa got the ball with 4 minutes to go, ran it down their throats, 12 play drive leading to a 19 yd FG with one second left.

Big plays of the game:

45 yd run by Tulsa's HB Ja'terian Douglass to tie it at 7-7
Tulsa gets a 92 yd kickoff return for touchdown by Douglass after he breaks a tackle and then outruns the kicker, just seconds after Marshall tied the game at 35-35

Why is that cheesy? Sounds like what a nohuddle spread offense really does, its tough to deal with sometimes but I kinda like that cpu throw different offenses at us now.

fsupenguin wrote:

jsence2 wrote:Playing Marshall was like playing a fucking lobby game, holy shit.....

Nonstop no-huddle, a QB who would run out of shotgun 5 wide, he took off on 9 of the 44 times he dropped back to pass, would scramble on a bunch of others; just pure cheesy bullshit by the computer.

Too bad Tulsa got the ball with 4 minutes to go, ran it down their throats, 12 play drive leading to a 19 yd FG with one second left.

Big plays of the game:

45 yd run by Tulsa's HB Ja'terian Douglass to tie it at 7-7
Tulsa gets a 92 yd kickoff return for touchdown by Douglass after he breaks a tackle and then outruns the kicker, just seconds after Marshall tied the game at 35-35

Why is that cheesy? Sounds like what a nohuddle spread offense really does, its tough to deal with sometimes but I kinda like that cpu throw different offenses at us now.

In the 24 hour dynasty I had to play them on Heisman, what's worse is I played Nebraska and they were a lot better at Marshall at doing it.

We have advanced, great job staying on schedule guys! This weeks user game is...............

(Shift) San Jose State vs (BigMike) Utah State

Next planned advance will be by Tuesday night.

I think Shift is out of town Pen, just a heads up. Hes on auto pilot in mine.

viewtopic.php?f=7&t=28365

buckeye76 wrote:I think Shift is out of town Pen, just a heads up. Hes on auto pilot in mine.

viewtopic.php?f=7&t=28365

Thanks for the heads up, he is now on auto. The mercy rule is 50 in this OD Mike .

fsupenguin wrote:

jsence2 wrote:Playing Marshall was like playing a fucking lobby game, holy shit.....

Nonstop no-huddle, a QB who would run out of shotgun 5 wide, he took off on 9 of the 44 times he dropped back to pass, would scramble on a bunch of others; just pure cheesy bullshit by the computer.

Too bad Tulsa got the ball with 4 minutes to go, ran it down their throats, 12 play drive leading to a 19 yd FG with one second left.

Big plays of the game:

45 yd run by Tulsa's HB Ja'terian Douglass to tie it at 7-7
Tulsa gets a 92 yd kickoff return for touchdown by Douglass after he breaks a tackle and then outruns the kicker, just seconds after Marshall tied the game at 35-35

Why is that cheesy? Sounds like what a nohuddle spread offense really does, its tough to deal with sometimes but I kinda like that cpu throw different offenses at us now.

No, I meant the part about the QB sending guys out from 5 wide, waiting two seconds, and then running w no pass rush

Sounds like a draw, you sure that was what was called?

fsupenguin wrote:Sounds like a draw, you sure that was what was called?

No, he wasn't running draws. Trust me.

The computer learns as the game goes on and adapts. If it has a couple big scrambles early it is going to make the decision to run earlier as the game goes on. You just need to adapt and spy him or set your defense to be aggressive at stopping the scramble on the preplay menu. A spy usually shuts them down though.
I dont think it's cheesy though. I check the attributes before the game so I'm not caught off guard. I dont knock on coach reports either if I play someone with a scrambling qb if they take off a couple times in a game unless it is obvious that's what they planned to do when they called the play. (Sprint rolling). More teams offenses are based off scrambling or balanced qb's now than pocket passers.

Just played Northwestern and they ran hurry all game and had so many QB scrambles. Gotta love the CPU!

OracleHCR wrote:The computer learns as the game goes on and adapts. If it has a couple big scrambles early it is going to make the decision to run earlier as the game goes on. You just need to adapt and spy him or set your defense to be aggressive at stopping the scramble on the preplay menu. A spy usually shuts them down though.
I dont think it's cheesy though. I check the attributes before the game so I'm not caught off guard. I dont knock on coach reports either if I play someone with a scrambling qb if they take off a couple times in a game unless it is obvious that's what they planned to do when they called the play. (Sprint rolling). More teams offenses are based off scrambling or balanced qb's now than pocket passers.

I ran spies, I ran contain, he'd still run around and throw at the last second or take off running. Got to the point where I just gave up trying and just blitzed the shit out of him

jsence2 wrote:

OracleHCR wrote:The computer learns as the game goes on and adapts. If it has a couple big scrambles early it is going to make the decision to run earlier as the game goes on. You just need to adapt and spy him or set your defense to be aggressive at stopping the scramble on the preplay menu. A spy usually shuts them down though.
I dont think it's cheesy though. I check the attributes before the game so I'm not caught off guard. I dont knock on coach reports either if I play someone with a scrambling qb if they take off a couple times in a game unless it is obvious that's what they planned to do when they called the play. (Sprint rolling). More teams offenses are based off scrambling or balanced qb's now than pocket passers.

I ran spies, I ran contain, he'd still run around and throw at the last second or take off running. Got to the point where I just gave up trying and just blitzed the shit out of him

Yep, its fun though, but its crazy cause you start running around waiting for the qb to take off then next thing you know someone is wide open.

jsence2 wrote:

OracleHCR wrote:The computer learns as the game goes on and adapts. If it has a couple big scrambles early it is going to make the decision to run earlier as the game goes on. You just need to adapt and spy him or set your defense to be aggressive at stopping the scramble on the preplay menu. A spy usually shuts them down though.
I dont think it's cheesy though. I check the attributes before the game so I'm not caught off guard. I dont knock on coach reports either if I play someone with a scrambling qb if they take off a couple times in a game unless it is obvious that's what they planned to do when they called the play. (Sprint rolling). More teams offenses are based off scrambling or balanced qb's now than pocket passers.

I ran spies, I ran contain, he'd still run around and throw at the last second or take off running. Got to the point where I just gave up trying and just blitzed the shit out of him

That works too.
A lot of times I'll call a play with a blitzing lb or cb and set them to spy the qb instead. A spy takes away the short passes over the middle too so it you have that going for you as well.

Tulsa and UTEP were tied at 17 at halftime, but Tulsa gets 24 in the 4th quarter to win easily 48-17.

However the win came at a cost--having already lost the top player on the team, the offense suffers another blow as the #2 wideout on the team (85 ovr) goes down with essentially a season-ending broken rib, as he will miss 11 weeks. Less than a quarter later, the man who replaced him, #3 wideout (80 overall) gets horsecollared on an incomplete pass and tears his groin, and he will miss 5 weeks.

Tulsa sits at 7-0 and will lkely be ranked in both polls next week, but they cannot afford many more injuries on either side of the ball.

So we have had some ad storms here in Panama City Beach and I lost my connection playing my game earlier this morning. I'm going to give it another go tomorrow before heading down to the beach.

Ok, we will advance Wednesday then.